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: Requirements and defintions documents

There were errors when I sent this Thursday and it bounced.
Didn't see this until after checking out of the hotel, so 
you won't get this until after the deadline.

Hi all,

These are a few comments on the definitions document.

First a general comment.  These definitions are not object oriented.
Not that this is bad, but if ebXML wishes to deal with objects and 
componemts, as my short time with the Architecture WG indicated they 
wanted to do, we may requrie object oriented definitions, too.  We 
really need to find out what the general ebXML approach is/will be.
Perhaps we should contact the Architecture WG?

Clause 1.1
Is a wrapper itself a documnt?  thus, making the definition fully 

Clause 1.2
I would suggest revising the first sentence to read:
A Document is any collection of data elements that can ... .

Clause 1.2.2
Rather than saying "a message is data", it might be better to say "a 
message is a document" (which I think is true).

Clause 1.3.4
Since a Service includes the exchange and processing of a 
(set of) document(s), I believe we want to add an item to the list 
of dependencies which would characterize a two-phase commit transaction, 
i.e., either completes successfully or rolls-back (never an error state), 
which is semantics for once-and-once-only.  Not sure what to call it.
Suggestions?  (In the OLTP world, it is generally referred to as a 
transaction, but that term has already been taken to mean something 
else in the EDI and XML world).

Best reqards,
At 04:53 PM 01/11/2000 -0800, David Burdett wrote:
>I attach updated versions of the requirements and defintions documents. You
>will find quite a few changes since I received quite a lot of feedback. Some
>of the suggestions came in emails sent privately to me so not everyone will
>be able to trace the original unless those individuals to whom I've posted a
>reply want to forward my reply to the list.
>There are three pdf files:
>*      Version 5 of the requirements (with changes highlighted)
> <<ebXML Transport Requirements 5.pdf>> 
>*      the same as the previous item but with no changes highlighted - this
>is much easier to read
> <<ebXML Transport Requirements 5 without changes highlighted.pdf>> 
>*      and the ebXML Transport definitions document that is unchanged but
>I'm including in case someone new to the list hasn't seen it yet.
> <<ebXML Transport Definitions 1.pdf>> 
>We really need to tie these down and, after discussion with Rik, he's
>suggesting that we finally freeze the requirements document by 5PM PST this
>Advanced Technology, CommerceOne
>1600 Riviera Ave, Suite 200, Walnut Creek, CA 94596, USA
>Tel: +1 (925) 941 4422 or +1 (650) 623 2888; 
>mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com

[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