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] | [Elist Home]

Subject: Re: [ebxml-msg] Multiple Acknowledgment elements with the sameactorURI?


That approach would probably be workable.  We'd also need to nail down the
significance of the RefToMessageId element in the Acknowledgment element.
Is it required if this value always duplicates the MessageData contents?
Should we require an Inconsistent error if MessageData and Acknowledgment
contain different RefToMessageId values, for example?

Small note for Matt: Since the schema we provide is an extension to the SOAP
schema for a message rather than a schema for the overall document, we can't
enforce any rules on the number of appearances of any top level element in
that document.  We can describe how MessageHeader, Manifest, et cetera
should appear at most once and detail when AckRequested or Acknowledgment
may appear twice.  We just can't put these conditions into the schema.


Dave Elliot wrote:

> Hi Christopher,
> On Sat, 2002-10-19 at 10:33, 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.
> Thanks for the clarification, this approach is then consistent with that
> for AckRequested elements which makes sense.
> > I believe that you'll find the rules for this quite well defined and
> > constrained in the normative prose of the spec.
> I'd agree that the rules are well defined for AckRequested elements,
> however the discussion for Acknowledgment elements is much more vague.
> Here's why Section 6.3.2 of MSS 2.0 final left me wondering:
> * It does not make mention of element multiplicity (0, 1, 2);
> * It does not include a discussion (as in AckRequested) of what rules
> apply to an MSH node when adding such elements to a message;
> * It makes no mention of constraints regarding Acknowledgment elements
> on the same message sharing the same Actor URI;
> * Its 'Interaction' section relies upon/references the AckRequested
> 'Interaction' section and thus only indicates that an Acknowledgment
> MshSignal should not include an AckRequested element (doesn't address
> the interaction between Acknowledgment elements themselves).
> I think section 6.3.2 of the spec could be improved by the addition of a
> statement that two Acknowledgment elements on the same message can't
> have the same Actor URI.  Or do you feel that text elsewhere in the
> Acknowlegment element discussion _is_ making this issue clear ??
> 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>

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

Powered by eList eXpress LLC