W3C home > Mailing lists > Public > xmlschema-dev@w3.org > June 2001

Re: ID/IDREF/IDREFS as elements

From: Henry S. Thompson <ht@cogsci.ed.ac.uk>
Date: 17 Jun 2001 20:48:19 +0100
To: vdv@dyomedea.com
Cc: xmlschema-dev@w3.org
Message-ID: <f5by9qqripo.fsf@cogsci.ed.ac.uk>
Eric van der Vlist <vdv@dyomedea.com> writes:

> My understanding of the recommendation is that while "For compatibility
> (see Terminology (§1.4)) this datatype should be used only on
> attributes", it was still valid to use it for elements.
> This interpretation seems to be confirmed by the fact that ID typed
> elements do contribute to the PSVI ID/IDREF table like attributes:
> "...it has an attribute information item in its [attributes] or an
> element information item in its [children] which was ·validated· by the
> built-in ID simple type definition or a type derived from it whose
> [schema normalized value] is the [id] of this ID/IDREF binding."
> This is quite different from the way both XSV 1.2 ('XSV 1.190/1.95 of
> 2001/05/07 08:38:12'
> ) and XML Spy 4.0b1 are handling ID and/or IDREF elements (simple repro
> cases available if needed) and I'd like a confirmation that defining ID,
> IDREF and IDREFS as elements is valid and equivalent to defining them as
> attributes and that the styles can be mixed (for instance defining an ID
> as an attribute and an IDREFS to these IDs as element).

Absolutely.  XSV doesn't currently check ID/IDREF/IDREFS at all,
attributes or elements, but when it does it will check them regardless 
of how they appear.

  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: ht@cogsci.ed.ac.uk
		     URL: http://www.ltg.ed.ac.uk/~ht/
Received on Sunday, 17 June 2001 15:48:51 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:55:52 UTC