| CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 07:19:40 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 20 Jul 2023 23:26:49 GMT
cache-control: max-age=2592000, public
expires: Sat, 08 Nov 2025 07:19:40 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bc1c6abdd31eef
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=jWYmutdCqn3oobvU1Md3ixTc5VFQdyIvH_I9U8QOk.c-1759994380-1.0.1.1-lnGFfGnM5tnwzLdNuByygRktjKndS8zK6ePZWftxAV.mms9mCSvTLfhXIz79ASz.Bmebk6H8fDDfqtWjZs6nDwxmuahoW716cGYbknl.Vcc; path=/; expires=Thu, 09-Oct-25 07:49:40 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc1c6abdd31eef-BLR
alt-svc: h3=":443"; ma=86400
Confusion between binding and element names from Yaron Goland on 2004-01-22 (www-ws-desc@w3.org from January 2004)
Confusion between binding and element names
- From: Yaron Goland <ygoland@bea.com>
- Date: Thu, 22 Jan 2004 15:08:17 -0800
- To: <www-ws-desc@w3.org>
- Message-ID: <02bb01c3e13c$9fb40b90$65e5e40c@bea.com>
Some of the children of the interface and binding XML elements, specifically the XML elements operation, input, output, infault and outfault, use the same names but have different, although related, meanings in the two locations. It would be friendlier to those writing WSDLs, especially to those talking about WSDLs, if slightly different names were used. For example, one can imagine that the names for the children of interface would stay the same but the children of binding would change to bindOperation, bindInput, bindOutput, bindInFault, bindOutFault and bindMessageReference. This small change would make simple sentences such as "The second infault has an error" much clearer as one would know that an interface was being discussed. Thanks, Yaron
Received on Thursday, 22 January 2004 18:12:31 UTC