Michel; To get the "Deur" resource to appear in the class hierarchy,
you will need to assert that it is a subclass of owl:Thing. It is
already a subclass of ob:Element, which is not a class, and you just
need to be clear that you also want to view this as a class. The
modeling intent in this area of your model is very unclear and may
need some refactoring (see other confusions and mismatches that have
occurred below).
Note also that your type triple for :Deur_1 (in bim.ttl) mismatches
with ob:Deur. Currently you have:
:Deur_1 rdf:type :Deur
...but Deur is defined in a different namespace as ob:Deur. I think
the intent is to have:
:Deur_1 rdf:type ob:Deur
There are other type triples with this confusion that will also need
modification. (Again, with autocomplete, this would have been much
clearer - type in Deu<ctl-space> and you will get the right qname -
ob:Deur. I'll re-state that autocomplete solves 90+% of the problems
that occur when hand-editing models.)
The namespace mismatches are causing other problems. Specifically
what you see in Protégé contains two versions of the resource "Deur" -
it's a completely masked mismatch. To explain, note that a triple in
bim.ttl states:
:Deur_1 rdf:type :Deur
where the qnames break out to the following:
<http://www.bimtoolset.org/ontologies/bim.ttl#Deur_1> rdf:type
<http://www.bimtoolset.org/ontologies/bim.ttl#Deur>
However, the URI for "Deur", whose qname is ob:Deur in bim.ttl is:
<http://www.bimtoolset.org/ontologies/ob.ttl#Deur>
...that's a different resource than the type triple points to.
So the Deur you see in the classes view of Protégé, or after running
the CONSTRUCT query I sent earlier, is <http://www.bimtoolset.org/
ontologies/bim.ttl#Deur>, which is different than ob:Deur . I think
Protégé's extra, non-standard, inferences has caused a lot of
confusion in this example.
Note that once you have the namespaces properly aligned, you can
navigate between :Deur_1 and ob:Deur by pressing the ctl key and
mousing over the name in Composer's form interface. This helpful for
understanding your model, and is also a check that everything aligns
properly.
-- Scott
On Feb 16, 4:41 am, "Bohms, H.M. (Michel)" <[email protected]>
wrote:
> Intersting: even when I add 'rdf:type owl:Class', "Deur" is not appearing in
> the class tree (nor is the Deur_1 as instance accessible)
>
> I must be doing something wrong, Michel
>
> TNO.NL
>
> Michel Böhms
>
> sr. Research Scientist Building Innovation
>
> TNO
>
> Van Mourik Broekmanweg 6 | PO Box 49
>
> 2600 AA | Delft | The Netherlands
>
> Tel +31 888663107
>
> Moblie +31 6 30381220
>
> E-mail [email protected]
>
> LinkedInhttp://www.linkedin.com/in/michelbohms
>
> Skype michelbohms
>
> Twitter @MichelBohms
>
> Disclaimer
>
>
>
> > -----Original Message-----
> > From: [email protected]
> > [mailto:[email protected]] On Behalf Of Scott Henninger
> > Sent: woensdag 16 februari 2011 0:37
> > To: TopBraid Suite Users
> > Subject: [topbraid-users] Re:
>
> > Michel; So a question is why not assert that :Deur is a
> > class? It's used that way in your model, so it would be
> > proper to add the type triple (e.g. :Deur rdf:type
> > owl:Class), and there are no problems with doing this. It's
> > not a metamodeling issue, as you are not making subclasses of
> > owl:Class, etc.
>
> > In this case it appears Protégé interprets that anywhere
> > something is used in a type statement, infer that it is an
> > instance of owl:Class.
> > Many would have disagreements with this kind of default
> > inference, so I don't think it would be a good idea as an
> > enhancement request (as background, TBC minimizes the number
> > of behind-the-scenes inferences to avoid these usability
> > issues). But you could add the inference with the following query:
> > CONSTRUCT {?type a owl:Class}
> > WHERE
> > { ?s rdf:type ?type .
> > NOT EXISTS {?type rdf:type ?x .}
> > }
>
> > This can be added by a SPARQLMotion script or inferring after
> > running it in the SPARQL View. Since the triples are
> > inferred, you can assert triples around these inferences an
> > it will all work as needed. As near as I can tell, this is
> > what Protégé does - it just runs the above query by default.
>
> > But the real answer, IMO, is to define :Deur as an owl:Class.
> > There are no negative implications of doing this, and it's a
> > more accurate model.
>
> > -- Scott
>
> > On Feb 15, 4:14 pm, "Bohms, H.M. (Michel)" <[email protected]>
> > wrote:
> > > Well, to give you one example.
>
> > > If you open the bim.ttl its very hard to find the Deur_1 as
> > instance of ob:Door.
>
> > > You would expect to find it via:
> > > Select in class tree: mm:Object, goto its instances and
> > select ob:Door then I would expect to find Deur_1 as backlink
> > (incoming reference) in its resource form because the Deur_1
> > has ob:Door as rdf:type.
>
> > > (before I split mm, ob and bim I am sure this worked)
>
> > > To compare, now use Protégé 4.1beta and browse a bit in the
> > class view. Here you see all stuff collected now:
> > metaclasses, classes and with direct access to their
> > meta-individuals/individuals including Door_1.
>
> > > I guess this is caused by some assumptions in your GUI
> > which might not suit meta-modelling capabilities best, I am
> > not sure...
>
> > > Hope this explains a bit the kind of issues I encounter
> > editting our stuuf in tbc and why I sometimes move to code
> > for convenience.
>
> > > Michel
>
> > --
> > You received this message because you are subscribed to the
> > Google Group "TopBraid Suite Users", the topics of which
> > include TopBraid Composer, TopBraid Live, TopBraid Ensemble,
> > SPARQLMotion and SPIN.
> > To post to this group, send email to
> > [email protected]
> > To unsubscribe from this group, send email to
> > [email protected]
> > For more options, visit this group at
> >http://groups.google.com/group/topbraid-users?hl=en
>
> This e-mail and its contents are subject to the DISCLAIMER
> athttp://www.tno.nl/disclaimer/email.html
--
You received this message because you are subscribed to the Google
Group "TopBraid Suite Users", the topics of which include TopBraid Composer,
TopBraid Live, TopBraid Ensemble, SPARQLMotion and SPIN.
To post to this group, send email to
[email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/topbraid-users?hl=en
