[Bug 16869] HTML5 is missing mechanism for preventing clashes of vendor-neutral extensions

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16869

--- Comment #4 from Jirka Kosek <jirka@kosek.cz> 2012-04-26 19:27:52 UTC ---
(In reply to comment #3)
> Do you really think anybody else will mint its-*="" attributes? This hasn't
> been a problem in practice.

A lot of parties are interested in using ITS in HTML5. If there is way how to
make localization and translation process more automated, then it will be used
to $$$. And a lot of content is now stored and processed primarly as HTML.

Technically its-* attributes can be used without any problem. The trouble is
that such attributes will be marked as non-conforming. And for many government
and Fortune 500 customers it is unacceptable to use HTML which isn't formally
valid.

As it seems that there is no consensus on getting generic distributed
extensibility in HTML5 there should be at least simple and non-distributed
mechanism how to put such data in HTML and keep validaty of document.

It is just conservative extension of mechanism that is already in spec --
data-* attributes. But data-* attributes are targeted for private application
use, while its-* is used by different tools and different stages of document
workflow.

> RESOLVED WORKSFORME, in this context, meant that the existing extensibility
> mechanisms are good enough for your stated use case.

In MultilingualWeb WG we made extensive research and have long discussion about
another possibilities including data-* attributes, RDFa and Microdata. However
using its-* is technically the best approach. What we are asking here is just
to lift conformance criteria little bit, so larger communities can register
prefix and use their custom attributes to convey additional metadata in HTML
files without getting red flags from validators.

Impact on implementations will be almost zere. No single line of web browser
has to be changed. Validators will just add simple rule similar to one already
bypassing data-* attributes from validation. That is.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 26 April 2012 19:27:57 UTC