RE: ebxml trp mhs spec and workflow

[Stefano POGLIANI <stefano.pogliani@sun.com>]

I do not think it belongs to Ph 2 or ph 3.
We may postpone the issue to ph 2 / ph 3 because of contingent 
problems but the issue is not, IMHO, a second-level need. 

As soon as you try to model some BP which is a little bit more 
complex than "send me the money that I send you the goods", the 
Workflow issue comes along...

My 2 cents
/Stefano
 
> > -----Original Message-----
> > From: Rik Drummond [mailto:rvd2@worldnet.att.net]
> > Sent: Tuesday, October 31, 2000 6:52 PM
> > Cc: ebXML-transport@lists.ebxml.org
> > Subject: RE: ebxml trp mhs spec and workflow
> > 
> > 
> > no, i don't think it belongs somewhere else completely. however it is
> > clearly phase ii or phase iii. the mhs will have to support it 
> which will
> > require more headers... so it is probably on of those over lap areas....
> > best regards, rik
> > 
> > -----Original Message-----
> > From: Christopher Ferris [mailto:chris.ferris@east.sun.com]
> > Sent: Tuesday, October 31, 2000 10:47 AM
> > To: Rik Drummond
> > Cc: ebXML-transport@lists.ebxml.org
> > Subject: Re: ebxml trp mhs spec and workflow
> > 
> > 
> > This is something which in truth belongs not in TR&P
> > but in TP/BP. Stefano Pogliani of Sun is very interested
> > and knowledgable in this domain and is exploring how
> > this might map to ebXML.
> > 
> > In truth, this is something which rightly belongs in
> > a phase II of ebXML (IMHO). It is also the domain of
> > a market exchange service provider and could easily
> > be mapped onto ebXML through an intermediary router.
> > 
> > My $0.02,
> > 
> > Chris
> > 
> > Rik Drummond wrote:
> > >
> > > i just spent an hour or more on a conference call with 
> several exchanges
> > > attempting to route data among themselves. they call it 
> > routing, but what
> > > they really need is multi-organizational workflow.  we need to discuss
> > this
> > > next week. who in this group has workflow experience? best 
> regards, rik
> > 
> >