If there is a precedent that is fine with me.
Phillip Hallam-Baker FBCS C.Eng.
Principal Scientist
VeriSign Inc.
781 245 6996 x227
> -----Original Message-----
> From: Eve L. Maler [mailto:]
> Sent: Friday, February 08, 2002 3:39 PM
> To:
> Subject: RE: [security-services] Changes for Core 26
>
>
> At 11:14 AM 2/8/02 -0800, Hallam-Baker, Phillip wrote:
>
> >The canonical form in 2396 is pretty robust and the rules are very
> >straightforward,
> >
> >Essentially the only place where case insensitivity comes in
> is in the part
> >of a URI that is a DNS name.
> >
> >Even if the file is located on a Windows or VMS machine
http://foo.com/Fred
>is not equivalent to http://foo.com/FRED or http://foo.com/fred
Even so, I think we should continue to restrict string matches to exact,
case-sensitive matches, as XML Namespaces does for namespace URIs. Since
we don't mandate that any of these URIs necessarily be resolvable, using
URI resolution machinery (which *might* know about the special http:
matching rules) to handle them seems too heavyweight in most cases.
Eve
--
Eve Maler +1 781 442 3190
Sun Microsystems XML Technology Center eve.maler @ sun.com
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
