CfC: close ISSUE-126 charset-vs-backslashes by amicable resolution

On 12/01/2010 07:35 AM, Sam Ruby wrote:
> The current status for this issue:
> We have a single change proposal to parse backslashes in Content-Type
> headers in <meta> elements in a HTTP compliant manner:
> At this time the Chairs would also like to solicit alternate Change
> Proposals (possibly with "zero edits" as the Proposal Details), in case
> anyone would like to advocate the status quo or a different change than
> the specific one in the existing Change Proposals.
> If no counter-proposals or alternate proposals are received by January
> 12th, 2011, we will proceed to evaluate the change proposal that we have
> received to date.

As we have received no counter-proposals or alternate proposals, the 
chairs are issuing a call for consensus on the proposal that we do have. 
  If no objections are raised to this call by 26 January 2011, we will 
direct the editor to make the proposed change.  If anybody would like to 
raise an objection during this time, we strongly encourage them to 
accompany their objection with a concrete and complete change proposal.

> - Sam Ruby

- Sam Ruby

Received on Tuesday, 18 January 2011 16:26:29 UTC