W3C home > Mailing lists > Public > www-xml-schema-comments@w3.org > July to September 2005

[Bug 2314] R-200: Problem with erratum E1-18 (datatypes)

From: <bugzilla@wiggum.w3.org>
Date: Wed, 28 Sep 2005 13:47:14 +0000
To: www-xml-schema-comments@w3.org
Cc:
Message-Id: <E1EKcHC-0004YK-6p@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=2314

           Summary: R-200: Problem with erratum E1-18 (datatypes)
           Product: XML Schema
           Version: 1.0
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Keywords: unclassified
          Severity: normal
          Priority: P2
         Component: XSD Part 2: Datatypes
        AssignedTo: cmsmcq@w3.org
        ReportedBy: cmsmcq@w3.org
         QAContact: www-xml-schema-comments@w3.org


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.
Received on Wednesday, 28 September 2005 13:47:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Sunday, 6 December 2009 18:13:09 GMT