- From: Roger L. Costello <costello@mitre.org>
- Date: Thu, 03 Jul 2003 06:37:21 -0400
- To: www-rdf-interest@w3.org
- CC: "Costello,Roger L." <costello@mitre.org>, tpassin@comcast.net, jon@spin.ie
Tom Passin wrote: That is why I prefer to use an abstract Transformation thing that could be specialized for one to one length comparisons, for example. Better not to have to remodel when we hit other cases, within reason of course. ...... My Comments: Tom, are you saying that you prefer this: <River rdf:ID="Yangtze"> <length> <Length> <measurement> <LengthMeasure> <transform rdf:resource="LengthInMiles"/> <number>3914</number> </LengthMeasure> </measurement> </Length> </length> </River> to this: <River rdf:ID="Yangtze"> <length> <Length> <measurement> <LengthInMiles> <number>3914</number> </LengthInMiles> </measurement> </Length> </length> </River> I am not clear on why the transform version is more flexible? You mentioned an example of expressing an area in two different units (miles by inches). Let's take that example. Here it is using <transform>: <Farm> <length> <Length> <measurement> <LengthMeasure> <transform rdf:resource="LengthInMiles"/> <number>0.25</number> </LengthMeasure> </measurement> </Length> </length> <width> <Length> <measurement> <LengthMeasure> <transform rdf:resource="LengthInInches"/> <number>2500</number> </LengthMeasure> </measurement> </Length> </width> </Farm> Here it is using the other approach: <Farm> <length> <Length> <measurement> <LengthInMiles> <number>0.25</number> </LengthMeasure> </measurement> </Length> </length> <width> <Length> <measurement> <LengthInInches> <number>2500</number> </LengthMeasure> </measurement> </Length> </width> </Farm> I don't understand how the <transform> version is more flexible. Would you elaborate please? /Roger
Received on Thursday, 3 July 2003 06:39:10 UTC