Lists Home |
Date Index |
I'm totally with you on this one, Elliotte, but quoting the W3C's own
rules to it seems to accomplish nothing whatsoever. So far as I can
tell they treat the Process document as W3C Recommendations are supposed
to be read: as guidelines, not capital S Standards.
I'm not sure what to make of the many last-minute changes to W3C XML
Schema, or of the XHTML WG's penchant for skipping CR, or of poisonous
namespace features added at the very end of the XPointer process. It
happens. The W3C doesn't appear to care institutionally.
email@example.com (Elliotte Rusty Harold) writes:
>How about before reading it and before it gets pushed to PR, I note
>that a change of this nature is a violation of the W3C's advertised
>process? Specifically, section 7.4.3,
>After gathering implementation experience, the Working Group MAY
>remove features from the technical report that were identified as
>being "at risk" and request that the Director Call for Review of a
>Proposed Recommendation. If the Working Group makes other substantive
>changes to the technical report, the Director MUST return it to the
>Working Group for further work.
>If the Working group feels it's important to make this substantive
>change in the BNF grammar of XML 1.1 at this point in time, then it
>must go back to working draft, not forward to PR.