- From: <bugzilla@jessica.w3.org>
- Date: Sun, 25 Jul 2010 22:17:37 +0000
- To: www-xml-schema-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10235
Summary: ID/IDREF constraints for complex types with simple
content
Product: XML Schema
Version: 1.0/1.1 both
Platform: PC
OS/Version: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: Structures: XSD Part 1
AssignedTo: David_E3@VERIFONE.com
ReportedBy: mike@saxonica.com
QAContact: www-xml-schema-comments@w3.org
CC: cmsmcq@blackmesatech.com
Both in 1.0 and 1.1, when elements have a complex type with simple content and
the simple content type is xs:ID or xs:IDREF, they do not generate entries in
the ID/IDREF table, and their "IDness" is therefore ignored.
See Part 1, section 3.17.5.2 "ID/IDREF Table", rule 2 of the definition of
"eligible item set".
This is highly counter-intuitive; if an existing schema has an element <ssid>
serving as an xs:ID value, then one would not expect that evolving the schema
to allow the <ssid> element to have an attribute should silently eliminate the
uniqueness checking of the element's content.
Another argument: if the user didn't intend the content to be checked for
uniqueness, why would they specify its type as xs:ID?
It seems we fixed the corresponding bug for key/keyref/unique in 1.1, but did
not fix it for ID/IDREF.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Sunday, 25 July 2010 22:17:38 UTC