Making your e-business work  

Home

Standards
    Conformance
    Reference Model
    Public Documents
    XPDL_2.0
    Wf-XML 2.0



About WfMC

Events

Information and
Publications


Free downloads

Membership Information

Press Room

Excellence Awards

Marvin L Manheim Award

Workflow Handbook
   2001
   2002
   2003

   2004
   2005
   2006 NEW!


Associated sites:
AIIM
WARIA

e-workflow.org

Got a question?
Join our Discussion Forums
 Discussion Forum for Workgroups (WfMC-specific)

Workflow and BPM Research

BPM Community Forum
 


Edna Murby CT0098 Attachment 1.



Here is the list of interface functions which we propose for the core implementation:

ProcessDefinition, ProcessInstance and Observer:



ProcessDefinition: Supporting methods should include CreateProcessInstance, ListInstances,

and Propfind. In the case of Propfind, the method should only be used to get some very elemental

properties such as the description, and not for obtaining the interface definition intformation;

rational is that this is not essential for interoperability and the assumption that participants know

what's available on the other end.



ProcessInstance: Supporting methods should include Propfind, Proppatch, and Terminate. In the

case of Propfind, we propose the method should allow users to query the status of the entity

including the results produced by the entity, not its structure. The method PropPatch will have

some parameters, e.g., ResourceID, which cannot be 'patched', i.e., that are read-only. PropPatch

this should basically allow users to change the status of the entity and to set process relevant

data. Should not include support for methods Subscribe, Unsubscribe and GetHistory.



Observer: Supporting methods should include Propfind, Propatch, Terminate and Complete. For

the method Propfind, we would like to note this is not for information on meta-info like

ResultDataAttributes. The method PropPatch (as generalisation of Terminate and Complete,

optional). Notify should be optional.



The table from appendix A has been highlighted to show the recommended core implementation in

black, and the items which are beyond the scope of the core implementation in italics. Rationale is

defining the scope of specification.



Process

Definition Process

Instance Observer Activity

Observer Work

List Work

Item Entrypoint

PropFind X X X X X X X

PropPatch X X X X

CreateProcess

Instance X X X

ListInstances X X

Terminate

Subscribe

Unsubscribe X

GetHistory X

Complete X X X

Terminated X

Notify X?





Attachment 2. Tbd.

Issue 54
UTF-8

Resolution: See Issue 7.

Edna Murby CT0076.8 2.2--Page 6--Recommend UTF-8 for first release of standard and support for UTF-16.; it doesn’t

seem like a good idea to use ISO-8859-1--Proposed Modification: Propose supporting only

UTF-8 for now, with consideration for UTF-16 if required and remove ISO-8859-1 from text

---Rational:The XML 1.0 recommendation is defined based on the ISO-10646 (unicode) character

set. The only binary representation requirements for conforming parsers is support for UTF-8 and

UTF-16. (UTF-8 and UTF-16 are variable length encodings of the Unicode character set.)

Friday, June 09, 2000 Page 16 of 18
First Previous Next Last
Standards
Published Docs
Standards
Reference Model
Conformance
XPDL support

Wf-XML 2.0
 

Information Services
Info Services
Awards
Books
Workflow Handbook

Membership
How to join
Application
Country Chapters
List of members
Officers
Fellows


NEW!

Workflow Handbook 2006
NOW SHIPPING!



CDROM Companion to the Workflow Handbook 2005

 

horizontal rule

home | membership | standards | info | events | members only

All brand names and product names mentioned in this website are trademarks or service marks of their respective companies. Any omission or misuse should not be regarded as intent to infringe on the property of others. The WfMC recognizes and respects all marks used by companies, manufacturers and developers as a means to distinguish their products. The “WfMC” logo and “Workflow Management Coalition” are service marks of the Workflow Management Coalition. http://www.wfmc.org.

horizontal rule