W3C home > Mailing lists > Public > xml-dist-app@w3.org > January 2006

Re: What it means to "get rid of MEPs"

From: Hervé Ruellan <herve.ruellan@crf.canon.fr>
Date: Wed, 04 Jan 2006 17:33:01 +0100
To: noah_mendelsohn@us.ibm.com
Cc: David Hull <dmh@tibco.com>, xml-dist-app@w3.org
Message-id: <43BBF8BD.9050702@crf.canon.fr>

noah_mendelsohn@us.ibm.com wrote:
> David Hull writes:
> a) Choose a binding and read the specification for that binding  -- 
> implement what the binding says.  By the way, most bindings assert that 
> they implement one or more MEPs, but that's not required.  The binding 
> does what the binding does.  Maybe it does it in a way conformant to a 
> SOAP MEP, maybe not.  Of course, if it says it implements an MEP it must 
> do so properly. 

Reading the SOAP Protocol Binding Framework again, I discovered that 
bindings MUST implement one or more MEPs.

Third paragraph of 4.2 in part 1 says:
... A binding specification MUST enable one or more MEPs.

So it just seems that we made MEPs first class citizens of SOAP and that 
it might be hard to get rid of them.


Received on Wednesday, 4 January 2006 16:33:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:28 UTC