Add owl:Thing subclass, range, and domain assertions in the build by script

[rjyounes]

Could do either in the existing subclass inferencing script or separately. Suggested by Holger Knublauch for tool support.

[rjyounes]

@dylan-sa Thoughts on whether it makes sense to include in the existing script or an independent one?

[dylan-sa]

Seems like it should go in with the materialize_subclass_inferences script, perhaps with an additional command line argument. Each set of assertions (the subclass assertions and the owl:Thing assertions) would be there primarily for tooling purposes, so it makes sense that they'd go together.

[rjyounes]

Maybe, but I just realized many tools also want domains and ranges on properties (the latter perhaps only on object properties). For object properties we'd want to use owl:Thing on both ends. If we want to include all of this it should be a separate tool.

[rjyounes]

Description of the task: Create a new process that will apply during the gist build (via bundle.yaml), that will add rdfs:subClassOf owl:Thing to any class that does not have another named superclass, rdfs:domain owl:Thing to any property that does not already have a domain, and rdfs:range owl:Thing to any object property that doesn't already have a range.

These assertions should be output to a new file in the gist ontologies directory. See the other examples in the gist 13.0.0 release package:

• gistRdfAnnotations13.0.0.ttl - generated by a query in bundle.yaml
• gistSubClassAssertions13.0.0.ttl - generated by running the script /tools/subclass_inferences/materialize_subclass_instances.py invoked in bundle.yaml

It might be possible to do this using a query, as in the first example, but it might require a script, like the second. The query is preferred as a simpler alternative if it works.

[brett-heffelfinger]

I did a bit of testing and I think this could be done with 3 actions in the bundle.yaml, like so:

For rdfs:subClassOf:

CONSTRUCT
{
    ?s rdfs:subClassOf owl:Thing .
}
WHERE
{
    ?s ?p ?o .
    FILTER(!isBlank(?s))
    FILTER NOT EXISTS { ?s rdfs:subClassOf ?any . }
}

The query would be the same for rdfs:domain and rdfs:range with the predicates replaced, respectively. I don't think it can be done with all constructs for rdfs:domain and rdfs:range in one query as the ?s values would get the constructs for each predicate even if they already have a property for them.

For example, if we have:

ex:Class1 rdfs:domain ex:Something .
ex:Class2 rdfs:subClassOf ex:Class1 .

And the query:

CONSTRUCT
{
    ?s rdfs:subClassOf owl:Thing .
    ?s rdfs:domain owl:Thing .
    ?s rdfs:range owl:Thing .
}
WHERE 
{
    {
        ?s ?p ?o .
        FILTER(!isBlank(?s))
    }
    UNION
    {
        ?s ?p ?o .
        FILTER(!isBlank(?s))
        FILTER NOT EXISTS { ?s rdfs:subClassOf ?any . }
    }
    UNION
    {
        ?s ?p ?o .
        FILTER(!isBlank(?s))
        FILTER NOT EXISTS { ?s rdfs:domain ?any . }
    }
    UNION
    {
        ?s ?p ?o .
        FILTER(!isBlank(?s))
        FILTER NOT EXISTS { ?s rdfs:range ?any . }
    }
}

We'll get this as the result:

ex:Class1 rdfs:subClassOf owl:Thing ; 
    rdfs:domain owl:Thing, ex:Something ; 
    rdfs:range owl:Thing ; 
.
ex:Class2 rdfs:subClassOf owl:Thing, ex:Class1 ;
    rdfs:domain owl:Thing ; 
    rdfs:range owl:Thing ; 
.

Proposal: add 3 query actions to the bundle.yaml to handle creating the assertions following the gistRdfAnnotations13.0.0.ttl example.

Does anyone know if the results can be concatenated or appended from multiple actions? If I can, I can add the result triples to something like gistRdfTriples{version].ttl (name pending) and not have multiple result files.

[uscholdm]

I'm confused. Classes do not have domains and ranges. Sent from an input-challenged device. On Aug 24, 2025, at 19:47, Brett Heffelfinger ***@***.***> wrote:  [https://avatars.githubusercontent.com/u/158492846?s=20&v=4]brett-heffelfinger left a comment (semanticarts/gist#1252)<#1252 (comment)> I did a bit of testing and I think this could be done with 3 actions in the bundle.yaml, like so: For rdfs:subClassOf: CONSTRUCT { ?s rdfs:subClassOf owl:Thing . } WHERE { ?s ?p ?o . FILTER(!isBlank(?s)) FILTER NOT EXISTS { ?s rdfs:subClassOf ?any . } } The query would be the same for rdfs:domain and rdfs:range with the predicates replaced, respectively. I don't think it can be done with all constructs for rdfs:domain and rdfs:range in one query as the ?s values would get the constructs for each predicate even if they already have a property for them. For example, if we have: ex:Class1 rdfs:domain ex:Something . ex:Class2 rdfs:subClassOf ex:Class1 . And the query: CONSTRUCT { ?s rdfs:subClassOf owl:Thing . ?s rdfs:domain owl:Thing . ?s rdfs:range owl:Thing . } WHERE { { ?s ?p ?o . FILTER(!isBlank(?s)) } UNION { ?s ?p ?o . FILTER(!isBlank(?s)) FILTER NOT EXISTS { ?s rdfs:subClassOf ?any . } } UNION { ?s ?p ?o . FILTER(!isBlank(?s)) FILTER NOT EXISTS { ?s rdfs:domain ?any . } } UNION { ?s ?p ?o . FILTER(!isBlank(?s)) FILTER NOT EXISTS { ?s rdfs:range ?any . } } } We'll get this as the result: ex:Class1 rdfs:subClassOf owl:Thing ; rdfs:domain owl:Thing, ex:Something ; rdfs:range owl:Thing ; . ex:Class2 rdfs:subClassOf owl:Thing, ex:Class1 ; rdfs:domain owl:Thing ; rdfs:range owl:Thing ; . Proposal: add 3 query actions to the bundle.yaml to handle creating the assertions following the gistRdfAnnotations13.0.0.ttl example. Does anyone know if the results can be concatenated or appended from multiple actions? If I can, I can add the result triples to something like gistRdfTriples{version].ttl (name pending) and not have multiple result files. — Reply to this email directly, view it on GitHub<#1252 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACSHHSO37TAKQR7M3IGORS33PJFH3AVCNFSM6AAAAACDOIOTM6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTEMJYGQ2TSOBZGM>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>