May wish to consider some real-world, potential instances of use of
multi-hop as discussed in last week's eBES ebXML Interoperability Pilot.
Thanks.
-----Original Message-----
From: Matthew MacKenzie [mailto:]
Sent: Sunday, October 20, 2002 11:56 AM
To:
Subject: Re: [ebxml-msg] Multiple Acknowledgment elements with the same
actorURI?
During the face to face, there was discussion of
a) Fixing multi-hop, since there is a perception by vendors that it is
broken or not worthy of implementation.
b) Removing multi-hop altogether, and possibly supporting it in the
future via our new modular MessageHeader if BPSS/CPPA indicate that we
need to provide this functionality.
We should add a note to the applicable requirement pointing to this
email so that if (b) is followed, we can make sure the schema/spec
restricts the acknowledgment element.
-Matt
On Saturday, October 19, 2002, at 10:33 AM, Christopher B Ferris wrote:
Dave, it isn't a bulk acknowledgment message, this is to accomodate
the potential need to have both a point-to-point and and-to-end
acknowledgment carried in the header of the same message.
I believe that you'll find the rules for this quite well defined and
constrained
in the normative prose of the spec.
Cheers,
Christopher Ferris
Architect, Emerging e-business Industry Architecture
email:
phone: +1 508 234 3624
<image.tiff>
Hi all,
Would anybody be able to confirm that it is the intention of the MSS 2.0
specification to allow multiple Acknowlegdment elements with the same
actor URI on a single ebXML message? (something of a 'bulk
acknowledgment' message).
The schema allows it, the 'interaction' rules allow it, although the
spec wording always refers to Acknowledgment elements in a singular
sense when discussing inclusion in a message.
Thanks and Best Regards,
Dave Elliot
XML Global Technologies
----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>
