- From: Mark Nottingham <mark.nottingham@bea.com>
- Date: Fri, 21 Jan 2005 14:06:41 +1100
- To: "Jonathan Marsh" <jmarsh@microsoft.com>
- Cc: <public-ws-addressing@w3.org>
This is now issue 045; http://www.w3.org/2002/ws/addr/wd-issues/#i045 On Jan 15, 2005, at 7:37 AM, Jonathan Marsh wrote: > > There is a potential problem in the Action defaulting algorithm we've > selected. It works great for http: URIs as the namespace, and > continues > the http hierarchy by adding new path components separated by slashes. > > However, slash isn't allowed as a path component by all URI schemes. > Notably, URNs don't allow slash as far as I can tell, and you often see > paths delimited by ":" instead. If a URN is used as a targetNamespace > (which seems reasonable, though we can argue whether this trend will > wither or flourish), you might end up with a default Action like: > > urn:com:microsoft:schemas:thisWsdl/dohicky/sendMoneyRequest > > which is a bad URN. > > Some possible solutions: > > a) Note in the spec that the default algorithm doesn't work for > urn: targetNamespaces, and an explicit value must be specified > in this case. > b) Redo the algorithm replacing \ with ; (or similar) that is > acceptable to both http and urn URI schemes. > c) Adjust the default algorithm to use : as a separator for urns, > retain \ for all other URI schemes. > > My two cents is that option c is the most complex to spec and to > implement, but the most user-friendly in that you get a clean default > when using http: (the most common case today), but you don't silently > get garbage when using urn:. > > URI: http://www.ietf.org/rfc/rfc2396.txt > URN: http://www.ietf.org/rfc/rfc2141.txt > > > -- Mark Nottingham Principal Technologist Office of the CTO BEA Systems
Received on Friday, 21 January 2005 03:06:42 UTC