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 CT0084 2.2.3--Page 8--The note regarding applications using their own specific elements within

context-specific data areas will require some discussion. It seems to be a requirement to allow user

defined data definitions for context-specific data areas and certainly will be an area of interest to

tooling vendors. It doesn’t seem that the simple name value approach will be sufficient.

Proposed Modification: We would like to propose consideration for providing two methods for

user defined data definitions for context-specific data. The first is the current method of {name,

(value | type)}, and the other by using an entity which can be included and will provide the

capability for user defined data structures.



Please see attachment 2 for discussion. Ratioal for Modification: Retain the simple

{name+(value|type)} method for defining data, and extend the item tag to include a method for user

defined data definition.

Issue 11
Valid States

Resolution: Version 1.0 of the specification contains a list of valid states agreed upon by the coalition. The

specification describes several levels of granularity of these states, and the requirements for supporting

these states for conformance.

Michael Rossi CT0120 This issue has no associated comments.

Issue 12
Observers

Resolution: The WF-XML doc should section 2.1, paragraph 5 should be made to include the following: “The

Observer interface provides a means by which a process instance may communicate its completion. In

nested subprocesses, there must be a way for a requestor of a service enactment to determine or be informed

when a subprocess completes. Any resource wishing to be informed must register by giving the process

instance an identifier (e.g. URL). The process instance then will inform that resource of any status

changes by using the Observer interface. Any number of resources may register themselves as observers

Keith Swenson CT0002 This paragraph mentions informed when a subprocess completes. The Observer interface will

provide this information by giving a process instance the resource identifier of the requestor. The

observer interface receives this information, not provides. This could be worded more clearly. Here

is how I would put it: Keith Swenson SWAP Update Page 2 of 6 SWAP Update.doc June 12,

1999 Page 2 of 6 The Observer interface provides a means by which a process instance may

communicate its completion. In nested subprocesses, there must be a way for a requestor of a

service enactment to determine or be informed when a subprocess completes. Any resource

wishing to be informed must register by giving the process instance an identifier (e.g. URL). The

process instance then will inform that resource of any status changes by using the Observer

interface. Any number of resources may register themselves as observers of a process instance.

CSC/JCALS RW0003 Agree. Should incorporate in the specification.

Issue 13
Case Sensitive

Resolution: All XML ideftifiers should be made mixed case where initial letters of words are capitalized, even if they

are in the middle of an identifier. Underscores should not be used.

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