W3C home > Mailing lists > Public > xml-dist-app@w3.org > March 2000

Re: XTech 2000 XML protocol BOF notes

From: Eric Prud'hommeaux <eric@w3.org>
Date: Thu, 23 Mar 2000 15:36:08 -0500
To: Larry Masinter <LM@att.com>
Cc: xml-dist-app@w3.org
Message-ID: <20000323153608.C13432@w3.org>
On Mon, Mar 20, 2000 at 06:03:54PM -0800, Larry Masinter wrote:
> Given the larger problem statements in the BOF, I think it is worthwhile
> for people to look at SWAP (Simple Workflow something Protocol) and also the
> WfMC
> spec (www.wfmc.org) as a source of additional design insights and
> problem definition.

FoRK has an EDI thread that touches on SWAP and WfMC. Go to
http://www.xent.com/FoRK-archive/may98/ and look for "EDI and XML".

If we start modeling XML protocols as a series of layers
we can take a diverse set of requirements, categorize them, and parcel
them out to smaller groups. This will allow greater parallel
development and allow more rapid development of a core which would
unify most of the functionality of XML-RPC [http://www.xmlrpc.com/]
and SOAP [http://www.msdn.microsoft.com/xml/general/soapspec-v1.asp].

I am now looking for a way to express the categories and inter-layer
dependencies in a clear way. For example, from the picture in the
Viewpoints document:

Authentication (digital signatures)
  stacks on: core
   provides: some auth API

Procedure Invocation
  stacks on: core
   provides: RPC

Transaction Management
  stacks on: RPC
   provides: some ACID API

Object Interface
  stacks on: RPC
   provides: object API

Object Persistence
  stacks on: object API
   provides: object API
   comments: may need Transaction Management and 
             distributed garbage collection

What is the relationship between worlflow layers? What are their
dependencies? Anybody? Bueler?


Received on Thursday, 23 March 2000 15:36:08 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 22:01:09 UTC