Minutes
Resolution: June 19, 2008 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00003.html approved
Resolution: June 26, 2008 minutes located at http://lists.oasis-open.org/archives/sca-bpel/200806/msg00008.html approved
AI review
a) AI #0021
Chairs - to follow up with Mary to post the CD docs to OASIS repository.
<Mike Edwards>
she has had the Assembly CD-01 for nearly 5 months
Mary's task list is full. No ETA from Mary. AI pending.
Updated on AI b) AI #0042
Editors to incorporate all issue resolutions by 10 july 2008: Pending
Dieter won't be able regularly with the proposed time.
No supporter to change the time.
Action: To Anish/chair to get back SCA-J TC to informour inability to swap the times
Discussions on new issues:
Dieter:
It is a typo. Easily fixable and can be treated as an
Action Item as against a new issue.
Action: Dieter to fix all the typos/errors in SCA BPEL XML schema
Other aspect is inconsistency of name space prefix . Dieter
ready to volunteer to fix.
Status of spec - Update from the editors
Najib informed that he is done with his changes.
Martin moved a motion to cancel the next call on Jul 17th 2008. Second: Danny
No discussion. No Objections. Motion passed unanimously
Resolution: Jul 17, 2008 call is canceled
Action: Editors to updates specs(Agenda 9) by Jul 23rd 2008call.
Discussions on LOAs in August.
Action: To all: Email your availabilities in the month of Aug. to Anish
issue 17
Discussion on Agenda item 10. Issue 17
http://www.osoa.org/jira/browse/BPEL-17TITLE - Allow Component Type side file to override defaults for
service/reference
This issue was waiting on Assembly-52, which was recently closed with no
action.
There is a proposal to resolve this issue in JIRA.
<Mike Edwards>
helpful people, these Assembly folks
Assembly-52 was closed by the SCA Assembly TC with no action
<Mike Edwards>
why wasn't the name constructed using the Scope name?
<Mike Edwards>
ah - scratch that comment of mine
MikeR updates On the SCA-BPEL TC call of 2008-02-28 we
resolved that the following text will be used as the resolution of this
issue, if the SCA Assembly specification adopts the @implementationRef
attribute that has been proposed:
The @implementationRef attribute MUST contain a valid XPath 1.0
expression, which when executed on a BPEL process returns exactly one
<partnerLink> element. The partnerLink thus identified will be
considered to correspond to the service or reference that contained the
@implementationRef attribute. If a service or reference does not have an
@implementationRef attribute, then it will act as if it had
@implementationRef=//partnerLink[@name=$name], where $name is the value
of the @name attribute of that service or reference.
MikeR:
Open question : whether to use new prefix for this new
implementationRef attribute?
Anish:
This attribute meant to be sca-bpel extension or bpel
extension.
MikeR:
This is in componentType file and no extensions over
there.
Anish:
For scdl and component type file there is one name
space. For BPEL, it is bpel extensions.
The idea of creating a separate schema for one attribute is
not appropriate.
Najeeb:
we can create a new schema file and import the
existing namespace.
Anish:
There is no one good way now. We should have a
separate namespace for implementation.bpel
However, we do not need another discussion on single
namespace for implementation.bpel
MikeR and Anish preferred to put in sca-bpel namespace.
Dieter:
We should not be creating complicated dependencies.
<anish>
existing proposal:
<anish>
The @implementationRef attribute MUST contain a valid XPath 1.0
expression, which when executed on a BPEL process returns exactly one
<partnerLink> element. The partnerLink thus identified will be
considered to correspond to the service or reference that contained the
@implementationRef attribute. If a service or reference does not have an
@implementationRef attribute, then it will act as if it had
@implementationRef=//partnerLink[@name=$name], where $name is the value
of the @name attribute of that service or reference.
<Michael Rowley>
Proposed issue resolution: An
@sca-bpel:implementationRef attribute on a component type's service or
reference MUST contain a valid XPath 1.0 expression, which when executed
on a BPEL process returns exactly one <partnerLink> element. The
partnerLink thus identified will be considered to correspond to the
service or reference that contained the @sca-bpel:implementationRef
attribute. If a service or reference does not have an
@sca-bpel:implementationRef attribute, then it will act as if it had
@sca-bpel:implementationRef=//partnerLink[@name=$name], where $name is
the value of the @name attribute of that service or reference.
Motion passed unanimously
Resolution: Issue 17 closed with above resolution.
Schreiber diagnostics output
[Delete this section before publishing the minutes]
citation-detection-scribed: Line 205: Check for possible unrecognized nick 'Motion'
statistics: Schreiber found 161 input lines
edits: Schreiber found no text-edit commands
citation-detection-irc1: Line 16: Check for possible unrecognized nick 'http'
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 36: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 44: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 49: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 54: Check for possible unrecognized nick '10. Issue 17 http'
citation-detection-irc1: Line 62: Check for possible unrecognized nick '11. Issue 18 http'
citation-detection-irc1: Line 67: Check for possible unrecognized nick 'http'
command-scribe: Line 71: Khanderao Kand recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 76: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 81: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 97: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 111: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 145: Check for possible unrecognized nick 'http'
system: Transformer: SAXON 9.0.0.2
[End of Schreiber diagnostic output]