Re: [css3-namespace] Last call comments from XHTML2 WG

Hi fantasai,

Thanks for the clarification that you are responding to last call comments 
without the CSS working group's approval of the responses.

Please see the process document description of formally addressing issues 

It describes a very different model than the one you explained is being 
used in the CSS working group.  Throughout the process document, and 
specifically at the above link, it is the group (singular form) that 
formally addresses an issue, and in particular if *the* group believes a 
reviewer's comments result from a misunderstanding (as you've implied you 
believe is the case here), then "*the* group *should* seek clarification 
*before* reaching a decision." (Quote is from the process document link 
above, but emphasis is mine).

It is troublematic that last call comments are being addressed, whether 
accepting or rejecting, without group consensus.  In the case of 
rejection, there are many cases where others agree but do not post a 
comment since it has already been posted.  In the case of acceptance, you 
may be accepting something that is unacceptable to others, or also your 
way of a addressing the problem may be unacceptable to others on the 

If CSS would like the W3C to start operating under a different policy like 
the one you described, then the chair(s) should escalate this up to the 
W3C management and ensure that the new modus operandi is adequately 
covered in the process document.

John M. Boyer, Ph.D.
Senior Technical Staff Member
Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab

Blog RSS feed:

fantasai <> 
Sent by:
03/28/2008 09:11 AM

John Boyer/CanWest/IBM@IBMCA
Steven Pemberton <>, Bjoern Hoehrmann 
<>, Forms WG <>, XHTML WG 
Re: [css3-namespace] Last call comments from XHTML2 WG

John Boyer wrote:
> I've hit reply to the latest in the thread, but this message is in 
> further response to Bjoern and the thread in general.
> I would like to point out that the W3C process document specifically 
> states that last call commenters are not required to develop full 
> spec-ready solutions to the problems they identify.  It is the 
> responsibility of the CSS working group to come up with a proposed 
> solution and then ask the commenter if they are satisfied.


> I have not yet seen a satisfactory explanation in this email thread for 
> why the CSS group is choosing to violate the axiom that Steven has 
> described clearly below (and just as clearly in his last call comment).

I've tried to explain our rationale. I think the axiom Steven believes
is an axiom of CSS is subtly different from (and stricter than) the axiom
that we use in designing CSS. We take backwards and forwards compatibility
very seriously in CSS, and those are both principles that we apply in
designing new features. But that doesn't always mean every level must
either interpret the same code exactly the same or ignore everything
associated with it.

> What I have seen on this thread is a last call comment being rejected 
> without the rejection even being approved by the CSS working group (or 

The last call comment is being rejected. You have raised a formal 
to that rejection, and Anne and I will take that back to the working group
for discussion. I don't see any good reason to consult the WG on every
comment we choose to reject if the commenter later agrees with our 
Which has happened. In this case it hasn't, and you will get a response
from the full CSSWG.


Received on Friday, 28 March 2008 20:21:46 UTC