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 3994 - value constraints with type ENTITY/ENTITIES
Summary: value constraints with type ENTITY/ENTITIES
Status: NEW
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Structures: XSD Part 1 (show other bugs)
Version: 1.0 only
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: David Ezell
QA Contact: XML Schema comments list
URL:
Whiteboard:
Keywords:
Depends on: 2039
Blocks:
  Show dependency tree / graph
 
Reported: 2006-11-22 04:18 UTC by Sandy Gao
Modified: 2012-12-04 00:53 UTC (History)
0 users

See Also:

Attachments

Description Sandy Gao 2006-11-22 04:18:39 UTC 
When a value constraint is specified on an element/attribute declaration, it's 
required for the canonical lexical representation to be "string valid" with 
respect to the type. When the type is or is derived from ENTITY or 
ENTITIES, "string valid" requires that entity values need to be "declared 
entity name"s. 2 questions:
- Should we enforce "entity" constraints when checking value constraint values? 
(I tend to think the answer should be "No".)
- Assume the answer to the above question is yes, then do the values need to be 
entity names declared in the schema document?