Re: [iri] #88: A number of ABNF issues in 3987bis

Previous Topic Next Topic
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: [iri] #88: A number of ABNF issues in 3987bis

iri issue tracker
#88: A number of ABNF issues in 3987bis

Changes (by masinter@…):

 * status:  new => closed
 * resolution:   => worksforme


 (a) changed ipath-empty as suggested. (this part fixed)

 (b) did not change path-sep to eliminate it; there is at least some
 possibility that some specifications might want to allow \ as path-sep in
 defining a new very-non-legacy-extended-URI-thingie or some such (such as
 HTML); in any case, leaving it as a semantic production seems harmless.

 (c) did not allow iprivate in iquery:

 The reason why iprivate is allowed in iquery and not in ifragment is that
 a query component is part of a very specific workflow of filling out a
 form and sending it back for specific processing, while fragments have a
 much wider profile of interoperability they require. Originally, iprivate
 wasn't allowed at all, but there were specific, credible use cases where
 they made sense in queries. There have not been any use cases demonstrated
 where this is true for fragments.

 So: status change is, for three reports: one fixed, two won't fix.  Can't
 say that in tracker, so this is now marked as 'worksforme'.

 Reporter:  evnikita2@…  |       Owner:  draft-ietf-iri-3987bis@…
     Type:  defect       |      Status:  closed
 Priority:  major        |   Milestone:
Component:  3987bis      |     Version:
 Severity:  -            |  Resolution:  worksforme
 Keywords:               |

Ticket URL: <>
iri <>