Changeset 102


Ignore:
Timestamp:
Mar 11, 2012, 1:46:28 AM (8 years ago)
Author:
duerst@…
Message:

fixing grammar/syntax mistakes, updating references

File:
1 edited

Legend:

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

    r99 r102  
    105105rules are given for IRIs and related syntactic forms.</t>
    106106
    107 <t>Defining IRI as new protocol element (rather than updating or
     107<t>Defining IRI as a new protocol element (rather than updating or
    108108extending the definition of URI) allows independent orderly
    109 transitions: other protocols and languages that use URIs must
     109transitions: protocols and languages that use URIs must
    110110explicitly choose to allow IRIs.</t>
    111111
     
    147147people, handling Latin characters is as difficult as handling the
    148148characters of other scripts is for those who use only the Latin
    149 alphabet. Many languages with non-Latin scripts are transcribed with
     149script. Many languages with non-Latin scripts are transcribed with
    150150Latin letters. These transcriptions are now often used in URIs, but
    151151they introduce additional difficulties.</t>
     
    159159
    160160<t>URIs are composed out of a very limited repertoire of characters;
    161 this design choice was made to support global transcription(<xref
     161this design choice was made to support global transcription (see <xref
    162162target="RFC3986"/> section 1.2.1.).  Reliable transition between a URI
    163163(as an abstract protocol element composed of a sequence of characters)
     
    175175
    176176<t>This document defines the protocol element called Internationalized
    177 Resource Identifier (IRI), which allow applications of URIs to be
     177Resource Identifier (IRI), which allows applications of URIs to be
    178178extended to use resource identifiers that have a much wider repertoire
    179179of characters. It also provides corresponding "internationalized"
     
    192192intended to replace <xref target="RFC3987"/>.
    193193<xref target="Bidi"/> discusses the special case of
    194 bidirectional IRIs using characters from scripts written
     194bidirectional IRIs, IRIs using characters from scripts written
    195195right-to-left.
    196196<xref target="Equivalence"/> gives guidelines for applications wishing
     
    227227  schema <xref target="XMLSchema"/> has an explicit type "anyURI" that
    228228  includes IRIs and IRI references. Therefore, IRIs and IRI references
    229   can be in attributes and elements of type "anyURI".  On the other
    230   hand, in the <xref target="RFC2616"/> definition of HTTP/1.1, the
     229  can be used in attributes and elements of type "anyURI".  On the other
     230  hand, in HTTP/1.1 (<xref target="RFC2616"/>) , the
    231231  Request URI is defined as a URI, which means that direct use of IRIs
    232232  is not allowed in HTTP requests.</t>
     
    241241  percent sign ("%") in any syntactic component, SHOULD define the
    242242  interpretation of sequences of percent-encoded octets (using "%XX"
    243   hex octets) as octet from sequences of UTF-8 encoded strings; this
     243  hex octets) as octets from sequences of UTF-8 encoded characters; this
    244244  is recommended in the guidelines for registering new schemes, <xref
    245245  target="RFC4395bis"/>.  For example, this is the practice for IMAP URLs
     
    299299    URIs.</t>
    300300   
    301 <t hangText="LEIRI (Legacy Extended IRI) processing:">  This term was used in
     301<t hangText="LEIRI (Legacy Extended IRI):">  This term is used in
    302302   various XML specifications to refer
    303    to strings that, although not valid IRIs, were acceptable input to
     303   to strings that, although not valid IRIs, are acceptable input to
    304304   the processing rules in <xref target="LEIRIspec" />.</t>
    305305
     
    331331   an IRI directly, following the general syntax or a scheme-specific
    332332   syntax, the result is a set of parsed IRI components, each of
    333    which has a type (corresponding to the syntactice definition)
     333   which has a type (corresponding to the syntactic definition)
    334334   and a sequence of IRI characters. (This definition is analogous
    335335   to "parsed URI component".)</t>
     
    346346<t>RFCs and Internet Drafts currently do not allow any characters
    347347outside the US-ASCII repertoire. Therefore, this document uses various
    348 special notations to denote such characters in examples.</t>
     348special notations for such characters in examples.</t>
    349349     
    350350<t>In text, characters outside US-ASCII are sometimes referenced by
     
    398398
    399399<t>The syntax and use of components and reserved characters is the
    400 same as that in <xref target="RFC3986"/>. Each "URI scheme" thus also
    401 functions as an "IRI scheme", in that scheme-specific parsing rules
    402 for URIs of a scheme are be extended to allow parsing of IRIs using
     400same as that in <xref target="RFC3986"/>. Each URI scheme thus also
     401functions as an IRI scheme, in that scheme-specific parsing rules
     402for URIs of a scheme are extended to allow parsing of IRIs using
    403403the same parsing rules.</t>
    404404
     
    637637<t><list style="hanging">
    638638
    639 <t hangText="Convert to UTF-8">Convert the character to a sequence of
     639<t hangText="Convert to UTF-8:">Convert the character to a sequence of
    640640  one or more octets using UTF-8 <xref target="RFC3629"/>.</t>
    641641
    642 <t hangText="Percent encode">Convert each octet of this sequence to %HH,
     642<t hangText="Percent encode:">Convert each octet of this sequence to %HH,
    643643   where HH is the hexadecimal notation of the octet value. The
    644644   hexadecimal notation SHOULD use uppercase letters. (This is the
     
    694694
    695695<t>For example, the IRI
    696 <vspace/>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"<vspace/> MAY be
    697 converted to <vspace/>"http://xn--rsum-bad.example.org"<vspace/>.</t>
     696<vspace/>"http://r&amp;#xE9;sum&amp;#xE9;.example.org"<vspace/> is
     697converted to <vspace/>"http://xn--rsum-bad.example.org".</t>
    698698  <t>This conversion for ireg-name will be better able to deal with legacy
    699699    infrastructure that cannot handle percent-encoding in domain names.</t>
     
    10261026and percent-encoded representation of that character). On the other
    10271027hand, for a document with a URI of
    1028 "http://www.example.org/r%E9sum%E9.html", the percent-encoding octets
     1028"http://www.example.org/r%E9sum%E9.html", the percent-encoded octets
    10291029cannot be converted to actual characters in an IRI, as the
    10301030percent-encoding is not based on UTF-8.</t>
     
    10861086straightforwardly; the algorithms of <xref target="RFC3986"/> can
    10871087be applied directly, treating the characters additionally allowed
    1088 in IRI references in the same way that unreserved characters are in URI
     1088in IRI references in the same way that unreserved characters are treated in URI
    10891089references.</t>
    10901090
     
    11161116</preamble>
    11171117        <artwork>
    1118            leiri-ucschar  = " " / "&lt;" / "&gt;" / '"' / "{" / "}" / "|"
    1119       / "\" / "^" / "`" / %x0-1F / %x7F-D7FF
    1120       / %xE000-FFFD / %x10000-10FFFF
     1118leiri-ucschar  = " " / "&lt;" / "&gt;" / '"' / "{" / "}" / "|"
     1119               / "\" / "^" / "`" / %x0-1F / %x7F-D7FF
     1120               / %xE000-FFFD / %x10000-10FFFF
    11211121        </artwork>
    11221122        <postamble>The restriction on bidirectional formatting characters in <xref target="Bidi"></xref> is lifted.
     
    18501850    <author initials="M." surname="Duerst"/>
    18511851    <author initials='L.' surname='Masinter' />
    1852     <date year="2011" month="August" day="14" />
     1852    <author initials='A.' surname='Allawi' />
     1853    <date year="2012" month="March" day="9" />
    18531854  </front>
    1854   <seriesInfo name="Internet-Draft" value="draft-ietf-iri-bidi-guidelines-00"/>
     1855  <seriesInfo name="Internet-Draft" value="draft-ietf-iri-bidi-guidelines-02"/>
    18551856</reference>
    18561857
     
    18601861    <author initials='L.' surname='Masinter' />
    18611862    <author initials="M." surname="Duerst"/>
    1862     <date year="2011" month="August" day="13" />
     1863    <date year="2012" month="March" day="2" />
    18631864  </front>
    1864   <seriesInfo name="Internet-Draft" value="draft-ietf-iri-comparison-00"/>
     1865  <seriesInfo name="Internet-Draft" value="draft-ietf-iri-comparison-01"/>
    18651866</reference>
    18661867
     
    19121913<reference anchor="XML1" target="http://www.w3.org/TR/REC-xml">
    19131914  <front>
    1914     <title>Extensible Markup Language (XML) 1.0 (Forth Edition)</title>
     1915    <title>Extensible Markup Language (XML) 1.0 (Fifth Edition)</title>
    19151916    <author initials="T." surname="Bray" fullname="Tim Bray"><organization/></author>
    19161917    <author initials="J." surname="Paoli" fullname="Jean Paoli"><organization/></author>
     
    19191920    <author initials="E." surname="Maler" fullname="Eve Maler"><organization/></author>
    19201921    <author initials="F." surname="Yergeau" fullname="Francois Yergeau"><organization/></author>
    1921     <date day="16" month="August" year="2006"/>
     1922    <date day="26" month="November" year="2008"/>
    19221923  </front>
    1923   <seriesInfo name="World Wide Web Consortium" value="REC-xml-20081126"/>
     1924  <seriesInfo name="World Wide Web Consortium" value="REC-xml-20081116"/>
    19241925</reference>
    19251926
Note: See TracChangeset for help on using the changeset viewer.