ebxml-msg-as4 message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Comments on draft 0.9
- From: "Durand, Jacques R." <JDurand@us.fujitsu.com>
- To: <ebxml-msg-as4@lists.oasis-open.org>
- Date: Tue, 30 Dec 2008 11:06:13 -0800
Summary of early
comments made during 12/21 AS4 meeting, about the latest profile draft (V0.9)
uploaded 12/19:
- Replacement of
"Deployment profile" by "Usage profile" was done partially: need be done in
Intro section as well.
- section 4.1.1 need
be more concise at best: no need for a separate table for each
module.
- about bundling of
Receipts not supported: better to require that the user message Sender be able
(SHOULD) to handle the bundling of a received Receipt with another message, in
particular the combination of a PulRequest + Receipt of previously pulled
message.
(even if a Receiver
MSH - the one doing pulling - is not required to support this
bundling)
- may need a
definition / terminology section, e.g. to define:
. delivery
awareness
. synchronous /
asynchronous transport
. notion of receipt
(and make a parallel with AS2 MDN)
- question about
AS4-specific error code still unanswered: see 4.2.2 (usage profiling
"d")
- in 4.2.3, usage
profiling "b" needs a new PMode parameter.
- in 4.2.6: do we
need new PMode parameters to cover these? First of all: if these options are for
the user to decide, then OK to leave them in this section. But if there are AS4
rules here that all users must comply with, should move to
4.1.
- the format of
tables in 4.2.7, 4.2.8, 4.2.9 should be aligned with previous tables (i.e. the
"question / option" should be in column 2, not 1)
-
others?
Jacques
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]