Maintenance Alert - This service will be undergoing planned maintenance from Tuesday 23 April 2024, 07:00UTC until Tuesday 23 April 2024, 09:00UTC. During this time the service will be unavailable.

Search



Versions Compared

Key

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

...

The OWL ontology reference set should only have one single active entry of

Concept
tOWL ontology header
 for ontology declaration. For extensions of SNOMED CT, the OWL ontology header for SNOMED CT international release should be inactivated. A new entry for OWL ontology header should be added for an extension edition with the extension module id and a new effective time. The OWL ontology header for SNOMED CT international release should be inactivated. The   The identifier for the ontology URI should be the most dependent module for that particular edition. Please refer to the general authoring principles for changes that can be made by extensions.

It is possible that modules in SNOMED CT can be directly translated into OWL ontologies, with the module dependency reference set describing how these ontologies are imported. Extensions can import the ontology of SNOMED CT core module since the content in the model component module has already been included. The new OWL ontology header should include extension module identifier and import statement(s). This approach could avoid accidental changes to the imported ontology. However, the implementation could be more complicated than the representation of an entire edition as a single ontology. Therefore, it is not recommended to use an ontology import statement at the current stage. Instead, each edition will be rendered as one OWL ontology, without any ontology import statement.