W3C home > Mailing lists > Public > public-webont-comments@w3.org > July 2003

Re: unsupported datatypes

From: Ian Horrocks <horrocks@cs.man.ac.uk>
Date: Tue, 15 Jul 2003 18:01:59 +0100
Message-ID: <16148.13191.31188.976959@merlin.horrocks.net>
To: "Gary Ng" <Gary.Ng@networkinference.com>
Cc: <public-webont-comments@w3.org>

On July 15, Gary Ng writes:
> Another question, this time about unsupported datatypes.
> In the reference doc, it says:
> "For unsupported datatypes, lexically identical literals should be
> considered equal, whereas lexically different literals would not be
> known to be either equal or unequal. Unrecognized datatypes should be
> treated in the same way as unsupported datatypes."
> The first half of the sentence would suggest to treat a literal of
> unknown type as just a string. However, I am not entirely sure what is
> expected from a reasoner with respect to the behaviour of "would not be
> known to be either equal or unequal".

Unknown or unrecognised datatypes are treated as being the lexical
form (a string) of some unknown datatype. It is obviously the case
that, whatever the datatype, identical lexical forms map to the same
element of the value space, and can thus be considered equal. For
non-identical lexical forms, however, it *cannot* be assumed that they
do not map to the same element of the value space and are thus

E.g., the lexical forms "1.0" and "01.00" would map to the same value
(and thus be considered equal) in some datatypes (e.g., decimal), but
not in others (e.g., string).


> Views?
> Cheers,
> G
> Gary Ng, PhD 	     gary.ng@networkinference.com
> Senior Software Engineer
> Network Inference (Holdings) Ltd
> Tel: +44 (0) 20 7616 0717 Fax: +44 (0) 20 7616 0701
Received on Tuesday, 15 July 2003 13:02:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:06:34 UTC