SNOMED CT OWL Guide

Search

SNOMED CT Document Library

    Loading...

Versions Compared

Old Version 10

changes.mady.by.user Yongsheng Gao

Saved on

compared with

New Version 11

changes.mady.by.user Yongsheng Gao

Saved on

Key

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

...

For inferred relationships in the Necessary Normal Form (NNF), SubclassOf, SubObjectProperty and SubDataProperty in the OWL refset should be represented as

Concept
ShowPartsterm
t116680003 |Is a|
 relationships. The explanation for the Necessary Normal Form and the rules for calculating the NNF can be found in the section Necessary Normal Form for Inferred Relationships.
The following additional two 
Concept
ShowPartsterm
t116680003 |Is a|
 relationships should always be included in the inferred relationship file because they cannot be derived from the OWL axiom refset. Table 2.4.1 Additional inferred 
Concept
ShowPartsterm
t116680003 |Is a|
 relationships in the NNF file



SourceId

TypeId

DestinationId

762705008 |Concept model object attribute (attribute)|

116680003 |Is a (attribute)|

410662002 |Concept model attribute (attribute)

762706009 |Concept model data attribute (attribute)|

116680003 |Is a (attribute)|

410662002 |Concept model attribute (attribute)

...

Any changes to the NNF should have a history of changes in the OWL refset. This will ensure that all entries in the NNF can be derived from the OWL refset except relationships in the table 2.4.-1. The NNF will still have the computed effectiveTime for each inferred relationship. The version of each inferred relationship can be derived from the OWL refset but it is not true in reverse.

...