W3C home > Mailing lists > Public > public-html@w3.org > September 2012

Re: Clarification of "Extensibility" section (Was: Re: Getting HTML5 to Recommendation in 2014)

From: Jirka Kosek <jirka@kosek.cz>
Date: Thu, 20 Sep 2012 14:37:29 +0200
Message-ID: <505B0E09.6030402@kosek.cz>
To: Sam Ruby <rubys@intertwingly.net>
CC: Benjamin Hawkes-Lewis <bhawkeslewis@googlemail.com>, Paul Cotton <Paul.Cotton@microsoft.com>, "public-html@w3.org" <public-html@w3.org>, Maciej Stachowiak <mjs@apple.com>, "Janina Sajka <janina@rednote.net> (janina@rednote.net)" <janina@rednote.net>, Philippe Le Hegaret <plh@w3.org>, "Judy Brewer <jbrewer@w3.org> (jbrewer@w3.org)" <jbrewer@w3.org>, Jeff Jaffe <jeff@w3.org>, Tim Berners-Lee <timbl@w3.org>
On 20.9.2012 14:17, Sam Ruby wrote:

> I can confirm what Benjamin stated: the existing validator already
> supports multiple specifications, including extension specifications.
> 
> The validator that is deployed on the W3C site is based on validator.nu.
>  It is an instance proof that it is indeed practical to build such a
> validator.

Hi Sam, given that I recently hacked private copy of validator.nu to
support extension specification I think that I can say that I have quite
good understanding what validator can and can't do. :-)

> The interface at the W3C site produces a message as which extensions are
> included by default.  The interface at the validator.nu site has an
> input field where you can list schemas to be included.

What I'm trying to say is that if number of extension specifications
will raise then it will be not so easy for validator. Given you have N
extension specifications there are 2^N of their combinations (hope I got
it right, it was long time ago since I attended last combinatory class
:-). And given the way how HTML5 schema is expressed in RELAX NG and
given some RELAX NG limitations on how it handles name classes (they are
not full fledget patterns) it is not just about having check box for
each additional schema.

Of course these are technical obstacles which can be solved with some
additional effort. But there is another side of problem -- users. Do you
think that ordinary Joe web designer will understand why he/she should
validate page as HTML5+BAR+FOO+BAZ instead just as HTML5?

I think that W3C and HTML WG should provide much clearer message about
role of extension specifications and their impact on document conformance.

				Jirka

-- 
------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------


Received on Thursday, 20 September 2012 12:38:01 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:34 UTC