Ignore:
Timestamp:
Oct 19, 2012, 10:01:00 PM (7 years ago)
Author:
duerst@…
Message:
  • removed domain name consideration from list of percent-encodings that cannot be eliminated (factual fix)
  • added consideration of query parts to URI->IRI procedure (non-escaping is now possible, but optional, see ticket 133)
  • minor wording changes
  • some paragraph reformatting by oXygen Author mode
File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-iri-3987bis/draft-ietf-iri-3987bis.xml

    r155 r156  
    741741<section title="Mapping query components" anchor="querymapping">
    742742
    743 <t>For compatibility with existing deployed HTTP infrastructure,
    744 the following special case applies for the schemes "http" and "https"
    745 when an IRI is found in a document whose charset is not based on UCS
    746 (e.g., not UTF-8 or UTF-16). In such a case, the "query"
    747 component of an IRI is mapped into a URI by using the document
    748 charset rather than UTF-8 as the binary representation before
    749 pct-encoding. This mapping is not applied for any other scheme
    750 or component.</t>
     743<t>For compatibility with existing deployed HTTP infrastructure, the following special case applies
     744          for the schemes "http" and "https" when an IRI is found in a document whose charset is not
     745          based on UCS (e.g., not UTF-8 or UTF-16). In such a case, the "query" component of an IRI
     746          is mapped into a URI by using the document charset rather than UTF-8 as the binary
     747          representation before pct-encoding. This mapping is not applied for any other schemes or
     748          components.</t>
    751749
    752750</section> <!-- querymapping -->
     
    764762<section title="Converting URIs to IRIs" anchor="URItoIRI">
    765763
    766   <t>In some situations, for presentation and further processing,
    767 it is desirable to convert a URI into an equivalent IRI
    768 without unnecessary percent encoding.
    769 Of course, every URI is already an IRI in its own right without any
    770 conversion. This section gives one possible procedure for URI to IRI mapping.</t>
    771 
    772 <t>
    773 The conversion described in this section, if given a valid URI, will
    774 result in an IRI that maps back to the URI used as an input for the
    775 conversion (except for potential case differences in percent-encoding
    776 and for potential percent-encoded unreserved characters).
    777 
    778 However, the IRI resulting from this conversion may differ
    779 from the original IRI (if there ever was one).</t>
     764  <t>In some situations, for presentation and further processing, it is desirable to convert a URI
     765        into an equivalent IRI without unnecessary percent encoding. Of course, every URI is already
     766        an IRI in its own right without any conversion. This section gives one possible procedure
     767        for converting a URI to an IRI.</t>
     768
     769<t>The conversion described in this section, if given a valid URI, will result in an IRI that maps
     770        back to the URI used as an input for the conversion (except for potential case differences
     771        in percent-encoding and for potential percent-encoded unreserved characters). However, the
     772        IRI resulting from this conversion may differ from the original IRI (if there ever was
     773        one).</t>
    780774
    781775<t>URI-to-IRI conversion removes percent-encodings, but not all
     
    800794      and <xref target="limitations"/> for further details.</t>
    801795
    802 <t hangText="4.">IRI to URI conversion has different rules for
    803     dealing with domain names and query parameters.</t>
     796<t hangText="4.">As described in <xref target="querymapping"/>, IRI to URI conversion may work
     797            somewhat differently for query components.</t>
    804798
    805799</list></t>
     
    824818      in UTF-8 represent characters that are not appropriate according
    825819      to <xref target="abnf"/>  and <xref
    826       target="limitations"/>.</t>
    827 
    828 <t hangText="5.">Interpret the resulting octet sequence as a sequence
    829       of characters encoded in UTF-8.</t>
    830 
    831 <t hangText="6.">URIs known to contain domain names in the reg-name
    832       component SHOULD convert punycode-encoded domain name labels to
    833       the corresponding characters using the ToUnicode procedure. </t>
     820      target="limitations"/>.</t>
     821          <t hangText="5.">Optionally, re-percent-encode octets in the query component if the scheme
     822            is one of those mentioned in <xref target="querymapping"/>.</t>
     823
     824<t hangText="6.">Interpret the resulting octet sequence as a sequence of characters encoded in
     825            UTF-8.</t>
     826
     827<t hangText="7.">URIs known to contain domain names in the reg-name component SHOULD convert
     828            punycode-encoded domain name labels to the corresponding characters using the ToUnicode
     829            procedure. </t>
    834830</list></t>
    835831
    836 <t>This procedure will convert as many percent-encoded characters as
    837 possible to characters in an IRI. Because there are some choices when
    838 step 4 is applied (see <xref target="limitations"/>), results may
    839 vary.</t>
     832<t>This procedure will convert as many percent-encoded characters as possible to characters in an
     833        IRI. Because there are some choices in steps 4 (see also <xref target="limitations"/>) and
     834        5, results may vary.</t>
    840835
    841836<t>Conversions from URIs to IRIs MUST NOT use any character
Note: See TracChangeset for help on using the changeset viewer.