This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2850 - RQ-15 Correct restriction of identity constraints (id-restriction)
Summary: RQ-15 Correct restriction of identity constraints (id-restriction)
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: Other All
: P3 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
Whiteboard: status?, idc cluster, restriction clu...
Keywords: resolved
Depends on:
Blocks: 5238
  Show dependency treegraph
Reported: 2006-02-11 01:42 UTC by C. M. Sperberg-McQueen
Modified: 2007-03-01 02:18 UTC (History)
0 users

See Also:


Description C. M. Sperberg-McQueen 2006-02-11 01:42:37 UTC
This issue was originally reported by Khaled Noaman/Henry S. Thompson.

Resolve the issues associated with restricting types whose elements
include identity constraints.  Specifically, (1) the rule must changed
to state that the restricted type must have a superset rather than a
subset of identity constraints, (2) the term superset must be clearly
defined, and (3) there must be a way to redefine identity constraints
in the restricted type without causing duplicate name problems.


Input from Straw Poll O-10

Interacts with RQ-17 (#restrictn-rules).

This item was discussed in the meeting of 2004-04-09
We agreed that we would like to see the proposal written down. The
minutes say "The description in the minutes may suffice as written
proposal; if not, HT will write it up.  Others to say if the minutes
are insufficient."

This item was discussed, and phase-1 agreement was reached, in the
meeting of 2004-05-13
Comment 1 Henry S. Thompson 2006-03-16 15:41:45 UTC
In the context of bringing forward a proposal for part of 2820 to the WG, this assumes increased urgency.

The required change comes as an addition to the second sub-case of the mapping rules for xs:element (file:///d:/work/1.1_xmlschema/structures/structures.html#declare-element), along the following lines:

 An element declaration as in the first case above, with the exception of its {target namespace}, {scope} and {identity-constraint definitions} properties, which are as below:

 {identity-constraint definitions} Let the *local ICDs* be A set consisting of the identity-constraint definitions corresponding to all the <key>, <unique> and <keyref> element information items in the [children], if any, otherwise the empty set.  Then iff the EII has <complexType> as an ancestor and the corresponding CTD has {derivation method} *restriction*, the union of the *local ICDs* and the *inherited ICDs*, otherwise just the *local ICDs*, where the *inherited ICDs* are the *inherited ICDs* of the corresponding Element Declaration, as defined in [3.4.6]

And we add after the definition of Particle Actually Restricts a somewhat tricky definition of the *inherited ICDs* of an ED as either the always-the-same set of ICDs found on _all_ the EDs in a base content model which ever 'map to' that ED in its (restriction) content model, or the empty set.
Comment 2 C. M. Sperberg-McQueen 2007-03-01 02:18:22 UTC
A wording proposal to resolve this issue was adopted by the WG at its
call of 12 January 2007.  Accordingly, I'm marking the issue resolved.

Henry Thompson, one of the originators, has been made aware of the
resolution of the issue through his participation in the WG; no
separate notification is being sent.