[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw minutes 15th may 08
Martin C: will be a couple of minutes late Sanjay: Agenda: Sanjay: Agenda: 1. Roll Call http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php 2. Appointment of scribe Scribe list attached below 3. Agenda bashing 4. Approval of may 8, 2008 minutes http://lists.oasis-open.org/archives/sca-bpel/200805/msg00007.html 5. Action items review http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php a) AI #0021 Chairs - to follow up with Mary to post the CD docs to OASIS repository b) AI #0035 (Due date 5/ Dieter - Create a proposal for Issue 16 - Ambiguous Service Resolution c) AI #0037 Anish - update the assembly RDDL file, file names and the references in the spec d) AI #0039 Anish - Provide an amendment to Danny's proposal to resolve issue 20. 6. New Issues NONE 7. Status of JIRA Update from issues editor 8. Issue Discussion a) Issue 20 http://www.osoa.org/jira/browse/BPEL-20 SCA-BPEL spec can not require bpel:mustUnderstand to be true (proposal in JIRA) b) Issue 15 http://www.osoa.org/jira/browse/BPEL-15 TITLE- Define Conformance Targets SUBMITTED BY- Martin Chapman http://lists.oasis-open.org/archives/sca-bpel/200803/msg00000.html http://lists.oasis-open.org/archives/sca-bpel/200803/msg00014.html http://lists.oasis-open.org/archives/sca-bpel/200803/msg00048.html http://lists.oasis-open.org/archives/sca-bpel/200804/msg00001.html http://lists.oasis-open.org/archives/sca-bpel/200804/msg00021.html Review of section 2.1 from CD-01-rev3 at http://lists.oasis-open.org/archives/sca-bpel/200804/msg00026.html c) Issue 18 http://www.osoa.org/jira/browse/BPEL-18 TITLE- Need to rewrite the SCA-BPEL specifications with RFC-2119 keywords/statements SUBMITTED BY- KHANDERAO KAND d) Issue 16 http://osoa.org/jira/browse/BPEL-16 TITLE- Ambigous Service Resolution SUBMITTED BY- Dieter Koenig 9. AOB Room information was updated by: Sanjay Dial-in: 1-888-967-2253 +1-650-607-2253 +61-2-8817-6100 +44-118-924-9000 Meeting ID: 877770 Meeting password: SCABPEL (7222735) Web-conf: http://webconf.soaphub.org/conf/room/sca-bpel-TC Acrobat connect room URL: http://my.adobe.acrobat.com/scabpel/ anonymous morphed into anish Mike Edwards: your line is very noisy Martin Martin C morphed into Scribe Scribe: Topic: Agenda Scribe: no additions. Approved Scribe: topic: minutes Scribe: Approval of may 8, 2008 minutes http://lists.oasis-open.org/archives/sca-bpel/200805/msg00007.html Scribe: no comments and no objections to approving Scribe: Topic: action items Scribe: a) AI #0021 Chairs - to follow up with Mary to post the CD docs to OASIS repository anonymous morphed into Najeeb Andrabi Scribe: Ongoing Scribe: b) AI #0035 (Due date 5/ Dieter - Create a proposal for Issue 16 - Ambiguous Service Resolution Scribe: extended complietion date to may 29. Ongoing Scribe: c) AI #0037 Anish - update the assembly RDDL file, file names and the references in the spec Scribe: Need to touch base with Ivana on the RDDL file Scribe: s/RDDL/BPEL RDDL/ Scribe: Done Scribe: d) AI #0039 Anish - Provide an amendment to Danny's proposal to resolve issue 20. Scribe: Done Scribe: Topic: new issues Scribe: No new issues recieved Scribe: Topic: Status of JIRA Scribe: is up to date withcurrent status. Scribe: Anish: need to upload a snapshot to the TC pages Scribe: Mike R will do Scribe: Topic: issues discussion Scribe: Issue 20 http://www.osoa.org/jira/browse/BPEL-20 SCA-BPEL spec can not require bpel:mustUnderstand to be true (proposal in JIRA) anish: amendment: http://lists.oasis-open.org/archives/sca-bpel/200805/msg00016.html Danny: Sanjay - can you mark me present, please. Sanjay1: yes Danny Scribe: Martin: does the extension need a name? Danny: not accoriding to ws-bpel syntax Anish moves to accept proposal in msg00016.html to resolve issue 20. Danny 2nds Scribe: No objcections to unanimous consent, motion passes. Scribe: Issue 20 can be moved to resolved state Scribe: Issue 15 http://www.osoa.org/jira/browse/BPEL-15 TITLE- Define Conformance Targets SUBMITTED BY- Martin Chapman http://lists.oasis-open.org/archives/sca-bpel/200803/msg00000.html http://lists.oasis-open.org/archives/sca-bpel/200803/msg00014.html http://lists.oasis-open.org/archives/sca-bpel/200803/msg00048.html http://lists.oasis-open.org/archives/sca-bpel/200804/msg00001.html http://lists.oasis-open.org/archives/sca-bpel/200804/msg00021.html Review of section 2.1 from CD-01-rev3 at http://lists.oasis-open.org/archives/sca-bpel/200804/msg00026.html anish: issue 18 http://lists.oasis-open.org/archives/sca-bpel/200804/msg00026.html Scribe: Mike R: walk thru of section 2.1 update proposal Danny: ". A simple static analysis of the control flow, which does not involve determining the values of any expressions, is used to determine which role can send the first message." Scribe: thanks Scribe: Sanjay: has been a dicussion on static analysis so may need to raise a separate issue. anish: i don't like 'component type generetor' and 'component' as the conformance targets anish: s/generetor/generator/ anish: the targets we should have are specific files or runtime anish: i don't know what i can do with a 'component type generator' target Scribe: well we can talk about elements being targets i.e. portions of documents anish: sure, but the target is still the composite Danny: I disagree. Otherwise we get all kinds of passive syntax anish: this is/was done in WS-I, and the syntax was not bad Scribe: Danny: need a discussion about static ananlysis and whether its an issue Scribe: Martin> Component Type generator is not a traget we should be talking about Scribe: Martin: its not something we wish to attach conformance requiremenst to Scribe: Anish: hard to see attaching tests to a component type generator. prefer talking about the sca runtime Scribe: Mike E: sympathize with not liking the component type generator. anish: how about 'the RUNTIME MUST generate the component type that ...' Scribe: there is a notial/virtual data structure being produced and we can talk about production rules without talking about generators Scribe: Mike R: didnt seem appropriate for an artifact nor a run-time Dieter Koenig: how about "a component type referencing this process MUST contain an SCA service ..."? Mike Edwards: "the introspected component type MUST...." Scribe: Mike R: sca runtime is too late in the process in this case Scribe: Anish: suggested sca runtime could do this Scribe: Anish: hard to mandate when checks are made or virtual data structure is created Scribe: Mike R: does the compontent type generator imply any time in the process Scribe: Anish: no but implying targeting a particular part of the run-time which is hard to isolate Scribe: Dieter: focus on the artifacts and the rules between them, and not fucuss of runtimes and generators Scribe: Martin C: +1 to Dieter Scribe: Sanjay: component type generator may be good for ease of writting but may give wrong impression for how to implement Scribe: Sanjay: with the virtual artifact it doesnt actually exist, however it shoudl be testable somehow Scribe: Mike E: it is still prefectly testable as you can depend on certain values being present. This is valid for any technology that does introspection and is not just specific to BPEL Scribe: Mike R: something should be claiming to pass a test Scribe: Mike R: cant have a non existing artifact to test Scribe: Mike R: doesnt imply any point in time the generator must execute anish: mikeR, what did you think of my suggestion in the chat? Scribe: Martin C: generator is too virtual Scribe: Mike E: how is a generator more testable than a virtual file Scribe: Mike R: entities at any point in time can claim to be a generator Scribe: Mike E: not real enough Scribe: Anish: can we substitute runtime for generator Scribe: Mike R: would prefer the runtime approach to Mike E and Dieter's approach Dieter Koenig: i can write a component type with notepad - what is the runtime in this case? Scribe: Sanjay: who do we make happy talking about genererors Scribe: dos? anish: dieter, that is a sidefile, i assume, in which case it is a valid target anish: any such file has to be merged with things like annotations, extensions anish: which would generate a virtual CT anish: so, RUNTIME is a target, SCDL is a target, CT side file is a target, BPEL process is a target Scribe: Motions to adopt: http://lists.oasis-open.org/archives/sca-bpel/200803/msg00000.html Scribe: Ran out of time so motion dies Scribe: Aob: stragler roll call anish i pasted those link in there, martin anish just been a while Scribe
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]