SNOMED CT Logic Profile Specification

Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 2

changes.mady.by.user David Markwell

Saved on

compared with

New Version 3

changes.mady.by.user Yongsheng Gao

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • assertions ( SameIndividual , DifferentIndividuals , ClassAssertion , ObjectPropertyAssertion , DataPropertyAssertion , NegativeObjectPropertyAssertion , and NegativeDataPropertyAssertion )

  • functional data properties ( FunctionalDataProperty )

  • keys ( HasKey )

  • domain restrictions ( ObjectPropertyDomain and DataPropertyDomain )

  • range restrictions ( ObjectPropertyRange and DataPropertyRange )

  • intersection of data ranges ( DataIntersectionOf )

  • existential quantification to a data range ( DataSomeValuesFrom )

  • existential quantification to an individual ( ObjectHasValue )

  • self-restriction ( ObjectHasSelf )

  • enumerations involving a single individual ( ObjectOneOf ) or a single literal ( DataOneOf )

  • universal quantification to a class expression ( ObjectAllValuesFrom ) or a data range ( DataAllValuesFrom )

  • cardinality restrictions ( ObjectMaxCardinality , ObjectMinCardinality , ObjectExactCardinality , DataMaxCardinality , DataMinCardinality , and DataExactCardinality )

  • disjunction ( ObjectUnionOf , DisjointUnion , and DataUnionOf )

  • class negation ( ObjectComplementOf )

  • enumerations involving more than one individual ( ObjectOneOf and DataOneOf ) 4

  • disjoint properties ( DisjointObjectProperties and DisjointDataProperties )

  • irreflexive object properties ( IrreflexiveObjectProperty )

  • inverse object properties ( InverseObjectProperties )

  • functional and inverse-functional object properties ( FunctionalObjectProperty and InverseFunctionalObjectProperty )

  • symmetric object properties ( SymmetricObjectProperty )

  • asymmetric object properties ( AsymmetricObjectProperty )

...

Therefore while some of the features are desirable for content modelling, moving to OWL 2 DL incurs too highhigh a cost to implementation of SNOMED CT to be supportable at this time. If these features become reasonably practical to add in future (e.g. due to advancements in reasoner technologies) then they may be added. Until that time, modelling patterns must be devised to address the content and use cases which that would benefit from these features to work around their absence.

All OWL 2 DL features not included in OWL 2 EL are excluded from the SNOMED CT Logic Profile. Additionally, the following features which are in the OWL 2 EL profile are not included in the SNOMED CT Logic Profile:

  • domain and range constraints are not supported in the SNOMED CT Logic Profile as they are supported via the SNOMED CT Machine Readable Concept Model rather than in the Description Logic constructs

  • as individuals are not supported in SNOMED CT due to a lack of overall utility in SNOMED CT’s context, individual related constructs are not supported

  • support exists for DataHasValue; however, usage is restricted to prohibit ranges