[Bug 5818] Unicode Database: shifting sands

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


C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cmsmcq@blackmesatech.com
           Keywords|                            |needsReview




--- Comment #3 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>  2009-05-09 14:38:36 ---
Reviewing this bug report with a view toward proposing a change to resolve it,
I have come to believe that the changes made to appendix G.1.1 in connection
with bug 5948 may already have addressed the concerns raised here (although not
the concerns about 1.0 2E in the email from James Clark cited in comment 2).

The note on which the comment was originally raised has been split into a
normative paragraph and a note.  The current text is 

    [Unicode Database] is subject to future revision.  For example,
    the mapping from code points to character properties might be
    updated. All ˇminimally conformingˇ processors ˇmustˇ support the
    character properties defined in the version of [Unicode Database]
    cited in the normative references (Normative (§K.1)).  However,
    implementors are encouraged to support the character properties
    defined in any later versions. When the implementation supports
    multiple versions of the Unicode database, and they differ in
    salient respects (e.g. different properties are assigned to the
    same character in different versions of the database), then it is
    ˇimplementation-definedˇ which set of property definitions is used
    for any given assessment episode.

        Note: In order to benefit from continuing work on the Unicode
        database, a conforming implementation might by default use the
        latest supported version of the character properties. In order
        to maximize consistency with other implementations of this
        specification, however, an implementation might choose to
        provide user options to specify the use of the version of the
        database cited in the normative references. The
        PropertyAliases.txt and PropertyValueAliases.txt files of the
        Unicode database may be helpful to implementors in this
        connection.

In addition, there is a later reference to changes in the Unicode database; the
current text at that location now reads:

    [Unicode Database] has been revised since XSD 1.0 was published,
    and is subject to future revision. In particular, the grouping of
    code points into blocks has changed, and may change again. All
    ˇminimally conformingˇ processors must support the blocks defined
    in the version of [Unicode Database] cited in the normative
    references (Normative (§K.1)). However, implementors are
    encouraged to support the blocks defined in earlier and/or later
    versions of the Unicode Standard. When the implementation supports
    multiple versions of the Unicode database, and they differ in
    salient respects (e.g. different characters are assigned to a
    given block in different versions of the database), then it is
    ˇimplementation-definedˇ which set of block definitions is used
    for any given assessment episode.

    In particular, the version of [Unicode Database] referenced in XSD
    1.0 (namely, Unicode 3.1) contained the following blocks which
    have been renamed in the version cited in this
    specification. Since these block names may appear in regular
    expressions within XSD 1.0 schemas, implementors are encouraged to
    support the superseded block names in XSD 1.1 processors for
    compatibility, either by default or at user option:

        #x0370 - #x03FF: Greek
        #x20D0 - #x20FF: CombiningMarksforSymbols
        #xE000 - #xF8FF: PrivateUse
        #xF0000 - #xFFFFD: PrivateUse
        #x100000 - #x10FFFD: PrivateUse

To see the text in context, consult the current CR document at 

    http://www.w3.org/TR/xmlschema11-2/#charcter-classes

or the current status-quo document at 

   
http://www.w3.org/XML/Group/2004/06/xmlschema-2/datatypes.html#charcter-classes

I'm marking this issue as needsReview to signal that I think the WG
needs to consider whether this issue has already been resolved (and
should have been so marked when we resolved bug 5948).


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 9 May 2009 14:38:45 UTC