W3C home > Mailing lists > Public > www-tag@w3.org > December 2005

Fw: EPRs, MAPs and MEPs

From: <noah_mendelsohn@us.ibm.com>
Date: Thu, 1 Dec 2005 15:18:29 -0500
To: www-tag@w3.org
Cc: David Hull <dmh@tibco.com>
Message-ID: <OF4B7044A4.BA351864-ON852570CA.006F2E91-852570CA.006F8F4A@lotus.com>

David Hull was kind enough to send this clarification to the dist-app 
list, but I think it is also of interest as the TAG comes up to speed on 
WS-Addressing.  Thanks David!

--------------------------------------
Noah Mendelsohn 
IBM Corporation
One Rogers Street
Cambridge, MA 02142
1-617-693-4036
--------------------------------------




----- Forwarded by Noah Mendelsohn/Cambridge/IBM on 12/01/2005 03:14 PM 
-----


David Hull <dmh@tibco.com>
Sent by: xml-dist-app-request@w3.org
12/01/2005 02:33 PM
 
        To:     xml-dist-app@w3.org
        cc:     (bcc: Noah Mendelsohn/Cambridge/IBM)
        Subject:        EPRs, MAPs and MEPs


As there has been some confusion:

WSA defines two core concepts: Endpoint References (EPRs) and Message 
Addressing Properties (MAPs).
EPRs provide a data representation for a destination for messages. 
Basically an IRI [address], [reference parameters] which are to be 
attached to the message sent (as SOAP headers in the SOAP binding), and 
[metadata], which is anything else of interest.
MAPs are analogous to the usual email headers such as from: to: reply-to: 
message-id: and in-reply-to: and, as the name suggests, are properties of 
the message.  There is also an [action] MAP defined analogous to the 
SOAPAction HTTP header.
As should be clear, a MAP is not the same as a MEP.  The names are 
confusing, but (one hopes) which one is meant should also generally be 
clear from context.
Received on Thursday, 1 December 2005 20:18:44 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:10 UTC