CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 15:59:49 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:51 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 15:59:49 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bf16591b5d1f95
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=ilhLBp_qbNCRlvVxZjvVg322DQw7q0awMnazmkYQH8k-1760025589-1.0.1.1-KnceLZeYm1lO0AYrVcTyxXjsho3NLOXcRDAy5KS8xbGqKLzLX7dpBo_2LT7WPU06_vN8I_fLQe0jfnIT64b30.gtAd61IWI2t52y0lbb.G8; path=/; expires=Thu, 09-Oct-25 16:29:49 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bf16591b5d1f95-BLR
alt-svc: h3=":443"; ma=86400
Minority objection to requiring unique GEDs or required feature to distinguish operations from Martin Gudgin on 2004-07-29 (www-ws-desc@w3.org from July 2004)
Minority objection to requiring unique GEDs or required feature to distinguish operations
- From: Martin Gudgin <mgudgin@microsoft.com>
- Date: Thu, 29 Jul 2004 08:07:13 -0700
- To: <www-ws-desc@w3.org>
- Cc: "Amelia A Lewis" <alewis@tibco.com>, "Sanjiva Weerawarana" <sanjiva@watson.ibm.com>, "Jeffrey Schlimmer" <jeffsch@windows.microsoft.com>
- Message-ID: <DD35CC66F54D8248B6E04232892B633802DC85F4@RED-MSG-43.redmond.corp.microsoft.com>
The WSDL 2.0 Part 1 Last Call Working Draft[1] (will) REQUIRE that if operations within an interface do not reference unique global element declarations then a WSDL Feature component MUST be used to indicate how operations are distinguished 'on-the-wire'. IBM Corp., Microsoft Corp. and TIBCO Software, Inc. object to this design for several reasons; 1. It reduces the expressive power of the language. 2. It forces services to disclose how they distinguish between operations which leads to tighter coupling between the service and its consumers than is necessary for interop. 3. For WSDL authors that want to distinguish between operations 'on-the-wire' then using unique global element declarations for each message is sufficient. 4. The mechanism can be trivially circumvented, by defining a 'null' feature that claims to satisfy the requirement but in fact provides no details on how operations are distinguished. Indeed, someone has proposed this[2] as a way of 'testing' this particular part of the specification. 5. This restriction makes WSDL 2.0 unable to describe a class of message exchanges allowed by WS-Addressing. Please note that IBM Corp., Microsoft Corp. and TIBCO Software, Inc. do NOT object to WSDL authors being able to write WSDL in such a way that distinguishing operations is 'obvious', for example by using unique global element declarations. The objection is to the specification requiring that WSDL be written in such a way. Regards Martin Gudgin, Microsoft Corp. Amelia A. Lewis, Tibco Software, Inc. Sanjiva Weerawarana, IBM Corp. [1] https://www.w3.org/2002/ws/desc/wsdl20 [2] https://lists.w3.org/Archives/Public/www-ws-desc/2004Jul/0336.html
Received on Thursday, 29 July 2004 11:08:02 UTC