W3C home > Mailing lists > Public > www-international@w3.org > January to March 2013

Re: I18N-ISSUE-207: Term data category and dfn element [.prep-ITS-20]

From: Felix Sasaki <fsasaki@w3.org>
Date: Tue, 15 Jan 2013 14:23:14 +0100
Message-ID: <50F55842.8080401@w3.org>
To: Yves Savourel <yves@opentag.com>
CC: www-international@w3.org
Am 15.01.13 14:10, schrieb Yves Savourel:
> Hi Felix, Richard, Jirka,
>>> It does seems that we have a number of ITS/HTML5 mappings
>>> that are treated differently and sometime enforced,
>>> sometime recommended, sometime not mentioned.
>> Understand ... but again: isn't that a guidance how to work with
>> ITS in HTML5? Of course this guidance will be helpful, and I'm
>> all for writing it up. And the topic could help to wake up our
>> "sleeping beauty": a best practice document about how to work with ITS2
> We have two HTML5 attributes (id and lang) that are explicitly mapped to ITS in the specification and are tested for in the test suite. If we put <dfn> (or the proper <dfn>/title combinations as Jirka noted) in the BP document, why id and lang get to be in the specification?
> (and where 'translate' goes? it's not explicitly declared in the specification, but we test for it in the test suite).
> We should be consistent: put either all mappings in the specifications or in the BP document.

Understand. So then rather do this normatively in the spec, and 
summarizing maybe in a section "existing HTML markup and ITS"?



> cheers,
> -yves
Received on Tuesday, 15 January 2013 13:23:42 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 21 September 2016 22:37:34 UTC