W3C home > Mailing lists > Public > www-tag@w3.org > January 2013

Scope of W3C recommendations; core issue for polyglot & DRM

From: Larry Masinter <masinter@adobe.com>
Date: Mon, 28 Jan 2013 05:53:03 -0800
To: "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D1E400E06AC@nambxv01a.corp.adobe.com>
In the heated debate about polyglot and also about DRM, there's a lurking question of scope of W3C and of the TAG that I think is the heart of the matter.

http://lists.w3.org/Archives/Public/public-html/2013Jan/0163.html

"On the open web ...  or inside closed systems and organizations? I don't see that the TAG has any duty to the latter, so it's an honest question."

I'd like to focus on this question, of whether the TAG and the W3C have any responsibility to address comments, requirements, use cases, to accept feedback that is only (or primarily) useful in "closed" systems, ranging across 'uses proprietary technology', 'open but spec not published by W3C' or 'only useful in controlled environments, and not the public web'.

Personally, I think W3C members and the web community care about interoperability of the public web to closed systems, and that many of the Recommendations and Working groups in W3C are developing standards whose initial deployment is focused on closed systems.

I think getting agreement on scope is necessary and possibly sufficient to resolve the polyglot and DRM issues. Is it OK for W3C to publish a FPWD/Recommendation track document which has limited scope of applicability, as long as there are at least _some_ proponents in the W3C community?

Larry
--
http://larry.masinter.net
Received on Monday, 28 January 2013 13:53:36 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:51 UTC