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: Mon, 14 Jan 2013 13:35:20 -0700
To: <www-international@w3.org>
Message-ID: <005801cdf296$ac498d10$04dca730$@com>
>> We probably need to consider how the its-term attribute relates 
>> to the dfn element, which I believe serves the same function, 
>> and describe that in this section.
> mm .. not sure if we need that in the ITS2 spec, but rather in 
> a best practice document: there are many existing (XML) 
> vocabularies that have existing similar or identical purposes 
> which you may want to fulfil with ITS markup or native markup,
> see e.g. the DITA "translate" or terminology markup.

There is a difference between the DITA and HTML5: the latter is described in the specification. For example we do state that 'lang' should be used as local markup for Language Information, or that 'id' should be used for Id Value.

We kind of say something about "<meta keywords>" and "<meta dcterms.subject>" for Domain, but without making it as strong as 'lang' or 'id'.

We do have an example that show translate in HTML (http://www.w3.org/TR/2012/WD-its20-20121206/examples/html5/EX-translate-html5-local-1.html) but we do not state anywhere (as far as I can see) that HTML's translate must be treated as its:translate (despite the example implying it and even having a test case for it (translate2html.html)).

It does seems that we have a number of ITS/HTML5 mapping that are treated differently and sometime enforced, sometime recommended, sometime not mentioned.

Received on Monday, 14 January 2013 20:35:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:01 UTC