| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 14:15:52 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:47 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 14:15:51 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98be7e11afa88cf1
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: EXPIRED
set-cookie: __cf_bm=m4mqoF._7LdUf.e8RrPsbD28HG6FBmtFSlCp2WX5VNQ-1760019352-1.0.1.1-LrZ2q6bjdBPvbR.8D_oKabUNjd9xBhmD18E91bz70Nsc6TywN3f6p1mDxjSC8NgOXlWeeIS4cADb0YN3i29M8RCfTgZx0wSSDV9uQ3Jj4oM; path=/; expires=Thu, 09-Oct-25 14:45:52 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98be7e11afa88cf1-BLR
alt-svc: h3=":443"; ma=86400
Updating WSDL Component Designators from Jonathan Marsh on 2003-09-15 (www-ws-desc@w3.org from September 2003)
Updating WSDL Component Designators
- From: Jonathan Marsh <jmarsh@microsoft.com>
- Date: Mon, 15 Sep 2003 13:06:02 -0700
- To: <www-ws-desc@w3.org>
- Message-ID: <DF1BAFBC28DF694A823C9A8400E71EA201211DA0@RED-MSG-30.redmond.corp.microsoft.com>
Appendix C [1] of our spec describes a mechanism for assigning URIs to WSDL components using fragment identifiers to combine the targetNamespace with an XPointer-like component identifier. The technical problems with this approach were referred to the TAG [2]. The heart of the issue is the inappropriateness of using fragment identifiers in conjunction with abstract URIs such as namespaces. By abstract I mean URIs without an expectations that dereferencing will return a representation of a resource. To avoid that problem, I propose using the query component of URI [3] instead of fragment identifiers. The syntax would be: <targetNamespace>?wsdl-<componentName>=<path1>.<path2>.<path3> Note that this is not recursive, nor accommodates target namespaces with query parameters in it. If these are desirable, the algorithm could look for a query component '?' and if one exists, use ':' as a delimiter instead: <targetNamespace>;wsdl-<componentName>=<path1>.<path2>.<path3> if the targetNamespace does contain a query component. Here's what such a proposal would do to the URIs in example C-2 [1]: https://airline.wsdl/ticketagent/?wsdl-interface=TicketAgent https://airline.wsdl/ticketagent/?wsdl-operation=TicketAgent.listFlights https://airline.wsdl/ticketagent/?wsdl-input=TicketAgent.listFlights.list FlightsRequest https://airline.wsdl/ticketagent/?wsdl-output=TicketAgent.listFlights.lis tFlightsResponse https://airline.wsdl/ticketagent/?wsdl-operation=TicketAgent.reserveFligh t https://airline.wsdl/ticketagent/?wsdl-input=TicketAgent.reserveFlight.re serveFlightRequest https://airline.wsdl/ticketagent/?wsdl-output=TicketAgent.reserveFlight.r eserveFlightResponse With the additional recursive functionality, and if the targetNamespace for some reason was a WSDL Component Designator such as "https://airline.wsdl/ticketagent/?wsdl-interface=TicketAgent", here's what you'd get: https://airline.wsdl/ticketagent/?wsdl-interface=TicketAgent;wsdl-input=s omething And if the targetNamespace already had a query param, like "https://airline.wsdl/ticketagent?wsdl", you'd get: https://airline.wsdl/ticketagent?wsdl;wsdl-interface=TicketAgent I think this mechanism is reversible. Comments? [1] https://dev.w3.org/cvsweb/~checkout~/2002/ws/desc/wsdl12/wsdl12.html#wsdl -uri-references [2] https://lists.w3.org/Archives/Public/www-tag/2003Feb/0042.html [3] https://www.ietf.org/rfc/rfc2396.txt
Received on Monday, 15 September 2003 16:06:40 UTC