OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-assembly message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [sca-assembly] Exit Criteria Incomplete


Since interop can only be demonstrated by supporting binding.ws, I think the Bindings TC need to consider this for its exit criteria. Assuming the Bindings TC satisfies your concerns for interop, the dependency between these two specs would imply no change to the Assembly exit criteria.

Martin.

> -----Original Message-----
> From: Jeff Mischkinsky
> Sent: 28 June 2011 15:53
> To: OASIS Assembly
> Subject: [sca-assembly] Exit Criteria Incomplete
> 
> hi,
> 
> I don't believe the TC has completed its job as required by the
> Charter wrt Exit Criteria - though we certainly have made concrete
> progress towards that goal.
> 
> The SCA Assembly Charter requires:
> "The TC shall define concrete exit criteria that include at least two
> independent offerings that implement and are compliant with the all
> normative portions of specifications and demonstrate interoperability
> and portability as appropriate. Note that these are minimums and that
> the TC is free to set more stringent criteria."
> 
> Last week the Assembly TC adopted exit criteria as follows:
> The Concrete Exit Criteria for the SCA Assembly V1.1 specification are
> that there shall be at least 2 independent SCA runtimes each of which
> are compliant with all normative portions of the specification as
> described in Section 12.2 of the SCA Assembly V1.1 specification
> 
> We have completed the first part and met the minimums required by the
> Charter wrt number of offerings, but we have NOT YET set criteria for
> the second part - "demonstrating interoperability and portability as
> appropriate".
> 
> I, and others, have struggled unsuccessfully so far, with words that
> would be satisfactory. Nevertheless, the TC still needs to do that
> before it can proceed to vote on whether those criteria have in fact
> been met.
> 
> EXAMPLES might include such things as: The easiest thing in my mind is
> demonstrate that the 2 impls pass the test suite with 100% (98% or 95%
> or nnn%) success. Other examples might be provide output that shows
> that 98.34% of TA's have been successfully tested. I'm sure there are
> lots of other possibilities.
> 
> 
>   NOTE: Adopting those criteria is a different act from VOTING that
> the criteria have been met. As we have discussed many, many times -
> making that decision is a judgment that each voting member of the TC
> will have to make when the time comes.
> 
>    Also, please note that there is nothing in the above suggestions as
> to who does the demonstrating. It could be a the provider of the
> offering. it could be another TC member. It could be an interested
> third party.
> 
> cheers,
>    jeff
> --
> Jeff Mischkinsky
> 	jeff.mischkinsky@oracle.com
> Sr. Director, Oracle Fusion Middleware 				+1(650)506-
> 1975
> 	and Web Services Standards           			500 Oracle
> Parkway, M/S 2OP9
> Oracle								Redwood Shores, CA 94065
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  Follow this link to all your TCs in OASIS at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]