Page History
...
- rdfs:label - if present, it is RF2 fully specified name
- skos:prefLabel - if present, it is RF2 preferred term
- skos:altLabel - if present, it is RF2 acceptable synonym
- skos:definition - if present, it is RF2 definition
- Declaration
Most declarations Declarations are excluded from the OWL refset to avoid duplication to the content that are represented by the RF 2 concept file.
- Declarations for the built in entities, e.g. owl:Thing, owl:Nothing, are excluded from the OWL Refset because they are implicitly presented in every OWL 2 ontology.
- Class declarations are excluded from the OWL Refset because the Concept file represents the same information. 138875005 |SNOMED CT Concept (SNOMED RT+CTV3)| is the only concept needs to be declared in the OWL axiom refset.
Declarations are included in the OWL refset.
- Property declarations should be included in the OWL axiom Refset to reduce the implementation burden for deriving such information at runtime.
...
The OWL Axiom Reference Set is designed to cover all logic definitions of SNOMED CT. A concept can be defined by one or more axioms in the same module or different modules. OWL Axioms are statements that indicate what is are true in the domain.
Each axiom is represented by a string in OWL Functional-Style Syntax in the owlExpression field.
Concepts are represented by concept IDs in the referencedComponentId in the refset.
- If an axiom is in the form of SubclassOf(C D) where concept C is a precoordinated concept, this axiom is a definition of concept C and concept id of C should be the referencedComponetId for this axiom.
- If an axiom is in the form of SubclassOf(C D) where concept C is NOT a precoordinated concept and D is a precoordinated concept, this is a General Concept Inclusion (GCI) axiom. Because concept C is a sufficient condition for concept D, the concept id of D should be the referencedComponentId for this axiom.
- If an axiom is in the form of SubclassOf(C D) or EquivalentClasses(C D) where both C and D are NOT precoordinated concepts, this is a GCI axiom and the referencedComponetId should be 733929006 |General concept inclusion axiom (metadata)|.
Special notes on axioms during the period of transformation from stated relationships.
Each concept can only have one axiom during the period of transformation from the existing stated relationships file to the OWL axiom reference set. Therefore, there should be only one active axiom in the reference set for all active relationships in conjunction for a concept at that snapshot across modules.
...
- .
...
ID
...
Module
...
Version
...
Role
...
Source
...
Target
...
111
...
A
...
1
...
Ra
...
X
...
W
...
222
...
A
...
1
...
Rb
...
X
...
Y
...
333
...
B
...
2
...
Rz
...
X
...
Z
Results in two versions of a single OWL reference set entry
...
UUID
...
Version
...
Module
...
Axiom
...
1
...
1
...
A
...
EquivalentClasses( :X ObjectIntersectionOf(
ObejctSomeValuesFrom( :Ra :W )
ObjectSomeValuesFrom( :Rb :Y )))
...
1
...
2
...
B
...
...
Representation of |is a| Relationships
relationships in SNOMED CT are represented by different axioms, SubClassOf, SubObjectPeroperty, SubDataPropery, or EquivalentClasses in the OWL axiom refset. Concept ShowParts term t 116680003 |Is a (attribute)|
...
- Concept as referenced component is inactivated.
- Axiom needs to be inactivated without any replacement.
- Any inactive concept or attribute in an axiom will not been replaced by active component.
Special notes on axioms during the period of transformation from stated relationships.
Each concept can only have one axiom during the period of transformation from the existing stated relationships file to the OWL axiom reference set. Therefore, there should be only one active axiom in the reference set for all active relationships in conjunction for a concept at that snapshot across modules.
If a dependant module (e.g. an extension) adds relationships to that concept, this will result in a new version of the axiom is added to the OWL reference set with the addition. This new version must be created if any of the relationships from the viewpoint of the module's dependencies changes, regardless of whether that change is on the module in question or not. For example,
ID | Module | Version | Role | Source | Target |
111 | A | 1 | Ra | X | W |
222 | A | 1 | Rb | X | Y |
333 | B | 2 | Rz | X | Z |
Results in two versions of a single OWL reference set entry
UUID | Version | Module | Axiom |
1 | 1 | A | EquivalentClasses( :X ObjectIntersectionOf( |
1 | 2 | B | EquivalentClasses( :X ObjectIntersectionOf( |
Overview
Content Tools
Apps