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 2314 - R-200: Problem with erratum E1-18 (datatypes)
Summary: R-200: Problem with erratum E1-18 (datatypes)
Status: RESOLVED WONTFIX
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: C. M. Sperberg-McQueen
QA Contact: XML Schema comments list
URL:
Whiteboard: important, hard, declared names cluster
Keywords: needsDrafting
Depends on:
Blocks:
 
Reported: 2005-09-28 13:47 UTC by C. M. Sperberg-McQueen
Modified: 2006-09-20 18:10 UTC (History)
0 users

See Also:


Attachments

Description C. M. Sperberg-McQueen 2005-09-28 13:47:14 UTC
The discussion of value space and lexical space in XML Schema
Datatypes 1.0 has some problems.  Although elsewhere the spec
suggests that every value in a value space has a lexical 
representation, and that every literal in a lexical space maps
to a value, the discussion of ENTITY in 1.0 suggests that 
some literals in the lexical space don't map to values.

Describing the value space as restricted to names of declared
entities also suggests to some readers that entity declarations
are part of datatype validity; some members (at least) of the
WG believe that this is not so and ought not to be implied by
the spec.

So: the description of value space and lexical space should
be revised, and notes should be added (analogous to those added
to Datatypes 1.1 for ID, IDREF, and IDREFS) saying the relevant
constraint is to be enforced at a different level, not as part of
datatype validity.

Cf. Bug 2193.
Comment 1 Sandy Gao 2005-11-18 03:43:26 UTC
The "so:..." part in comment #0 can be deemed as a phase-1 proposal (which I'm 
in favor of). If it's adopted, the following are suggested phase-2 changes.

Change section 3.4.11 (not including subsections) to

"3.4.11 ENTITY

[Definition:]   ENTITY represents the ENTITY attribute type from [XML].  The 
·value space· of ENTITY is the set of all strings that ·match· the NCName 
production in [Namespaces in XML]. The ·lexical space· of ENTITY is the set of 
all strings that ·match· the NCName production in [Namespaces in XML]. The 
·base type· of ENTITY is NCName.

For compatibility (see Terminology (§1.5)) ENTITY should be used only on 
attributes."

And change section 3.4.12 (not including subsections) to

3.4.12 ENTITIES

[Definition:]   ENTITIES represents the ENTITIES attribute type from [XML]. The 
·value space· of ENTITIES is the set of finite, non-zero-length sequences of 
·ENTITY·s. The ·lexical space· of ENTITIES is the set of space-separated lists 
of tokens, of which each token is in the ·lexical space· of ENTITY. The ·item 
type· of ENTITIES is ENTITY.

For compatibility (see Terminology (§1.5)) ENTITIES should be used only on 
attributes."
Comment 2 Sandy Gao 2005-11-18 17:41:46 UTC
Discussed at 2005-11-18 telecon.

It was determined that we also need notes parallel to those for IDREF and 
IDREFS to indicate that ENTITY related rules are enforced in structures.

RESOLUTION: Accept SG's text plus HT's suggestion as detailed Phase 1 
agreement, change to needsDrafting, assigned to HT
Comment 3 David Ezell 2006-09-20 18:10:49 UTC
Marked as RESOLVED/WONTFIX per the minutes
http://www.w3.org/XML/Group/2006/01/xml-schema-ftf-minutes.html#Review_of_open_issues