W3C home > Mailing lists > Public > public-ws-desc-comments@w3.org > April 2005

FW: HTTP binding's MEP use description

From: Jonathan Marsh <jmarsh@microsoft.com>
Date: Fri, 29 Apr 2005 16:24:14 -0700
Message-ID: <7DA77BF2392448449D094BCEF67569A507609CB1@RED-MSG-30.redmond.corp.microsoft.com>
To: "Hugo Haas" <hugo@w3.org>
Cc: <public-ws-desc-comments@w3.org>

Thank you for the comment below, and for your patience with us in
resolving it.  We tracked the comment below as Issue LC85 [1].  The
editors have addressed the editorial matters you highlight below in
their latest drafts [2].

If you agree with our disposition of your comment, we'd like you to
acknowledge it within two weeks; otherwise we will assume you are
satisfied.  The WG plans to enter a second (short) Last Call period in
the near future, and we invite you to review that publication as well.

[1] http://www.w3.org/2002/ws/desc/4/lc-issues/issues.html#LC85

-----Original Message-----
From: www-ws-desc-request@w3.org [mailto:www-ws-desc-request@w3.org] On
Behalf Of Hugo Haas
Sent: Friday, November 12, 2004 11:10 AM
To: www-ws-desc@w3.org
Subject: HTTP binding's MEP use description

I got an action item yesterday, in light of our discssion around the
binding of our MEPs, to make sure that there was appropriate text for
each of the MEPs claimed to be supported.

Based on our previous discussion[1], the HTTP binding supports 6 MEPs
(In-Only, Robust In-Only, In-Out, Out-Only, Robust Out-Only, Out-In).
It is not specifically specified how those map to HTTP request and
responses. I would propose adding the following clarification:

    Each of the supported MEPs involve one to two messages or faults
    being exchanged. The first is transmitted using an HTTP request,
    and the second is transmitted using the corresponding HTTP
    response. In cases where only one message is being sent, the
    message body of the HTTP response MUST be empty.

While reviewing this text, I noticed that section 3.7 "Specifying HTTP
Error Codes for Faults" talks about HTTP error code sent by the
service. Because of the out-first MEPs, we should remove "by the
service", as it could be done by the client.



  1. http://lists.w3.org/Archives/Public/www-ws-desc/2004Oct/0066.html
Hugo Haas - W3C
mailto:hugo@w3.org - http://www.w3.org/People/Hugo/
Received on Friday, 29 April 2005 23:24:27 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:05:56 UTC