Oughtn't the harmonization with the Workflow Management Coalition be part of the goals?
christer fernstrom, Xerox Research, France
-----Original Message-----
From: Surendra Reddy [mailto:skreddy@us.oracle.com]
Sent: Saturday, October 03, 1998 6:06 PM
To: swap-wg@netscape.com; ietf-swap@w3.org
Cc: moore@cs.utk.edu; paf@swip.net
Subject: SWAP WG Charter -- Second iteration
Here is the second iteration of SWAP Wg charter. I have removed
IN-SCOPE and NOT IN-SCOPE goals from the charter. Goals document,
which will be published as an informational RFC as first document
, describes goals of this working group. I also made some changes
to the milestones to make it more realistic. It is time for us
to move forward to work the goals document.
Apprciate your comments/suggestions.
Surendra
SWAP -- Simple Workflow Access Protocol Working Group
Chair(s)
* Surendra Reddy (skreddy@us.oracle.com)
Applications Area Director(s):
* Keith Moore <moore+swap@cs.utk.edu>
* Patrik Faltstrom <paf@swip.net>
Area Advisor
* TBD
Mailing List Information
* General Discussion: ietf-swap@w3.org
* To Subscribe: send msg to ietf-swap-request@3.org with "subscribe"
in subject
* Archive:http://lists.w3.org/Archives/Public/ietf-swap/
* Documents: http://www.ics.uci.edu/pub/ietf/swap/
Description of Working Group
There is no standard way to communicate and interoperate across
heterogeneous workflow engines in order to coordinate and execute work
process instances across those workflow engines. Most of the solutions
exist today are vendor specific. This means that Workflow vendors need
to support multiple protocols to enable interoperability between worflow
systems.
The goal of this working group is to develop the goals and requirements for
Workflow systems interoperability.
The further goal is to define an application level Workflow Interoperability
protocol. Workflow interoperability goals document defines the scope of the
protocol.
Deliverables
The final output of this working group is expected to be four documents:
1. A workflow interoperability goals document, which describes the scope
and limitations of the protocol.
2. A requirements document, which describes the high-level functional
requirements for Simple Workflow Access Protocol, including rationale.
3. A scenarios document, a description of how this protocol can be used
effectively.
4. A protocol specification, which describes methods, request bodies, and
response bodies, to implement the Simple Workflow Access Protocol
requirements.
Goals and Milestones
Oct 98 Publish Simple Workflow Access Protocol goals document as Internet
Draft.
Nov 98 Submit revised versions of Requirements, Scenarios and goals documents
as Internet-Drafts.
Feb 99 Submit goals document as an informational RFC
Submit revised protocol specification document as Internet Draft
Jun 99 Issue WG last call for requirements, scenarios and protocol specification
Jul 99 Submit requirements and scenarios documents as informational RFCs
Sep 99 Submit SWAP specification as a proposed standard
Current Internet-Drafts
Requirements for Simple Workflow Access Protocol(http://
www.ietf.org/internet-drafts/draft-sreddy-swap-requirements-01.txt)
SWAP Specification(strawman) ( http://www.ietf.org/internet-drafts/
draft-swenson-swap-prot-00.txt).
No Request For Comments
-----------------------------------------------------------------------------
Surendra K Reddy, Data Server Division, Oracle Corporation
phone: +1(650) 506 5441 . mobile: +1(650) 867 4757 . fax: +1(650) 506 7228
email: skreddy@us.oracle.com . URL: http://www-skreddy.us.oracle.com(Internal)
URL: http://www.skreddy.com(external)
Disclaimer : The statements and opinions expressed here are my own and
do not necessarily represent those of Oracle Corporation.