3968 2006-11-10 02:38:38 +0000 Elements with duplicate IDs 2007-04-13 16:55:20 +0000 1 1 1 Unclassified XML Schema Structures: XSD Part 1 1.0/1.1 both All All CLOSED WORKSFORME resolved P2 normal --- 1 sandygao cmsmcq www-xml-schema-comments oldest_to_newest 12908 0 sandygao 2006-11-10 02:38:38 +0000 Consider an element declaration <element name="e"> <complexType> <sequence> <element name="id1" type="ID"/> <element name="id2" type="ID"/> </sequence> </complexType> </element> And the instance <e><id1>abc</id1><id2>abc</id2></e> Many people would think the above is invalid, because there are duplicate ID values. But a careful reading of the "ID/IDREF Table" PSVI property suggests that the above is valid. There will only be one entry in the [binding], the element "e". Is this intended? Is this how most schema processors implemented ID/IDREF? Either way, some clarification will be helpful. 12909 1 ht 2006-11-10 09:31:29 +0000 No harm, no foul. The guarantee ID provides is that no ID is attached to two distinct items. In SGML and XML, there was also a declaration constraint which prevented items from having two IDs, but we explicitly did _not_ reconstruct this constraint except for attributes, although both parts 1 and 2 both suggest not using ID for the type of elements. The example schema given makes it possible for an element to have multiple IDs, but then the instance doesn't exploit this. In my view the resulting ID/IDREF table is correct -- one entry, with one binding, i.e. 'abc' bound to the doc. element. And I think the spec. correctly specifies that in case of an instance such as <e><id1>abc</id1><id2>xyz</id2></e> there will be _two_ entries in the ID/IDREF table, one binding 'abc' to the doc. elt and one binding 'xyz' to it. Your gun, your foot, your bullet. In other words, no bug, no change required. 13563 2 446 sandygao 2007-01-15 21:27:13 +0000 Created attachment 446 Test case: schema 13564 3 447 sandygao 2007-01-15 21:27:43 +0000 Created attachment 447 Test case: instance 13567 4 448 sandygao 2007-01-15 21:59:14 +0000 Created attachment 448 Test case 2: schema 13568 5 449 sandygao 2007-01-15 21:59:35 +0000 Created attachment 449 Test case 2: instance 13980 6 453 cmsmcq 2007-02-13 22:58:42 +0000 Created attachment 453 Test case 3: schema document One ID attribute, two ID (sub-)elements. 13981 7 454 cmsmcq 2007-02-13 23:00:39 +0000 Created attachment 454 Test case 3: XML instance Three dependents of type ID with different values, all on the same element. Several people have said all processors will behave the same on this, but some thing that all processors will accept it, others that all will reject it. The spec is I think clear that the schema is OK and the instance is valid against the schema. 14275 8 458 sandygao 2007-02-28 14:43:56 +0000 Created attachment 458 Test case 4: schema document When an element's simple content is of type ID and one of its attributes also has type ID, test whether the 2 IDs can have the same value. 14276 9 459 sandygao 2007-02-28 14:44:55 +0000 Created attachment 459 Test case 4: XML instance When an element's simple content is of type ID and one of its attributes also has type ID, test whether the 2 IDs can have the same value. 14726 10 sandygao 2007-04-13 16:55:02 +0000 The working group discussed this issue at the 2007-03 F2F meeting. It was observed that - Users and some specifications, as with schema itself, view elements with IDs as identifying their parents - Users may want to use different ways (sub-elements/attributes) to identify the same element, but using the same ID value. Based on these, the WG decided not to change the behavior in the current schema spec. 446 2007-01-15 21:27:13 +0000 2007-02-28 14:45:57 +0000 Test case: schema dupIDonElement.xsd text/xml 256 sandygao PHNjaGVtYSB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEiPg0KICA8ZWxl bWVudCBuYW1lPSJlIj4NCiAgICA8Y29tcGxleFR5cGU+DQogICAgICA8c2VxdWVuY2U+DQogICAg ICAgIDxlbGVtZW50IG5hbWU9ImlkMSIgdHlwZT0iSUQiLz4NCiAgICAgICAgPGVsZW1lbnQgbmFt ZT0iaWQyIiB0eXBlPSJJRCIvPg0KICAgICAgPC9zZXF1ZW5jZT4NCiAgICA8L2NvbXBsZXhUeXBl Pg0KICA8L2VsZW1lbnQ+DQo8L3NjaGVtYT4NCg== 447 2007-01-15 21:27:43 +0000 2007-01-15 21:27:43 +0000 Test case: instance dupIDonElement.xml text/xml 157 sandygao 77u/PGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5j ZSINCiAgIHhzaTpub05hbWVzcGFjZVNjaGVtYUxvY2F0aW9uPSJkdXBJRG9uRWxlbWVudC54c2Qi Pg0KIDxpZDE+YWJjPC9pZDE+DQogPGlkMj5hYmM8L2lkMj4NCjwvZT4NCg== 448 2007-01-15 21:59:14 +0000 2007-02-28 14:46:17 +0000 Test case 2: schema dupIDonElement2.xsd text/xml 256 sandygao PHNjaGVtYSB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEiPg0KICA8ZWxl bWVudCBuYW1lPSJlIj4NCiAgICA8Y29tcGxleFR5cGU+DQogICAgICA8c2VxdWVuY2U+DQogICAg ICAgIDxlbGVtZW50IG5hbWU9ImlkMSIgdHlwZT0iSUQiLz4NCiAgICAgIDwvc2VxdWVuY2U+DQog ICAgICA8YXR0cmlidXRlIG5hbWU9ImlkMiIgdHlwZT0iSUQiLz4NCiAgICA8L2NvbXBsZXhUeXBl Pg0KICA8L2VsZW1lbnQ+DQo8L3NjaGVtYT4NCg== 449 2007-01-15 21:59:35 +0000 2007-01-15 21:59:35 +0000 Test case 2: instance dupIDonElement2.xml text/xml 155 sandygao 77u/PGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5j ZSINCiAgIHhzaTpub05hbWVzcGFjZVNjaGVtYUxvY2F0aW9uPSJkdXBJRG9uRWxlbWVudDIueHNk Ig0KICAgaWQyPSJhYmMiPg0KIDxpZDE+YWJjPC9pZDE+DQo8L2U+DQo= 453 2007-02-13 22:58:42 +0000 2007-02-13 22:58:42 +0000 Test case 3: schema document dupIDonElement3.xsd text/xml 285 cmsmcq PHNjaGVtYSB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEiPgogIDxlbGVt ZW50IG5hbWU9ImUiPgogICAgPGNvbXBsZXhUeXBlPgogICAgICA8c2VxdWVuY2U+CiAgICAgICAg PGVsZW1lbnQgbmFtZT0iaWQxIiB0eXBlPSJJRCIvPgogICAgICAgIDxlbGVtZW50IG5hbWU9Imlk MiIgdHlwZT0iSUQiLz4KICAgICAgPC9zZXF1ZW5jZT4KICAgICAgPGF0dHJpYnV0ZSBuYW1lPSJp ZCIgdHlwZT0iSUQiLz4KICAgIDwvY29tcGxleFR5cGU+CiAgPC9lbGVtZW50Pgo8L3NjaGVtYT4K 454 2007-02-13 23:00:39 +0000 2007-02-13 23:00:39 +0000 Test case 3: XML instance dupIDonElement3.xml text/xml 162 cmsmcq PGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5jZSIK ICAgeHNpOm5vTmFtZXNwYWNlU2NoZW1hTG9jYXRpb249ImR1cElEb25FbGVtZW50Mi54c2QiCiAg IGlkPSJhYmMiPgogPGlkMT5kZWY8L2lkMT4KIDxpZDI+Z2hpPC9pZDI+CjwvZT4K 458 2007-02-28 14:43:56 +0000 2007-02-28 14:46:27 +0000 Test case 4: schema document dupIDonElement4.xsd text/xml 281 sandygao PHNjaGVtYSB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMS9YTUxTY2hlbWEiPg0KICA8ZWxl bWVudCBuYW1lPSJlIj4NCiAgICA8Y29tcGxleFR5cGU+DQogICAgICA8c2ltcGxlQ29udGVudD4N CiAgICAgICAgPGV4dGVuc2lvbiBiYXNlPSJJRCI+DQogICAgICAgICAgPGF0dHJpYnV0ZSBuYW1l PSJpZCIgdHlwZT0iSUQiLz4NCiAgICAgICAgPC9leHRlbnNpb24+DQogICAgICA8L3NpbXBsZUNv bnRlbnQ+DQogICAgPC9jb21wbGV4VHlwZT4NCiAgPC9lbGVtZW50Pg0KPC9zY2hlbWE+DQo= 459 2007-02-28 14:44:55 +0000 2007-02-28 14:44:55 +0000 Test case 4: XML instance dupIDonElement4.xml text/html 143 sandygao 77u/PGUgeG1sbnM6eHNpPSJodHRwOi8vd3d3LnczLm9yZy8yMDAxL1hNTFNjaGVtYS1pbnN0YW5j ZSINCiAgIHhzaTpub05hbWVzcGFjZVNjaGVtYUxvY2F0aW9uPSJkdXBJRG9uRWxlbWVudDQueHNk Ig0KICAgaWQ9ImFiYyI+DQogYWJjDQo8L2U+DQo=