Issue: WS-Addressing schemaLocation

Two potential minor issues:

1. Should bf-1 and sg-1 use a WS-A schemaLocation of "
http://www.w3.org/2005/03/addressing" (same as namespace URI) rather than
"http://www.w3.org/2005/03/addressing/" (with a trailing slash)? Both of
these URIs (as well as "http://www.w3.org/2005/03/addressing/ws-addr.xsd")
resolve to the same schema resource but WS-RF uses the latter (with
trailing /) and WS-N uses the former (no trailing /).
Is this really an issue? Yes, when you consider that that WS-N imports
WS-RF bf-1 and fails to validate in some schema validators because of this
inconsistency. The validators that fail are doing so because the WS-A
schema is getting imported twice (as if the 2 schemaLocations represent 2
schemas) and consequently produce many duplicate definition errors. This
may be a bug in the various validators but it seems a fairly common
problem. Since the WS-A spec gives no guidance on the appropriate
schemaLocation to use, the safect and most consistent chaoice would seme to
be to use the namespace URI (ie with no trailing /).

2. rpw-1 and sgw-1 declare a wsdl:definitions ns attribute of
xmlns:wsa="http://www.w3.org/2005/03/addressing" even though these WSDLs do
not need to. These 2 WSDLs should be fixed to remove this ns attribute.


Regards,
Ian