Jody,

there is a triple qud:Unit rdfs:subClassOf rdfs:Datatype in n1qud,  
which is (in theory) sufficient to make all units also RDF datatypes.  
I have made these triples a bit more explicit in the qudspin file to  
make life easier for tools that do not handle subclassing datatypes  
(such as TBC 3.1, no longer needed for TBC 3.2).

But you are right, both design choices are supported and we want to  
leave it to the users to decide whether they want to "instantiate" the  
units as datatypes, or just use them somehow else, e.g. by annotating  
their existing, traditional datatype properties that then may have  
xsd:double etc as ranges.

> I was seeing that, while I could put a unit datatype
> on a value, the functions to convert types returned values as
> xsd:double.  There was no way to say that it was both a double and a
> unit datatype.  I'm guessing that is why you first tried to subclass
> xsd:double.

Yes. Regarding the function, you are of course free to cast your  
values back to a datatype using functions such as smf:cast.

>
> Another big question in my mind is, which was the intended way of QUDT
> to express a value and unit?
>  a. Units as Datatypes (as in SPIN examples)
>  b. Units express the subject of a triple (examples below)
> Or was it designed not to tackle this question and instead to work for
> either?

One of the main benefits of the QUDT ontology IMHO is that it defines  
some stable URIs for those units. Time will tell which aspect of those  
URIs will be used.

I am not really involved in the QUDT sub-project beside the SPIN/SM  
stuff, so the rest of your questions would be better handled by the  
authors (if you don't get a response here, try contacting James  
Masters directly).

Regards,
Holger


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TopBraid Composer Users" group.
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-composer-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to