| CARVIEW |
Select Language
HTTP/2 200
date: Tue, 07 Oct 2025 19:25:27 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: Thu, 06 Nov 2025 19:25:27 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98afc8cfed34c1b3
strict-transport-security: max-age=15552015; preload
x-frame-options: deny
x-xss-protection: 1; mode=block
cf-cache-status: MISS
set-cookie: __cf_bm=JOBj1NaINkjSf4dFZtsIhxI_Xt0TLEZwS4hbjfM2_3I-1759865127-1.0.1.1-Ktqqy80Z5UkOlcvE2jnnAnN2oicdjk1M3WulCTiAJMlO2f0m_llk1ujCuvcoSMo1xZnRxCJaBnIfEWwNbNdNw4XjF2cxYLN1CTiKzdF2YW4; path=/; expires=Tue, 07-Oct-25 19:55:27 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98afc8cfed34c1b3-BLR
alt-svc: h3=":443"; ma=86400
messageReference semantics on binding from Yaron Goland on 2004-01-22 (www-ws-desc@w3.org from January 2004)
messageReference semantics on binding
- From: Yaron Goland <ygoland@bea.com>
- Date: Thu, 22 Jan 2004 15:02:35 -0800
- To: <www-ws-desc@w3.org>
- Message-ID: <02b701c3e13b$d35eeec0$65e5e40c@bea.com>
The messageReference semantics on bindings have me a bit confused. I think that what is intended is that the value of the messageReference attribute on a binding is to point to a role name in a MEP and in so doing indirectly associate the binding input/output XML element with its counterpart in the interface definition. But the language currently in the spec in section 2.10 makes no mention of MEPs at all, rather it talks about the interface definition itself. If the intention is to relate the binding and interface input/output elements via the role in the MEP then wouldn't it make sense to more clearly spell this out in section 2.10? If that isn't the intention, then what is it? Thanks, Yaron
Received on Thursday, 22 January 2004 18:02:37 UTC