Difference between revisions of "BioPortal Mappings"

From NCBO Wiki
Jump to navigation Jump to search
(→‎Related Mapping Documents: deleted dead link)
 
(20 intermediate revisions by 6 users not shown)
Line 1: Line 1:
This page defines common mappings types in the [http://bioportal.bioontology.org NCBO BioPortal] and provides examples of different mappings that already exist in BioPortal. We welcome comments on this set of mapping relations. Please send email to [mailto:support@bioontology.org support@bioontology.org].
+
= BioPortal Mapping Notes =
  
= BioPortal Mapping Types =
+
This page documents mapping sources and common relationships in the [http://bioportal.bioontology.org NCBO BioPortal], with examples of different mappings that already exist in BioPortal. We welcome comments on the mapping processes and relations; please send email to [mailto:support@bioontology.org support@bioontology.org].
 +
 
 +
== Related Mapping Documents ==
 +
 
 +
* [http://bioportal.bioontology.org/mappings BioPortal Mappings]: the BioPortal mapping service
 +
 
 +
= Mapping Sources =
 +
 
 +
* [http://www.bioontology.org/ The National Center for Biomedical Ontology (NCBO)]
 +
** '''NCBO lexical mapping (loom)''': Mappings were generated by the LOOM algorithm automatically based on close lexical match between preferred names of terms or a preferred name and a synonym.  The lexical match involves removing white-space and punctuation from labels.  Any labels with no more than 3 characters are excluded. These mappings are represented by the mapping relationship '''skos:closeMatch'''.
 +
** '''NCBO Identical URI (loom)''': Mapping for terms with the same URI from different ontologies. These mappings are represented by the mapping relationship '''skos:exactMatch'''.
 +
 
 +
* [http://www.nlm.nih.gov/research/umls/ Unified Medical Language System (UMLS)]
 +
** '''NLM UMLS (CUI)''': Mappings between terms from different ontologies that were created automatically, linking terms with the same UMLS concept unique identifier (CUI). The CUIs are assigned to terms in the UMLS by editors at the NLM. These mappings are represented by the mapping relationship '''skos:closeMatch'''.
 +
** '''NLM UMLS (MRMAP)''': Mappings between terms from the UMLS MRMAP.RRF data. These mappings are represented by the mapping relationship '''skos:closeMatch'''.
 +
 
 +
* [http://obofoundry.org/ The Open Biological and Biomedical Ontologies (OBO)]
 +
** '''OBO xref''': Mappings between ontology terms related by an OBO xref property. These mappings are represented by the mapping relationship '''skos:relatedMatch'''.
 +
** See also, [http://obofoundry.org/index.cgi?show=mappings OBO mappings]
 +
 
 +
= Mapping Relationships =
  
 
There are mappings of the following types in BioPortal:
 
There are mappings of the following types in BioPortal:
Line 7: Line 27:
 
* '''identical, the same''' : [http://www.w3.org/2002/07/owl#sameAs owl:sameAs]
 
* '''identical, the same''' : [http://www.w3.org/2002/07/owl#sameAs owl:sameAs]
 
** '''Definition''' (from [http://www.w3.org/TR/owl-ref/#sameAs-def OWL]): <tt>owl:sameAs</tt> is used to state that two URI references refer to the same individual
 
** '''Definition''' (from [http://www.w3.org/TR/owl-ref/#sameAs-def OWL]): <tt>owl:sameAs</tt> is used to state that two URI references refer to the same individual
* [http://www.casino-spielen.biz casino online spielen]
+
 
* '''exact match''': [http://www.w3.org/2008/05/skos#exactMatch  skos:exactMatch]
 
** '''Definition''' (from [http://www.w3.org/TR/skos-reference/#mapping SKOS]): The property <tt>skos:exactMatch</tt> is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. <tt>skos:exactMatch</tt> is a transitive property, and is a sub-property of <tt>skos:closeMatch</tt>.
 
* '''close match''': [http://www.w3.org/2008/05/skos#closeMatch  skos:closeMatch]
 
** '''Definition''' (from [http://www.w3.org/TR/skos-reference/#mapping SKOS]): The property <tt>skos:closeMatch</tt> is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, <tt>skos:closeMatch</tt> is not declared to be a transitive property.
 
 
* '''related''' (but not necessarily similar): [http://www.w3.org/2000/01/rdf-schema#seeAlso  rdfs:seeAlso]
 
* '''related''' (but not necessarily similar): [http://www.w3.org/2000/01/rdf-schema#seeAlso  rdfs:seeAlso]
 
** '''Definition''' (from [http://www.w3.org/TR/2000/CR-rdf-schema-20000327/#s2.3.4 RDFS]): The property <tt>rdfs:seeAlso</tt> specifies a resource that might provide additional information about the subject resource.  
 
** '''Definition''' (from [http://www.w3.org/TR/2000/CR-rdf-schema-20000327/#s2.3.4 RDFS]): The property <tt>rdfs:seeAlso</tt> specifies a resource that might provide additional information about the subject resource.  
* '''homologous to''' (for anatomical terms): ''not defined yet''
 
** '''Definition''': The property links two anatomical terms from different species that refer to terms that have a common ancestor (evolutionary derived form a common ancestor).
 
  
= Survey of BioPortal Mappings =
+
* '''related match''': [http://www.w3.org/2004/02/skos/core#relatedMatch skos:relatedMatch]
The table below presents the statistics and examples of BioPortal mappings as of July 2010.
+
** '''Definition''': (from [http://www.w3.org/TR/skos-reference/#mapping SKOS-REFERENCE]): The property <tt>skos:relatedMatch</tt> is used to state an associative mapping link between two concepts; <tt>skos:relatedMatch</tt> is a sub-property of <tt>skos:mappingRelation</tt>.
 +
** '''Symmetry''': <tt>skos:relatedMatch</tt> is an instance of <tt>owl:SymmetricProperty</tt>; for bidirectional mappings between <tt><conceptA></tt> and <tt><conceptB></tt> that are <tt>rdf:type skos:Concept</tt>:
 +
 
 +
    <conceptA> skos:relatedMatch <conceptB> .
 +
    <conceptB> skos:relatedMatch <conceptA> .
 +
 
 +
* '''close match''': [http://www.w3.org/2004/02/skos#closeMatch  skos:closeMatch]
 +
** '''Definition''' (from [http://www.w3.org/TR/skos-reference/#mapping SKOS-REFERENCE]): The property <tt>skos:closeMatch</tt> is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, <tt>skos:closeMatch</tt> is not declared to be a transitive property.  The <tt>skos:closeMatch</tt> is a sub-property of <tt>skos:mappingRelation</tt>.
 +
** '''Symmetry''': <tt>skos:closeMatch</tt> is an instance of <tt>owl:SymmetricProperty</tt>; for bidirectional mappings between <tt><conceptA></tt> and <tt><conceptB></tt> that are <tt>rdf:type skos:Concept</tt>:
 +
 
 +
    <conceptA> skos:closeMatch <conceptB> .
 +
    <conceptB> skos:closeMatch <conceptA> .
 +
 
 +
* '''exact match''': [http://www.w3.org/2004/02/skos#exactMatch  skos:exactMatch]
 +
** '''Definition''' (from [http://www.w3.org/TR/skos-reference/#mapping SKOS-REFERENCE]): The property <tt>skos:exactMatch</tt> is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications.  The <tt>skos:exactMatch</tt> it is a sub-property of <tt>skos:closeMatch</tt> and, in addition, it is an instance of <tt>owl:TransitiveProperty</tt>.  Also, <tt>skos:exactMatch</tt> is disjoint with each of the properties <tt>skos:relatedMatch</tt>, <tt>skos:broadMatch</tt> and <tt>skos:narrowMatch</tt>.
 +
** '''Symmetry''': <tt>skos:exactMatch</tt> is an instance of <tt>owl:SymmetricProperty</tt>; for bidirectional mappings between <tt><conceptA></tt> and <tt><conceptB></tt> that are <tt>rdf:type skos:Concept</tt>:
  
{| border="1" cellpadding="2"
+
    <conceptA> skos:exactMatch <conceptB> .
| align="center" style="background:#f0f0f0;"|'''relationship'''
+
    <conceptB> skos:exactMatch <conceptA> .
| width="125" align="center" style="background:#f0f0f0;"|'''basis'''
 
| align="center" style="background:#f0f0f0;"|'''Manual/Automatic'''
 
| align="center" style="background:#f0f0f0;"|'''Source'''
 
| align="center" style="background:#f0f0f0;"|'''Total mappings'''
 
| align="center" style="background:#f0f0f0;"|'''Notes'''
 
|-
 
| skos:closeMatch||identical UMLS CUIs||Manual||LEXEVS_UMLS_MAPPER||2,028,186||Mappings between terms in UMLS ontologies that were created automatically, linking terms with the same CUI. Because CUIs were assigned manually by UMLS editors, we treat these mapings as manual mappings
 
|-
 
| skos:closeMatch||lexical similarity||Automatic||LOOM||1,449,303||Mappings were generated by the LOOM algorithm automatically based on close lexical match between preferred names of terms or a preferred name and a synonym
 
|-
 
| skos:closeMatch||lexical similarity||Automatic||||2,562||Mappings were generated automatically based on the exact match of preferred names or synonyms for terms in FMA, ZFA, and mouse anatomy. Note: These mappings are likely homology mappings
 
|-
 
| skos:closeMatch||lexical similarity||Automatic with manual review||||628||Mappings were generated manually by a user and uploaded to  BioPortal. The mappings were generated automatically based on lexical similarity but later manually reviewed by a domain expert. All mappings involve terms in the MGED ontology
 
|-
 
| owl:sameAs||shared id||Manual||LOOM||271,000||Mappings between the terms that share the same ID
 
|-
 
| rdfs:seeAlso||OBO xref||Manual||||17,776||Mappings based on OBO xref mappings, which indicate related terms
 
|-
 
| skos:exactMatch||Dbxref||Manual||||7,028||Mappings based on the use of Dbxref to indicate term reuse in OBO Foundry ontologies. Very close to having identical ids, but because the ids are different, we use exact match rather than owl:sameAs
 
|-
 
| skos:exactMatch||||Manual||||68||Mappings generated manually by a user; all involve terms from NEMO
 
|-
 
| skos:closeMatch||identical UMLS CUIs||Manual||||902||Mappings between non-UMLS ontologies where concepts do have cui. So, technically, similar to inter-cui mappings
 
|-
 
| skos:closeMatch||||Manual||BioPortal UI||117||Mappings created by users through the BioPortal user interface
 
|-
 
| skos:closeMatch||||Manual||NCICB||3078||Manual mappings between Mouse anatomy and NCIT
 
|-
 
| skos:closeMatch||lexical similarity||Automatic||EFO||673||Mappings generated automatically based on lexical similarity
 
|-
 
| skos:closeMatch||||Manual||NLM||2,662||Manual mappings between Mouse anatomy and NCIT
 
|}
 

Latest revision as of 17:42, 23 January 2017

BioPortal Mapping Notes

This page documents mapping sources and common relationships in the NCBO BioPortal, with examples of different mappings that already exist in BioPortal. We welcome comments on the mapping processes and relations; please send email to support@bioontology.org.

Related Mapping Documents

Mapping Sources

  • The National Center for Biomedical Ontology (NCBO)
    • NCBO lexical mapping (loom): Mappings were generated by the LOOM algorithm automatically based on close lexical match between preferred names of terms or a preferred name and a synonym. The lexical match involves removing white-space and punctuation from labels. Any labels with no more than 3 characters are excluded. These mappings are represented by the mapping relationship skos:closeMatch.
    • NCBO Identical URI (loom): Mapping for terms with the same URI from different ontologies. These mappings are represented by the mapping relationship skos:exactMatch.
  • Unified Medical Language System (UMLS)
    • NLM UMLS (CUI): Mappings between terms from different ontologies that were created automatically, linking terms with the same UMLS concept unique identifier (CUI). The CUIs are assigned to terms in the UMLS by editors at the NLM. These mappings are represented by the mapping relationship skos:closeMatch.
    • NLM UMLS (MRMAP): Mappings between terms from the UMLS MRMAP.RRF data. These mappings are represented by the mapping relationship skos:closeMatch.

Mapping Relationships

There are mappings of the following types in BioPortal:

  • identical, the same : owl:sameAs
    • Definition (from OWL): owl:sameAs is used to state that two URI references refer to the same individual
  • related (but not necessarily similar): rdfs:seeAlso
    • Definition (from RDFS): The property rdfs:seeAlso specifies a resource that might provide additional information about the subject resource.
  • related match: skos:relatedMatch
    • Definition: (from SKOS-REFERENCE): The property skos:relatedMatch is used to state an associative mapping link between two concepts; skos:relatedMatch is a sub-property of skos:mappingRelation.
    • Symmetry: skos:relatedMatch is an instance of owl:SymmetricProperty; for bidirectional mappings between <conceptA> and <conceptB> that are rdf:type skos:Concept:
   <conceptA> skos:relatedMatch <conceptB> .
   <conceptB> skos:relatedMatch <conceptA> .
  • close match: skos:closeMatch
    • Definition (from SKOS-REFERENCE): The property skos:closeMatch is used to link two concepts that are sufficiently similar that they can be used interchangeably in some information retrieval applications. In order to avoid the possibility of "compound errors" when combining mappings across more than two concept schemes, skos:closeMatch is not declared to be a transitive property. The skos:closeMatch is a sub-property of skos:mappingRelation.
    • Symmetry: skos:closeMatch is an instance of owl:SymmetricProperty; for bidirectional mappings between <conceptA> and <conceptB> that are rdf:type skos:Concept:
   <conceptA> skos:closeMatch <conceptB> .
   <conceptB> skos:closeMatch <conceptA> .
  • exact match: skos:exactMatch
    • Definition (from SKOS-REFERENCE): The property skos:exactMatch is used to link two concepts, indicating a high degree of confidence that the concepts can be used interchangeably across a wide range of information retrieval applications. The skos:exactMatch it is a sub-property of skos:closeMatch and, in addition, it is an instance of owl:TransitiveProperty. Also, skos:exactMatch is disjoint with each of the properties skos:relatedMatch, skos:broadMatch and skos:narrowMatch.
    • Symmetry: skos:exactMatch is an instance of owl:SymmetricProperty; for bidirectional mappings between <conceptA> and <conceptB> that are rdf:type skos:Concept:
   <conceptA> skos:exactMatch <conceptB> .
   <conceptB> skos:exactMatch <conceptA> .