[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Raw chat log of 2008-02-28 telcon
Martin C: scribe: Martin C
Martin C: Agenda:
1. Roll Call
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/roster.php
2. Appointment of scribe
Rotating list attached below
3. Agenda bashing
4. Approval of Feb 21, 2008 meeting minutes
http://lists.oasis-open.org/archives/sca-bpel/200802/msg00021.html
5. Action items review
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php
#0021 chairs to follow up with Mary to post the CD docs to OASIS repository
#0024 Martin Chapman to write up a proposal for issue 15 (Define
Conformance Targets) http://osoa.org/jira/browse/BPEL-15
#0025 Michael Rowley to raise issue with the Assembly TC to allow for
expressing implementation type specific Service/Reference identification
and naming in the ComponentType files.
DONE
#0026 Michael Rowley to propose a partial resolution to the SCA BPEL
Issue 17 using the proposal suggested in earlier action (#0025)
DONE
#0027 Michael Rowley to update status of issue 1
6. F2F meeting in May: do we need it?
In a previous concall we decided to discuss whether we want to have a
f2f meeting or not on Feb 28th. Issue stats: Of the 7 new and open
issues -- 2 (15 & 1 are about conformance targets and RFC 2119 keywords
2 (8 & 12) are postponed 1 (17) is close to being resolved That leaves
just 2 non-conformance target/language issues + testing. The meeting is
in May. With two months to go, a f2f does not seem to be justified
(especially for folks not on the west coast). I suggest we cancel it.
7. CD 01 namespace URI
We agreed to a NS design and versioning policy document
(http://lists.oasis-open.org/archives/sca-bpel/200710/msg00050.html).
There are two things to consider:
a. the NS URI that OASIS has asked us to use contains an extra 'ns'
component. This is not what the TAB recommends. Are we ok with that? b.
the NS URI in CD 01 is:
http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801 whereas the NS URI
in CD 01 of SCA Policy document is:
http://docs.oasis-open.org/ns/opencsa/sca/200712. We need to have
consistency across specs since we are sharing the NS URI.
8. New Issues
NONE
9. Issue Discussion
a) Issue 17 http://osoa.org/jira/browse/BPEL-17
TITLE: Allow Component Type side file to override defaults for
services and references
SUBMITTED BY: Anish Karmarkar
Partial resolution proposal at
http://lists.oasis-open.org/archives/sca-bpel/200802/msg00024.html
b) Issue 14 http://www.osoa.org/jira/browse/BPEL-14
TITLE: Allow sca-aware processes to specify everything that can be
specified in a CT side file
SUBMITTED BY: Anish Karmarkar
c) Issue 15 http://www.osoa.org/jira/browse/BPEL-15
TITLE: Define Conformance Targets
SUBMITTED BY: Martin Chapman
d) 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
e) Issue 16 http://osoa.org/jira/browse/BPEL-16
TITLE: Ambigous Service Resolution
SUBMITTED BY: Dieter Koenig
10. AOB
Martin C: topic: agenda
Martin C: agenda approved
Martin C: topic: approval of minutes
Martin C: http://lists.oasis-open.org/archives/sca-bpel/200802/msg00021.html
Martin C: approved unanimously
Martin C: topic: AIs
Martin C: #0021 chairs to follow up with Mary to post the CD docs to
OASIS repository
Martin C: to be convered in agenda
Martin C: #0024 Martin Chapman to write up a proposal for issue 15
(Define Conformance Targets) http://osoa.org/jira/browse/BPEL-15
Martin C: ongoing
Martin C: #0027 Michael Rowley to update status of issue 1
Martin C: Done
Martin C: topic: F2F meeting in May: do we need it?
Martin C: Anish says not many issues so many not be easy to justify a F2F.
Martin C: Mike R: agree
Martin C: Danny, Deiter, agree
Martin C: Mike R: was going to do this at OASIS symposium. Editors might
want to meet then.
Martin C:
Anish: that would not be a TC meeting for voting rights
Martin C: no objection to cancelling F2F in May
Martin C: ACTION: Chairs to inform Jane about room at the Symposium
Martin C: topic: CD 01 namespace URI
Martin C: The TC agreed a format based on a liaison SC document.
Martin C: There is a namespace in the CD
Martin C: it differs from Policy
Martin C: the format in the CD includes an /ns/ token recomemneded by
OASIS Staff
Martin C: Sanjay: policy and bpel are ahead of assembly managing the
shared namespace
Martin C: what is the common namespace we should use?
Dieter Koenig: current contents of the cd document:
- sca http://docs.oasis-open.org/ns/opencsa/sca/200712
- sca-bpel (defined here)
http://docs.oasis-open.org/ns/opencsa/sca-bpel/200801
Martin C: Martin: liaison should coordinate the namespace name between tcs
Martin C: sanjay: what deiter pasted is fine
Martin C: the bpel specific namespace doesnt have to have the same date
as the shard one
anish apologies, should have read the NS prefixes carefully
Martin C: sanjay: ask assmebly tc to finalise common namespace uri
before publishing the CD
Dieter Koenig:
Martin C: Danny: we just publish that we are compatible with a certain
namespace, we dont need permission
Martin C: Danny: they may give us a namespace before they formalise it.
Its a bootstrapping problem
Martin C: and shouldn't occur in the future
Sanjay: Adopt the format
http://docs.oasis-open.org/ns/opencsa/sca-bpel/[yyyymm] for the SCA BPEL
TC defined namespace URI
Martin C: Motion: Sanjay, to adopt the namespace as suggested by tc admin
Martin C: 2nd: martin
Martin C: discussion: none
Martin C: no objections, motion passes
Martin C: topic: Issues
Martin C: Issue 17 http://osoa.org/jira/browse/BPEL-17
TITLE: Allow Component Type side file to override defaults for
services and references
SUBMITTED BY: Anish Karmarkar
Partial resolution proposal at
http://lists.oasis-open.org/archives/sca-bpel/200802/msg00024.html
Martin C: part of it moved to assembly
Martin C: Mike R goes thru msg00024
Michael Rowley: 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.
Martin C: Mike R: assumes assembly will accept the proposal
anish: minor syntax Q: shouldn't it be: //partnerLink/[@name=$name] ?
Dieter Koenig: "//partnerLink/[@name=$name]" is ambigous if there are
multiple partner links with the same name
Martin C: Mike R: an alternative is not mention xpath version as people
could be using 2.0 and it wouldnt really matter
Martin C: deiter: the xpath expression could be ambiguous
Martin C: mike r: thats ok, will result in more than one partnerlink
Martin C: the last line of proposal covers this
Martin C: Mike R: Need to wait for assembly before we can resolve this
Martin C: Motion: Mike R add this text to the jira for issue-17 noting
that it will be used as the resolution if assembly adopts the sca-bpel
proposal
Martin C: 2nd Dieter
Martin C: no objections. Approved
Martin C: Issue 14 http://www.osoa.org/jira/browse/BPEL-14
TITLE: Allow sca-aware processes to specify everything that can be
specified in a CT side file
Martin C: Anish: describes the issue
Michael Rowley: Perhaps @sca:serviceName="foo" or
@sca:referenceName="foo" on partnerLinks.
Michael Rowley: hi
Michael Rowley responds to an IM in the wrong window.
Martin C: scribed lost the thread
Martin C: but no decisions have been made
Sanjay: do we want to have a call in the next week given that SCA-J TC
is meeting for their F2F
Martin C: Topic: meeting next week
Martin C: F2f going on, so inclined to cancel
Martin C: Anish: next weeks meeting is cancelled
Martin C: Adjourned
Sanjay: Next mtg: Mar 13
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]