Choreography component meeting agenda (1st June):

1. Actions from last meeting:
	- Koustubh will continue to track BPEL TC progress on issue 147 etc.
	- Antony will write an example BPEL file which demonstrates test data aggregation and data collection
	- Antony will write an example BPEL file which demonstrates Eclipse Workbench interaction (e.g. pause a running test)
	- Augustus will take a look at the new beginners tutorial on the choreography documentation page
	- Antony will commit API changes before the next meeting

2. Discuss any recent developments in BPEL TC with regard to specification finalisation and Issue 147.

3. Discuss design of the new public APIs and requirements anyone has on the APIs


Attending:
	Antony Miguel (Scapa)
	Augustus Kalimuthu (CA)
	Diana Vega (Fokus)


Apologies:
	Koustubh Parwar (CA)


Absent:	
	Harm Sluiman (IBM)
	Serge Lucio (IBM)
	Jim Saliba (CA)
	Kent Siefkes (IBM Rational)
	Joe Toomey (IBM Rational)
	George Din (Fokus)
	Scott Schneider (IBM Rational)
	Srinivas P Doddapaneni (Intel)
	George Christelis (Scapa)
	Shobhit Maini (CA)
	Tejas Patel (CA)
	Paul Brown (Fivesight)
	Marc Erickson (IBM)


Point 1 discussion:

	Antony has finished the workbench interaction BPEL example and will try to write the data aggregation example
	for next week.
	
	Augustus' suggests that the beginners tutorial would benefit from an explanation of the different launch
	configuration types (run/profile/debug), and an explanation of the different distributions and main/mini engines
	(what happens if each is selected)


Point 2 discussion:

	Issue 147 on the BPEL list has plenty of activity and resolutions are being proposed and discussed on the 
	BPEL TC mailing lists.  This is a good sign and if all goes well it looks like this issue may well be resolved
	before the BPEL specification is released.
		

Point 3 discussion:

	No one has been able to look at the public APIs in depth for this week - everyone should try to take a look at them
	for next week.


Other discussion:
	CA has no plans to build on APIs
	
	Diana suggested the creation of an extension point to provide example BPEL files to the choreography as the current
	example files are only accessible via CVS.  This seems like a good idea - any new internal extension points should
	be named of the form 'internal_ExtensionPointName' to mark them as non-public APIs.
	
	The group should discuss the design and implementation of the extension points in email.

Actions:
	- Antony will write an example BPEL file which demonstrates test data aggregation and data collection
	- Koustubh will continue to track BPEL TC progress on issue 147 etc.
	- Everyone should take a look at the public APIs and provide any feedback in the next meeting