Orphan Class in AgentOntology.ttl

[Skreen5hot]

There is an orphan Class that should either be specified or removed:

https://www.commoncoreontologies.org/ont00000207

cco:ont00000207 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000472

cco:ont00000472 rdf:type owl:Class .

https://www.commoncoreontologies.org/ont00000487

cco:ont00000487 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 .

https://www.commoncoreontologies.org/ont00001836

cco:ont00001836 rdf:type owl:ObjectProperty .

https://www.commoncoreontologies.org/ont00001809

cco:ont00001809 rdf:type owl:ObjectProperty .

https://www.commoncoreontologies.org/ont00001907

cco:ont00001907 rdf:type owl:ObjectProperty .

https://www.commoncoreontologies.org/ont00001920

cco:ont00001920 rdf:type owl:ObjectProperty .

https://www.commoncoreontologies.org/ont00001942

cco:ont00001942 rdf:type owl:ObjectProperty .

[johnbeve]

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

[Skreen5hot]

Master and Dev are the same, AgentOntology.ttl

It appears that these are classes coming from imported ontologies (or imports of imports).
e.g. Common Core Ontologies Geospatial Ontology
One-Dimensional Geospatial Boundary

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.