W3C home > Mailing lists > Public > public-iri@w3.org > December 2011

Re: [iri] #105: recycle at Proposed or do not allow characters previously allowed

From: iri issue tracker <trac+iri@trac.tools.ietf.org>
Date: Wed, 28 Dec 2011 01:02:00 -0000
Cc: public-iri@w3.org
To: draft-ietf-iri-3987bis@tools.ietf.org, masinter@adobe.com
Message-ID: <074.6c35368041bd74edc86066d824014f28@trac.tools.ietf.org>
#105: recycle at Proposed or do not allow characters previously allowed

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => wontfix


Comment:

 if we make any changes to the spec to bring it in alignment with current
 implementations, the changes we are making may not appear to be compatible
 (either "forward compatible" in that old implementations accept new IRIs,
 or "backward compatible" in that new implementations accept old IRIs.).

 Adding new allowed characters is backward compatible but not forward.
 Removing new characters is forward compatible but not backward.

 When bringing specs into alignment with widespread current implementations
 depends on whether there are existing deployed implementations that will
 break when presented with new stuff, etc.

 This judgment can be made when we're done, let's not avoid moving toward
 resolution with current implementations for some IETF process reasons.

-- 
------------------------+---------------------------------------
 Reporter:  masinter@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  defect      |      Status:  closed
 Priority:  major       |   Milestone:
Component:  3987bis     |     Version:
 Severity:  -           |  Resolution:  wontfix
 Keywords:              |
------------------------+---------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/iri/trac/ticket/105#comment:1>
iri <http://tools.ietf.org/wg/iri/>
Received on Wednesday, 28 December 2011 01:02:38 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 30 April 2012 19:52:04 GMT