Opened 8 years ago

Last modified 8 years ago

#93 reopened defect

clarify which characters are disallowed vs. not recommended

Reported by: evnikita2@… Owned by: draft-ietf-iri-3987bis@…
Priority: minor Milestone:
Component: 3987bis Version:
Severity: - Keywords:
Cc: evnikita2@…

Description

From http://lists.w3.org/Archives/Public/public-iri/2011Aug/0039.html:


Section 6 (chars not allowed) contains the "Private use codepoints"
bullet; however ABNF allows such chars to be present in IRIs. Please
align these two sections.

Change History (3)

comment:1 Changed 8 years ago by masinter@…

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

iprivate characters are only allowed in query components; the introduction of Section 6 is clear, viz:

"This section provides a list of the groups of characters and code
points that are allowed in some contexts but are not allowed in IRIs or are
allowed in IRIs only in the query part. "

We changed the name of section 6 to ""Characters Disallowed or Not Recommended in IRIs"

comment:2 Changed 8 years ago by masinter@…

  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Summary changed from Private-use chars are allowed? to clarify which characters are disallowed vs. not recommended

Addison wrote: "I don't have a problem with the name change. However, the various paragraphs aren't always specific about whether the characters are not allowed or just not recommended. The private use paragraph is a good example of this."

Reopening with a broader scope. (I suppose I could open this as a new issue but the history is relevant; this section originally was 'characters Allowed in Legacy Extended IRIs but not in IRIs " back in http://tools.ietf.org/html/draft-duerst-iri-bis-06.

comment:3 Changed 8 years ago by masinter@…

The problem here is that in some cases, the difference between LEIRI and IRI is not uniform. For example, private use characters are allowed in IRIs in the query component, and in LEIRIs everywhere. So the advice on "Converting LEIRIs to IRIs" isn't quite accurate, since you might want to utf-8 percent-hex-encode private use characters in other parts of the LEIRI when converting to an IRI but leave the private use characters in the query component alone.

Two choices: change IRIs to allow them everywhere, or change the section on converting LEIRIs. Which does the WG prefer?

Note: See TracTickets for help on using tickets.