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
- From: "Pim van der Eijk" <pvde@sonnenglanz.net>
- To: <ebxml-msg@lists.oasis-open.org>
- Date: Wed, 25 Jan 2012 19:15:53 +0100
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.
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.
Section 6.3 "support [..] are required" --> "support [..]
is required".
Pim
Submitter's message
AS4 profile (source) update based on
meeting review Jan 18. (see diffs)
-- Mr Jacques Durand
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]