- From: iri issue tracker <trac+iri@trac.tools.ietf.org>
- Date: Wed, 28 Dec 2011 01:02:00 -0000
- To: draft-ietf-iri-3987bis@tools.ietf.org, masinter@adobe.com
- Cc: public-iri@w3.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 UTC