Skip to main content
. Author manuscript; available in PMC: 2014 Feb 1.
Published in final edited form as: J Biomed Inform. 2012 Sep 28;46(1):128–138. doi: 10.1016/j.jbi.2012.09.003

Table 5.

Guidelines for Semantic Information: Column 1 shows the guideline numbers; Column 2 shows the guideline descriptions; and Column 3 gives some examples of how to represent information according to the guidelines.

No. Guideline Example
SKOS Route
S1a Use skos:Concept for concepts that are not from OWL Use skos:Concept to represent OBO terms
S2a Defining any relationship or association between two concepts as an instance of owl:ObjectProperty and a sub-property of skos:semanticRelation representing OBO relationships
S3a Use rdfs:subClassOf for parent-child hierarchical relationships Use rdfs:subClassOf to represent relationships such as OBO is_a and UMLS hasSubtype
S3a Use skos:broader and skos:narrower to assert any kind of direct hierarchical link between two SKOS concepts [31] Defining OBO part_of as a sub-property of skos:broader
S4a Use skos:related to assert an associative link between two SKOS concepts [31] Use skos:related to represent Mesh see_also
OWL Route
S1b Use owl:Class for all the concepts Use owl:Class to represent OBO terms
S2b Use owl:ObjectProperty and assertions for relationships between two concepts representing OBO relationships
S3b Use rdfs:subClassOf for parent-child hierarchical relationships Use rdfs:subClassOf to represent relationships such as OBO is_a and UMLS hasSubtype
S4b Use owl:equivalentClass for stating the equivalence of two named classes Use owl:equivalentClass to represent relationships such as UMLS same_as
S5b Use owl:disjointWith to assert that the class extensions of the two class descriptions involved have no individuals in common Use owl:disjointWith to represent relationships such as OBO disjoint_from
S6b Use owl:intersectionOf to describe a class for which the class extension contains precisely those individuals that are members of the class extension of all class descriptions in the list. Use owl:intersectionOf to represent relationships such as OBO intersection_of
S7b Use owl:unionOf to describe an anonymous class for which the class extension contains those individuals that occur in at least one of the class extensions of the class descriptions in the list. Use owl:unionOf to represent relationships such as OBO union_of
S8b Use owl:complementOf to describe two classes that are complement to each other.
S9b Use owl:ObjectProperty, owl:DataTypeProperty, and owl:AnnotationProperty in a semantically correct way e.g., owl:AnnotationProperty cannot be inherited by subclasses.