OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-transport message

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

Subject: RE: Manifest inclusion issue

That's my understanding.

-----Original Message-----
From: owner-ebxml-transport@lists.oasis-open.org
[mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of Nicholas
Sent: Thursday, April 13, 2000 4:32 PM
To: ebXML Transport (E-mail)
Subject: Re: Manifest inclusion issue

Just so that I'm on the same page. A <null> payload is *explicitly* denoted
by the absence of  Manifest details - the Manifest itself is present. Agreed


At 04:57 PM 4/13/2000 -0400, Nikola Stojanovic wrote:
>I think that, in both examples, option 2 is the better XML style.
>I agree (not only XML style). In 2. we have consistent relationship by
>and in 1. we have relationship by value/existence (where existence is an
>exception). If I recall correctly, this is in line with Ian's, Chris's and
>others' feelings about mandatory manifest. This might be a design rule for
>the whole ebXML?

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC