Opened 9 years ago

Closed 8 years ago

#34 closed defect (fixed)

Incomplete sentence in Section 3.7: "and in general there This section gives"

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

Description

There is an incomplete sentence in Section 3.7, Converting URIs to IRIs (reported by Robin Cover):

In some situations, for presentation and further processing, it is
desirable to convert a URI into an equivalent IRI in which natural
characters are represented directly rather than percent encoded. Of
course, every URI is already an IRI in its own right without any
conversion, and in general there This section gives one such
procedure for this conversion.

Change History (2)

comment:1 Changed 8 years ago by masinter@…

Peter:

In some situations, for presentation and further processing, it is
desirable to convert a URI into an equivalent IRI in which natural
characters are represented directly rather than percent encoded. Of
course, every URI is already an IRI in its own right without any
conversion. However, this section gives one possible procedure for
conversion.

What I think I wanted to say here was that there were many possible uri -> iri conversions, including the one that didn't do anything.

However, as I thought about it, what I realized was that the requirements for
uri -> iri conversion weren't clear, and when I went to write down those
requirements, i wasn't sure all the desirable properties could be accomplished.

For example, if you convert uri A to iri Alpha, you would like the result of
processing A and processing Alpha to be the same. But which results? The
"parsed URI components"?

But any variability in IRI processing (such as whether you punycode the
host name) might mean that you'd get a different result.

I suppose I should just fix the typo and submit a new issue...

comment:2 Changed 8 years ago by masinter@…

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

Martin and I came up with:

In some situations, for presentation and further processing, it is
desirable to convert a URI into an equivalent IRI without unnecessary percent encoding. Of course, every URI is already an IRI in its own right without any
conversion. This section gives one possible procedure for URI to IRI mapping.

Note: See TracTickets for help on using tickets.