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 5
Appendix C

Resolution: An HTTP binding has been specified and accepted. This binding uses the HTTP POST method. The

HTTP binding appears in section 6.1 of the Wf-XML version 1.0 specification. If modifications to this

binding are required, they will be made in a subsequent version of the specification.

Rainer Weber CT0040 Which http-method is use? Get?

Proposal: Clarify

David CT0074 I agree with other comments that HTTP is a key one and must be specified.

Issue 7
XML Character Encoding

Resolution: UTF-8 and UTF-16 are supported.

Michael Rossi CT0119 This issue has no associated comments.

Issue 8
Observer Interface

Resolution: In the 1.0 version of the specification, Interfaces have been more clearly defined as a logical construct

only. As opposed to Interfaces and Methods, the 1.0 version simply defines "Operations". The only

Operation currently defined that is logically a part of the Observer Interface is

Edna Murby CT0076.7 2.1--Page 6--5th paragraph, sentence 3. The Observer interface as described is inconsistent with

jointFlow--Proposed Modification: (a) Do we want Observer (jointFlow WfRequester) as a part

of the core implementation? (b) If we wish to include Observer, then to maintain consistency

with jointFlow we should remove the sentence "Any number of other resources may also register

themselves as observers of a process instance and will also be informed when the instance

Issue 9
Context-specific data.

Resolution: Version 1.0 of the Wf-XML specification contains a detailed explanation of the issues around

context-specific data. After much debate on the Working Group 4 mailing list, it was determined that the

WfMC could not specify a content model for this data without restricting implementations to a fixed

approach for processing it. Context-specific data areas are, therefore, completely user-defined. Several

examples are given to illustrate the different ways this data may be modelled.

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