Not all SNOMED attributes are represented as OWL properties

[bsara]

It seems that all attributes that are children of Concept model object attribute are correctly converted to be OWL properties. However, all other attributes are only created as OWL classes. I would expect that at least everything that is a subclass/sub-property/sub-attribute of one of the subclasses of Attribute would be an OWL property of some kind after conversion is complete (including Is a, which is a direct child of Attribute, but doesn't have any children itself and seems like it should be a property...that, or a sub-property of either rdf:type or rdfs:subClassOf).

(The same could probably be argued for everything under Link assertion as well.)

[kaicode]

Hi @bsara, thanks for your question. Yes, only the children of 762705008 |Concept model object attribute (attribute)| are converted to ObjectProperty in OWL. This is because other descendants of 246061005 |Attribute (attribute)| are not permitted to be used as attributes of a concept model:

• 410663007 |Concept history attribute (attribute)|
  • Used within historical association reference sets (900000000000522004 |Historical association reference set (foundation metadata concept)|)
• 116680003 |Is a (attribute)|
  • OWL SubClassOf / EquivalentClasses
• 408739003 |Unapproved attribute (attribute)|
  • Not permitted in the concept model, these are historical concepts.

More information is available on the permitted attributes used within concepts in the Machine Readable Concept Model (MRCM), See technical documentation and MRCM Browser.

Please note that the July 2021 International release of SNOMED CT will introduce descendants of 762706009 |Concept model data attribute (attribute)|. These will be converted to DataProperty and used in DataHasValue fragments.

[bsara]

thanks again for your quick responses and thorough explanations!