CARVIEW |
Select Language
HTTP/2 200
date: Sat, 11 Oct 2025 11:04:03 GMT
content-type: text/html
content-encoding: gzip
last-modified: Thu, 13 Jul 2023 17:28:48 GMT
cache-control: max-age=2592000, public
expires: Mon, 10 Nov 2025 11:04:03 GMT
vary: Accept-Encoding
access-control-allow-origin: *
x-request-id: 98cddfd74a4ac469
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=x_Ac2VIgz00V6GzVVdjzc2YFDMK4WukabBhXwsPtFbo-1760180643-1.0.1.1-KjdF6ohTROuPXk52YtY6tkqQCHmf3EwBehJH86KOUXmhzmCZPSROdWl3og3kC.KZs5HBJRYJrnzLohgg6YXzeOufZRriLgLjMwzqn06rnD8; path=/; expires=Sat, 11-Oct-25 11:34:03 GMT; domain=.w3.org; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 98cddfd74a4ac469-BLR
alt-svc: h3=":443"; ma=86400
LC Comment: Multiple reply relationships from David Hull on 2005-05-05 (public-ws-addressing-comments@w3.org from May 2005)
LC Comment: Multiple reply relationships
- From: David Hull <dmh@tibco.com>
- Date: Thu, 05 May 2005 16:51:18 -0400
- To: public-ws-addressing-comments@w3.org
- Message-id: <427A8746.3060004@tibco.com>
The rules for formulating a reply in section 3.2 state that "a new pair of IRIs is /added /to this value as follows ..." (emphasis added). We have recently clarified (in LC15) that there should only be one reply relation in a compliant message. A compliant processor is required to produce a compliant message in response to a compliant request. However, it is possible for a request also to be a reply, particularly outside the context of the usual WSDL MEPs. In this case, the request message may still be compliant, but if it is, the responder is obligated to produce a non-compliant message by adding a reply relation to a message that already has one. This could be resolved either by prohibiting request messages to have reply relations or by allowing (but discouraging) multiple reply relations in compliant messages.
Received on Thursday, 5 May 2005 20:51:24 UTC