- From: Shane McCarron <shane@aptest.com>
- Date: Thu, 29 Jan 2009 13:03:01 -0600
- To: "Phillips, Addison" <addison@amazon.com>
- CC: Misha Wolf <Misha.Wolf@thomsonreuters.com>, Tina Holmboe <tina@greytower.net>, Dan Brickley <danbri@danbri.org>, "public-rdf-in-xhtml-tf.w3.org" <public-rdf-in-xhtml-tf@w3.org>, XHTML WG <public-xhtml2@w3.org>, "www-international@w3.org" <www-international@w3.org>
Actually, M12N says 3066 or its successor, so I think we are covered. However, I have made a note to update M12N to reference BCP 47 directly in the next revision. Phillips, Addison wrote: >> They do by inclusion, in that the datatype for @lang is the XHTML >> M12N >> datatype LanguageCode, which is based upon the XML Schema datatype >> language, which is inturn based upon BCP 47. >> > > It's true if you mean Schema 1.1 Part 2, located here: > > http://www.w3.org/TR/xmlschema11-2/#language > > But XHTML M12N (shudder, another numeronym) references RFC 3066 directly (and not BCP 47) and XML Schema 1.0. These are only references to BCP 47 insofar as RFC 3066 used to be BCP 47. > > Addison > > Addison Phillips > Chair -- W3C Internationalization WG > Editor -- IETF LTRU WG (BCP 47) > > Internationalization is not a feature. > It is an architecture. > > > -- Shane P. McCarron Phone: +1 763 786-8160 x120 Managing Director Fax: +1 763 786-8180 ApTest Minnesota Inet: shane@aptest.com
Received on Thursday, 29 January 2009 19:04:02 UTC