RE: Collaboration Services (was: Business Service Interface)

[Krishna Sankar <ksankar@cisco.com>]

Collaborating Business sub-processes or Collaborating business
activities/tasks

-----Original Message-----
From: Welsh, David [mailto:David.Welsh@nordstrom.com]
Sent: Sunday, October 22, 2000 5:26 PM
To: 'Bob Haugen'; 'Welsh, David'
Cc: 'ebXML-BP@llists.ebxml.org'; ebxml-tp@lists.ebxml.org
Subject: RE: Collaboration Services (was: Business Service Interface)


Would you care to help me replace "collaborating workflows" with some other
phrase. I do admit 'workflow' is very general term, especially when you've
seen half a dozen vendors claim to have workflow and all implementations are
different.
I think the phrase needs to be something simple to understand / not too
technical, yet something for the person in the street that triggers a 'Very
cool !' response.

Dave



-----Original Message-----
From: Bob Haugen [mailto:linkage@interaccess.com]
Sent: Sunday, October 22, 2000 5:02 PM
To: 'Welsh, David'
Cc: 'ebXML-BP@llists.ebxml.org'; ebxml-tp@lists.ebxml.org
Subject: RE: Collaboration Services (was: Business Service Interface)


<David Welsh>
So ... in simple terms ...
we should have "collaborating workflows" representing (core) business
processes (expressed in XML and made from core components) hosted in the
Registry/Repository and normally 'qualified thru some standard methods' when
a trading part??? (with all respect to party or partner) agreement is
automatically negotiatied ?
</David Welsh>

Very cool!  I like it! (except for the term "workflow", but I suppose
that depends on what is meant.)

Thanks for condensing,
Bob Haugen