I just saw this discussion.

This echoes a permathread in the GI community as well, and is arguably
one of the biggest gaps in almost all computer languages in terms of
their application to the real world.

The point is that 304.8mm=1ft, 1kg=2.205lb, etc.
They are alternative and entirely equivalent serializations of the
same quantity.
Quantities have no meaning without a unit of measure, and generally
should not be transported without the uom being provided either
locally or by the context.

Your solution here seems to be to give the same context (units) to all
values of a particular property.
The GI community has traditionally used UML for conceptual modelling,
and has a base class 'Measure' to handle this.
Translated into OWL it looks llike this:

base:Measure
      a       rdfs:Class ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality "1"^^xsd:nonNegativeInteger ;
                owl:onProperty meas:units
              ] ;
      rdfs:subClassOf
              [ a       owl:Restriction ;
                owl:cardinality "1"^^xsd:nonNegativeInteger ;
                owl:onProperty meas:value
              ] .

meas:units
      a       owl:FunctionalProperty , owl:DatatypeProperty ;
      rdfs:comment "Value should be a valid UCUM symbol"^^xsd:string ;
      rdfs:domain base:Measure ;
      rdfs:range xsd:string ;
      dc:description "The value of this property is a designator for
the units of measure or scale for the quantity"^^xsd:string .

meas:value
      a       owl:FunctionalProperty , owl:DatatypeProperty ;
      rdfs:domain base:Measure ;
      rdfs:range base:Number ;
      dc:description "The value of this property is a number that is
scaled by the unit of measure to obtain a quantity"^^xsd:string .


Simon

On Oct 5, 6:53 pm, "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

Reply via email to