mged ontology [--usage]

29
MGED Ontology [-- usage] MGED Ontology Working Group Dec, 2003

Upload: homer

Post on 22-Feb-2016

50 views

Category:

Documents


0 download

DESCRIPTION

MGED Ontology [--usage]. MGED Ontology Working Group Dec, 2003. Outline. Brief overview of MGED Ontology (MO) Structure of MO What is in MO Uses of MO MAGE and MO MGED Ontology use policies Simple examples Nested term examples Referencing outside terms with MO. Ontologies in general. - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: MGED Ontology [--usage]

MGED Ontology [--usage]

MGED Ontology Working GroupDec, 2003

Page 2: MGED Ontology [--usage]

Outline• Brief overview of MGED Ontology (MO)

– Structure of MO– What is in MO– Uses of MO– MAGE and MO

• MGED Ontology use policies– Simple examples– Nested term examples– Referencing outside terms with MO

Page 3: MGED Ontology [--usage]

Ontologies in general• Explicit specification of a conceptualization

– Defines a vocabulary with which queries and assertions are made• Classes - base type

– Animal, Cat, Dog– BioMaterial, Age, TechnologyType– IS-A relationships: Cat IS-A Animal

• Properties - attributes of classes– number_of_legs, natural_enemy– HAS-A relationships: Cat HAS 4 legs

• Individuals - instantiations of classes– calico, hound, “Stinky Pete”

• Axioms - logic statements– Cat != Dog

Page 4: MGED Ontology [--usage]

MGED Ontology (MO)• Core ontology limited

to MAGE-OM v.1.1• Extended Ontology

augments the Core with terms currently outside the scope of MAGE v.1.1

OilEd editor: http://oiled.man.ac.uk/ Protogé: do google search for it

Page 5: MGED Ontology [--usage]

MAGE and MO

Page 6: MGED Ontology [--usage]

MAGE and MO

Page 7: MGED Ontology [--usage]

Main focus of MGED Ontology• Structured and rich

description of BioMaterials

BioMaterial

OntologyEntry

+characteristics

+associations

Page 8: MGED Ontology [--usage]
Page 9: MGED Ontology [--usage]

A graph representation

Page 10: MGED Ontology [--usage]

MGED Ontology Announcements

• http://www.mged.sf.net/ontologies– About to release first stable release of the Core ontology

(version 1.1.7)– Provide usage of the ontology and examples– Lot’s of links to ontology resources on the web

• Policies – Any term not referenced via DatabaseEntry is by default

user-defined and not part of MO• ‘accession’ and ‘URI’ are not both needed• Refers to OntologyEntry.value

– MO terms may be used in “category” for other ontology’s term (e.g. “Organism”)

Page 11: MGED Ontology [--usage]

Referencing MO Terms<MAGE-ML> …<Database name="The MGED Ontology" identifier="MO"

URI="http://mged.sourceforge.net/ontologies/MGEDontology.php" />…<OntologyEntry category="SomeMOClass" value= "some_MO_instance"> <OntologyReference_assn> <DatabaseEntry accession="#some_MO_instance" URI="http://mged.sourceforge.net/ontologies/MGEDontology.php#some_MO_instance"> <Database_assnref>

<Database_ref identifier="MO"/> </Database_assnref> </DatabaseEntry> </OntologyReference_assn></OntologyEntry>…</MAGE-ML>

Page 12: MGED Ontology [--usage]

Graph representation of previous slide’s XML

Page 13: MGED Ontology [--usage]

Individuals

• Instance term goes into value and is the referenced term.

• Parent term goes into category

Page 14: MGED Ontology [--usage]
Page 15: MGED Ontology [--usage]

Classes with Properties• Nested structure via OntologyEntry.Association• Fillers:

– base types (boolean, string, etc.)– Classes/Instances– Enumeration of Instances

• OntologyEntry category & value = Property• Filler is given as OntologyEntry Association

– follow the rules– When a base type, OntologyEntry.category = Property

Page 16: MGED Ontology [--usage]

Measurement Example

Page 17: MGED Ontology [--usage]

Enumeration of instances Base type Class/Instance

Page 18: MGED Ontology [--usage]

Enumerated instances example

Page 19: MGED Ontology [--usage]

Base type example

Page 20: MGED Ontology [--usage]

Class/Property example

Page 21: MGED Ontology [--usage]

This is BAD! An example of node skipping or tree collapsing

Page 22: MGED Ontology [--usage]

Including parent classes

• You may include parent classes for ease of queries, but you must reproduce all of the structure from the parent to the term of interest

Page 23: MGED Ontology [--usage]

Here we have included the parent term “Action” to the instance term “add” and have included the full term tree.

Page 24: MGED Ontology [--usage]

“Abstract” classes• These are classes without individuals

– Usually have “user-defined” instance terms• Term goes in OntologyEntry “category” and

“value” attributes and referenced via DatabaseEntry

• User-defined term is “Association” (or child OntologyEntry term) with abstract class in category and new term in value, unreferenced

• Example: Your BioMaterial source had a Disease “foobar”

Page 25: MGED Ontology [--usage]
Page 26: MGED Ontology [--usage]

Referencing terms in other ontologies

• Special case of last slide, were new term optionally references some other ontology via its DatabaseEntry

• In addition, specify from within the MGED Ontology where the term hailed from– Is-a “OntologyEntry” term has properties:

• has_database = source for the term• accesion = accession for the term in• value = the term from the source

Page 27: MGED Ontology [--usage]

Without extra DatabaseEntry

Page 28: MGED Ontology [--usage]

With DatabaseEntry

Page 29: MGED Ontology [--usage]

Thanks

• MGED Ontology Working Group