|
Michel; It is the case that units, such as unit:Centimeter
and unit:Kilogram are not defined as rdfs:Datatypes in the unit
model. Note that the blog post says "For this use case, all units
have also been declared to be rdfs:Datatypes". If you want to use
these units as range definitions, then you can do that also - i.e.
add a type definition to units you want to use in property
ranges. E.g. {unit:Centimeter rdf:type rdfs:Datatype}. -- Scott On 10/6/11 3:35 AM, Bohms, H.M. (Michel) wrote: --Sorry Scot/Holger, I don't understand. What I did: - I imported the local file unit.rdf that is default in: C:\Documents and Settings\bohmshm\TBCMEWorkspace\TopBraid\Linked Models - this file contains 1445 units amoung which unit:Kilogram - Looking at Holger's blog: http://composing-the-semantic-web.blogspot.com/2009/08/units-ontology-with-spin-support.htmlYou see the example: http://2.bp.blogspot.com/_44lV0kDjySE/SpwwsVGuD_I/AAAAAAAAAKo/5-gzDVc-X1s/s1600-h/QUDT-Property-Example.png With text: " ... The other alternative is to embed the unit directly into the literals. For this use case, all units have also been declared to be rdfs:Datatypes. This makes it possible, to assign units as rdfs:ranges of a property as shown below:" So this is eaxctly I tried but now with another unit (Kilogram instead of Centimeter) What I could imagine, just an idea: in the definition of the unit in Holger's example I see that the unit is also of type rdfs:datatype wherein the def. in the current local file it is not...maybe that is related....(and as the text quote above suggest..this rdfs:Datatype might just make the embedding possible!) Thx again, Michel Ps Uri conflict is known, no probblem -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Scott Henninger Sent: woensdag 5 oktober 2011 18:21 To: TopBraid Suite Users Subject: [topbraid-users] Re: unit as range error Michel; By the "great unit pattern/ontology" I expect you mean QUDT? I looked that this some and I don't see an error. Any class can be added as the rang for a datatype. I do not know where unit:Kilogram comes from, though, and whether it is defined somewhere in your model. This is the likely source of the problem, and I can reproduce that. Define unit:Kilogram in your model and it should work. BTW, the screen shot was helpful. It also reveals that you have a base URI conflict - the files names test.ttl and test2.ttl have the same base URI - http://example.org/text. Test2.ttl is currently the "primary file". This means that currently test2.ttl is opened whenever http://example.org, but if you modify the primary then data that imports this URI will change. If you're aware of these consequence, then ignore this. If you need further explanation, please ask. -- Scott On Oct 5, 5:53 am, "Bohms, H.M. (Michel)" <[email protected]> wrote:Hi Holger I just recently discovered the great unit pattern/ontology. However when I try to put say unit:Kilogram as range the box stays red. (I imported the local file) I see this issues reported earlier for older versions but should have been resolved in later versions. [cid:738164810@05102011-25D7] thx for feedback, Michel This e-mail and its contents are subject to the DISCLAIMER athttp://www.tno.nl/emaildisclaimer Outlook.jpg 203KViewDownload-- 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 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 |
- RE: [topbraid-users] spin syntactic sugar? Bohms, H.M. (Michel)
- Re: [topbraid-users] spin syntactic sugar? Holger Knublauch
- RE: [topbraid-users] spin syntactic sugar? Bohms, H.M. (Michel)
- Re: [topbraid-users] spin syntactic sugar? Holger Knublauch
- RE: [topbraid-users] spin syntactic sugar? Bohms, H.M. (Michel)
- RE: [topbraid-users] spin syntactic sugar? Bohms, H.M. (Michel)
- Re: [topbraid-users] spin syntactic sugar? Holger Knublauch
- RE: [topbraid-users] spin syntactic sugar? Bohms, H.M. (Michel)
- [topbraid-users] Re: unit as range error Scott Henninger
- RE: [topbraid-users] Re: unit as range error Bohms, H.M. (Michel)
- Re: [topbraid-users] Re: unit as range error Scott Henninger
- [topbraid-users] Re: unit as range error Simon Cox
- RE: [topbraid-users] Re: unit as range error Irene Polikoff
- RE: [topbraid-users] Re: unit as range error Bohms, H.M. (Michel)
- Re: [topbraid-users] Re: unit as range error Scott Henninger
- RE: [topbraid-users] Re: unit as range error Bohms, H.M. (Michel)
- [topbraid-users] Re: unit as range error Simon Cox
