Changeset 159


Ignore:
Timestamp:
Oct 19, 2012, 10:50:51 PM (7 years ago)
Author:
duerst@…
Message:
  • removed/replaced text about IANA with reference to 4395bis. This addresses ticket #129.
  • in a place or two, changed "URI scheme" to "URI/IRI scheme"
File:
1 edited

Legend:

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

    r158 r159  
    10151015target="RFC3986"/>.</t>
    10161016
    1017 <t>For new URI schemes, using UTF-8 is recommended in <xref
     1017<t>For new URI/IRI schemes, using UTF-8 is recommended in <xref
    10181018target="RFC4395bis"/>.  Examples where UTF-8 is already used are the URN
    10191019syntax <xref target="RFC2141"/>, IMAP URLs <xref target="RFC2192"/>,
     
    10451045via percent-encoding, or if a scheme definition currently uses highly
    10461046scheme-specific provisions for the encoding of non-ASCII characters.</t>
    1047 
    1048 <t>This specification updates the IANA registry of URI schemes to note
    1049 their applicability to IRIs, see <xref target="iana"/>.  All IRIs use
    1050 URI schemes, and all URIs with URI schemes can be used as IRIs, even
    1051 though in some cases only by using URIs directly as IRIs, without any
    1052 conversion.</t>
    10531047
    10541048<t>Scheme definitions can impose restrictions on the syntax of
     
    14911485<section title="IANA Considerations" anchor="iana">
    14921486
    1493 <t>NOTE: THIS SECTION NEEDS REVIEW AGAINST HAPPIANA WORK.</t>
    1494 
    1495 <t>RFC Editor and IANA note: Please Replace RFC XXXX with the
    1496 number of this document when it issues as an RFC, and RFC YYYY
    1497 with the number of the RFC issued for draft-ietf-iri-rfc3987bis. </t>
    1498 
    1499 <t>IANA maintains a registry of "URI schemes".  This document attempts
    1500 to make it clear from the registry that a "URI scheme" also serves an
    1501 "IRI scheme", and makes several changes to the registry. </t>
    1502 
    1503 <t>The description of the registry should be changed: "RFC 4395
    1504 defined an IANA-maintained registry of URI Schemes. RFC XXXX updates
    1505 this registry to make it clear that the registered values also serve
    1506 as IRI schemes, as defined in RFC YYYY." </t>
    1507 
    1508 <t>The registry includes schemes marked as Permanent or Provisional.
    1509 Previously, this was accomplished by having two sections, "Permanent"
    1510 and "Provisional". However, in order to allow other status
    1511 ("Historical", and possibly a Proposed status for proposals which have
    1512 been received but not accepted), the registry should be changed so
    1513 that the status is indicated in a separate "Status" column, whose
    1514 values may be "Permanent", "Provisional" or "Historical".
    1515 Changes in status as well as updates to the entire registration
    1516 may be accomplished by requests and expert review.
    1517 </t>
    1518 
     1487  <t>This specification does not affect IANA.
     1488    For details on how to define a URI/IRI scheme and register it with IANA,
     1489    see <xref target="RFC4395bis"/>.</t>
    15191490
    15201491</section> <!-- IANA -->
Note: See TracChangeset for help on using the changeset viewer.