Top Banner

Click here to load reader

When Hydrospheres Collide

Jan 02, 2016

ReportDownload

Documents

When Hydrospheres Collide. Lessons in Practical Environmental Ontologies John Graybeal, Luis Bermudez Marine Metadata Interoperability Project 12 October 2006. MMI: Brief Introduction. Started 2004 with NSF funding; recent 3-year NSF award - PowerPoint PPT Presentation

  • When Hydrospheres CollideLessons in Practical Environmental Ontologies

    John Graybeal, Luis BermudezMarine Metadata Interoperability Project12 October 2006

    Marine Metadata Interoperability Project

    MMI: Brief IntroductionStarted 2004 with NSF funding; recent 3-year NSF awardMission: Improve the use and understanding of metadata in marine sciencesInternational participation and supportMain deliverables: web site, tools, community300-plus membersNumerous open-source tools like VINE, Voc2OWLCollaborations with many in communityTechnical Lead: Luis Bermudez

    Marine Metadata Interoperability Project

    Vocabulary Integration Environment

    Marine Metadata Interoperability Project

    Background and MotivationGuide a marine data repository to tag data sets with the appropriate data source tagHelp a data portal discover data through semantic inferencingHelp an instrument manufacturer to categorize their instruments in a consistent and useful wayGuide other domains to better categorized their data sources

    Marine Metadata Interoperability Project

    Background and MotivationMMI Workshop Advancing Domain Vocabularies Aug. 2005 Sensor Group

    Marine Metadata Interoperability Project

    Plan A: A Sensors OntologyFollow-on to Advanced Domain Vocabulary workshop last yearMultiple science domains, plus sensorsWorkshop Sensors Team: 6-7 peopleStarted with GCMD, SWEET vocabulariesFormulated a technique-based hierarchyOntology work was to continue that effortSome of us were nervous about the work required to make a sensors ontology

    Marine Metadata Interoperability Project

    Plan B: A Platforms OntologyGood to gain experience with the processOf direct interest to several activitiesSeaSearch: Roy LowryMBARI data systems: John Graybeal et alMetadata interfaces: Bob ArkoEasier problem on which to startFewer critical concepts for categorizationFewer existing vocabulariesFewer stakeholdersUseful for sensor work later

    Marine Metadata Interoperability Project

    Ontology Context

    Marine Metadata Interoperability Project

    Tools and ResourcesConcept Schemes: SWEET, CDI Platform Codes, GCMD and Wordnet.Dictionaries: Wikipedia, Dictionary.org.Search Engine: Google, for individual marine science and technology sites.Tools: Protg, SWOOP and Pellet.Collaboration: WebEx and telephone.Web Site: http://marinemetadata.org/sourcesont

    Marine Metadata Interoperability Project

    Principal PlayersLuis Bermudez, MMI/MBARI (Lead)Roy Lowry, BODCRob Raskin, SWEETRobert Arko, LDEOJohn Graybeal, MMI/MBARIMichael Hughes, BODCMarilyn Drewry, UAHKevin ONeill, BODCGroup Photo

    Marine Metadata Interoperability Project

    Principal CustomersPortals that want to sort or classify data by platform typesProgrammers or Data Managers that want to tag their data sets with a sourceTypeInteroperable systems that want to mediate between two or more controlled vocabulariesOperators, developers, manufacturers who describe their platforms in metadata recordsOperation managers who manipulate assets Funders who allocate money to/for assets

    Marine Metadata Interoperability Project

    The Simple Part

    Marine Metadata Interoperability Project

    What Are The Rules?Syntactic GoalsShort words or phrasesConsistent capitalization/punctuationLinguistic GoalsMaintain concept order (noun or modifiers first)Avoid acronyms At each level, divide concept space into non-overlapping concepts that fill the spaceSemantic GoalsCommon terms (ideally the most common)Unambiguous words in English & AmericanMatch other vocabularies where possible

    Marine Metadata Interoperability Project

    Class Name ConstructsAdjectives-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 over the logic term. (DriftingBuoy instead of UnmooredBuoy)CamelCase preferred vs Hyphen and underscores. (ResearchVessel instead of Research_Vessel or Research-Vessel) (but: Nonautonomous)The Professor says

    Marine Metadata Interoperability Project

    Little Surprises Everywhere

    Marine Metadata Interoperability Project

    Unexpected MeaningsAUVs* operate in the hydrosphereTo me (and many), this is earthbound liquid waterAUVs can operate there, even in canals and pondsBut to hydrologists everywhere, this includes water vaporAn airborne AUV is not a useful conceptBut then, what to do with atmosphere and terrasphere?* AUV = autonomous underwater vehicle

    Marine Metadata Interoperability Project

    No More Hydrosphere for Us!Hydrosphere

    Marine Metadata Interoperability Project

    What Are The Rules (Part 2)?How do you organize the ontology? Whats the basis for the framework?Deployment medium was a clear winnerHow do you choose between 2 equally valid alternatives?It depends on how you will use it.Helps little in a general purpose ontologyTry to keep model close to realityTrouble coming in the sensors work?

    Marine Metadata Interoperability Project

    Organizational Basis

    Marine Metadata Interoperability Project

    Criteria to add a new termIt 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).The Professor says

    Marine Metadata Interoperability Project

    The Results (Ta da!)

    Marine Metadata Interoperability Project

    Future Work: Sensors!Sensor Metadata Interoperability Workshop

    October 19-20, 2006

    Choosing Standards / Learning Standards

    http://marinemetadata.org/workshop06

    Marine Metadata Interoperability Project

    Thank youMMI: http://marinemetadata.orgObserving Sources Work: http://marinemetadata.org/sourcesont Ontologies: http://marinemetadata.org/platformonts Ontology Mailing List: [email protected]

    Email: [email protected] | [email protected]

    Also, most of the ontologies I look use CamelCase when labeling the terms (i.e. Words are joined without spaces, and each word is capitalized within the compound) instead of Hyphens and underscores. So I suggest using Camel Case. In the case of using prefixes like "non", we don't capitalize the word following the prefix, for example Nonautonomous.

Welcome message from author
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.