- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Wed, 8 Dec 2004 14:25:46 -0800
- To: <public-ws-addressing@w3.org>
I took an action to propose how to reuse wsdli:wsdlLocation to hint as to where one might find an appropriate service description. wsdlLocation is defined in the WSDL 2.0 spec [1] but that section does not actually constrain it identification of WSDL 2.0 documents (this is probably unintentional, and we should confirm with the WSDL WG.) The examples in Rebecca's mail [2] (as interpreted by me): <wsa:EndpointReference xmlns:my="http://example.com/mynamespace"> ... <wsa:service>my:Service</wsa:service> <wsa:serviceDescription> http://example.com/fetch/the/wsdl/here </wsa:serviceDescription> ... </wsa:EndpointReference> can thus be rewritten as: <wsa:EndpointReference xmlns:my="http://example.com/mynamespace" xmlns:wsdli="http://www.w3.org/@@@@/@@/wsdl-instance" wsdli:wsdlLocation="http://example.com/mynamespace http://example.org/fetch/the/wsdl/here"> ... <wsa:service>my:Service</wsa:service> ... </wsa:EndpointReference> My proposal is to: 1) Confirm (or lobby) with the WSDL WG that wsdli:wsdlLocation applies to WSDL 1.1 as well as WSDL 2.0. 2) Show examples in our spec using wsdli:wsdlLocation on wsa:EndpointReference. I'm not sure we'd need a wsa property [description(s)], the wsdlLocation implies that and I think cleanly composes without a property but I don't see real harm in defining that property either. If a property is useful, perhaps it should be defined in the WSDL spec so it is associated with the syntax more closely. [1] http://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl20/wsdl20.html?cont ent-type=text/html;%20charset=utf-8#wsdl-uri-references [2] http://lists.w3.org/Archives/Public/public-ws-addressing/2004Nov/0297.ht ml
Received on Wednesday, 8 December 2004 22:26:29 UTC