URP: value v. representation

Section 5.3.4 ends with the sentence:
  Whenever a CSN for some value is refreshed the value is
  also refreshed using the exact value from the primitive
  so that all directory servers use exactly the same
  representation for the value. 

It should likely read:
  Whenever a CSN for some value is refreshed the value is
  also refreshed using the exact value from the primitive
  so that all directory servers use the same value.  Each
  server is, of course, free to represent the value
  in any form allowed by the attribute's syntax.

Replicas must converge to the same value, not to the same
representation of that value.  Note: CN value 'Foo Bar'
is not the same value as CN 'Foo  Bar' though they
equal per the equality rule.  Replicas must converge to
one or the other (per URP).  However, a member
value of 'CN=Foo Bar' is the same as CN='Foo\20Bar'; no
change is required by either replica.

That is, URP must not force one replicas preferred form
upon another server.

BTW, the URP seems to be dependent upon having an EQUALITY
rule defined for each attribute type and for each replica
to implement this rule.  What happens when the attribute
does have an EQUALITY matching rule? or one replica implements
the rule and another doesn't?

Kurt