ebxml-core message


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

 


Help: OASIS Mailing Lists Help | MarkMail Help
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]

Subject: Re: Syntax Free Models


This brings up another question

Who is the customer

private and perhaps buying over the web

or

commercial with a formal process of RFQ's

In your sample flexibility may be required to remove steps
welcome to shop
select payment method
place priced product for delivery in 24hrs into shopping basket.
confirm list of products for delivery
"thank's for shopping xyz"
Bob keeps speaking about flexability - it is a key issue to be considered by
all

regards
Doug Tozer
Digerati Pty Ltd
Australia
Telephone 61 3 9859 5800
http://www.digerati.com.au
----- Original Message -----
From: "Martin Bryan" <mtbryan@sgml.u-net.com>
To: "Bob Haugen" <linkage@interaccess.com>;
<ebxml-core@lists.oasis-open.org>
Sent: Monday, February 14, 2000 7:52 PM
Subject: Re: Syntax Free Models


> Bob
>
> > Fully understood.  Here is an article that may be useful,
> > discussing different methods for presenting interactions,
> > ending up recommending a simplified form of Dooley graphs:
> > http://www.erim.org/~van/dooley.pdf
>
> I prefer the tabular form used in Table 4 to the more visually oriented
> version (but then I'm a text man, not an artist!)
>
> I like the REQUEST > COMMIT/REFUSE part of the sequence but feel that the
> SHIP > PAY model is too weak for a general model of business transactions.
>
> > No guarantee that anything there is better, but I do find
> > the linear sequence confusing.  Maybe it will be good
> > for stimulating ideas...
>
> The alternative is the directroy representation, but this is more space
> consuming:
>
>       Order
>           |_______Acknowledgement
>                   |___Despatch Advice
>                                      |____Receipt
>                                                        |______Invoice
>                                                                |___Tax
> Statement
>
> |____Payment
>
>
> >
> > >In most cases
> > >the best thing to do with interactive processes is to "build" a single
> > >message as a set of subprocesses. A good example of how this can be
done
> is
> > >illustrated by OTP.
> >
> > For example? (In other words, I might have a vague idea of what you
mean,
> > or might have missed the point altogether.)
>
> Select item for shopping trolley
>      |__ Provide quote
>               |____Accept quote
>                         |____Offer delivery method
>                                     |___Accept delivery method
>                                             |___Offer payment method
>                                                      |___Accept payment
> method
>
> Martin
>
>
>



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC