RE: [regrep] ebXML Registry and Workflow

["Peter Kacandes" <pkacande@adobe.com>]

Hi Joe,

Well, I'm here at the ACORD standards meeting this week and that is the kind
of stuff that they are building into their requirements documents.

Meeting Minutes of JAG (Joint Architecture Group) Framework Team
Teleconference June 11 2003

Target Plan Topics
Messaging - SOAP w/attachments, ebXML

ACORD Emerge Message Exchange Functional Requirements page 3:

Originator to Repository:
- push to repository; this may be complemented by notification to potential
recipients of documents being added, with referencing and/or keyword
information

Receipient from Repository:
-pull from repository; this may include search mechanisms by which the
attachment is rerieved after several interactions.

These guys are seriously considering adopting messaging and CPP/A. We've got
a great opportunity to show them how the registry fits into that.

cheers

pk


-----Original Message-----
From: Chiusano Joseph [mailto:chiusano_joseph@bah.com]
Sent: Wednesday, June 25, 2003 6:53 AM
To: regrep@lists.oasis-open.org
Subject: [regrep] ebXML Registry and Workflow


[I've got my marketing hat on again]

It seems to me that there is a high synergy between ebXML Registry and
workflow, from the perspectives of:

- Registering/maintaining workflow definitions (UML, BPEL4WS, WSCI
scripts, etc.) in an ebXML Registry

- Associating a CPA with a workflow definition

- Potentially constructing XML-based workflow definitions (such as
BPEL4WS and WSCI) from vendor tools that access ebXML Registry for the
workflow definitions schemas

...and probably several more. Does anyone else see this? If so, should
we promote this aspect further?

Joe