Page History

...

The transformation from the OWL refset to OWL ontology document should process the description file and language refset when descriptions are included. They should be represented by the following annotation properties for a given language refset.

...

• If an axiom is in the form of SubClassOf(C D) or EquivalentClasses(C D) where concept C is a precoordinated concept, the concept ID of C should be the referencedComponetId referencedComponentId 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 but not necessary 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 referencedComponentId should be 733929006 |General concept inclusion axiom (metadata)|.
• If an axiom is in the form of DisjointClasses(C D) where both C and D are precoordinated concepts, the concept ID of C should be the referencedComponetId referencedComponentId for this axiom.

The definition status of a concept is 

Concept
ShowParts term t 900000000000073002|Sufficiently defined concept definition status (core metadata concept)|

 if the concept has one EquivalentClasses axiom no matter other associated axioms are SubClassOf or EquivalentClasses.

...

• SubObjectProperty or SubDataProperty represents the 

  Concept
  ShowParts term t 116680003 |Is a (attribute)|

   relationship between attributes in SNOMED CT.

• EquivalentClasses , in DL, it means that two concepts are subclass of each other in description logics , e.g. SubClassOf(C D) and SubClassOf(D C). EquivalentClasses are usually used to represent the equivalence between a precoorrdinated concept(a named class) and an expression such as ObjectIntersectionOf() that has one part of a precoordinated superconcept and the other part is an expression that usually refines the superconcept, e.g. ObjectSomeValuesFrom() or intersection of expressions.

...

Role group must be explicitly stated and represented by the attribute 

Concept
t 609096000|Role group (attribute)|

 in the OWL refset. Furthermore, role group should allow having only one attribute and value as "self-grouped". These are key differences to the numeric number representation of role group in the RF2 relationship file.
For diagram of stated relationships in the OWL axiom refset, the attribute

Concept
t 609096000|Role group (attribute)|

 should still be represented by a circle rather than an object property.

Current diagram representation for attribute in role group 0

For diagram of relationships in logical model, the circle should be used for 'self-grouped' attribute(s) in the role group 0.

...

The editing of entries in the OWL refsets can only be performed by the owner of that module. In general, the extensions must not modify the OWL refset entries from the dependant dependent modules, such as 900000000000445007|International Health Terminology Standards Development Organisation maintained Organization maintained module (core metadata concept)|.
SNOMED CT extensions can add new axioms for the concepts in the international release by following the General Authoring Principles for extensions. A new axiom in the extension module can be represented by two approaches with different semantics.

• Axiom overriding - a new axiom with inclusion of the axiom from the international release as part of the axiom. The new axiom has the same UUID from the international release with a new effectiveTime and module id in the extension. This approach should be avoided because it overrides the axiom from the dependant dependent module.
• Multiple axioms - a new axiom without inclusion of the axiom from the international release as part of the axiom. The new axiom has a new UUID and effectiveTime in the extension. This approach provides multiple axioms for an concept in the extension module.

...

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.

It is allowed to make direct modification to a published axiom without inactivation by the owner of the module. The same UUID should be used with a new effectiveTime. Since any modification to an axiom could potentially alter its meaning, it is not necessary to inactivate an axiom and create a new axiom. It is also not necessary to reinstate an inactivated axiom in the previous release when the same axiom is created as a new expression. This approach can simplify the tooling and authoring process and it is a different approach to the history of changes to individual relationship.

...

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, during the period of transformation from the existing stated relationships file to the OWL axiom reference set. Therefore, this is the axiom overriding approach and should only be used for the transformation once. Then, these axioms should be reviewed and many of them could be more suitable for multiple axioms.   

If a dependant dependent 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,

...