My inclination is to preserve the uri
semantics for uri objects. I think the use of string semantics likely to
cause more inadvertent errors than one might expect from the more restrictive
uri constraints.
Cheers!
Ron Williams
Sr. Enterprise Architect
IBM Tivoli Security
+1.512.838.0073
+1.512.633.7711
Anne Anderson <>
06.08.06 01:56 PM
Please respond to
To
OASIS XACML TC <>
cc
Subject
[Fwd: Re: [xacml] url/uri-string-concatenate]
Rich Salz asked, regarding the url/uri-string-concatenate
discussion,
whether uri or string semantics were used in the concatenation. He
has
examples in the attached e-mail.
I suggested string, as being probably more flexible, but have no strong
grounds for either. What do other TC members think?
Regards,
Anne
--
Anne H. Anderson Email:
Sun Microsystems Laboratories
1 Network Drive,UBUR02-311 Tel: 781/442-0928
Burlington, MA 01803-0902 USA Fax: 781/442-1692
----- Message from Richard Salz <> on Thu, 08 Jun
2006 13:18:01 -0400 -----
To:
Subject:
Re: [xacml] url/uri-string-concatenate
Thanks. :) But the bigger question, are they
string or URI semantics?
http://a/b + c --> http://a/b/c (uri semantics)
http://a/b + c --> http://a/bc (stringsemantics)
--
SOA Appliances
Application Integration Middleware
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. You may a link to this group and all your TCs
in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
S/MIME Cryptographic Signature
