W3C home > Mailing lists > Public > public-i18n-its@w3.org > April to June 2006

Reply to last call comment on "Internationalization Tag Set"

From: Felix Sasaki <fsasaki@w3.org>
Date: Mon, 26 Jun 2006 14:52:40 +0900
Message-ID: <449F7628.4020608@w3.org>
To: w3c-html-wg@w3.org
Cc: public-i18n-its@w3.org
Hello Steven, HTML Working Group,

This is an reply of the ITS Working Group to your last call comment on
the "Internationalization Tag Set" WD
http://www.w3.org/TR/2006/WD-its-20060518/ .
Your comment:
[[This is a last call comment from the HTML WG.

Please use XHTML Modularization for defining the DTD and Schema, since
this allows easier integration into existing and new markup languages that
use Modularization.

We would be happy to provide help in producing the necessary modules.

Best wishes,

Steven Pemberton
For the HTML WG]]

Our reply:

- We don't have a usage scenario like "use *the* ITS schema module", but
rather "use the markup which is appropriate for your purposes".
See also the conformance section
http://www.w3.org/TR/2006/WD-its-20060518/#conformance-product-schema :
[[At least one of the following MUST be in the schema:
    * rules element
    * one of the local ITS attributes
    * span element
    * ruby element
1-2: If the rules element is used, it MUST be part of the content model
of at least one element declared in the schema. It SHOULD be in a
content model for meta information, if this is available in that schema
(e.g. the head element in XHTML).
1-3: If the ruby element is used, it SHOULD be declared as an inline
1-4: If the span element is used, it SHOULD be declared as an inline

- Hence, in our view it is not adequate for the purpose of ITS to define
a normative schema module. The schemas in the ITS specification are only
non-normative examples.

- However, we want to follow the XHTML modularization approach, and we
would like to have an XHTML modularization example in our XML i18n BP
document, see http://www.w3.org/TR/2006/WD-xml-i18n-bp-20060518/
Also, in the XML i18n BP, we would recommend that any possible
proprietary modularization (as opposed to the ITS example, non-normative
one) related to HTML should follow the XHTML Modularization.

Would this address your concerns?

Best regards, Felix.

Received on Monday, 26 June 2006 05:53:01 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:43:07 UTC