Scheduled SCA Assembly Conf Call (Conference Call) | |
Name | Scheduled SCA Assembly Conf Call (Conference Call) |
Time | Tuesday, 26 March 2013, 11:00am to 12:00pm EDT
(Tuesday, 26 March 2013, 03:00pm to 04:00pm UTC) |
Description |
TC teleconference |
Minutes |
Draft Minutes SCA Assembly TC Meeting 29th January 2013
Attendees:
Oracle Chapman, Martin
IBM Edwards, Mike
IBM Booz, David
TIBCO Software Inc. Johnson, Eric
Individual Marino, Jim
SAP AG Patil, Sanjay
IBM Aupperle, Bryan
IBM Kaiser, Mike
Oracle Karmarkar, Anish
Oracle Mischkinsky, Jeff
Oracle Pilz, Gilbert
TIBCO Software Inc. van der Rijn, Danny
Scribe: Mike Edwards
Meeting 6/10 voting members = quorate
Item 1 Agenda Bashing
No changes
Item 2 Approval of Minutes
https://lists.oasis-open.org/archives/sca-assembly/201302/msg00002.html
Martin: We need to correct the date to 2013
Minutes are accepted with change of date to 2013.
Item 4 Discussion of Future of the SCA Assembly TC
Bryan: The flurry of recent activity should be allowed to play out
- the Java TC may have the longest running activity to complete
Anish: Yes, need to see how the submissions play out
- not motivated to do a lot of work
Jeff: I agree with Anish
Jim: I am motivated to complete stuff
anish: gartner report http://www.gartner.com/id=1660515
anish: ... and that was in 2011
Jim M: Yes and Gartner has an excellent track record of predicting new technologies. Seriously, we have received excellent feedback from people using SCA
Eric: I have a question - where were the exit criteria
anish: i'm not suggesting that gartner is always right. And i was hoping to prove them wrong. That was in 2011. We have gotten a lot of excellent feedback too. But I was hoping to see a very widely implemented standard
Jim M: me too
& there is nothing to say that we have to abide by the decision of the other TCs in order for the Assembly TC to make its decision on the conformance of some runtime?
Jim M: there are four open source implementations already
Bryan: For Policy & Bindings, I think we are obliged to accept the judgement of the relevant TCs
for the implementation language, things are more nuanced
Martin: From an Assembly TC perspective, providing there are 2 conforming impls, including the flexiblity about the implementation language, then that is fine. There is a separate question about the grouping of specifications and the need to advance them together, when they are intertwined
Jim: The flexibility is there and there is an argument that Assembly can progress
anish: i know of three, which is the 4th one?
Jeff: It does make sense to view the specs as a set
Eric: I don't see where it says who judges the conformance to a particular implementation language spec
Mike: I dont think that it does say, but for the ones belonging to one of the other TCs it seems more logical to let them make the judgement
Danny: We're in a bind - my read of the intention of the acceptance language is 2 things 1) get the specs out the door = 2 conformant impls 2) can't get the language specs "out the door" unless there are 2 impls for each spec
- once out the door, any runtime can claim conformance in the way stated for some random language
Danny; we don't need to play strict attention to the language expressed
Danny: We should only keep the Assembly TC going for the purpose of getting a 2nd implementation - and not for any other purpose
Eric: I'm agreeing with Danny
MartinC : my poor eventing work
MartinC : down the tubes
Anish: I agree with only continuing for purposes of getting to Committee Spec status
anish: i know, we did spend a lot of time/effort on it. Oh well. Sigh.
Danny: We could raise the bar for a new issue, for example.
Danny moves that the committee announce its attention to remain open for a time for the purpose of accepting new conformant implementations and not for changing the specification materially.
Mike Kaiser seconds
Martin: What happens if there is a requirement for maintenance - if a problem is reported?
- we should be interested in maintenance.
Danny: not sure I intend to cover maintenance - we are only concerned with getting to Committee Specification state
once we get there, this motion can expire
Anish: the motion will expire when someone actually tries to do something
- I'm not sure that the motion is very meaningful in that the TC is already not doing stuff
Jeff: If I vote no, what does that mean
- I think this motion is irrelevant
Danny: It was a means of putting a stake in the ground
Danny withdraws the motion
Item 5. Fabric3 SCA Conformance claim
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00000.html
discussion
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00009.html
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00010.html
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00011.html
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00012.html
MartinC : https://lists.oasis-open.org/archives/sca-assembly/201108/msg00047.html
Bryan: Assembly TC already accepted that Fabric3 conforms to the Assembly Model spec, as in the minutes above
Mike: So it seems that Assembly TC should wait for the other TCs to pass judgement on the claims for conformance against their specs.
...which brings us to the date of the next meeting
Item 6 Date of next meeting
May 7th
agreed
Item 7 AOB
None
COB |
Agenda |
1. Intro
Roll call
Scribe confirmation
Agenda bashing
2. Approval of minutes of previous SCA-Assembly TC meeting
https://lists.oasis-open.org/archives/sca-assembly/201302/msg00002.html
3. Action Items
None
4. Discussion of Future of the SCA Assembly TC
Consideration following the failed vote to close the TC
5. Fabric3 SCA Conformance claim
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00000.html
discussion
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00009.html
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00010.html
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00011.html
https://lists.oasis-open.org/archives/sca-assembly/201303/msg00012.html
6. Date of Next Meeting
7. AOB |
Submitter | Dr. Mike Edwards |
Group | OASIS Service Component Architecture / Assembly (SCA-Assembly) TC |
Access | This event is visible to OASIS Service Component Architecture / Assembly (SCA-Assembly) TC and shared with
|