CARVIEW |
Select Language
HTTP/2 200
date: Thu, 09 Oct 2025 07:04:42 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 07:04:41 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98bc06794906ad8b
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=iilPuFu1qZBB5LtuNX8ZWdHyDFtAUp6qwHD7S757Isc-1759993482-1.0.1.1-TlJnX7y.njQSBy8XyJHovRwJOKtHYBmOWQt65DNPc133fA.CfDtvf9HS2AVXHjbMlmYV0618ECnPEHySo2qTWJ9U0EmVzN6VOtROio2zhYM; path=/; expires=Thu, 09-Oct-25 07:34:42 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98bc06794906ad8b-BLR
alt-svc: h3=":443"; ma=86400
query about /definitions/interface/operation/input etc. from Sanjiva Weerawarana on 2003-09-10 (www-ws-desc@w3.org from September 2003)
query about /definitions/interface/operation/input etc.
- From: Sanjiva Weerawarana <sanjiva@watson.ibm.com>
- Date: Wed, 10 Sep 2003 23:53:45 +0600
- To: <www-ws-desc@w3.org>
- Message-ID: <032b01c377c5$1893d4f0$72545ecb@lankabook2>
We say currently that a message reference component has a property called direction (incoming or outgoing). The value of this property comes from whether the message reference is via <input> or via <output>. Given that the operation has a pattern, it seems to me that the direction is now redundantly specified. That is, the patttern will say that there are messages A, B & C and indicate which are going "in" and which are going "out". Based on the discussion Amy's leading on the name of the message reference attribute, we're likely to have something like: <operation pattern="p1"> <input messageName="A" element=e1 headers=../> .. etc. where the @messageName refers to the name given in the pattern spec for pattern p1. Thus, we now have two places where the direction of the "A" message is specified: by the pattern spec for pattern p1 and by the user by using "<input messageName='A'..>" etc. instead of "<output messageName='B'..>". Is my understanding correct? At this point I'm just trying to make sure I got this right .. not certain that I will try to propose a change as I certainly understand the practical appeal of saying "<input>" etc. instead of something more cryptic that picks up the direction from the pattern. Sanjiva.
Received on Wednesday, 10 September 2003 13:58:43 UTC