FINAL. SCA-Assembly TC Teleconference. 13 Jan Chair. Scribe. Attendees. Mike Edwards, Martin Chapman. Dave Booz

Transcription

1 FINAL SCA-Assembly TC Teleconference 13 Jan 2009 Chair Mike Edwards, Martin Chapman Scribe Dave Booz Attendees Name Company Status Michael Rowley Active Endpoints, Inc. Group Member fred carter AmberPoint Group Member Mark Combellack Avaya, Inc. Group Member Dale Moberg Axway Software* Group Member Bryan Aupperle IBM Group Member Michael Beisiegel IBM Group Member David Booz IBM Group Member Mike Edwards IBM Group Member Dieter Koenig IBM Group Member Jim Marino Individual Group Member Simon Nash Individual Group Member Peter Furniss Iris Financial Solutions Ltd. Group Member Jeff Estefan Jet Propulsion Laboratory:* Group Member Martin Chapman Oracle Corporation Group Member Khanderao Kand Oracle Corporation Group Member Anish Karmarkar Oracle Corporation Group Member Ashok Malhotra Oracle Corporation Group Member Sanjay Patil SAP AG* Group Member SCA Assembly TC meeting minutes Page 1 of 10

2 Plamen Pavlov SAP AG* Group Member Peter Walker Sun Microsystems Group Member Sabin Ielceanu TIBCO Software Inc. Group Member Scott Vorthmann TIBCO Software Inc. Group Member Contents Resolutions... 2 Actions... 3 Agenda... 3 (Item 2) Agenda Bashing... 6 (Item 3) Minutes from previous meeting of Assembly TC... 6 (Item 4) Action Items... 6 (Item 5) TC Administrivia... 6 (Item 6) Conformance and Test... 6 (Item 7) Letter from the SCA Liaison Committee... 6 (Item 8) New Issues... 8 Issue 99: Missing Conformance point for callbackinterface on interface.wsdl... 8 (Item 9) Latest Revision of Specification... 8 (Item 10) Existing Issues... 9 Issue #94: Remove Conversational interfaces functionality... 9 AOB Resolutions Resolution: Minutes of Assembly TC meeting of 6th January 1009 accepted. Resolution: Respond to the Liaison committee using the words: " The SCA Assembly specification currently requires conformance to the SCA Policy specification" Resolution: Issue 99 is opened Resolution: Resolution: Issue 99 is resolved with the text " The attribute, if present, MUST reference a porttype of a WSDL 1.1 document." Resolution: Publish sca-assembly-1.1-spec-cd01-rev8_a.pdf as Committee Draft CD02 Resolution: Make CD02 and related Schemas public and ask OASIS admin to put it into the public repository SCA Assembly TC meeting minutes Page 2 of 10

3 Actions Action : Martin C to raise an issue for a proposal of the definition of an SCA runtime Agenda 1. Opening Introductions Roll call Scribe confirmation Agenda bashing 2. Approval of minutes of SCA-Assembly TC meeting of 6th January 3. Action Items: id= status=pending Editors to review issues with hyperlinks in PDF versions; perhaps the package used to generate the PDF might need to be carefully selected id= status=pending Edwards to generate a proposal on Assembly-34 id= status=pending Vorthmann to produce precise text for the resolution of Assembly-37 consistent with the previous directional decision id= status=pending Edwards to require an update to ASM to deal with binding on implementation type id= status=pending Edwards to raise an issue dealing with the conflict in muliplicity on line 1447 of revision 8 of the spec id= status=pending Nash to prepare resolution text for Assembly-95 id= status=pending Omnis to review open issues and decide to volunteer to create proposals 4. TC Administrivia Assembly F2F Meeting - Jan 26/27 Assembly 28/29 Policy Oracle Conference Center, Bay Area - request from Dave Booz to keep clear of the SCA-J telecon on Monday 26, 07:30-9:00 Pacific. 5. Conformance & Test SCA Assembly TC meeting minutes Page 3 of 10

4 Latest Test Assertions document: Latest Testcase document: Testcase artifacts: 6. Latest Revision of Specification - also attached to this intention is to vote this as CD-02 today - need to agree that all issues listed in the following are correctly applied in this revision of the spec: 7. Letter from the SCA Liaison Committee See: Proposed response (that the TC should vote on): "The SCA Assembly specification does not require conformance to any other SCA specification in order to be conforming to the Assembly specification" 7. New Issues ASSEMBLY-99 Missing Conformance point for callbackinterface on interface.wsdl 8. Existing Issues ASSEMBLY-94 Remove Conversational interfaces functionality Lot of debate on the list - too long to list it all here ASSEMBLY-98: Conformance Assertion [ASM50012] is invalid SCA Assembly TC meeting minutes Page 4 of 10

5 ASSEMBLY-90: in the context of composite includes Proposal: ASSEMBLY-34: Define error handling ASSEMBLY-37 Need to clarify contents of an SCA Domain virtual composite Latest proposal: ASSEMBLY-95 "wiredbyimpl" is an invalid attribute for a Composite Reference ASSEMBLY-46: Dynamic Aspects of the Domain not adequately described in the Assembly Specification ASSEMBLY-86: Abstract CRUD APIs for definitions infoset ASSEMBLY-87: A single definitions infoset is not sufficient ASSEMBLY-80: Create an Event Processing Model for SCA ASSEMBLY-2: use of UML ASSEMBLY-91: Details needed for sca:conversationviolation ASSEMBLY-97 Need Assembly level definition for "AllowsPassByReference" 8. Issue Status 17 Open Issues x opened x resolved SCA Assembly TC meeting minutes Page 5 of 10

6 9. AOB (Item 2) Agenda Bashing (Item 3) Minutes from previous meeting of Assembly TC Meeting minutes from Jan 6 telecon. Approved unanimously Resolution: Minutes of Assembly TC meeting of 6th January 1009 accepted. (Item 4) Action Items No changes to action item status as shown in Agenda (Item 5) TC Administrivia Mike E asks for attendees to notify chairs if you are attending Dave B asks for 9AM start time on Monday for F2F to accomodate SCA-J TC telecon Mike E: 9AM is the start time for Monday is agreed (Item 6) Conformance and Test Mike E: FYI for main TC members - test SC making progress, see document pointers in agenda for test assertions, test case document and working test artifacts Mike E: Test SC committee would welcome additional help (Item 7) Letter from the SCA Liaison Committee See: Mike E: provides brief overview of the letter and goes through a proposal to answer Liason's question - proposal is in the agenda Martin C: who defines what an SCA runtime is? Mike E: Liason is asking what specs are required to be compliant with Assembly...this is a different question Martin C: Isn't Assembly dependent on Policy? several: no Martin C: Policy requires compliance to Assembly for sure, but is it really possible to be compliant to just assembly? SCA Assembly TC meeting minutes Page 6 of 10

7 Martin C: Should we raise a new issue to have assembly define what specs are required to be conformed to in order to claim compliance to SCA? Suggested wording: Mike Edwards: "The current SCA Assembly specification (CD01-Rev8) does not require conformance to any other SCA specification in order to be conforming to the Assembly specification"...and we can change to CD-02 if we agree it Martin C: doesn't want to rule out the possibility of assembly defining what specs are required for compliance to an SCA runtime Simon N: we can always change our minds Anish: observes that in fact assembly schema so assembly does depend on policy Anish: policy schema is in the base schema files, not in seperate files as is done for other SCA specs Anish: should compliance to policy schema bits be optional in assembly? Anish: If compliance to assembly does not include policy then policy schema should be in an extension Mike R: found a normative req on policy from Assembly Michael Rowley: ASM60024 Mike Edwards: Section Mike Edwards: Updated wording: "The SCA Assembly specification requires conformance to the SCA Policy specification" Martin C: ok with these new words Ashok: we could move all of the normative stmts in assembly on policy into the policy spec Pete W: suggests adding 'currently requires' Mike Edwards: "The SCA Assembly specification currently requires conformance to the SCA Policy specification" Motion: m:ashok s Pete W: "respond to Liason using the words 'The SCA Assembly specification currently requires conformance to the SCA Policy specification'" Motion passes w/o Resolution: Respond to the Liaison committee using the words: " The SCA Assembly specification currently requires conformance to the SCA Policy specification" Action : Martin C to raise an issue for a proposal of the definition of an SCA runtime SCA Assembly TC meeting minutes Page 7 of 10

8 (Item 8) New Issues Issue 99: Missing Conformance point for callbackinterface on interface.wsdl Bryan A: introduces the issue Motion: m: Bryan s: Anish Open issue 99 Motion passes w/o Resolution: Issue 99 is opened Bryan A: would like to resolve 99 now Bryan Aupperle: The attribute, if present, MUST reference a porttype of a WSDL 1.1 document. - proposed resolution above anish: minor ed suggestion: The attribute, if present, MUST reference a WSDL 1.1 porttype anish: takes the 'document' part out, which can be tricky for wsdl Motion: m: Bryan s: Anish resolve 99 with proposal "The attribute, if present, MUST reference a porttype of a WSDL 1.1 document." Motion passes w/o Resolution: Issue 99 is resolved with the text " The attribute, if present, MUST reference a porttype of a WSDL 1.1 document." (Item 9) Latest Revision of Specification Mike E: would like to vote this as CD02 Mike E: Bryan made some editorial adjustments in followup Mike E produced a new doc based on those changes Mike Edwards: Mike E describes changes in 8_a Mike Edwards: WSDL Interface Type 2839 The WSDL interface type is used to declare interfaces for services and for references, where the interface 2840 is defined in terms of a WSDL document. An interface is defined in terms of a WSDL 1.1 Port Type with 2841 the arguments and return of the service operations described using XML schema SCA Assembly TC meeting minutes Page 8 of 10

9 2843 A WSDL interface is declared by an interface.wsdl element. The following shows the pseudo-schema 2844 for the interface.wsdl element: 2845 <!-- WSDL Interface schema snippet --> 2846 <interface.wsdl interface="xs:anyuri" callbackinterface="xs:anyuri"?> 2847 The interface.wsdl element has the following attributes: 2848 interface (1..1) - the URI of a WSDL Port Type 2849 The attribute MUST reference a porttype of a WSDL document. [ASM80001] 2851 callbackinterface(0..1) - an optional callback interface, which is the URI of a WSDL Port 2852 Type 2853 The attribute, if present, MUST reference a porttype of a 2854 WSDL 1.1 document. [ASM80016] The form of the URI for WSDL port types follows the syntax described in the WSDL 1.1 Element 2857 Identifiers specification [WSDL11_Identifiers] Bryan: issue 99 resolution not noted in change activity at end of document Motion: m: Anish s: Bryan "make rev8_a document as CD02" Bryan: are we publishing to OASIS doc repo? several: we should Anish: we can handle as a separate motion Motion passes w/o Resolution: Publish sca-assembly-1.1-spec-cd01-rev8_a.pdf as Committee Draft CD02 Motion: m:anish s: Bryan "make cd02 and related schemas public and ask admin to put it into the public repo" Motion passes w/o Resolution: Make CD02 and related Schemas public and ask OASIS admin to put it into the public repository (Item 10) Existing Issues Issue #94: Remove Conversational interfaces functionality Martin C: what are the options on the table? a) Remove conversations b) leave as-is c) some form of modification Simon N: haven't heard any discussion of c Mike E: is there a proposal like/along the lines of c) that someone can bring forward? SCA Assembly TC meeting minutes Page 9 of 10

10 Mike R: Does anyone who dislikes converations think a change to annotations or other aspect would be interesting? Mike R: seems like we're debating between a) and b) Motion: m: Anish s: Simon "resolve 94 by accepting proposal in JIRA" Mike R: Can we defer discussion to the F2F? expresses desire for that Martin C: Is this a motion for direction? I don't see text in JIRA. Anish: yes Anish: impact on spec text is not so much Simon N: removal should be easy for an editor Mike R: There's alot of specs with conversations in them Simon N: would not like to defer discussion to F2F, Java TC needs a decision very soon Sanjay: Is support for conversations optional in the current specs? anish: amemdment: accept the current proposal in JIRA as a sense of direction for issue 94 Dave Booz: amendment: m: Anish s: Simon N accept the current proposal in JIRA as a sense of direction for issue 94 Martin C: anything with a MAY is optional Amendment passes w/o Dave Booz (to call the question) Martin C: Other TC could retain this function if they want to Mike R: feels BPEL needs conversations for engine managed correlation Aren't callbacks sufficient for bpel-engine-managed-correlation? Dave B: calls the question Mike E: are there objections to calling the question? yes, there are objections (Jim Marino) Dave Booz: time expired AOB None Next meeting 20 th January 2009 Close of Business SCA Assembly TC meeting minutes Page 10 of 10