W3C home > Mailing lists > Public > public-html@w3.org > January 2010

over specification is anti-competitive (blog post)

From: Larry Masinter <masinter@adobe.com>
Date: Wed, 27 Jan 2010 12:45:15 -0800
To: "public-html@w3.org" <public-html@w3.org>
Message-ID: <C68CB012D9182D408CED7B884F441D4D5FE8C2@nambxv01a.corp.adobe.com>
> Maybe this is off-topic for this list, but I've seen this notion of
> over-specification being anti-competitive raised before.  Can you
> explain why that is specifically?

http://masinter.blogspot.com/2010/01/over-specification-is-anti-competitive.html

Not entirely off-topic, but we've been encouraged to keep 
discussion to particular issues rather than general 
principles, so I think talking about the general issue
should be done elsewhere. (www-tag@w3.org would be OK with
me since I think it's a general architectural principle for
specifications and not just specific to HTML5.)

The particular issue was ISSUE-56

http://www.w3.org/Bugs/Public/show_bug.cgi?id=8207#c6
and 
http://www.w3.org/html/wg/tracker/issues/56

The implementations of URI processing that I've seen in the
past don't match the specific algorithm that used to be in
the HTML5 document, and I'd like some evidence that the
change proposal:
http://lists.w3.org/Archives/Public/public-html/2009Nov/0670.html
is actually "woefully inadequate" for anything.

(reminder http://www.w3.org/Bugs/Public/show_bug.cgi?id=8207#c6 )

Larry
--
http://larry.masinter.net
Received on Wednesday, 27 January 2010 20:45:51 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:00 GMT