7
Séminaire RVP ÉCONOMIE-DROIT Baccalauréats professionnels tertiaires Rénovation nécessaire Nouvelle approche des contenus Présentation différente des programmes Démarche pédagogique revisitée Nouvelles modalités d’évaluation

An Ontology for Marine Observables

  • Upload
    belita

  • View
    26

  • Download
    0

Embed Size (px)

DESCRIPTION

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 - PowerPoint PPT Presentation

Citation preview

Page 1: An Ontology for Marine Observables

An Ontology for Marine Observables

May 2006

Luis Bermudez

Robert Arko

Marilyn Drewry

John Graybeal

Roy Lowry

Kevin O’Neill

Rob Raskin

Page 2: An Ontology for Marine Observables

2

Marine M

etadata Interoperability Initiative

Started with Platforms.. We thought it was easier…

Page 3: An Ontology for Marine Observables

May 2006

Luis Bermudez

Robert Arko

Marilyn Drewry

John Graybeal

Roy Lowry

Kevin O’Neill

Rob Raskin

An Ontology for Instrument Platforms

Page 4: An Ontology for Marine Observables

4

Marine M

etadata Interoperability Initiative

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.

Background and MotivationMarine Metadata Interoperability

Page 5: An Ontology for Marine Observables

5

Marine M

etadata Interoperability Initiative

Background and Motivation

MMI Workshop Advancing Domain Vocabularies Aug. 2005 Sensor Group

Page 6: An Ontology for Marine Observables

6

Marine M

etadata Interoperability Initiative

Background and Motivation

SensorML instance for a system (http://vast.nsstc.uah.edu/SensorML/)To be used in Tethys and OpenIOOS interoperability demonstrations

Controlled Vocabulary for Data Producers

Page 7: An Ontology for Marine Observables

7

Marine M

etadata Interoperability Initiative

Background and Motivation

MOQuA environment (http://aosn.mbari.org/moqua/)

Controlled Vocabulary for Web Portals

Page 8: An Ontology for Marine Observables

8

Marine M

etadata Interoperability Initiative

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: [email protected] One meeting face to face: Lunch at

Geoinformatics Conference this month.

Page 9: An Ontology for Marine Observables

9

Marine M

etadata Interoperability Initiative

Ontology - Classes

Page 10: An Ontology for Marine Observables

10

Marine M

etadata Interoperability Initiative

Ontology - Classes

Alignment with other vocabularies

CDI = Common Data Index developed bySEA-SEARCH partners. (30 European Coastal States)

Page 11: An Ontology for Marine Observables

11

Marine M

etadata Interoperability Initiative

Ontology - Classes

Page 12: An Ontology for Marine Observables

12

Marine M

etadata Interoperability Initiative

Ontology - Classes

Page 13: An Ontology for Marine Observables

13

Marine M

etadata Interoperability Initiative

Ontology - Properties of a Platform

20060410

20060514

Extensible Approach

Page 14: An Ontology for Marine Observables

14

Marine M

etadata Interoperability Initiative

Universal Realms - based on SWEET

Page 15: An Ontology for Marine Observables

15

Marine M

etadata Interoperability Initiative

Lessons Learned

Page 16: An Ontology for Marine Observables

16

Marine M

etadata Interoperability Initiative

Use - case driven

The construction process depends on how will the ontology be used

Page 17: An Ontology for Marine Observables

17

Marine M

etadata Interoperability Initiative

Use - case driven

http://marine.rutgers.edu/coolroom/education/upwelling.htm

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) ?

Page 18: An Ontology for Marine Observables

18

Marine M

etadata Interoperability Initiative

Guides necessary for ontology non-experts

First session: Protégé Pizza Ontology

Page 19: An Ontology for Marine Observables

19

Marine M

etadata Interoperability Initiative

Ontology guides

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

Page 20: An Ontology for Marine Observables

20

Marine M

etadata Interoperability Initiative

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 ?

Ontology guides

Page 21: An Ontology for Marine Observables

21

Marine M

etadata Interoperability Initiative

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)

Page 22: An Ontology for Marine Observables

22

Marine M

etadata Interoperability Initiative

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.)

Page 23: An Ontology for Marine Observables

23

Marine M

etadata Interoperability Initiative

Debugging an Ontology

We use Pellet reasoner to automatically classified the ontology and to find inconsistencies.

Page 24: An Ontology for Marine Observables

24

Marine M

etadata Interoperability Initiative

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.

Page 25: An Ontology for Marine Observables

25

Marine M

etadata Interoperability Initiative

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.

Page 26: An Ontology for Marine Observables

26

Marine M

etadata Interoperability Initiative

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 !

Page 27: An Ontology for Marine Observables

27

Marine M

etadata Interoperability Initiative

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.

Page 28: An Ontology for Marine Observables

28

Marine M

etadata Interoperability Initiative

Future Work

Sensor Interoperability Metadata workshop

October 2006

http://marinemetadata.org/workshop06

Page 29: An Ontology for Marine Observables

29

Marine M

etadata Interoperability Initiative

MMI: http://marinemetadata.org

Observing Sources Work: /sources

Ontology: /sources/platforms20060508.owl

Ont List: [email protected]

Email: [email protected]

Thank you