* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #128 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

use of the term 'origin'

Reported by: stpeter@stpeter.im Owned by: duerst@it.aoyama.ac.jp
Priority: minor Milestone:
Component: 3987bis Version:
Severity: - Keywords:
Cc:

Description

While reviewing 3987bis for i18n terminology, I came across this
paragraph (Section 3.5):

For compatibility with existing deployed HTTP infrastructure, the
following special case applies for schemes "http" and "https" and
IRIs whose origin has a document charset other than one which is UCS-
based (e.g., UTF-8 or UTF-16). In such a case, the "query" component
of an IRI is mapped into a URI by using the document charset rather
than UTF-8 as the binary representation before pct-encoding. This
mapping is not applied for any other scheme or component.

The term 'origin' could be ambiguous here. It doesn't seem to be
referencing the Web Origin Concept (RFC 6454) but instead seems to be
based on the "document" (broadly construed) in which the http or https
URL is found (e.g., as a hyperlink in an HTML document or perhaps as
running text in an email message). It would be good to make that clear.

Change History

comment:1 Changed 3 years ago by stpeter@stpeter.im

One way to remove the ambiguity would be to change "origin" here to
something else, but even then I think we'd need additional text. I
tentatively propose the following:

For compatibility with existing deployed HTTP infrastructure, the
following special case applies for the schemes "http" and "https"
when an IRI is found in a document whose charset is not based on UCS
(e.g., not UTF-8 or UTF-16). In such a case, the "query" component
of an IRI is mapped into a URI by using the document charset rather
than UTF-8 as the binary representation before pct-encoding. This
mapping is not applied for any other scheme or component.

comment:2 Changed 2 years ago by duerst@it.aoyama.ac.jp

  • Owner changed from draft-ietf-iri-3987bis@tools.ietf.org to duerst@it.aoyama.ac.jp

This change looks good to me. I have included this in the SVN copy with revision 120. I'm leaving the issue open just in case somebody has some better idea.

comment:3 Changed 2 years ago by stpeter@stpeter.im

  • Status changed from new to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.