Orphan Classes in ArtifactOntology.ttl

[Skreen5hot]

https://www.commoncoreontologies.org/ont00000170

cco:ont00000170 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000205

cco:ont00000205 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000253

cco:ont00000253 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000686

cco:ont00000686 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000958

cco:ont00000958 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000965

cco:ont00000965 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00001341

cco:ont00001341 rdf:type owl:Class .

[johnbeve]

On/in what branch/file are you seeing this?

[Skreen5hot]

Master and Dev, ArtifactOntology.ttl

It appears that these are classes coming from imported ontologies (or imports of imports).
e.g. Common Core Ontologies Geospatial Ontology
Object Track Point
https://www.commoncoreontologies.org/ont00000170

If I materialize all imports, there is no problem. However, I am intentionally not materializing the full import closure for this project (that’s the point of using modules).

The current structure assumes full import closure. In a single working graph without that closure, these classes are effectively orphaned—i.e., they have no locally accessible superclass or grounding axioms—and this breaks in partial-closure scenarios.

[johnbeve]

@Skreen5hot Thank you for pointing this out. Looks like there are dangling orphans as you said and that should have a proper home. @mark-jensen @neilotte @APCox