1 / 29

An Ontology for Marine Observables

An Ontology for Marine Observables. Luis Bermudez Robert Arko Marilyn Drewry John Graybeal Roy Lowry Kevin O’Neill Rob Raskin. May 2006. Started with Platforms .. We thought it was easier…. An Ontology for Instrument Platforms. Luis Bermudez Robert Arko Marilyn Drewry John Graybeal

belita
Download Presentation

An Ontology for Marine Observables

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. An Ontology for Marine Observables Luis Bermudez Robert Arko Marilyn Drewry John Graybeal Roy Lowry Kevin O’Neill Rob Raskin May 2006

  2. Started with Platforms.. We thought it was easier…

  3. An Ontology for Instrument Platforms Luis Bermudez Robert Arko Marilyn Drewry John Graybeal Roy Lowry Kevin O’Neill Rob Raskin May 2006

  4. Background and MotivationMarine Metadata Interoperability • NSF starter funding, with SURA(ONR) in-kind support, NOAA CSC bridge funds. • International contributions and support. • Main deliverables: web site, a community, demonstrations and tools. • Goal for future: Solve the metadata problem.

  5. Background and Motivation MMI Workshop Advancing Domain Vocabularies Aug. 2005 Sensor Group

  6. Controlled Vocabulary for Data Producers Background and Motivation SensorML instance for a system (http://vast.nsstc.uah.edu/SensorML/) To be used in Tethys and OpenIOOS interoperability demonstrations

  7. Controlled Vocabulary for Web Portals Background and Motivation MOQuA environment (http://aosn.mbari.org/moqua/)

  8. Strategy • Overall Strategy: Public Effort -> Invited all the communities interested. • One milestone: Version 1.0 Beta - May 2006 • 5 Web conferencing Telecons - 3 hours each • Mailing List: ont@marinemetadata.org • One meeting face to face: Lunch at Geoinformatics Conference this month.

  9. Ontology - Classes

  10. Alignment with other vocabularies Ontology - Classes CDI = Common Data Index developed by SEA-SEARCH partners. (30 European Coastal States)

  11. Ontology - Classes

  12. Ontology - Classes

  13. Ontology - Properties of a Platform 20060410 20060514 Extensible Approach

  14. Universal Realms - based on SWEET

  15. Lessons Learned

  16. Use - case driven The construction process depends on how will the ontology be used

  17. Use - case driven A buoy senses an upwelling event Is there a research vessel around to measure in more detail the phenomena? Are there any AUVs near by that can change their route (adapt) ? http://marine.rutgers.edu/coolroom/education/upwelling.htm

  18. Guides necessary for ontology non-experts First session: Protégé Pizza Ontology

  19. Ontology guides A Practical guide to building OWL Ontologies using the Protege-OWL Plugin.. (Horridge M., Knublauch H., et. al.)

  20. Ontology guides • Issues Pizza Guides: • Lack of complicated properties such as Mobility. • Lack of comparison between individuals (Wine ont.) vs classes (Pizza Ont.) constructs. • Ontology expertise in the group is essential to provide real-time input. For example… is immobile a mobile quality ?

  21. Class Name Constructs • Adjectives-Noun placement order. In English adjective goes first. (ResearchVessel instead of VesselResearch). Same pattern was applied in DOLCE. KOALA, PIZZA ontologies. • Prefer the common marine term than the logic term. (DriftingBuoy instead of UnmooredBuoy) • CamelCase preferred vs Hyphen and underscores. (ResearchVessel instead of Research_Vessel or Research-Vessel)

  22. Criteria to add a new term • It is not already in the ontology. • It can have a property that differentiates it from its siblings. (e.g. ship and boat. The dimension of a ship is bigger than a boat.) • A super-class is promoted when similarities are found among concepts. (e.g. Both Buoy and Research Vessel hasEarthRealmBase water. A new class can be created called WaterBasedPlatform.) • A term can be categorized under 2 or more categories. (e.g. Amphibious crawler.)

  23. Debugging an Ontology We use Pellet reasoner to automatically classified the ontology and to find inconsistencies.

  24. Tools and Resources • Concept Schemes: SWEET, CDI Platform Codes, GCMD and Wordnet. • Dictionaries /pedias: Wikipedia, Dictionary.org. • Google, where you can get individual marine science and technology web sites. • Tools: Protégé, SWOOP and Pellet.

  25. Web Conferencing • WEBEX better than solely email list. • We should explore other options like Access Grid VC. • If possible face to face meetings is the best choice.

  26. Conclusions • More classes were created for WaterBasedPlatforms than others - due to the expertise of the participants in this domain. • ObjectProperties are preferred over DatatypeProperties. • Is a long process - agreement is not easy. • Keep guides and ontology experts around. • Keep groups maximum around 5-7. • Watch out - you may become addicted !

  27. Future Work • Clean up the ontology. • Publishing it. • Find best mechanism to “keep it alive”. Reviewing concepts, adding new concepts, controlling versioning, etc… • Continue the work towards a sensor ontology. • Build services ( Web Services to query and map ) around these ontologies. • Promote the ontology to enrich it.

  28. Future Work Sensor Interoperability Metadata workshop October 2006 http://marinemetadata.org/workshop06

  29. Thank you MMI: http://marinemetadata.org Observing Sources Work: /sources Ontology: /sources/platforms20060508.owl Ont List: ont@marinemetadata.org Email: bermudez@mbari.org

More Related