WfMC Technical Committee Meeting, Oct 11-12, 2007

Agenda

Technical Committee, Chair: Keith Swenson

• Welcome and Introductions
• Anti-trust and intellectual property statement
• Approval of previous minutes
• Addition of any other business to the agenda
• Approval of the agenda

WG1-XPDL (Process Definition Interchange)

• Status Update Briefing (Robert Shapiro)
• XPDL 2.1 Status
• Working Session on Enhancements Identified for XPDL v2.1
• Conformance Criteria
• Demonstration of Interchange Testing

WG4 - Wf-XML (Run-time Interoperability)

• Open Geospacial Consortium situation, status of MOU
• New Proposal for REST oriented Wf-XML (Wf-XML 3.0?)

Work and Activities: Status / Overview / Update

• Industry Architecture & Standards Stack
• Glossary update
• Other standardization initiatives including
• ISO status,
• OMG BPDM status.
• Reference Model update

WG5 meeting (Audit)

• Master list of events & Data Structure
• Status of BPRI
• Future work & AOB

Any other business

• ??

Steering Committee Agenda

I. Steering Committee, Chair: Jon Pyke

• Approval of Minutes of Previous Meeting
• Agenda Discussion
• Introductions
• Officer and Committee Openings
• Update/Action Items on WfMC Talking Points

II. ER Committee, Chair: Ken Mei

• 2008 Meeting Schedule
• XPDL Adoption and Publicity Campaign
• 2007/2008 Awards Programs

III. Executive Director

• Summary of Activities
• New Members and Membership Activity
• New Programs
• Change in Country Chapter Charter

IV. Treasurer?s Report

V. Additional Business

Notes from the meeting

• Meeting called to order 9.30AM, Paris, France

• Objective of the meeting
• Need to come to agreement on what would be on XPDL 2.1
• schedule as follow:
• October 12 : Finalize List of Proposed Changes
• November 15 : Finalize Details for Identified Changes in BPMN 1.1
• December 15 : Draft Specification for Internal Review
• January 15 : Updated Specification For Public Review
• February 20 : Vote on Adoption of Final XPDL 2.1 Specification

• Discussion: XPDL 2.1
• Need to be at least compliant with the core BPMN 1.2
• Matrix available now on diff on XPDL 2.0 and 2.1, Mike Amend and Justin Brunt will continue working on this, and sync up with Robert Shapiro on the final document
• Discussion on 'pixel' definition, Justin to clarify with Robert and the TIBCO team
• Need to add list of test case
• Do not include activity model in 2.1
• Mike Amend suggested moving forward that members would share extended attributes to solicit commonality for possible standard adoption
• Specifying (encoding) icons in the spec: discussions on whether it's worth adding this element, suggested evaluate with respective vendors on their product, defer 'icon' after 2.1
• Activity/event management discussion: Roberto Audi Grivetta went over the questions outlined in the document, Michael zur Muehlen and Keith responded with their thoughts. Keith suggested Roberto used the forum and other member resources to help with implementation of XPDL
• Discussion on queue time and waiting time on run time matrix in the activity duration
• Good idea to have simulation information, but 2.1 may not be the time to do this, need to do a better scoping to make it useful for everyone, parking lot item for the time being
• Run time information will be tabled for 2.1
• Monitor Indicators will also be tabled
• Mike Amend suggested a standardized proposal template for submitting into future specs, Nathaniel suggested putting a time line on XPDL 2.2 for mandate usage of the submission template
• Proposed XPDL 2.2 to be released around Feb 2009
• Proposed scripting to push back after 2.1

• Lunch break

• Antoine Lonjon of MEGA International presented an overview of BPMN 1.2, which is a roll up of BPDM and BPMN, the new BPMN stands for Business Process Metamodel and Notation.

• Resumed XPDL 2.1 discussion
• Process and activity viewer push back post 2.1
• not sure what application drop is, awaiting clarification
• assigning ID to object, likely not a big task, Keith proposed unique ID for every packet, no requirement for global ID, Robert joined in the discussion at this point, agreed with this suggestion plus all previous ones
• Minor addition to lane/pool element
• Robert is a week away from review of the diff matrix, Mike Amend will work with Robert and Justin on consolidating check

• Conformance
• more vendors has uploaded XPDL files
• add contact information (readme) with the XPDL
• we currently have 6 sample processes
• Bruce Silver suggested using the BPMN (the one design with BPEL in mind) to do export/import of XPDL, discussion on how to use that process effectively, since it was designed with system centric only in mind
• Discussion on using a different process for the real-life sample process, for example the one in the OMG repository
• Shank Gadby discussed run time information by calling in the conversation, it was decided that it will be included for 2.1
• Discussed adding separate files for simulation result and so on, instead of inline information to include those type of data, no one argued much about this approach
• for the run time interface, will tabled for working group 5 for consideration

• wf-xml
• oasis tc working group is shut down since the dead line of filing IP was passed
• possibly working with OGC (open geo spacial consortium) on ASAP
• they offer to include ASAP with their big annual demo, would be a good marketing plus for wfmc
• awaiting MOU 'memo of understanding' from OGC to proceed
• people all agree it's a good idea, need resources/volunteer to proceed forward

• Keith move the meeting close for the day at 6.30pm, Michael seconded the motion

Notes for second day

• Human Process Diagram for Issue Voting process
• Process Diagram for Trouble Ticket Process
• Need an acronym for "simulation results file format"
• Discuss scripts again
• Someone needs to map Issue Voting Diagram from spec to XPDL

Conformance Profile #1

• Graphic Infos: there will only one instance of a graphical info for an object.
• When reading an XPDL, the first graphic info encountered will always be used.
• XOR gateways will be "empty" (no cross)
• Beginning gateway of a set of parallel path will have a thin line to indicate the "beginning", and the ending gateway of that set of paths will have a thick line to indicate the "end"
• coordinates are always pixels
• origin is always upper left corner of screen

Steering Committee Notes

• Calendar
• Feb 7-8 2008 - Gartner BPM Summit, Las Vegas, WG Meeting
• Feb 25-27 2008 - Nashville, "BPM Showcase", BPM and Workflow Excellence Awards, WfMC meeting
• March 2008 - Cordys Castle, Dutch BPM Forum, Tutorial of European
• April 21-23, 2008 - Washington DC Transformations and Innovation Conference
• Sept 1-4 - BPM Forum in Milan

• Review of Activities
• At the Orlando BPM Summit we presented a tutorial

• TC