Changeset 94


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

ticket 96

File:
1 edited

Legend:

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

    r84 r94  
    150150if they are "the same" unless it has full knowledge or control of
    151151them. For this reason, determination of equivalence or difference of
    152 IRIs is based on string comparison, perhaps augmented by reference to
    153 additional rules provided by URI scheme definitions.  We use the terms
     152IRIs is based on string comparison, augmented by reference to
     153additional rules provided by scheme definition.  We use the terms
    154154"different" and "equivalent" to describe the possible outcomes of such
    155155comparisons, but there are many application-dependent versions of
     
    177177target="ladder"></xref>.</t>
    178178</section> <!-- equivalence -->
     179
     180<section title="Comparison, Equivalence, Normalization and  Canonicalization">
     181
     182<t>In general, when considering a set of items or strings, there are several
     183interrelated concepts. A comparison method determines, between two items in the
     184set, their relationship. In particular, a comparison method for determining
     185equivalence might result in a determination that two (different) items are equivalent,
     186known to be different, or that equivalence isn't determined.  </t>
     187<t> One way to define a comparison for equivalence is to define a
     188a normalization or canonicalization algorithm. For each item in a set
     189of equivalent items, one of them could be designated the "normal" or
     190"canonical" form. </t>
     191
     192<t>These general concepts are used with IRIs in this document,
     193and in other circumstances, where a mapping from one sequence of Unicode
     194characters to another one could be described as a "normalization" algorithm.</t>
     195<t> In general, this document tries to stay with the "equivalence" or
     196"comparison" methods, become some times the mathematical notion of
     197"normalization" results in forms that ordinary users might not consider "normal"
     198in an ordinary sense.
     199 </t>
     200</section>
    179201
    180202<section title="Preparation for Comparison">
Note: See TracChangeset for help on using the changeset viewer.