[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: raw minutes 13th December 2007
Martin: scribe: Martin
Martin: Agenga approved:
Martin: 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 Dec 6, 2007 meeting minutes
Raw transcript: http://lists.oasis-open.org/archives/sca-bpel/200712/msg00020.html
5. Action items review
http://www.oasis-open.org/apps/org/workgroup/sca-bpel/members/action_items.php
6. Review of latest Working Drafts
Latest Working Draft: http://www.oasis-open.org/committees/download.php/26339/sca-bpel-1.1-spec-WD-04.doc
Editors note: http://lists.oasis-open.org/archives/sca-bpel/200712/msg00023.html
a) Are we ready to vote on a CD?
OASIS IPR Policy section related to a CD vote:
http://www.oasis-open.org/who/intellectualproperty.php#types_obligations
7. Call Schedule
a) Next calls: 12/20, 1/10
Do we want to have a call on 12/20?
8. New Issues
9. Issue Discussion
a) Issue 11 http://www.osoa.org/jira/browse/BPEL-11
TITLE: BPEL variable initialization and SCA properties
SUBMITTED BY: Mark Ford
Additional Emails:
http://lists.oasis-open.org/archives/sca-bpel/200712/msg00027.html
http://lists.oasis-open.org/archives/sca-bpel/200712/msg00025.html
b) Issue 2 http://www.osoa.org/jira/browse/BPEL-2
TITLE: Does the spec allow a componentType side file
SUBMITTED BY: Anish Karmarkar
Email thread:
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00040.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00041.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00042.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00043.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00044.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00048.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00049.html
http://lists.oasis-open.org/archives/sca-bpel/200710/msg00055.html
http://lists.oasis-open.org/archives/sca-bpel/200711/msg00003.html
c) Issue 15 http://www.osoa.org/jira/browse/BPEL-15
TITLE: Define Conformance Targets
SUBMITTED BY: Martin Chapman
d) Issue 1 http://www.osoa.org/jira/browse/BPEL-1
TITLE: support for BPEL4WS 1.1
SUBMITTED BY: Martin Chapman
e) 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
10. AOB
Martin: topic: Mintutes
Martin: http://lists.oasis-open.org/archives/sca-bpel/200712/msg00020.html
Martin: minutes dec 6th approved
Martin: topic: Review of latest working drafts
Martin: Latest Working Draft: http://www.oasis-open.org/committees/download.php/26339/sca-bpel-1.1-spec-WD-04.doc
Editors note: http://lists.oasis-open.org/archives/sca-bpel/200712/msg00023.html
charlton: Dieter, do you want to share the CD on adobe connect>
Martin: Chair: Do we want to vote on CD yet? Reminded TC members of IPR policy WRT CDs
charlton: http://my.adobe.acrobat.com/scabpel
Martin: Dieter, main goal was a clean copy to baseline comments.
Martin: Martin: Once we go to CD we won't go back to Workign Drafts as per naming guidelines
Martin: Mike R: Moves to accept as a CD; 2nd Dieter.
Martin: This requires full majority vote
Martin: (more than 50% of total TC voting membership)
Martin: Danny: what is the quorum issue?
Martin: Martin: If meeting is quorate and no one objects, full member vote carries
Martin: Jacques: Company is in process of doing an IP search, so if made a CD today Fujistu would have to leave as memebers for the
present.
Martin: Martin: don't see the need for a rush
Martin: Charlton: given timings of holiday might be curteous to hold off vote until a month from today
Martin: hold a CD on 17th January
charlton: Any reason why we couldn't wait until January 17th>
charlton: i agree with Martin, is there a need to do this now?
Martin: Mike R: moves to postone previous motion
charlton: I second the postpone
Martin: s/postpone/postpone to 17th January
Martin: 2nd chalrton
Martin: No objections, motion carried
Martin: Are there any immediate comments on the document
Martin: Martin: we just tried to vote as CD why do we need an overview now.
Martin: Please read and post comments on the list
Martin: Topic: call schedule
Martin: next two calls planned: 20 dec and 10th jan
Martin: 3td jan has already been cancelled (as 27th)
charlton: i would not be able to attend dec 20th
Alex Yiu: question ... : do we have the raw minute for last week conf call?
Martin: quorom is 8, so need this to make decisions
Mark Ford: +1 to cancelling meeting
Martin: Chair: seems likely to be quorate
Martin: Mark Ford: motions to cancel 20th Dec meeting; charlton 2nds
Martin: no discussion, no objections, motion carried.
Martin: next call on january 10th
Martin: Topic: new issues
Martin just realised i should be on another call by now and shouldnt have done minutes
Martin: no new issues raised
Martin: topic: issues discussion
Martin: Issue 11 http://www.osoa.org/jira/browse/BPEL-11
Michael Rowley: If the variable has an initialization expression (a from-spec) then that becomes the default value for the variable
in cases where the SCA component does not provide a value for that property. If a value is provided for the property, the
expression is not evaluated. If the from-spec is a literal value, where it has the following form:
<from><literal>literal value</literal></from>
then the literal value will be represented as the default value in the component type for the process. Any other kind of
initialization expression will not be represented in the component type.
Michael Rowley: Update:
Michael Rowley: If the variable has an initialization from-spec then that becomes the default value for the variable in cases where
the SCA component does not provide a value for that property. If a value is provided for the property, the initialization from-spec
is not evaluated.
If the from-spec is a literal value, where it has the following form:
<from><literal>literal value</literal></from>
then the literal value will be represented as the default value in the component type for the process. Any other kind of
initialization from-spec will not be represented in the component type. However, even though the other kinds of initialization
from-spec are not represented in the component type, they would still be computed and used as the default value for the property
when the component does not provide a value for that property.
Martin: Sanjay: can the value of a property include a bpel expression?
Martin: Mike R; Yes
Martin: Mike E: point on mailing list. any value can be set to a complex expression computed at runtime, and prob need changes in
assembly spec
Martin: Mike R: assembly spec allows this
Michael Rowley: From the assembly spec: "Implementation types other than composite can declare properties in an
implementation-dependent form (eg annotations within a Java class), or through a property declaration of exactly the form described
above in a componentType file."
Mike Edwards: that text does not deal with the default values in the componentType
Martin: Danny: there wont be a default value if its computed
Alex Yiu: Does the proposal need to address the "mustSupply" issue also?
Martin: Mike R: only literals in the Component Type
Martin: Najeeb: this can be non-deterministic
Martin: Mike R: can only mark a varibale as a property if it is unique across process.
Martin: Mike R: so rules are deterministic
Martin: Mark: discussion is relevent to the issue raised
Martin: Alex: does the mustSupply flag need to be considered as part of this issue?
Martin: Chair: do you have any proposed text?
Martin: Alex: not yet
Michael Rowley: If a BPEL variable that is used as a property has an initialization expression (a from-spec) then mustSupply="false"
must be specified.
Martin: Chair: might also be a different issue
Martin: Chair: include Mike R's text above at end of proposed resolution
Michael Rowley: ... on the component type property declaration.
Alex Yiu: I would suggest to just use "from-spec" instead of "expression (a from-spec)".
Martin: so text of full proposal to issue 11 is:
Michael Rowley: If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be
specified on the component type property declaration.
Michael Rowley: If the variable has an initialization from-spec then that becomes the default value for the variable in cases where
the SCA component does not provide a value for that property. If a value is provided for the property, the initialization from-spec
is not evaluated.
If the from-spec is a literal value, where it has the following form:
<from><literal>literal value</literal></from>
then the literal value will be represented as the default value in the component type for the process. Any other kind of
initialization from-spec will not be represented in the component type. However, even though the other kinds of initialization
from-spec are not represented in the component type, they would still be computed and used as the default value for the property
when the component does not provide a value for that property.
Michael Rowley: If a BPEL variable that is used as a property has an initialization from-spec then mustSupply="false" must be
specified on the component type property declaration.
Martin: the last two entries marked Michael Rowley are the single proposal
Martin: Mike R moves to adopt the propsal above, Alex 2nds
Martin: s/propsal/proposal/
Martin: Alex: how does intraspection effect this
Martin: chair: is this/could this, be a new issue
Martin: Mike R: its relevant and would only need some minor text
Michael Rowley: If a component property value is specified (and the default is not to be used) then the initialization from-spec
will be evaluated, but it will not be used for the variable. The component property value will be used.
Martin: Sanjay: does this contradict assembly
Martin: Mike R: no it supports it
Martin: Mark Ford objects to unanimous consent
Martin: motion expires due to lack of time
Martin: AOB: None
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]