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 2041 - Apply value constraints for attributes with type IDREF/IDREFS/ENTITY/ENTITIES
Summary: Apply value constraints for attributes with type IDREF/IDREFS/ENTITY/ENTITIES
Status: CLOSED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0/1.1 both
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: XML Schema WG
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-09-08 03:26 UTC by Sandy Gao
Modified: 2007-05-25 13:36 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2005-09-08 03:26:39 UTC 
When an attribute value constraint is applied and the corresponding declaration 
has one of these 4 types or a type derived from one of them, should 
IDREF/ENTITY rules be enforced? My intuition is they should, but the spec seems 
to suggest they are not checked, because those attributes are 
neither "validated" (required by IDREF in section 3.15.3) nor "string valid" 
(required by ENTITY in section 3.14.4).

Seems that when applying element value constraints with those types, 
IDREF/ENTITY special rules are enforced.
Comment 1 Sandy Gao 2005-09-19 21:19:34 UTC 
Discussed during 2005-09-09 telecon. Classify as clarification with corrigendum.

http://lists.w3.org/Archives/Member/w3c-xml-schema-ig/2005Sep/att-0073/2005-09-
09telcon.html#item07
Comment 2 Sandy Gao 2007-05-25 13:35:21 UTC 
Discussed at 2007-05-18 telecon. Adopted the following proposal.

- When attributes with ENEITY/ENTITIES types are defaulted, the constraint "String Valid" is used to ensure there are corresponding entities declared in the instance document.
- When applying ID/IDREF rules, take into account default element/attribute values.