W3C home > Mailing lists > Public > www-tag@w3.org > October 2011

RE: Friction and cross pollination

From: Larry Masinter <masinter@adobe.com>
Date: Mon, 17 Oct 2011 14:37:25 -0700
To: Robin Berjon <robin@berjon.com>, Michael Champion <Michael.Champion@microsoft.com>
CC: Noah Mendelsohn <nrm@arcanedomain.com>, "ndw@nwalsh.com" <ndw@nwalsh.com>, "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D05D4AC0A83@nambxv01a.corp.adobe.com>
> we'll simply shut down once the report is published

Yes, task forces should produce a report and shut down. The report should identify follow-on work that needs to be done, whether in working groups or community groups.

However, in the case where there are ongoing activities in W3C developing incompatible material (XML and HTML, RDFa and microdata, or, say, WebVTT and TTML) insufficient regard to cross-specification compatibility and interoperability, I don't think sending the remaining work to a "community group" is appropriate.   I'm glad to hear that "most involved parties" are happy with the current direction wrt canvas/SVG/CSS, but I haven't seen any documents about the situation other than a talk at last year's TPAC in Lyon. Is there a report or analysis I'm missing?

Community groups seem more appropriate for new work in new areas, not for trying to fix problems caused by previous and ongoing conflicts.

IMHO

Larry
--
http://larry.masinter.net


> For the HTML-XML situation, there are probably profiles, best 
> practices, APIs, etc. that people could work on together  that could 
> address some of the use cases, without trying to "fix" XML (which is 
> largely done and burned into silicon) or add a boat anchor on the evolution of HTML.
> That seems more suited to a community-specific approach than a global 
> architecture approach to me.

That's precisely what I was aiming for with my list of suggestions for further work. If it wasn't clear, we should clarify the text.

> I do suspect the same thing applies to the RDFa/Microdata and canvas/SVG/CSS situations, but that's getting into areas I'm not really up to speed on and don't wish to debate with the TAG.  

FWIW I think that the canvas/SVG/CSS situation is well on its way to being fixed with most involved parties happy with the current direction.

--
Robin Berjon - http://berjon.com/ - @robinberjon
Received on Monday, 17 October 2011 21:38:07 UTC

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