Opened 10 years ago

Closed 8 years ago

#13 closed defect (invalid)

fixes to IRI parsing algorithm for clarity (!?)

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

Description

The IRI -> URI transformation path is through parsed components.

When converting a URI to an IRI, the reverse needs to hold.

684,686c709,713
< <t>Replace the ireg-name part of the IRI by the part converted using
< the ToASCII operation specified in Section 4.1 of <xref
< target="RFC3490"/> on each dot-separated label, and by using U+002E
---

<t>In converting an ireg-name of an IRI to the corresponding
reg-name of an equivalent URI, some care must be taken.
In most circumstances, the appropriate conversion is to
apply the ToASCII operation specified in Section 4.1 of <xref
target="RFC3490"/> on each dot-separated label, using U+002E

688,695c715,734
< to FALSE, and with the flag AllowUnassigned? set to FALSE.
< The ToASCII operation may
< fail, but this would mean that the IRI cannot be resolved.
< In such cases, if the domain name conversion fails, then the
< entire IRI conversion fails. Processors that have no mechanism for
< signalling a failure MAY instead substitute an otherwise
< invalid host name, although such processing SHOULD be avoided.
< </t>
---

to FALSE, and with the flag AllowUnassigned? set to FALSE.</t>

<t>This advice is inappropriate in the following circumstances:
<list style="symbols">

<t>The ireg-name contains no "." characters. In this case,

it may be a local name intended for some other resolution
mechanism.</t>

<t>The "scheme" of the IRI is known to be an exception

to the rule that IRI schemes that allow non-ASCII
characters in the ireg-name field should only use
those for DNS names.</t>

</list>
</t>

<t>In addition, the ToASCII operation may fail; this would generally
mean that the IRI cannot be resolved. If the conversion fails, then
the entire IRI conversion would fails. However, Processors that have
no mechanism for signalling a failure MAY instead substitute an
otherwise invalid encoded name, although such processing SHOULD be
avoided.</t>

Change History (4)

comment:1 Changed 10 years ago by lmm@…

should reference idnabis, though, not IDNA

comment:2 Changed 10 years ago by lmm@…

  • Summary changed from URI to IRI should also be by parsed components to fixes to IRI parsing algorithm for clarity (!?)

comment:3 Changed 10 years ago by lmm@…

also add another step

755,758c792,794
< mapping above (from IRI to URI components) and then reassembling a URI
< from the parsed URI components using the original punctuation that
< delimited the IRI components. </t>
<
---

mapping above (from IRI to IRI components to URI components) and then
reassembling a URI from the parsed URI components, using the original
punctuation that delimited the IRI components. </t>

comment:4 Changed 8 years ago by masinter@…

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

The ticket proposes replacing text that is no longer in the document, and was probably handled under another (duplicate) issue. In any case, marking this one as invalid.

Note: See TracTickets for help on using tickets.