Re: Mixed type fields

James Clark <> writes:

> What happens if fields in identity constraints evaluate to values of
> different types for different target node-sets? This would require be to
> compare values of different types.  Is this an error, always false,
> false only if they do not have a common super type or what?

Should be clarified.  I _think_ (need confirmation from the Datatypes
editors) that values from distinct value spaces always compare not
equal, but that a derived type's values _are_ in the same value space as
its base type, so e.g. 

3 [integer] = 3 [short]

and "foo" [string] = "foo" [token]

  Henry S. Thompson, HCRC Language Technology Group, University of Edinburgh
          W3C Fellow 1999--2001, part-time member of W3C Team
     2 Buccleuch Place, Edinburgh EH8 9LW, SCOTLAND -- (44) 131 650-4440
	    Fax: (44) 131 650-4587, e-mail:

Received on Monday, 22 January 2001 04:50:44 UTC