sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Draft Minutes of 2008-11-18 are attached
- From: Bob Freund <bob.freund@hitachisoftware.com>
- To: sca-assembly@lists.oasis-open.org
- Date: Tue, 18 Nov 2008 12:27:12 -0500
Title: SCA-Assy - 2008-11-18
Hide Chat
Action Items
- Done:
- id=2008-10-30-1 status=done Vorthmann to examine the specification and create text that implements the directional resolution to Assembly-37
- id=2008-10-30-3 status=done Karmaker to develop concrete text consistent with the directional resolution to Assembly-36
- id=2008-10-30-8 status=done Freund to draft a conformance statement
- Pending:
- id=2008-06-03-6 status=pending Test sub cttee produce test assertions and test artifacts and test harness
- id=2008-08-26-2 status=pending Edwards to produce text that re-considers the application of the resolution to assembly-57
- id=2008-09-16-1 status=pending owner="Editors" Add text to justify no operator overloading as described in DaveB's E-mail
- id=2008-10-30-4 status=pending Editors to fix pseudoschemas a/r to be consistent with the resolution that resolves Assembly-32
- id=2008-10-30-5 status=pending Vorthman to create a proposal relative to potential solution for issue 5
- id=2008-10-30-6 status=pending Karmarkar do the detailed work to implement the resolution to Assembly-60
- New:
- id=2008-11-18-1 status=pending Edwards to coordinate and socialize this directional decision to the resolution of Assembly-33 with the affected TCs
Minutes
Opening
Roll - quorate with 18 of 25 voting members present
Will defer Conformance and test after conclusion of proposals
Resolution: Minutes of 2008-11-04 approved w/o
Action Items
Action: id=2008-06-03-6 status=pending Test sub cttee produce test assertions and test artifacts and test harness
Action: id=2008-08-26-2 status=pending Edwards to produce text that re-considers the application of the resolution to assembly-57
Action: id=2008-09-16-1 status=pending owner="Editors" Add text to justify no operator overloading as described in DaveB's E-mail
Action: id=2008-10-30-1 status=done Vorthmann to examine the specification and create text that implements the directional resolution
to Assembly-37
Action: id=2008-10-30-3 status=done Karmaker to develop concrete text consistent with the directional resolution to Assembly-36
Action: id=2008-10-30-4 status=pending Editors to fix pseudoschemas a/r to be consistent with the resolution that resolves Assembly-32
Action: id=2008-10-30-5 status=pending Vorthman to create a proposal relative to potential solution for issue 5
Action: id=2008-10-30-6 status=pending Karmarkar do the detailed work to implement the resolution to Assembly-60
Action: id=2008-10-30-8 status=done Freund to draft a conformance statement
Administrivia
Next Tuesday's call will proceed as planned despite Thanksgiving
Active Issues
Edwards and Koenig discuss the proposal
Koenig:
proposal includes the proposal document as well as the background information
Booz:
I prefer to remove the Java material since the Java TC has not agreed to it
Chapman:
I am not easy with resolving this since it does not demonstrate, for example, that java and BPEL would interoperate
Chapman and Edwards - perhaps it ought to be circulated to the language and bindings groups and determined to not be problematical
before we adopt it.
<anish>
dave, what would the c&i do, if the intent is present on the service but not on the reference?
<anish>
at the binding level, it is slightly easier because you would look at both ends
<anish>
for the c&i this is a little tricky
<Dave Booz>
Anish, I'm not sure this affects the C&I of a service
Amendment: m:Chapman s: Aupperle s/Resolve/ Set a direction for
<anish>
i didn't mean the service, i did mean the client
<anish>
there is no intent on the reference side but one on the service side
<anish>
what interfaces would be generated on the client side
<Scott Vorthmann>
I suspect the client just does what it does... the presence or absence of the intents helps the assembler know that the wire
won't work
<anish>
if the metadata on teh service side is not examined
<anish>
i guess my point is that: to do the "right thing" on the client side, you would have to look at both ends
<anish>
unless we mandate that the intent be present on the reference
Action: Edwards to coordinate and socialize this directional decision to the resolution of Assembly-33 with the affected TCs
Vorthmann discusses his proposal
Edwards discusses his proposal
further action defered due to press of time
AOB
[End of Minutes]
Formatted on 2008-11-18 at 12:26:41 GMT-5
Minutes formatted by Schreiber, a collection of XSLT
stylesheets by Bob Freund modeled after David Booth's scribe
Schreiber diagnostics output
[Delete this section before publishing the minutes]
statistics: Schreiber found 65 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 26: s/Koenig/Karmarkar
edits: Line 35: s/word/proposal
edits: Line 36: s/ground/ground information
command-scribe: Line 4: Bob Freund is recognized
command-scribe: Line 4: Bob Freund's nick bob has been selected
edit-substitute: command on line 26 succeeded, changed line 25 from 'Koenig' to 'Karmarkar'
edit-delete: Line 26 was deleted
edit-substitute: command on line 35 succeeded, changed line 34 from 'word' to 'proposal'
edit-substitute: command on line 36 succeeded, changed line 34 from 'ground' to 'ground information'
edit-delete: Line 35 was deleted
edit-delete: Line 36 was deleted
command-kaviroll: Line 71: Attempting to fetch roll from http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16066
system: Transformer: SAXON 9.0.0.6
[End of Schreiber diagnostic output]
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]