W3C home > Mailing lists > Public > public-html@w3.org > June 2010

Re: CfC: Adopt ISSUE-101 us-ascii-ref Change Proposal to replace ASCII reference

From: Sam Ruby <rubys@intertwingly.net>
Date: Tue, 15 Jun 2010 14:31:11 -0400
Message-ID: <4C17C6EF.2030905@intertwingly.net>
To: Henri Sivonen <hsivonen@iki.fi>
CC: HTML WG <public-html@w3.org>
On 06/15/2010 02:13 PM, Henri Sivonen wrote:
>
> Here's a counter-Change Proposal:
>
> Rationale
>
> To put spec readers ahead of theoretical purity, spec references
> should be followable in a browser without paywalls when feasible. In
> the case of ASCII, it is feasible.
>
> Details
>
> The reference for ASCII must not be to a document that cannot be
> obtained as plain text, HTML or PDF free of charge without a wrapper
> format (such as zip) by issuing an HTTP GET request. The reference
> should be to any resource, at the editor's discretion, that describes
> ASCII and that can be obtained as plain text, HTML or PDF free of
> charge without a wrapper format (such as zip) by issuing an HTTP GET
> request.

The above does not meet the criteria for a change proposal. Specifically[1]:

Proposal Details: This may take one of the following four forms:

  * A set of edit instructions, specific enough that they can be
    applied without ambiguity.
  * Spec text for a draft to be published separate from HTML5
    (though such a draft can be proposed at any time without a
    Change Proposal).
  * Exact spec text for the sections to be changed, and a baseline
    revision for the version of the spec being changed.
  * With prior permission from the chairs, a high-level prose
    description of the changes to be made.

- Sam Ruby

[1] 
http://dev.w3.org/html5/decision-policy/decision-policy.html#change-proposal
Received on Tuesday, 15 June 2010 18:32:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:17:09 GMT