W3C home > Mailing lists > Public > public-i18n-core@w3.org > January to March 2007

Comments from i18n core WG on "Basic XML Schema Patterns for Databinding Version 1.0"

From: Felix Sasaki <fsasaki@w3.org>
Date: Mon, 29 Jan 2007 22:28:01 +0900
Message-ID: <45BDF661.9000808@w3.org>
To: public-xsd-databinding-comments@w3.org
Cc: "public-i18n-core@w3.org" <public-i18n-core@w3.org>

Dear XML Schema Patterns for Databinding Working Group,

I'm sorry that these comments are after the LC period of your document
http://www.w3.org/TR/2006/WD-xmlschema-patterns-20061122/ , but would it
still be possible to take them into account? I'm sending them on behalf
of the i18n core WG.

comment 1)
http://www.w3.org/TR/2006/WD-xmlschema-patterns-20061122/#document-conformance
describes how an XML Schema document should look like , to ease
processing with data binding tools. You have also recommendations about
the BOM. It would be great if you could add a link to the Unicode FAQ on
the BOM
http://www.unicode.org/unicode/faq/utf_bom.html#BOM , to provide
implementers with a way to get more detailed information.

comment 2) various subsections in
http://www.w3.org/TR/2006/WD-xmlschema-patterns-20061122/#group-ElementPredefinedTypes
and
http://www.w3.org/TR/2006/WD-xmlschema-patterns-20061122/#group-AttributePredefinedTypes
talk about time / date related patterns, see subsections
2.14.6 - 2.14.11, also 2.15.6 - 2.15.11 .
It would be great if you could add a note pointing to the document
"Working with Time Zones"
http://www.w3.org/TR/2005/NOTE-timezone-20051013/ . It provides
information e.g. about the difference between dateTime in XML Schema vs.
programming languages, which seems to be relevant for your audience.

comment 3) subsections 2.14.17 and 2.15.17 , on the LanguageElement /
LanguageAttribute . The definition of the language type at
http://www.w3.org/TR/xmlschema-2/#language refers only to RFC 3066 and
the pattern [a-zA-Z]{1,8}(-[a-zA-Z0-9]{1,8})* . It would be great if you
could point to BCP 47 instead, see
http://www.rfc-editor.org/rfc/bcp/bcp47.txt . BCP 47 is the "Best Common
Practice" for language identification. Currently, BCP 47 is represented
by the successor of RFC 3066, which is RFC 4646 (Tags for Identifying
Languages) and RFC 4647 (Matching of Language Tags).

Thank you very much in advance. Regards, Felix
Received on Monday, 29 January 2007 13:28:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 1 October 2008 10:18:51 GMT