Semantic Web Tutorial

From Federation of Earth Science Information Partners
Revision as of 22:12, January 13, 2011 by Erinmr (talk | contribs)

Hands on: semantic web application development from use case to user testing.

This 6 hr session presented over two half-days is intended to provide both the novice/ beginner/ manager and those already familiar with semantic web technologies in the context of an end-to-end application example. Material to be covered includes: Motivation and use case development. Use case analysis and model/ ontology development, technology and infrastructure options and methods for choosing. implementation and simple application development, user testing and discussion.

Sponsors: Semantic Web Cluster, with assistance from the Products & Services Committee and Information Technology & Interoperability Committee.

See -

Notes from the Session

Peter Fox
Things attributed with Semantic Web;

  • Use case
  • Small team and mixed skills
  • Analysis
  • Develop model ontology
  • Use tools
  • Science reviews and iteration
  • Adpot Technology approach
  • Leverage technology Infrastructure
  • Rapid Prototype
  • Open world: evolve iterate etc.
  • All of which are evaluated and led back to use case.

Chris Lynnes
Use Case
Problem Statement: within ESIP it is difficult to know who is working on similar technologies and who is working with similar datasets. If we could find out this info, we could improve knowledge sharing and even new connections. Meanwhile, agency program managers sometimes need to know who is working on what data with what technologies.

Basic concept: develop a simple ontology of projects, people datasets, and tech Populate with ACCESS, MEaSUREs and similar project instance info, store triples in ESIP Testbed.

Sample queries:

  • Which projects are working with semantic web technology?
  • What tech are being used in NASA ACCESS?
  • Are any projects working with the same dataset?

Use Case Template:

  1. Use Case Identification
  2. Short Definitions
  3. Primary Actor
  4. Purpose
  5. Assumptions about use case
  6. Scenario: meat of use case take step by step
  7. Extensions
  8. Definition of success
  9. Notes/ issues

Use case 1 is enter project data Populate the triple store with project info. Simple web interface, the actor is the project staff member. Purpose is to enter info into the triple store. Assume that the member of the staff knows enough about the project to enter the info.

Use Case 2 Produce Program Tech inventory Program manager gets a report on what techs are being use in his program. Prom manager is the actor, get a report of the tech usage for planning purposes, assumptions programs projects entered in triple store.

Use Case 3 Discovering dataset commonality Discover other projects working with the same datasets. Actor is project investigator. Purpose to discover other projects working on the same dataset, the triple store is used to hold the data and find the rest

Peter Fox
Elements of KR in Semantic web
Declarative knowledge
Statements as triple {subject-predicate-object}
Interferometer is-a optical instrument etc
A query: select all optical instruments which have operating mode vertical.
An inference: infer operating modes for a Fabry-Perot Interferometer which measures neutral temperature
Representing knowledge with objects
Take all individuals that we need to keep track of and place them into different buckets based on how similar they are to each other. Each bucket is given a descriptive based on what objects It contains.
Since the individuals in a given bucket are at least somewhat similar, we can avoid needing to describe every inconsequential detail about each individual. Assign properties that are common to all individuals.
Cannot have multiple inheritances in ontology. Can have several classes in the same but cannot inherit.
UML universal modeling language
Ontology definition metamodel/ meta object facility for UML
White board and text files are helpful for developing a knowledge representation-visual.
Interactive portion! Use Case Models maps or CMAPS
Peter used these CMAPS to get the crowd to share and question each other and work together and figure out what to do with the maps and a use case. He helped create an interesting discussion and showed the transition of preliminary ideas and slowly getting them to become more focused and less general.
First iteration, instead of implementing an interface as defined in the add record so that we can rapid prototype, we will generate a set of instances by hand. We’ll upload it and run some queries