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

Re: Reply to last call comment on "Internationalization Tag Set"

From: Felix Sasaki <fsasaki@w3.org>
Date: Fri, 07 Jul 2006 23:03:42 +0900
Message-ID: <44AE69BE.6050801@w3.org>
To: Felix Sasaki <fsasaki@w3.org>
Cc: w3c-html-wg@w3.org, public-i18n-its@w3.org
Hello Steven, HTML Working Group,

This is just a reminder about our reply to your comment on
"Internationalization Tag Set", see below. We had send our reply 11 days
ago and have not heard from. Do you still intend to reply?

If we don't hear from you within a week, we would like to assume this
issue as closed.

Regards, Felix.

Felix Sasaki wrote:
> 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:
> http://lists.w3.org/Archives/Public/www-i18n-comments/2006Jun/0002.html
> [[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
> element.
> 1-4: If the span element is used, it SHOULD be declared as an inline
> element.]]
> 
> - 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 Friday, 7 July 2006 14:04:09 UTC

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