Changeset 95


Ignore:
Timestamp:
Mar 1, 2012, 5:22:27 PM (8 years ago)
Author:
masinter@…
Message:

remove todo list from doc, submitting tix, fix other minor issues

File:
1 edited

Legend:

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

    r94 r95  
    104104methods.</t>
    105105
    106 <t>Things to do:
    107 <list style="symbols"><t>Introductory section on comparison, equivalence, normalization and
    108 canonicalization.</t>
    109 <t> Verify acknowledgements for this component.</t>
    110 <t> Verify cross-references from other documents.</t>
    111 <t> Consider making 4395bis reference this document and recommend scheme definitions describe equivalence
    112 specifically.
    113 </t>
    114 <t> Consider making this document 'update' 3986 in order to resolve which one is normative if there are conflicts. </t>
    115 <t> alternatively? Consider making this document BCP rather than standards track, since it basically gives
    116   guidance for protocols and applications needing equivalence, and doesn't directly have a scope of application? </t>
    117 <t> Distingish between IRIs as sequence-of-unicode characters and presentations of IRIs. </t>
    118 <t> Should we insist that percent-hex encoding equivalence of non-reserved characters
    119   MUST be always used if there is any equivalence at all? </t>
    120 <t> Update security considerations to describe security concerns specific to comparison.</t>
    121 <t> Consider making sections talk about 'equivalent' rather than 'normalization' where
    122   appropriate. </t>
    123 </list></t>
    124 
    125106<t>One of the most common operations on IRIs is simple comparison:
    126107Determining whether two IRIs are equivalent, without using the IRIs to
     
    296277</section> <!-- stringcomp -->
    297278
    298 <section title="Syntax-Based Normalization">
     279<section title="Syntax-Based Equivalence">
    299280
    300281<figure><preamble>Implementations may use logic based on the
     
    316297normalization, and removal of dot-segments.</t>
    317298
    318 <section title="Case Normalization">
     299<section title="Case Equivalence">
    319300
    320301<t>For all IRIs, the hexadecimal digits within a percent-encoding
    321302triplet (e.g., "%3a" versus "%3A") are case-insensitive and therefore
    322 should be normalized to use uppercase letters for the digits A-F.</t>
     303should be considered equivalent to forms which use
     304uppercase letters for the digits A-F.</t>
    323305
    324306<t>When an IRI uses components of the generic syntax, the component
     
    342324</section> <!-- casenorm -->
    343325
    344 <section title="Character Normalization" anchor="normalization">
     326<section title="Unicode Character Normalization" anchor="normalization">
    345327
    346328<t>The Unicode Standard <xref target="UNIV6"></xref> defines various
     
    409391</section> <!-- charnorm -->
    410392
    411 <section title="Percent-Encoding Normalization">
     393<section title="Percent-Encoding Equivalence">
    412394
    413395<t>The percent-encoding mechanism (Section 2.1 of <xref
     
    439421</section> <!-- pctnorm -->
    440422
    441 <section title="Path Segment Normalization">
     423<section title="Path Segment Equivalence">
    442424
    443425<t>The complete path segments "." and ".." are intended only for use
     
    455437</section> <!-- ladder -->
    456438
    457 <section title="Scheme-Based Normalization" anchor="schemecomp">
     439<section title="Scheme-Based Comparison" anchor="schemecomp">
    458440
    459441<t>The syntax and semantics of IRIs vary from scheme to scheme, as
     
    517499</section> <!-- schemenorm -->
    518500
    519 <section title="Protocol-Based Normalization">
     501<section title="Protocol-Based Comparison">
    520502
    521503<t>Substantial effort to reduce the incidence of false negatives is
Note: See TracChangeset for help on using the changeset viewer.