NEW ISSUE (v1.1): SCA Runtime Conformance Language & NormativeReferences

["Estefan, Jeff A (3100)" <jeffrey.a.estefan@jpl.nasa.gov>]

Raiser:  Jeff Estefan

 

Target:  sca-assembly-1.1-spec-cd06.doc

 

Title:  SCA Runtime Conformance Language & Normative References

 

Description:

 

Add language to the SCA Assembly 1.1 spec to permit an SCA runtime to claim conformance if it (only) supports an implementation type which is described in the manner required by the 2 documents that have now completed public review.

 

Proposal:

 

1.       Add two documents that just completed public review, i.e., Test Suite Adaptation and Implementation Type Documentation Requirements, to Section 1.2 Normative References.  Suggest shorthand reference of [SCA-TSA] and [SCA-IMPLTYPDOC] but open to alternatives.

 

2.       Update Section 12.2 SCA Runtime section as follows (revised Sanjay proposal).  New language in blue, recommended deleted language in strikethrough:

An implementation that claims to conform to the requirements of an SCA Runtime defined in this specification MUST meet the following conditions:

1.      The implementation MUST comply with all statements in Appendix C: Conformance Items related to an SCA Runtime, notably all MUST statements have to be implemented.

2.      The implementation MUST conform to the SCA Policy Framework v1.1 Specification [Policy].

3.      The implementation MUST support at least one implementation type standardized by the OpenCSA Member Section or comply with the following rules for at least one of the other implementation types:

a.      The implementation type is defined in compliance with the SCA Assembly Extension Model (Section 10 9 of the this SCA Assembly Specification).

b.      A document describing the mapping of the constructs defined in the SCA Assembly specification with those of the implementation type is made publicly available to its prospective development community. Such a document should help in understanding how SCA components can be developed using the implementation type, how these components can be configured and assembled together (as instances of Components in SCA compositions). A template for such a document entitled "Implementation Type Documentation Requirements for SCA Assembly Model Version 1.1 Specification" [SCA-IMPLTYPDOC] has been provided by this Technical Committee.  The contents outlined in this document template MUST be completed in order for an implementation type to claim compliance with the SCA Assembly Specification. To get an idea about the purpose and scope of such a document that describes the implementation type, see the Client and Implementation specifications for the implementation types standardized by the OpenCSA Member section.

c.      An adapted version of the SCA Assembly Test Suite for testing the implementation type is created and is made publicly available to its prospective development community. A template for such a document entitled "Test Suite Adaptation for SCA Assembly Model Version 1.1 Specification" [SCA-TSA] has been provided by this Technical Committee.  The contents outlined in this document template MUST be completed in order for an implementation type to claim compliance with the SCA Assembly Specification.

4.      The implementation MUST support one or more binding types.  If only one binding type is supported, it MUST be the default SCA binding type, binding.sca.