Choreography component meeting agenda (27th July):

1. Actions from last meeting:
	- Antony will write an example BPEL file which demonstrates test data aggregation and data collection
	- (Postponed pending discussions) Antony will add engine output support to the public APIs
	- Example files should be imported via the standard mechanism - same as the TPTP log import

2. Recent relevant project proposals
	- ALF
		gist of project is that it acts as an event based interoperation layer between 
		apps at different stages in lifecycle, plans to use BPEL for the events etc
		
	- JWT
	- BPEL-Designer
		choreography UIs that we can pick up, tending towards BPEL designer but may become
		a single project or share code anyway

3. Deployment
	- Basic deployment added, covers first host & even spread
	- Other required deployment strategies?
		Suggest host weighted deployment strategy to specify particular hosts
		mention firewall issue
		demonstrate what the string would look like
		

4. createInstance attribute
	- requirement for tight specification implementation
		Is is necessary - this will be gated by what the UIs we pick up can manage
		If we want other BPEL engines to run it then we MUST deal with it.
		
5. adoption roadmap
		asked Harm to clarify requirement
		go through general roadmap so far

Attending:
	Antony Miguel (Scapa)


Apologies:


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


Point 1 discussion:


Point 2 discussion:


Point 3 discussion:


Other discussion:

(zero attendance - meeting cancelled)

Actions:
	- Antony will write an example BPEL file which demonstrates test data aggregation and data collection
	- (Postponed pending discussions) Antony will add engine output support to the public APIs
	- Example files should be imported via the standard mechanism - same as the TPTP log import