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

[Bug 1836] New: RQ-100 define canonical form for language type, update RFC reference

From: <bugzilla@wiggum.w3.org>
Date: Tue, 09 Aug 2005 14:04:21 +0000
To: www-xml-schema-comments@w3.org
Cc:
Message-Id: <E1E2UiL-00010F-T8@wiggum.w3.org>

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

           Summary: RQ-100 define canonical form for language type, update
                    RFC reference
           Product: XML Schema
           Version: 1.1
          Platform: PC
               URL: http://www.w3.org/XML/Group/2002/07/xmlschema-1.1-
                    current-reqs-list.html#canon-language
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSD Part 2: Datatypes
        AssignedTo: cmsmcq@w3.org
        ReportedBy: cmsmcq@w3.org
         QAContact: www-xml-schema-comments@w3.org


(Opportunistic desideratum)

(1) We need a canonical form for the language datatype. Both upper and 
lower case variants are permitted by our type, but the relevant
RFC says they should be treated the same.  If we don't provide for
case mapping, we should at least have a health warning.

Further consideration shows other problems that need solution:

(2) Which RFC should be referred to?

(3) Should all the provisions of the RFC be enforced?  None? Some?

(4) What should happen when the RFC is replaced by a newer 
one on the same topic?  Should XML Schema processors be
automatically rendered non-conforming if they don't support it?
Should they be automatically non-conforming if they do
support the new RFC? Should implementors have a choice?
Users?
Received on Tuesday, 9 August 2005 14:04:33 GMT

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