ebxml-transport message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Subject: ebXML Transport, Routing and Packaging V0.98
- From: Martin West <Martin.West@Spirit-Soft.com>
- To: "ebXML Transport (E-mail) (E-mail)" <ebxml-transport@lists.ebxml.org>
- Date: Fri, 09 Mar 2001 22:33:41 +0000
Some quick Firday
night comments ...
Sequence Number in
Conversations:
At around line 575.
My model of
conversations is that they are formed of a series of exchanges. If the exchange
is a message based transmission that can be formed of one or more messages,
then sequence number specification seems flawed. Message sequence numbers are
usually used for reasssembly of a message which has been segmented for what ever
reason. If the message is the exchange then OK, but I think there should be some
clarification.
#wildcard
at around line
358
The spec states that
items may be ignored if mustUnderstand is not true.
Is there a problem
here for the MSH routing scenario described around 750. Not understood items
should be transparently passed on.
regards
Martin West
VP of Research and Development
http://www.spirit-soft.com
Phone:+44(0)20-7464-4030
Mobile:+44(0)7879-680-096
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [Elist Home]
Powered by eList eXpress LLC