RE: [sca-assembly] NEW ISSUE (v1.1): SCA Runtime Conformance Language & NormativeReferences

[Bryan Aupperle <aupperle@us.ibm.com>]

As an observation, the Test Suite Adaptation
document [1] allows for the use of an alternative test client and states
that the client SHOULD execute testcases through web services to ensure
separation of the test client and the runtime under test [TST10008].  It
goes on to say that a test client MUST be able to start the runtime under
test [TST10009].

As I read this, an implementation MUST
have an external means of invoking services, which implies that am implementation
MUST support some binding other than binding.sca but that this binding
could be vendor or third-party defined (with its own test suite of course).
   

[1] http://docs.oasis-open.org/opencsa/sca-assembly/sca-assembly-1.1-testsuite-adaptation-cd01.pdf

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of
Excellence Application Integration Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

From:	"Konradi, Philipp" <philipp.konradi@siemens.com>
To:	Martin Chapman <MARTIN.CHAPMAN@oracle.com>, "Estefan, Jeff A (3100)" <jeffrey.a.estefan@jpl.nasa.gov>, "sca-assembly@lists.oasis-open.org" <sca-assembly@lists.oasis-open.org>
Date:	11/04/2010 12:08 PM
Subject:	RE: [sca-assembly] NEW ISSUE (v1.1): SCA Runtime Conformance Language & Normative References

---

The proposed resolution sounds reasonable
to me and would adequately adress the concerns raised by Siemens. 
 
An yes Martin is right, the second part of
Siemens comment regarding making support of binding.ws optional and only
binding.sca a must, has been moved to a separate issue (http://www.osoa.org/jira/browse/ASSEMBLY-152).
 
Regards, 
Philipp 
 
From: Martin Chapman [mailto:MARTIN.CHAPMAN@oracle.com]
Sent: Tuesday, November 02, 2010 3:52 PM
To: Estefan, Jeff A (3100); sca-assembly@lists.oasis-open.org
Subject: RE: [sca-assembly] NEW ISSUE (v1.1): SCA Runtime Conformance
Language & Normative References
 
The proposed new text for
4 (only requiring bindings.sca) is a different issue and should not be
confused with the impltype and test adaptation issue.
 
Martin.
 
From: Estefan, Jeff A (3100) [mailto:jeffrey.a.estefan@jpl.nasa.gov]
Sent: 02 November 2010 14:42
To: sca-assembly@lists.oasis-open.org
Subject: [sca-assembly] NEW ISSUE (v1.1): SCA Runtime Conformance Language
& Normative References
 
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.