W3C home > Mailing lists > Public > public-html@w3.org > April 2011

Re: editors comments in the W3C HTML5 specification

From: Richard Schwerdtfeger <schwer@us.ibm.com>
Date: Wed, 13 Apr 2011 08:16:22 -0500
To: Steve Faulkner <faulkner.steve@gmail.com>
Cc: Ian Hickson <ian@hixie.ch>, Maciej Stachowiak <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, HTMLWG WG <public-html@w3.org>, public-html-request@w3.org, Sam Ruby <rubys@intertwingly.net>
Message-ID: <OFD1262F82.1538821F-ON86257871.0041B211-86257871.0048E874@us.ibm.com>

That is unacceptable and unprofessional. Ian, apparently has carte blanche
to write whatever he deems appropriate into the HTML specification yet all
other working group members have to go through a formal review process?

Ian's editorial comments, if left in, may be considered to reflect the
position of all working group members. This is a consensus process and not
an Ian process. I would ask that the W3C and chairs of this working group
address this immediately. Anyone can view  the source of a W3C spec. and
see this.

Rich Schwerdtfeger
CTO Accessibility Software Group



From:	Steve Faulkner <faulkner.steve@gmail.com>
To:	Sam Ruby <rubys@intertwingly.net>, Maciej Stachowiak
            <mjs@apple.com>, Paul Cotton <Paul.Cotton@microsoft.com>, Ian
            Hickson <ian@hixie.ch>
Cc:	HTMLWG WG <public-html@w3.org>
Date:	04/13/2011 04:03 AM
Subject:	editors comments in the W3C HTML5 specification
Sent by:	public-html-request@w3.org



I don not believe the W3C HTML5 specification is a notebook for Ian to
scribble his personal opinions about changes he disagrees with.

The W3C HTML5 specification is being littered with comments by the
HTML5 editor,, these seem to appear whenever a working group decison
does not go his way,  for example:

[1]
<!-- The following paragraph is not included in the WHATWG copy
because it
is wrong. For example, content models are not syntax. It's
also unnecessary.
What kinds of things are conformance requirements is
explained in the
previous section, which talks about RFC 2119. -->

[2]
<!--(the following is not included in the WHATWG spec for quality
reasons)-->

[3]
<!--(there's no reason to convey <img> elements with alt="" text as
images
to an AT)-->
<!--(none of the following six rows make any sense)-->

While i believe it is Ian hicksons right to add whatever comments he
likes to his whatwg specification, I do not believe such comments are
helpful or useful or correct in the the context of the W3C HTML5
specification.

I would ask Ian to remove such comments from the W3C HTML5
specification, if he is unwilling then I ask the chairs advice on how
to resolve this issue.


[1] http://html5.org/tools/web-apps-tracker?from=5997&to=5998
[2] http://html5.org/tools/web-apps-tracker?from=5995&to=5996
[3]http://html5.org/tools/web-apps-tracker?from=5995&to=5996

--
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar -
www.paciellogroup.com/resources/wat-ie-about.html






graycol.gif
(image/gif attachment: graycol.gif)

Received on Wednesday, 13 April 2011 13:17:16 UTC

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