W3C home > Mailing lists > Public > www-rdf-interest@w3.org > November 2001

RE: Cutting the Patrician datatype knot

From: <Patrick.Stickler@nokia.com>
Date: Fri, 30 Nov 2001 19:19:43 +0200
Message-ID: <A03E60B17132A84F9B4BB5EEDE57957B07F577@trebe006.NOE.Nokia.com>
To: ashokma@microsoft.com, pfps@research.bell-labs.com
Cc: www-rdf-interest@w3.org, joint-committee@daml.org


> -----Original Message-----
> From: ext Ashok Malhotra [mailto:ashokma@microsoft.com]
> Sent: 29 November, 2001 08:25
> To: Stickler Patrick (NRC/Tampere); pfps@research.bell-labs.com
> Cc: www-rdf-interest@w3.org; joint-committee@daml.org
> Subject: RE: Cutting the Patrician datatype knot
> 
> 
> > In the above union "data type", the literal "7" maps to
> > two members of the value space. Therefore, it is not a
> > valid data type.
> 
> If you define a union type then such anomalies can arise.
> XML Schema specifies how to resolve them.  If a literal can be 
> interpreted as a valid literal for more than one of the datatypes
> included in a union, it is assumed to have the datatype of the first
> datatype specified in the union for which it is a legal literal.
> 
> You may not think this is an elegant solution but it solves the 
> problem. 

But doesn't that then preclude the use of (hide) a subset
of the value space? I.e. whatever the intersection is between
the two (or more) value spaces, only the members of that
intersection belonging to the first data type are "accessible".

Well, if that's how the union data type is defined to work, then
it's not technically a problem -- i.e. there really is no actual
ambiguity in the mapping -- but it would still IMO be a very 
odd data type ;-)

Cheers,

Patrick
Received on Friday, 30 November 2001 12:19:47 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:51:52 GMT