These are mostly publication and nomenclature related issues, so I just flagged them in the same message.
Across a few of the files, it appears that the namespaces have a competing format. For example, http://mdix.org/ucm# seems to be the namespace specification in (unified-care-model, entity-model, participation-membership-view), but participation-model uses http://mdixinc.com/ucm#. I would be curious to know if this is intentional or if there is only supposed to be one canonical namespace. Additionally, I don't know if it's already been discussed, but is the namespace intended to be a vendor domain or is there an option to specify it such as w3id.org PURL? (e.g. https://w3id.org/ucm#)
Adjacently, unified-care-model.ttl and ucm-entity-model.ttl both declare http://mdix.org/ucm as their ontology IRI with different content. I would expect ontology tooling to treat these as the same ontology since they declare the same ontology IRI. Depending on the tooling, this could lead to one ontology replacing the other at import resolution or otherwise cause ambiguous import behavior. Curious if separate ontology IRIs with owl:versionIRI are intended here.
I also noticed that ucm-participation-model.ttl imports http://mdixinc.com/ucm/core, but I couldn't find a corresponding ontology in the repository. Is that intended to resolve externally, or is there a catalog mapping that's expected to provide it? I was wondering whether a fresh Protégé load might leave that import unresolved.
These are mostly publication and nomenclature related issues, so I just flagged them in the same message.
Across a few of the files, it appears that the namespaces have a competing format. For example, http://mdix.org/ucm# seems to be the namespace specification in (unified-care-model, entity-model, participation-membership-view), but participation-model uses http://mdixinc.com/ucm#. I would be curious to know if this is intentional or if there is only supposed to be one canonical namespace. Additionally, I don't know if it's already been discussed, but is the namespace intended to be a vendor domain or is there an option to specify it such as w3id.org PURL? (e.g. https://w3id.org/ucm#)
Adjacently, unified-care-model.ttl and ucm-entity-model.ttl both declare http://mdix.org/ucm as their ontology IRI with different content. I would expect ontology tooling to treat these as the same ontology since they declare the same ontology IRI. Depending on the tooling, this could lead to one ontology replacing the other at import resolution or otherwise cause ambiguous import behavior. Curious if separate ontology IRIs with owl:versionIRI are intended here.
I also noticed that ucm-participation-model.ttl imports http://mdixinc.com/ucm/core, but I couldn't find a corresponding ontology in the repository. Is that intended to resolve externally, or is there a catalog mapping that's expected to provide it? I was wondering whether a fresh Protégé load might leave that import unresolved.