Changeset 24


Ignore:
Timestamp:
Oct 22, 2010, 4:44:41 PM (9 years ago)
Author:
duerst@…
Message:

replaced reference to RFC 4395 with reference to new WG draft

File:
1 edited

Legend:

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

    r23 r24  
    1818<!ENTITY rfc3629 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3629.xml">
    1919<!ENTITY rfc3986 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.3986.xml">
    20 <!ENTITY rfc4395 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.4395.xml">
    2120<!ENTITY rfc5890 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5890.xml">
    2221<!ENTITY rfc5891 SYSTEM "http://xml.resource.org/public/rfc/bibxml/reference.RFC.5891.xml">
     
    191190URIs to be updated to handle IRIs. A "URI scheme" (as defined by <xref
    192191target="RFC3986"/> and registered through the IANA process defined in
    193 <xref target="RFC4395"/> also serves as an "IRI scheme". Processing of
     192<xref target="RFC4395bis"/> also serves as an "IRI scheme". Processing of
    194193IRIs is accomplished by extending the URI syntax while retaining (and
    195194not expanding) the set of "reserved" characters, such that the syntax
     
    226225  hex octets) as octet from sequences of UTF-8 encoded strings; this
    227226  is recommended in the guidelines for registering new schemes, <xref
    228   target="RFC4395"/>.  For example, this is the practice for IMAP URLs
     227  target="RFC4395bis"/>.  For example, this is the practice for IMAP URLs
    229228  <xref target="RFC2192"/>, POP URLs <xref target="RFC2384"/> and the
    230229  URN syntax <xref target="RFC2141"/>). Note that use of
     
    16671666
    16681667<t>For new URI schemes, using UTF-8 is recommended in <xref
    1669 target="RFC4395"/>.  Examples where UTF-8 is already used are the URN
     1668target="RFC4395bis"/>.  Examples where UTF-8 is already used are the URN
    16701669syntax <xref target="RFC2141"/>, IMAP URLs <xref target="RFC2192"/>,
    16711670and POP URLs <xref target="RFC2384"/>.  On the other hand, because the
     
    25882587&rfc1738;
    25892588&rfc2640;
    2590 &rfc4395;
    2591 
     2589<reference anchor='RFC4395bis'>
     2590  <front>
     2591    <title>Guidelines and Registration Procedures for New URI/IRI Schemes</title>
     2592    <author initials='T.' surname='Hansen' fullname="Tony Hansen"><organization/></author>
     2593    <author initials='T.' surname='Hardie' fullname="Ted Hardie"><organization/></author>
     2594    <author initials='L.' surname='Masinter' fullname="Larry Masinter"><organization/></author>
     2595    <date year="2010" month='September' day="30"/>
     2596    <workgroup>IRI</workgroup>
     2597  </front>
     2598  <seriesInfo name="IETF" value="draft-hansen-iri-4395bis-irireg-00"/>
     2599</reference>
     2600 
     2601 
    25922602<reference anchor="UNIXML" target="http://www.w3.org/TR/unicode-xml/">
    25932603<front>
Note: See TracChangeset for help on using the changeset viewer.