Download presentation
Presentation is loading. Please wait.
Published byGeorge Goodwin Modified over 8 years ago
1
Coastal Atlas Interoperability - Ontologies (continued) Luis Bermudez Stephanie Watson Marine Metadata Interoperability Initiative 1
2
Hands on exercise TBC 69
3
Atlas Interoperability Exercise For any interoperability endeavor the first thing that should happen is getting the requirements right ! Use Cases
4
4 Atlas Interoperability
5
Use Case and Proposed User Interface The topics found are the ones that will be explicitly created as well as inferred ones based on logic.
6
6 Atlas OntWeb
7
Note... Q: Where are the data coming from ? A: Distributed sources, which are simulated by each ontology you are creating. Very different from traditional databases.
8
Process 1. Create person-topic ontology (- 3:30) 2. Break (3:30 - 3:45) 3. Map with Upper Level person-topic ontology (- 4:30) 4. Publish to SVN 5. View web application - use case 1 completed ! 6. Discussion (-5:00) 7. Map topics with Atlas Topics 8. Publish mappings
9
Create a simple ontology that captures topics of interest of persons Use concepts from the CMAP exercise, if possible Create at least: –3 Classes (on any level) –1 Object Property - define domain and range –2 Datatypes Properties - define domain and range –2 Individuals for class Person, and 4 for each of the other classes you create –Add properties and values to individuals. e.g. luis hasInterest YOGA For example, include as topics recreational concepts that you would expect to find on an atlas Have fun If problems occur, use help system or TBC tutorial. If more problems occur, raise your hand 75
10
Make your person-topic ontology (XYZ) interoperable with the FOAF ontology 75
11
11 Interoperability
12
We will make your person-topic ontology (XYZ) interoperable with the FOAF ontology 75 aX.owl your ontology
13
13 Experts are now “Atlases” Which two groups created more topics than anybody else ? They will become atlases. They will map their classes and properties to a a super atlas ontology. Change the class name “person” to “atlas” to avoid confusion. Import superatlas.owl (an upper atlas ontology) Make your classes subclasses of Atlas, and Feature. Make one of your properties a subclass of hasFeature. Follow similar instructions as the other groups to make your ontology aligned with superatlas.owl.
14
Map with Person Upper Level Ontology (foaf.owl) 75 Import upper person ontology foaf.owl
15
75 Map with person upper ontology Make your classes as subclasses of a FOAF class. For example if you have a class Person, make it subclass of foaf:Person
16
75 Make one of your properties sub-properties of foaf:topic_of_interest
17
75 Commit to SVN
18
75 Check the web - is your filename there ? URL is: http://marinemedata.org:9600/fs
19
19 Discussion 75 Did you need to do any changes to your ontology ? We are presenting values of instances in the web interface, but this is not always the case.
20
20 Discussion 75 You are a FOAF person because you created a statement that said that: –You foaf:topic_of_interest Topic AND –foaf:topic_of_interest has domain foaf:person Test it ! Make your person class not a subclass of foaf:Person Run the inference engine
21
21 Day 2
22
Wednesday Advanced Fun 77
23
23 Recap from Yesterday We had an introduction to ontologies We had a hands on experience on linking “topics of interest” ontologies to an upper level ontology.
24
Overview Goals Introduction to Ontologies Ontology Components and Practical Exercise Discussions 2
25
25 Mapping ala SKOS An RDF vocabulary for describing the basic structure and content of concept schemes such as thesauri, classification schemes, subject heading lists, taxonomies, 'folksonomies', other types of controlled vocabulary, and also concept schemes embedded in glossaries and terminologies
26
26 SKOS provides a standardized way of representing KOS, such as thesauri, classification schemes, and taxonomies uses RDF –RDF vocabularies: SKOS Core (for describing KOS) SKOS Mapping (for mapping between concepts - broad, narrow, exact match) SKOS Extensions 26
27
27 Mapping ala SKOS import skos.owl it defines 3 convenient properties to relate instances
28
28 Import the 2 atlas ontologies that were created by the 2 groups
29
29 Make relations between your aX.owl file and one of the atlas files –select one of your favorite topics in your aX.owl file and create an skos:relation (broad, narrow, exact match) to a topic from one of the atlases. Need to add the skos:property in the Resource Form
30
30 Adding SKOS Property(ies) in Resource Form Drag and drop
31
31 Commit to SVN - check the web site to make sure your file is there Meanwhile, atlas experts - make SKOS type mappings among the terms in your atlases
32
32 Ontology Engineering
33
33
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.