Right and this was exactly my issue....I've asked Bijan if he can comment on this, Thx a lot, Michel
> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Scott Henninger > Sent: zaterdag 21 augustus 2010 7:46 > To: TopBraid Suite Users > Subject: [topbraid-users] Re: userdefined datatype revisited > > Michel; Looking at the spec a bit closer, owl:equivalentClass > is required to define OWL 2 user defined datatypes. As > stated earlier, using owl:equivalentClass allows one to name > the datatype and use it elsewhere in a model. Beyond that, > the full rationale for why this is the case could be asked on > W3C forums. > > You could use rdfs:subClassOf, and that can be handled easily > by Composer. But it will not be OWL 2 compliant. > > Thanks for pointing this out, Holger! > > -- Scott > > On Aug 20, 5:52 pm, Scott Henninger <[email protected]> > wrote: > > OK, thanks for the clarification, Michel. For item #1, you > should be > > able to replace owl:equivalentClass with rdfs:subClassOf > without any > > trouble. For item #2, it's really a questions for the OWL > 2 standards > > committee. > > > > -- Scott > > > > On Aug 20, 4:12 pm, "Bohms, H.M. (Michel)" <[email protected]> > > wrote: > > > > > Dear Scott, > > > > > Thanks for the bug (code is generated by our own excell > to owl converter). > > > (very strange btw we did not saw this trivial one > earlier....anyway). > > > > > Wrt Primer ref: forhttp://www.w3.org/TR/owl2-primer/ > > > > > At 1.2 set "show rdf/xml" syntax. > > > > > Then in Chapter 7 see the example "tiddlerAge": > > > > > <rdf:Description rdf:about="toddlerAge"> > > > <owl:equivalentClass> > > > <rdfs:Datatype> > > > <owl:oneOf> > > > <rdf:Description> > > > <rdf:first rdf:datatype="&xsd;integer">1</rdf:first> > > > <rdf:rest> > > > <rdf:Description> > > > <rdf:first > rdf:datatype="&xsd;integer">2</rdf:first> > > > <rdf:rest > > > rdf:resource="http://www.w3.org/1999/02/22-rdf-syntax-ns#nil"/> > > > </rdf:Description> > > > </rdf:rest> > > > </rdf:Description> > > > </owl:oneOf> > > > </rdfs:Datatype> > > > </owl:equivalentClass> > > > </rdf:Description> > > > > > (or in turtle: > > > :toddlerAge owl:equivalentClass > > > [ rdf:type rdfs:Datatype; > > > owl:oneOf ( "1"^^xsd:integer "2"^^xsd:integer ) > > > ] . > > > ) > > > > > Here you see my two issues: > > > > > 1. it says equivalentClass > you would expect a subClass > since not every string with these two allowed values is necc. > a "toddlerAge". Clearly this issue becomes more clear when > the restrictions are weaker and therefore less specifying. > > > > > 2. This construct does not have the > "<owl:withRestrictions rdf:parseType="Collection">" > > > part in in like in earlier examples in chapter 7. > > > > > Somehow this "one of" is not seen as an item under under > withRestrictions but something alternative to it. > > > > > Hope this clarifies, thanks again for your feedback, Michel > > > > > > -----Original Message----- > > > > From: [email protected] > > > > [mailto:[email protected]] On Behalf Of Scott > > > > Henninger > > > > Sent: vrijdag 20 augustus 2010 17:20Then at chapter 7 > > > > To: TopBraid Suite Users > > > > Subject: [topbraid-users] Re: userdefined datatype revisited > > > > > > Michel; It would be helpful if you were more specific > on what part > > > > of the primer (which one?) you are looking at. As far as > > > > equivalentClass is concerned, one way to look at is that > > > > subClassOf defines an unnamed class whose members meet the > > > > restriction. The equivalentClass definition names the > restriction > > > > to the name of the class. > > > > > > How was this code generated? The example has an error in it. > > > > It's "owl:equivalentClass", not > "rdfs:equivalentClass". Posting > > > > the Turtle serialization would make this more readable. > > > > > > -- Scott > > > > > > On Aug 20, 8:59 am, Michel Bohms <[email protected]> wrote: > > > > > Dear Holger, Scot and others, > > > > > > > We define user defined datatypes now (as we discussed quite > > > > some time > > > > > ago) as: > > > > > > > <rdfs:Datatype > > > > rdf:about="http://www.bimtoolset.org/ontologies/IntUBE- > > > > > EnergyBIM.owl#BuildingPartType"> > > > > > <rdfs:equivalentClass> > > > > > <rdfs:Datatype> > > > > > <owl:onDatatype rdf:resource="http://www.w3.org/2001/ > > > > > XMLSchema#string"/> > > > > > <owl:oneOf rdf:parseType="Resource"> > > > > > <rdf:rest rdf:parseType="Resource"> > > > > > <rdf:rest rdf:parseType="Resource"> > > > > > <rdf:rest rdf:parseType="Resource"> > > > > > <rdf:rest rdf:parseType="Resource"> > > > > > <rdf:rest rdf:parseType="Resource"> > > > > > <rdf:rest rdf:parseType="Resource"> > > > > > <rdf:rest > rdf:resource="http://www.w3.org/ > > > > > 1999/02/22-rdf-syntax-ns#nil"/> > > > > > <rdf:first > > > > rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >Door</rdf:first> > > > > > </rdf:rest> > > > > > <rdf:first > > > > > rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >Window</rdf:first> > > > > > </rdf:rest> > > > > > <rdf:first > > > > > rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >Panel</rdf:first> > > > > > </rdf:rest> > > > > > <rdf:first > rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >Wall</rdf:first> > > > > > </rdf:rest> > > > > > <rdf:first rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >SlopingRoof</rdf:first> > > > > > </rdf:rest> > > > > > <rdf:first rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >FlatRoof</rdf:first> > > > > > </rdf:rest> > > > > > <rdf:first rdf:datatype="http://www.w3.org/2001/ > > > > > XMLSchema#string" > > > > > >Floor</rdf:first> > > > > > </owl:oneOf> > > > > > </rdfs:Datatype> > > > > > </rdfs:equivalentClass> > > > > > </rdfs:Datatype> > > > > > > > I have still two questions here: > > > > > > > 1. Is EquivalentClass (as was also used in the > primer) really ok? > > > > > Shouldn't it be subClass (now all string with this > allowed set > > > > > are always aBuildingPartType which is ok but if the > restriction > > > > are milder > > > > > like >0 then it becomes more discutable since there are many > > > > > userdefined datatype that can be represented by a > positive integer.. > > > > > > > 2. In the primer in case of restriction like >x and > <y, the tag > > > > > withRestriction is used. Should this tag also not be used > > > > HERE in case > > > > > of a oneOf which can also be regarded as a restriction? > > > > > > > thanks for advice, 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 > This e-mail and its contents are subject to the DISCLAIMER at http://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
