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: Yves Savourel <yves@opentag.com>
Date: Tue, 15 Jan 2013 06:10:12 -0700
To: <www-international@w3.org>
Message-ID: <009301cdf321$a762c1f0$f62845d0$@com>
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.

Received on Tuesday, 15 January 2013 13:10:45 UTC

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