Ticket #128 (closed defect: fixed)
use of the term 'origin'
|Reported by:||firstname.lastname@example.org||Owned by:||email@example.com|
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.
- Owner changed from firstname.lastname@example.org to email@example.com