W3C home > Mailing lists > Public > public-multilingualweb-lt@w3.org > August 2012

RE: [ISSUE-34] Localization Quality

From: Yves Savourel <ysavourel@enlaso.com>
Date: Mon, 20 Aug 2012 11:02:02 -0600
To: "'Dave Lewis'" <dave.lewis@cs.tcd.ie>, <public-multilingualweb-lt@w3.org>
Message-ID: <assp.057995baa6.assp.0579afa2e1.006a01cd7ef5$84f1d160$8ed57420$@com>
Hi Dave,

Indeed, the Domain data category is a good example of where the pointers are needed for HTML.

Looking at it case by case make sense.


-----Original Message-----
From: Dave Lewis [mailto:dave.lewis@cs.tcd.ie] 
Sent: Monday, August 20, 2012 10:56 AM
To: public-multilingualweb-lt@w3.org
Subject: Re: [ISSUE-34] Localization Quality

Hi Yves,
I think this is difficult to determine in the general case. Pointer allows us to define a 'convergence' or 'coexistence' path with HTML markup usage we already know about or that someone else might think up without requiring a new attribute.

http://www.w3.org/TR/2012/WD-its20-20120731/#domain is a good example where ex 49 shows how meta type DC.subject could already be used in a similar manner as ITS domain, and hence the use of a pointer serves a useful function in allowing both markup functions to co-exist. One could image this happening with other proprietary uses of 'meta'.

But perhaps we should look at this on a case by case basis to decide if we think the Pointer option represents useful use case for HTML?


On 20/08/2012 15:30, Yves Savourel wrote:
> --- Pointers and HTML
> I wonder if the pointers mechanism really make sense in HTML (in general, not just for localization quality): Since HTML is a specific format we shouldn't have to provide a mechanism to map constructs that are equivalent to our its-... attributes.
Received on Monday, 20 August 2012 17:02:30 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:31:51 UTC