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 1937 - Interaction between "skip" and identity constraints
Summary: Interaction between "skip" and identity constraints
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.1 only
Hardware: All All
: P4 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: medium, work, idc cluster
Keywords: resolved
Depends on:
Blocks: 3993
  Show dependency tree / graph
 
Reported: 2005-09-01 17:10 UTC by Sandy Gao
Modified: 2009-04-21 19:21 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2005-09-01 17:10:28 UTC 
What happens if a 
selector or a field result in an EII or AII that's within a subtree headed 
by an EII that matches a skip wildcard?

Strictly following the current spec, it seems that IDCs still apply. Is 
this the intention?

See the second part in:
http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2005Mar/0015.html
Comment 1 Sandy Gao 2006-11-21 20:47:14 UTC 
proposal: identity constraints works as if the sub-tree rooted at the skipped element was *not* in the instance document.

Adopted at 2006-11-17 telecon.