Minutes
<Mike Edwards>
I'm on the call...
Simon checking his status in the TC
confirmed - Simon is Voting Member
Agenda bashing
Sanjay:
add on the agenda discussion of issue 14
Approval of Minutes from April 10th
AI #0021: still open. The discussion with Mary still in progress
AI #33: Michael R. posted two drafts
New issues
No new issues submitted for discussion
Status of JIRA
Up-to-date except for issue #14. It should be in state "resolved"
Issue #2: On Feb 7th this issue was resolved
Sanjay checking minutes of meeting on Feb 7th
<Sanjay>
Above are minutes of 2/7 meeting on which issue 2 was resolved
Issue #14
Michael R: in revision 2 the attribute is in the BPEL SCA namespace
<Dieter Koenig>
<partnerLink ... sca-bpel:requires="xsd:string" />
open question is whether this attribute should apply to myRole, partnerRole or both?
Michael R.: it is assumed to be on the partnerRole for the service
Dieter:
"requires" attribute could be defined for the role of partnerLinkType
Michael R. suggests to reopen the issue
Michael R: Motion to reopen issue #14
Resolution: issue 14 reopened.
Danny:
why is mustUnderstand "yes" for this attribute?
it is SCA related but there could be BPEL processes that do not use these attributes and run well
<Dr Martin>
response to Mike E: the mustunderstand is addressing the non-sca bpel processor
<Mike Edwards>
I am puzzled on this point - this is something specific to SCA - so is this implying tht IF this is present, you can't use
the process outode pf SCA
<Mike Edwards>
s/outside of SCA
<Dr Martin>
the mustunderstand is a WS-BPEL extension thingy, so signlas to the non-sca bpel engines that the process is no good to them
if they dont understand the extentions
<Mike Edwards>
is that what we want then - a BPEL process with SCA extensions can't be used outside of SCA?
<Dr Martin>
thats what mustunderstand means
<Sanjay>
I think it is on a per usage basis. that is some bpel processes might declare the extension as mustUnderstand and others might
not.
<Mike Edwards>
it would be good to spell out that BPEL processes with SCA extensions can only be used within SCA
<Mike Edwards>
it says that only in an oblique way right now
Disucssion to be continued on the emailing list
Schreiber diagnostics output
[Delete this section before publishing the minutes]
citation-detection-scribed: Line 63: Check for possible unrecognized nick 'AI #0021'
citation-detection-scribed: Line 64: Check for possible unrecognized nick 'AI #33'
citation-detection-scribed: Line 66: Check for possible unrecognized nick 'AI #34'
citation-detection-scribed: Line 67: Check for possible unrecognized nick 'AI #35'
citation-detection-scribed: Line 73: Check for possible unrecognized nick 'Issue #2'
citation-detection-scribed: Line 83: Check for possible unrecognized nick 'Michael R'
citation-detection-scribed: Line 87: Check for possible unrecognized nick 'Michael R.'
citation-detection-scribed: Line 90: Check for possible unrecognized nick 'Michael R'
statistics: Schreiber found 96 input lines
edits: Schreiber found no text-edit commands
command-scribe: Line 5: Ivana Trickovic recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 21: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 29: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 32: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 40: Check for possible unrecognized nick 'a) Issue 15 http'
citation-detection-irc1: Line 42: Check for possible unrecognized nick 'SUBMITTED BY'
citation-detection-irc1: Line 44: Check for possible unrecognized nick 'b) Issue 18 http'
citation-detection-irc1: Line 46: Check for possible unrecognized nick 'SUBMITTED BY'
citation-detection-irc1: Line 48: Check for possible unrecognized nick 'c) Issue 16 http'
citation-detection-irc1: Line 50: Check for possible unrecognized nick 'SUBMITTED BY'
system: Transformer: SAXON 9.0.0.2
[End of Schreiber diagnostic output]