Re: CfC addendum: Status wording for HTML5 Edition for Web Authors

On Mon, Jun 13, 2011 at 11:45 PM, Maciej Stachowiak <mjs@apple.com> wrote:
>
> Hi Everyone,
>
> There has been a lively discussion on the Call for Consensus to publish the HTML5 Edition for Web Authors as a proper Working Draft. Some objected to publication as a normative document, some objected if the document was *not* marked normative. There were several suggestions for text to put in the status objection that might satisfy both sets of objections.
>
> At this time, the Chairs would like to hear from the group on whether these status proposals are satisfactory. If you find one or more of the following options unacceptable, and would object to publication of the HTML5 Edition for Web Authors with that status text, please reply to this message and state your objection, as soon as possible. Alternately, if anyone has other concrete proposals for status wording, please submit them as soon as possible.
>
>
> Option 1
>
> "This document is an automated redaction of the full HTML5 specification. As such, the two documents are supposed to agree on normative matters concerning Web authors. However, if the documents disagree, this is a bug in the redaction process and the unredacted full HTML specification takes precedence. Readers are encouraged to report such discrepancies as bugs in the bug tracking system of the HTML WG."

This seems fine with me.

> Option 2
>
> "These two specifications are generated from common base text and are intended to be entirely consistent. Both are normative and authoritative. With respect to any matters on which they (unexpectedly) disagree, there is a bug in at least one, and neither specification is authoritative with respect to the point(s) of disagreement. In such cases we expect to resolve the bug by publishing versions that are changed to be consistent."

This at the very least suffers the problem that it doesn't mention
what happens in the case when one document leaves things undefined,
but the other document defines behavior. This is expected to be a very
common situation as a lot of edge cases and error handling is only
specified in the full HTML specification. Hence that situation is not
a bug which the above text could be interpreted to say.

/ Jonas

Received on Tuesday, 14 June 2011 08:07:12 UTC