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
