← Prev in month
← Prev in thread
Next in thread →
Next in month →
Draft minutes SCA-Assembly 2007-10-30 are attached
Title: SCA-Assy - 2007-10-30
Hide
IRC
- DRAFT -
SCA-Assembly TC Teleconference
30 OCT 2007
Attendees
Present
Charlton Barreto, (Adobe Systems)
fred carter, (AmberPoint)
Dale Moberg, (Axway Software*)
David DiFranco, (BEA Systems, Inc.)
Jim Marino, (BEA Systems, Inc.)
Michael Rowley, (BEA Systems, Inc.)
Jacques Durand, (Fujitsu Limited*)
Tom Rutt, (Fujitsu Limited*)
Robert Freund, (Hitachi, Ltd.)
Eisaku Nishiyama, (Hitachi, Ltd.)
Eric Wells, (Hitachi, Ltd.)
Michael Beisiegel, (IBM)
David Booz, (IBM)
Graham Charters, (IBM)
Mike Edwards, (IBM)
Peter Niblett, (IBM)
Matthew Peters, (IBM)
Martin Chapman, (Oracle Corporation)
Anish Karmarkar, (Oracle Corporation)
Jason Kinner, (Oracle Corporation)
Rich Levinson, (Oracle Corporation)
Ashok Malhotra, (Oracle Corporation)
Jeff Mischkinsky, (Oracle Corporation)
David Haney, (Rogue Wave Software)
Henning Blohm, (SAP AG*)
Sanjay Patil, (SAP AG*)
Peter Peshev, (SAP AG*)
Mark Hapner, (Sun Microsystems)
Peter Walker, (Sun Microsystems)
Scott Vorthmann, (TIBCO Software Inc.)
Chair
Martin Chapman and Mike Edwards
Scribe
Bob Freund
Agenda:
1. Opening
Introductions
Roll call
Scribe confirmation
Agenda bashing
2. Approval of minutes of SCA-Assembly TC meeting of 23rd October
http://www.oasis-open.org/archives/sca-assembly/200710/msg00114.html
3. Filename & URL Consistency
Consider adoption of the proposal approved by the Open CSA MS steering committee, detailed here:
http://lists.oasis-open.org/archives/sca-assembly/200710/msg00118.html
4. New Issues
ASSEMBLY-12 :Abstract base type for Service and Reference
http://www.osoa.org/jira/browse/ASSEMBLY-12
NEW ISSUE: Difficulty using source= attribute to pull values into complex types
5. Errata Submitted from Open SOA
As defined in Michael Rowley's email:
http://www.oasis-open.org/archives/sca-assembly/200710/msg00109.html
The TC needs to decide how to treat the errata listed in this email.
One proposal is to accept these errata as a whole without raising separate issues.
6. Open Issues
ASSEMBLY-6: usage of not promoted references
http://www.osoa.org/jira/browse/ASSEMBLY-6
Follow up on action item and discussion on the email list.
7. AOB
Contents
Topics
[1]
Opening
[2]
Proposal of Filename and URL Consistancy
[3]
New Issue Assembly-12
[4]
Errata Submitted from Open SOA at http://www.oasis-open.org/archives/sca-assembly/200710/msg00109.html
[5]
Assembly-6
Table of Resolutions
Table of Action Items
Action Items
New:
2007-10-30-1: Martin to take up the question of the incrementing process wrt to CD and WDs with Mary
2007-10-30-2: Edwards to review headings at end of submitted errata document and to open those that are appropriate in jira
Resolutions
2007-10-30-1: M:Fred Carter S:Pete Walker Minutes of 2007-10-23 are accepted w/o
2007-10-30-2: M:David DiFranco S:Henning New Issue Assembly-12 accepted w/o
2007-10-30-3: M:Rowley S:Booz request that the editors incorporate the errata into the working draft excluding those headers without specific
errata at the end of the email w/o
Minutes
Scribe: Bob Freund
Opening
Khandahar Kand has requested a leave for the next two weeks
meeting is quorate with 21 of 33 voting members
Resolution: M:Fred Carter S:Pete Walker Minutes of 2007-10-23 are accepted w/o
Proposal of Filename and URL Consistancy
Edwards:
The proposal has been handed down from the steering cttee with a recommendation for adoption
Co-Chair Edwards walks the TC through the highpoints of the proposal attached to http://lists.oasis-open.org/archives/sca-assembly/200710/msg00118.html
<Sanjay>
cd 01 rev 1
<Sanjay>
wd 0, wd 1, cd 01, cd 01 rev 1, cd 01 rev 2, cd 02, cd 02 rev 1, ....
<anish>
that would be a little confusing
<anish>
spec version #, CD # and revision #
Sanjay:
Mary's thinking is that the WG ends when the first CD is issued
... thus, further changes would be revisions to a particular cd
Chapman:
Sanjsy, I think that we need to take this up with Mary since it seems to be at odds to the TC process
<Sanjay>
when qualified with rev ##, CD looses its approved status
Anish:
If we fo from cd1 to rev1 of that cd, and it is something that the editors just came up with, it would be confusing since
it is not clear that the revision has no standing
<anish>
yes, that is what would be confusing sanjay
<anish>
i would not guess that CD 01, rev 1 had a different status than CD 01
Chapman:
You have to use the trm WD if the draft has not been approved with the TC.
<Dave Booz>
+1 to anish
<Sanjay>
Mary's argument was that - a WD ## would not reflect whether it has been approved as a CD ever
<Sanjay>
e.g. IN wd 01, wd 02, cd 01, wd 03, wd 04, cd 2, ..
<Sanjay>
you can't tell whether wd 04 has content that was approved as a CD
Edwards:
Perhaps it ought to be an AI to take it up with the steering cttee
<anish>
right, because the WD ##, is not approved, whether it is based on an older approved CD I don't think is relevant
<Sanjay>
yes, jeff
Action: Martin to take up the question of the incrementing process wrt to CD and WDs with Mary
Sanjay:
Mary's opinion was that if you go back to WG, then it is not clear where that version belongs in sequence
<jeffm>
there doesn't have to be ANY relationship between different WDs a/o CDs
<Sanjay>
Mary's argument: http://lists.oasis-open.org/archives/opencsa-ms/200710/msg00045.html
New Issue Assembly-12
Dave DiFranco takes us through his issue at http://www.osoa.org/jira/browse/ASSEMBLY-12
Resolution: M:David DiFranco S:Henning New Issue Assembly-12 accepted w/o
<henning>
we have component references/services and component type services/references. Can we do the same thing in both places?
<anish>
... and constrainingType ref/service
<henning>
right
Errata Submitted from Open SOA at http://www.oasis-open.org/archives/sca-assembly/200710/msg00109.html
Action: Edwards to review headings at end of submitted errata document and to open those that are appropriate in jira
Resolution: M:Rowley S:Booz request that the editors incorporate the errata into the working draft excluding those headers without specific
errata at the end of the email w/o
Assembly-6
Peter Peshev summarizes the current status of proposals
<Peter Peshev>
Latest PROPOSAL :
The following description should be added in section 1.6.2 References,
after line 1387 (that line is after the paragraph that explains
attaching a binding to a reference and before the paragraph explaining
callback) :
Promotion of references accessing endpoints via bindings is suggested
practice since it allows the assembler to change the targets of the
references or the specified bindings and encourages component reuse,
however the lack of such promotion by itself MUST NOT cause errors
during deployment or runtime if the target of the reference can be
identified. The assembler is expected to guarantee for an unpromoted
reference with multiplicity 1..1 or 1..n that one of the following
conditions holds : there is either internal wire within the scope of the
current composite or a binding that identifies correctly either the
component/service for a wire to an endpoint within the SCA domain or
the accessible address of some endpoint outside the SCA domain. If the
assembler does not provide these conditions for an unpromoted reference
that has a multiplicity of 1..1 or 1..n, then such an unresolved
reference MUST generate an error at latest during the first attempt to
use the component. If the assembler does not provide these conditions
for an unpromoted reference that has a multiplicity with 0..1 or 0..n ,
then the programming model MUST not generate deployment errors and the
reference's wiring state will be represented in accordance to the
implementation type in question (e.g. null, handle that throws
exceptions when accessed, extensibility hooks, etc.).
For example the following definition MUST NOT generate any error if the
composite is deployed to the domain :
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
name="MyValueComposite">
<component name="MyValueServiceComponent">
<implementation.java class="services.myvalue.MyValueServiceImpl"/>
<reference name="StockQuoteService">
<binding.ws uri="http://www.sqs.com/StockQuoteService"/>
</reference>
<reference name="StockQuoteService2">
<binding.jms>
<destination name="StockQuoteServiceQueue"/>
<connectionFactory name="StockQuoteServiceQCF"/>
</binding.jms>
</reference>
</component>
<!-- no references and promotion on purpose -->
</composite>
however the following definitions MUST generate error if the reference
defined in the component type has multiplicity 1..1:
<composite xmlns="http://www.osoa.org/xmlns/sca/1.0"
name="MyValueComposite">
<component name="MyValueServiceComponent">
<implementation.java class="services.myvalue.MyValueServiceImpl"/>
<reference name="StockQuoteService">
<binding.ws uri="http://www.sqs.com/StockQuoteService"/>
</reference>
<reference name="UnwiredReference">
<!-- the target cannot be determined, that should be an
error-->
<binding.ws/>
</reference>
</component>
<!-- no references and promotion on purpose -->
</composite>
There was discussion concerning various aspects of the proposal, especially surrounding guidance concerning promotion, without
any particular proposal being moved to the floor.
stragglers' roll
<Martin C>
bob roll is at: http://www.oasis-open.org/apps/org/workgroup/sca-assembly/event.php?event_id=16011&day=1193738400
[End of Minutes]
Formatted on 2007-10-30 at 18:20:10 GMT-4
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 177 input lines
edits: Schreiber found the following text-edit commands:
edits: Line 89: bob: s/quorate/quorate with 21 of 33 voting members
edits: Line 91: bob: s/Kile/File
edits: Line 93: bob: s/M:Fred/M:Fred Carter
command-scribe: Line 3: Bob Freund recognized
command-scribe: Schreiber detected that this section was scribed online
citation-detection-irc1: Line 16: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 22: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 26: Check for possible unrecognized nick 'ASSEMBLY-12 '
citation-detection-irc1: Line 27: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 29: Check for possible unrecognized nick 'NEW ISSUE'
citation-detection-irc1: Line 34: Check for possible unrecognized nick 'http'
citation-detection-irc1: Line 41: Check for possible unrecognized nick 'ASSEMBLY-6'
citation-detection-irc1: Line 42: Check for possible unrecognized nick 'http'
edit-substitute: command on line 89 succeeded, changed line 83 from 'quorate' to 'quorate with 21 of 33 voting members'
edit-substitute: command on line 93 succeeded, changed line 85 from 'M:Fred' to 'M:Fred Carter'
edit-substitute: command on line 91 succeeded, changed line 87 from 'Kile' to 'File'
edit-delete: Line 89 was deleted
edit-delete: Line 91 was deleted
edit-delete: Line 93 was deleted
citation-detection-irc1: Line 173: Check for possible unrecognized nick 'callback) '
citation-detection-irc1: Line 184: Check for possible unrecognized nick 'conditions holds '
system: Transformer: SAXON SA 8.9
[End of Schreiber diagnostic output]
← Prev in month
← Prev in thread
Next in thread →
Next in month →