Re: [security-services] Changes for Core 26

[Stephen Farrell <stephen.farrell@baltimore.ie>]

Eve,

<sophistry>
The problem with being logical, consistent and pure in this case
is that it ignores reality and results in saml conformant code
not being as useful as current proprietary products. 
</sophistry>

I'm mainly thinking of resource names which are read off the wire 
by saml components as written by non-saml components. I'm not sure 
if the namespace case is the same, but it clearly has less precedent 
than the resource URI case.

Stephen.

"Eve L. Maler" wrote:
> 
> 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>

-- 
____________________________________________________________
Stephen Farrell         				   
Baltimore Technologies,   tel: (direct line) +353 1 881 6716
39 Parkgate Street,                     fax: +353 1 881 7000
Dublin 8.                mailto:stephen.farrell@baltimore.ie
Ireland                             http://www.baltimore.com