Hi Richard, all, as MÄrcis wrote in his reply and as we discussed during yesterday's i18n call, HTML "dfn" has quite some ambiguity. For ITS implementations, the main point is this: the "its-term" attribute has the same semantics like its counterpart for XML content (its:term); an ITS processor will recognize "its-term" in HTML5, but won't know anything about "dfn" or "dt". And we don't want to change that behaviour with regards to "dfn" or "dt", due to reasons you summarized at http://lists.w3.org/Archives/Public/www-international/2013JanMar/0095.html Would it resolve your comment if we handle it together with http://lists.w3.org/Archives/Public/www-international/2013JanMar/0095.html "i18n-ISSUE-212: HTML5 in the ITS spec" and to add explanatory text like the above to the example? I'd encourage others to look into the i18n-ISSUE-212 issue too - it's quite important for getting the "ITS + HTML message" across. Best, Felix Am 16.01.13 20:43, schrieb Richard Ishida: > Example 44: The Terminology data category expressed locally in HTML > http://www.w3.org/TR/2012/WD-its20-20121206/#terminology-implementation > > This example seems to be recommending use of its-term in HTML5, > whereas there are other more standard ways of idnentifying terms in > HTML5, eg. using dfn. I don't think this is a useful example (unless > it gets heavily qualified by additional text - but even then, i'm > doubtful.) > > [comment not discussed by i18n WG] > > > >Received on Thursday, 17 January 2013 08:27:21 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:32:26 UTC