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 [http://www.w3.org/2000/03/15-XML-protocol-Viewpoints.html#proposedRequirements], 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? -- -eric (eric@w3.org)Received on Thursday, 23 March 2000 15:36:08 GMT
This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 27 October 2009 08:41:39 GMT