Modules and Ontologies

The Spackman transformation adds all of the descendants of 410662002 | Concept model attribute | with the exception of 116680003|is a| - the set of known predicates used in "semantic relationships" - as ObjectProperties to any OWL transformation output, with the RF2-OWL specification adding one additional concept - 410662002 | Concept model attribute | itself. The preferred names, synonyms and definitions not owned by the target moduleId are not emitted for the these concepts – only the rdfs:label (FSN) itself. It turns out, however, that not all RF2 extensions include content from the 900000000000442005 | Core metadata concept | module, meaning that the OWL output does not include predicate labels.

An alternative to this approach would be to have any OWL module emit, at bare minimum, an OWL importsstatement that references the core metadata concept module. This, however, leads to a number of secondary questions:

Should the import statement reference a specific version of the core metadata concept?
Can the module dependencies file be used to generate this import? Should other dependencies be included as imports as well?
Where would the imported modules reside? Would it be necessary for someone generating an extension module to download the SNOMED CT core and run the transformations on it to get what they need or would there be some place that the pre-converted modules would be accessible?

A related issue is that the transformation specification asserts that all active relationship file entries having a typeId that is a descendant of 410662002 | Concept model attribute | are emitted in the OWL. NO relationship entries are currently generated in the absence of the SNOMED CT Core model attribute hierarchy (!)

Note that these question go well beyond the scope of the initial RF2 to OWL transformation project, which was to formally document the implicit rules in the Spackman transformation in a way that it could be generalized for any SNOMED CT edition or extension.

Recommendation: For the purposes of the Spackman/OWL transformation, leave the rules as they sit. If the resource doesn't include the Concept model attributes, the resulting OWL output will not have labels for the predicates.