[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: NEW ISSUE: Use of wsdli:wsdlLocation does not match WSDL 2.0 specification
TARGET: Web Services Binding, draft 20070926 DESCRIPTION: This comes in at least two parts: Part #1) Section 2, (approx lines 219 - 224???), definition of /binding.ws/@wsdli:wsdlLocation Currently reads: "optional attribute that specifies the location of the WSDL document. This attribute can be specified in the event that the <WSDL-namespace-URI> in the ‘endpoint’ attribute is not dereferencable, or when the intended WSDL document is to be found at a different location than the one pointed to by the <WSDL-namespace-URI>. The use of this attribute indicates that the WSDL binding points to an existing WSDL document." This is not explicitly in line with the description in the WSDL 2.0 specification, wherein this attribute is described as a sequence of pairs of URIs, where the first in each pair is the namespace, and the second is the URI to the location of the WSDL file. (http://www.w3.org/TR/wsdl20/#wsdlLocation-aii) Part #2) Appendix A: References to "http://www.w3.org/2004/08/wsdl-instance" should be replaced by "http://www.w3.org/ns/wsdl-instance", since this is now the official namespace as set out by the WSDL 2.0 Recommendation. The "schemaLocation" for the "import" statement does not reflect the actual location of this schema: "http://www.w3.org/2007/06/wsdl/wsdl20-instance.xsd" PROPOSAL: Update the text in section #2 with an explicit reference to section 7.1 of the WSDL 2.0 specification, as well as restating the point that this is a list of pairs of URIs. Also update Appendix A to reflect the release of the WSDL 2.0 Recommendation
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]