Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Lists and unions derived from ID/IDREF

From: "Michael Kay" <mike@--------.--->
To: <xmlschema-dev@--.--->
Date: 11/3/2004 11:03:00 AM
Does the spec have anything to say about deriving list and union types from
ID and IDREF?

The description of the ID/IDREF table in 3.15.5 discusses IDREFS separately.
This suggests that in that section one should read "derived from" as meaning
"derived by restriction from" (otherwise it would not be necessary to
mention IDREFS).

Am I right in thinking that types derived by List or Union from ID and IDREF
are permitted, but that they imply no uniqueness or referential constraints?

Another reading of the spec is that if a simple type is a list of IDs, then
the entire list is required to be unique. Equally, if a simple type is a
union of ID and integer, then its values are required to be unique - which
becomes a nice trick for defining integer or date-valued unique ids.


Michael Kay
http://www.saxonica.com/


From ekimber@i... Wed Nov 03 15:35:3


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent