Opened 9 years ago

Closed 9 years ago

#35 closed defect (fixed)

Allow generic scheme-independent IRI to URI translation

Reported by: duerst@… Owned by: duerst@…
Priority: critical Milestone:
Component: 3987bis Version:
Severity: - Keywords:
Cc:

Description

(this issue is from the "Open Issues" section in draft -01)
Previous drafts of this specification proposed a generic IRI to URI transformation using pct-encoding, and allowed domain name translation to be optionally handled by retranslating host names from pct-encoding back into Unicode and then into punycode. This draft does not allow that behavior, but this should be fixed to be in line with RFC 3986 syntax and to lead implementations towards an uniform an long-term URI<->IRI correspondence. See also http://www.w3.org/DesignIssues/ModelConsequences.

Change History (2)

comment:1 Changed 9 years ago by duerst@…

  • Owner set to duerst@…

comment:2 Changed 9 years ago by duerst@…

  • Resolution set to fixed
  • Status changed from new to closed

Addressed with changesets 58 to 66 (http://trac.tools.ietf.org/wg/iri/trac/changeset?new=67%40draft-ietf-iri-3987bis&old=57%40draft-ietf-iri-3987bis).
Reinstated percent-encoding as the preferred long-term way to convert ireg-name to reg-name. Allowed punycode for backwards-compatibility. Described why/when to use each case.

Note: See TracTickets for help on using tickets.