Approved Minutes of Nov 20th Call

Date:  Th, 20 Nov 2008

Time:  10:00am - 11:00am PST


id: 190605#/654321#


+1 888-967-2253

+1 650-607-2253

+44 118 924-9000

+61 2-8817-6100

+49 89 14302323


Web-conf: http://webconf.soaphub.org/conf/room/sca-lsc


Agenda:

1.      Roll Call


Martin Chapman, Anish Karmarkar, Mike Edwards, Jeff Mischkinsky, 

Sanjay Patil, Bryan Aupperle

represented - Assembly, Bindings, BPEL, Steering Comm, c/c++, SDO

not representend - java, policy



2.      Scribe Assignment


Jeff


3.      Agenda Bashing


Proposal from Ashok to talk about camelcase case for SCA keywords 

(from Policy TC)



4.      Approval of transcript of 31 oct 2008


http://lists.oasis-open.org/archives/opencsa-liaison/200810/msg00022.html


Anish/Sanjay - approve transcript as record of minutes - UNAN


4a. Camelcase proposal

Martin asked "what's a keyword"?


policy at the very least wants "intent keywords" to be consistent -

anish/mike  - LSC recommends that all the TC's adopt the Policy TC 

recommendation that intents use camelCase (first letter lowercase) 

except for acronyms which would be all upper case. - UNAN


discussion of what to do in general:


martin/jeff - Recommend add some text to the "conventions" section of 

the Assembly TC which describes the naming conventions:

  e.g. intents as above, type names are CamelCase, element names are 

camelCase, attributes are @camelCase are preceded by an "@" sign, etc. 

- UNAN




5. OpenCSA Project Management

      Review of testing plans - output from last week f2f meetings


Mike has updated the Assembly spec to contain labels for all normative 

statements and produced a first draft companion test assertion 

document which is not yet complete.

There is a draft of the Test Architecture.

Recommendation is to use a common approach, with assembly to do the 

first exemplar.

The c/c++ TC has started to review.

Discussion of how to implement and what is required.


      Version Control and JIRA System recommendation status/update

conclusion is use subversion - oasis is in the process of putting it up


conclusion on JIRA, not to switch to OASIS JIRA for this iteration


   Schedule

Please read the report on java TC from dave. We will do a project/

schedule review at the next meeting.


     Any other blocker issues?


concern in identifying the 2 implementations that will be used for 

testing



7. Next conf-call


Next call will be in 2 weeks -- 4 Dec 2008 -- plan is to do a schedule 

review, Sanjay will chair.


8. AOB