Changeset 87


Ignore:
Timestamp:
Jan 11, 2012, 4:46:42 PM (8 years ago)
Author:
masinter@…
Message:

review LEIRI reversion edits

File:
1 edited

Legend:

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

    r86 r87  
    10761076
    10771077  <section title="Legacy Extended IRIs (LEIRIs)">
    1078     <t>For historic reasons, some formats have allowed variants of IRIs
    1079       that are somewhat less restricted in syntax. This section provides
    1080       a definition and a name (Legacy Extended IRI or LEIRI) for these
    1081       variants for easier reference. These variants have to be used with care;
    1082       they require further processing before being fully interchangeable as IRIs.
     1078    <t>In some cases, there have been formats which have used a protocol element
     1079      which is a variant of the IRI definition; these variants have usually been
     1080      somewhat less restricted in syntax. This section provides
     1081      a definition and a name (Legacy Extended IRI or LEIRI) for one of these
     1082      variants used widely in XML-based protocols. This variant has to be used with care;
     1083      it requires further processing before being fully interchangeable as IRIs.
     1084
    10831085      New protocols and formats SHOULD NOT use Legacy Extended IRIs.
    10841086      Even where Legacy Extended IRIs are allowed, only IRIs fully conforming
     
    10891091    <section title="Legacy Extended IRI Syntax">
    10901092      <figure>
    1091         <preamble>The syntax of Legacy Extended IRIs is the same as that for IRIs, except that ucschar is redefined as follows:</preamble>
     1093
     1094        <preamble>This section defines Legacy Extended IRIs (LEIRIs).  The syntax of
     1095   Legacy Extended IRIs is the same as that for &lt;IRI-reference&gt;, except
     1096   that the ucschar production is replaced by the leiri-ucschar
     1097   production:
     1098
     1099</preamble>
    10921100        <artwork>
    1093       ucschar        = " " / "&lt;" / "&gt;" / '"' / "{" / "}" / "|"
     1101           leiri-ucschar        = " " / "&lt;" / "&gt;" / '"' / "{" / "}" / "|"
    10941102      / "\" / "^" / "`" / %x0-1F / %x7F-D7FF
    10951103      / %xE000-FFFD / %x10000-10FFFF
     
    10981106        The iprivate production becomes redundant.</postamble>
    10991107      </figure>
    1100       <t>Likewise, the syntax for Legacy Extended IRI references (LEIRI references)
    1101       is the same as that for IRI references with the above redefinition of ucschar applied.</t>
    1102       <t>Formats that use Legacy Extended IRIs or Legacy Extended IRI references
    1103         MAY further restrict the characters allowed therein, either implicitly
    1104         by the fact that the format as such does not allow some characters, or explicitly.
    1105         An example of a character not allowed implicitly may be the NUL character (U+0000).
    1106         However, all the characters allowed in IRIs MUST still be allowed.</t>
    1107     </section>
     1108
     1109      <t>Likewise, the syntax for Legacy Extended IRI references
     1110      (LEIRI references) is the same as that for IRI references with
     1111      the above replacement of ucschar with leiri-ucschar.</t>
     1112
     1113     </section>
    11081114    <section title="Conversion of Legacy Extended IRIs to IRIs" anchor="LEIRIspec">
    11091115      <t>To convert a Legacy Extended IRI (reference) to
    11101116      an IRI (reference), each character allowed in a Legacy Extended IRI (reference)
    11111117      but not allowed in an IRI (reference) (see <xref target="notAllowed"></xref>)  MUST be percent-encoded
    1112       by applying steps 2.1 to 2.3 of <xref target="mapping"></xref>.</t>
     1118      by applying the steps in <xref target="compmapping"></xref>.</t>
    11131119    </section>
     1120     
    11141121    <section title="Characters Allowed in Legacy Extended IRIs but not in IRIs" anchor="notAllowed">
    11151122      <t>This section provides a list of the groups of characters and code points
     
    11211128        <list>
    11221129          <t>Space (U+0020): Some formats and applications use space as a delimiter,
    1123             e.g. for items in a list. Appendix C of <xref target="RFC3986"></xref>
     1130            e.g., for items in a list. Appendix C of <xref target="RFC3986"></xref>
    11241131            also mentions that white space may have to be added when displaying
    11251132            or printing long URIs; the same applies to long IRIs.
    1126             This means that spaces can disappear, or can make the Legacy Extended IRI
    1127             to be interpreted as two or more separate IRIs.</t>
     1133            Spaces might disappear, or a single Legacy Extended IRI
     1134            might incorrectly be interpreted as two or more separate ones.</t>
     1135     
    11281136          <t>Delimiters "&lt;" (U+003C), "&gt;" (U+003E), and '"' (U+0022):
    11291137            Appendix C of <xref target="RFC3986"></xref> suggests the use of
     
    11311139        (&lt;http://example.com/&gt;) as delimiters for URIs in plain text.
    11321140        These conventions are often used, and also apply to IRIs.
    1133         Legacy Extended IRIs using these characters will be cut off at the wrong place.</t>
     1141        Legacy Extended IRIs using these characters might be cut off at the wrong place.</t>
     1142     
    11341143          <t>Unwise characters "\" (U+005C),
    11351144          "^" (U+005E), "`" (U+0060), "{" (U+007B), "|" (U+007C), and "}" (U+007D):
    1136           These characters originally have been excluded from URIs because
     1145          These characters originally were excluded from URIs because
    11371146          the respective codepoints are assigned to different graphic characters
    11381147          in some 7-bit or 8-bit encoding. Despite the move to Unicode,
    11391148          some of these characters are still occasionally displayed differently
    1140           on some systems, e.g. U+005C as a Japanese Yen symbol.
     1149          on some systems, e.g., U+005C as a Japanese Yen symbol.
     1150     
    11411151          Also, the fact that these characters are not used in URIs or IRIs
    11421152          has encouraged their use outside URIs or IRIs in contexts that may
    11431153          include URIs or IRIs. In case a Legacy Extended IRI with such a character
    11441154          is used in such a context, the Legacy Extended IRI will be interpreted piecemeal.</t>
     1155     
    11451156          <t>The controls (C0 controls, DEL, and C1 controls, #x0  - #x1F  #x7F - #x9F):
    11461157            There is no way to transmit these characters reliably except potentially
     
    11721183            They are not appropriate for Legacy Extended IRIs because language information
    11731184            in identifiers cannot reliably be input, transmitted
    1174             (e.g. on a visual medium such as paper), or recognized.</t>
     1185            (e.g., on a visual medium such as paper), or recognized.</t>
    11751186          <t>Non-characters (U+FDD0-FDEF, U+1FFFE-1FFFF, U+2FFFE-2FFFF, U+3FFFE-3FFFF,
    11761187            U+4FFFE-4FFFF, U+5FFFE-5FFFF, U+6FFFE-6FFFF, U+7FFFE-7FFFF, U+8FFFE-8FFFF,
     
    14491460<section title="IANA Considerations" anchor="iana">
    14501461
     1462<t>NOTE: THIS SECTION NEEDS REVIEW AGAINST HAPPIANA WORK.</t>
     1463
    14511464<t>RFC Editor and IANA note: Please Replace RFC XXXX with the
    1452 number of this document when it issues as an RFC. </t>
    1453 
    1454 <t>IANA maintains a registry of "URI schemes". A "URI scheme" also
    1455 serves an "IRI scheme". </t>
    1456 
    1457 <t>To clarify that the URI scheme registration process also applies to
    1458 IRIs, change the description of the "URI schemes" registry
    1459 header to say "[RFC4395] defines an IANA-maintained registry of URI
    1460 Schemes. These registries include the Permanent and Provisional URI
    1461 Schemes.  RFC XXXX updates this registry to designate that schemes may
    1462 also indicate their usability as IRI schemes.</t>
    1463 
    1464 <t> Update "per RFC 4395" to "per RFC 4395 and RFC XXXX".
     1465number of this document when it issues as an RFC, and RFC YYYY
     1466with the number of the RFC issued for draft-ietf-iri-rfc3987bis. </t>
     1467
     1468<t>IANA maintains a registry of "URI schemes".  This document attempts
     1469to make it clear from the registry that a "URI scheme" also serves an
     1470"IRI scheme", and makes several changes to the registry. </t>
     1471
     1472<t>The description of the registry should be changed: "RFC 4395
     1473defined an IANA-maintained registry of URI Schemes. RFC XXXX updates
     1474this registry to make it clear that the registered values also serve
     1475as IRI schemes, as defined in RFC YYYY." </t>
     1476
     1477<t>The registry includes schemes marked as Permanent or Provisional.
     1478Previously, this was accomplished by having two sections, "Permanent"
     1479and "Provisional". However, in order to allow other status
     1480("Historical", and possibly a Proposed status for proposals which have
     1481been received but not accepted), the registry should be changed so
     1482that the status is indicated in a separate "Status" column, whose
     1483values may be "Permanent", "Provisional" or "Historical".
     1484Changes in status as well as updates to the entire registration
     1485may be accomplished by requests and expert review.
    14651486</t>
     1487
    14661488
    14671489</section> <!-- IANA -->
Note: See TracChangeset for help on using the changeset viewer.