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 2439 - ChecK new RFC 3066 bis
Summary: ChecK new RFC 3066 bis
Status: RESOLVED FIXED
Alias: None
Product: XML Schema
Classification: Unclassified
Component: Datatypes: XSD Part 2 (show other bugs)
Version: 1.0/1.1 both
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Ashok Malhotra
QA Contact: XML Schema comments list
URL:
Whiteboard: important, work, i18n cluster
Keywords: resolved
Depends on:
Blocks:
 
Reported: 2005-11-03 19:24 UTC by Ashok Malhotra
Modified: 2008-01-30 15:54 UTC (History)
0 users

See Also:


Attachments

Description Ashok Malhotra 2005-11-03 19:24:38 UTC
Check the new RFC 3066 bis to make sure no changes to the language datatype are
required for Schema 1.1.
Comment 1 C. M. Sperberg-McQueen 2007-12-14 19:38:24 UTC
The XML Schema Working Group discussed this issue at its teleconference of
14 December 2007.  The current reference to RFC 3066 is non-normative: the
xsd:language datatype is intended to hold language codes as defined by RFC 3066
or its successor(s), but type validity is defined solely by a simple regular
expression, and a note points out that for the full checking of language codes,
additional work is required beyond checking for type validity.

We did not choose to change that basic pattern; in the words of the issue
description, we decided (implicitly) that no changes to the datatype are
required.  

We did agree to refer to BCP 47 instead of RFC 3066 as appropriate; the
editors were so instructed.  (I'm marking this 'decided' as well as
needsDrafting, as a reminder that the WG does not want to see the wording
before it's integrated into the status quo.)

Ashok, as originator of the issue, please indicate your acceptance of this
disposition by changing the status of the bug to RESOLVED.  If the WG
doesn't hear from you in a month, we'll assume you're happy.
Comment 2 C. M. Sperberg-McQueen 2008-01-30 15:54:55 UTC
The changes agreed on 14 December have been made and are in the status
quo text of the spec.  Accordingly, I'm marking this issue resolved.

Ashok, NOW is the time for you to indicate assent or dissent by
closing or reopening the issue.