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
 


Issue 23
Naming

Resolution: Change the names to more intuitive values.

Keith Swenson CT0009 We originally used this obnoxious identifier to remain consistent with the WebDAV protocol,

which SWAP seems a natural extension of. Since none of the rest of the encoding is consistent

with WebDAV, and SWAP seems to be departing entirely away from precidents set by WebDAV,

then I don’t see any reason to keep this method name. Perhaps something more like “GetData” or

quite possibly just the well defined “GET” method, would be easier on the eyes.

Rainer Weber CT0041 This is again a more formal issue. The names could be more intuitive sometimes. E.g. in Example 7 I

would change: ContextDataInfo -> InputDataType ContextData -> InputData (or

InputDataValue) ResultDataInfo -> OutputDataType ResultData -> OutputData (or

OutputDataValue)

Edna Murby CT0079 2.2--Page 6--Suggested alternatives to the root element name, currently ‘WF_XML” would be

‘Wflow’ or ‘WfMessage’, which is more like the OMG jointFlow documentation in terms of

naming conventions, and it indicates the emphasis on a messaging interface. Proposed

Modification:Propose consider changing the root element name to reflect the jointFlow

specification. Ratioal:Having XML in the root element name is redundant

CSC/JCALS RW0010 GetData is a better option. Coalition members need to come up with a decision.

Issue 24
ProcessDefinition.CreateProcessInstance: parameter

"Name"

Resolution: Leave it out.

Rainer Weber CT0044 Parameter "Name" This seems to be superfluous.

Proposal: Leave it out.

Issue 25
Error Codes

Resolution: Resolution: A proposal has been made recommending a list of MainCode values for exceptions.

MainCodes:Data 100 Series These exceptions deal with incorrect input data, e.g. you need to create a

process instance of a process definition with an unknown ID. WF_INVALID_KEY 100

WF_INVALID_CONTEXT_DATA 101 WF_INVALID_RESULT_DATA 102

MainCode:Authorization 200 Series You may not be authorized to carry out this operation on that

resource, e.g. you may not create a process instance for that process definition; however, you might be

authorized to do this with another process definition. WF_NO_AUTHORIZATION 200

MainCode:Operation 300 Series The input data is syntactically correct, authorization is permitted, but

the operation could not be accomplished, e.g. for some temporary internal error in the workflow engine.

WF_OPERATION_FAILED 300 MainCode:Resource Access 400 Series A valid Key has been used,

however this operation cannot be currently invoked on the specified resource.

WF_NO_ACCESS_TO_RESOURCE 400 WF_SYNTAX_ERROR_IN_PROCESS_DEFINITION 401

WF_INVALID_PROCESS_DEFINITION 402 Main Code:Operation-specific 500 Series These are the

more operation specific exceptions. Typically, they are only used in a few operations, possibly a single

one. WF_INVALID_STATE_TRANSITION 500

WF_INVALID_OBSERVER_FOR_THAT_RESOURCE 501 Main Code:WfMessageHeader-specific

600 Series WF_INVALID_OPERATION_SPECIFICATION 600 WF_INVALID_VERSION 601

WF_PARSING_ERROR 602

Friday, June 09, 2000 Page 10 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