Re: [topbraid-users] hierarchy not displayed

[David Price]

I’m surprised any tool will read this at all.

owl:class is not defined in any standard. It’s owl:Class (case sensitive).

Also, I’m not sure why you’d do these odd things in your ontology, but Composer is not going handle them well. 

Asserting a class as its own subclass is not necessary (and will ruin many hierarchy viewers) and a resource being both a class and an ontology has no semantics. Classes are sets really, and an ontology is this according to the standard:

An OWL 2 ontology is an abstract notion defined in terms of the structural specification. Each ontology is associated with an ontology document, which physically contains the ontology stored in a particular way. The name "ontology document" reflects the expectation that a large number of ontologies will be stored in physical text documents written in one of the syntaxes of OWL 2. OWL 2 tools, however, are free to devise other types of ontology documents — that is, to introduce other ways of physically storing ontologies. 

So definitely not a set.

Cheers,

David

On 3 May 2021, at 16:36, bostoM <tayeb....@gmail.com> wrote:

Hello,

  I try to load an ontology with same URI in the <ontology> and the my class <root>. 

In protege the hierarchy is well dispalyed  but when I try to load my same ontology on topBraid the hierarchy disappears. And only the "thing" class if displayed.

<owl:Ontology rdf:about="http://example/onto">

    </owl:Ontology>

<owl:class rdf:about="http://example/onto">

</owl:class>

<owl:class rdf:about="http://example/onto/1">

<rdfs:subClassOf rdf:resource=" http://example/onto/1"/>

</owl:class>

Thanks for your help.

--
You received this message because you are subscribed to the Google Groups "TopBraid Suite Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to topbraid-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/799f5cea-8e82-4a90-be20-e68c215a2cabn%40googlegroups.com.

UK +44 (0) 7788 561308

US +1 (336) 283-0808‬

[bostoM]

Thanks.

But you know why it is displayed correctly on Protégé ?

[David Price]

On 4 May 2021, at 12:55, bostoM <tayeb....@gmail.com> wrote:

Thanks.

But you know why it is displayed correctly on Protégé ?

I’m afraid not. You’d have to ask them.

Composer is built on RDF and RDF-based OWL encodings, etc. which might explain the case sensitive issue as Protege also has an specific non-RDF XML encoding, but that’s just a guess.

Different customer requirements perhaps for any of the “odd things” I mention? FWIW I don’t think I’ve ever seen X subclass of X asserted in an ontology, it gets inferred. The ontology AND class resource is way outside DL as far as I understand, so unclear how doing so is useful.

Cheers,

David

To view this discussion on the web visit https://groups.google.com/d/msgid/topbraid-users/11ebbfce-51ec-4182-887c-9e93e1085e24n%40googlegroups.com.