OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-msg message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [ebxml-msg] Groups - AS4-Profile-wd-22.odt uploaded


Pim : inline.

 

From: ebxml-msg@lists.oasis-open.org [mailto:ebxml-msg@lists.oasis-open.org] On Behalf Of Pim van der Eijk
Sent: Wednesday, January 25, 2012 10:16 AM
To: ebxml-msg@lists.oasis-open.org
Subject: RE: [ebxml-msg] Groups - AS4-Profile-wd-22.odt uploaded

 

 

Some comments:

 

Section 2.2 introduction,  "It is not required and often not even possible",  is the word "often" correct? It looks like this is never possible.

 

<JD> never possible only if the two MSH are strictly conforming to Light Client. But an MSH can support more than Light Client and be able to get incoming requests.

 

Section 2.2.1 and 2.2.1,  would it be possible to explicitly allow for Two Way MEPs,  provided they are not synchronous ?   We discussed this a few times before.  The only requirement is for an MSH to allow a submitting application to set a RefToMessageId.     It would increase the range of applicability of AS4 to include SOA-style exchanges rather than just document exchanges.

 

Section 3.5,  perhaps clarify that this also supports situations where there message does not contain an explicit @mpc value.  In that case, the PullRequest is the concatenatation of the default MPC value (defined in the ebMS3 specification), a separator and the subMPCext.   By the way,  in theory MPC values can be URNs, so the separator varies depending on whether the MPC is a URL or URN.  We might also require the separator to part of the subMPCext.

<JD> Well, trying to make this not too complex we could decide that there are a few accepted separators (“/”,”-“,”.”…), and if the extension subMPCext does NOT start with any of these then the MSH will insert the default one “/”. As for default MPC, not sure that would help much, the PullRequest still has to provide the full MPC text. But we could indeed cover that case.

 

Section 6.3 "support [..] are required" --> "support [..] is required".

<JD> OK

 

Pim

 

 

 

 

 

 


From: ebxml-msg@lists.oasis-open.org [mailto:ebxml-msg@lists.oasis-open.org] On Behalf Of Jacques Durand
Sent: 23 January 2012 07:18
To: ebxml-msg@lists.oasis-open.org
Subject: [ebxml-msg] Groups - AS4-Profile-wd-22.odt uploaded

Submitter's message
AS4 profile (source) update based on meeting review Jan 18. (see diffs)
-- Mr Jacques Durand

Document Name: AS4-Profile-wd-22.odt


Description
AS4 profile (source) update based on meeting review Jan 18. (see diffs)
Download Latest Revision
Public Download Link


Submitter: Mr Jacques Durand
Group: OASIS ebXML Messaging Services TC
Folder: documents
Date submitted: 2012-01-22 22:17:35
Revision: 15

 



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]