sca-assembly message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: [ASSEMBLY 252] (v1.1): SCA Runtime Conformance Language & NormativeReferences - Alternative Proposal
- From: Mike Edwards <mike_edwards@uk.ibm.com>
- To: "OASIS Assembly" <sca-assembly@lists.oasis-open.org>
- Date: Tue, 9 Nov 2010 11:16:09 +0000
Folks,
I'd like to propose an alternative proposal
to resolve this issue, that differs from the original proposal in not changing
the conformance
requirements relating to bindings, which
are not dealt with by the "Implementation
Type Documentation Requirements" and
"Test Suite Adaptation" documents.
I have also cleaned up the wording of item #3.
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].
2. Update
Section 12.2 SCA Runtime section as follows.
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 mandatory statements listed in table
Mandatory Items in Appendix C: Conformance Items, related to an SCA Runtime.
2. The
implementation MUST conform to the SCA Policy Framework v1.1 Specification
[Policy].
3. The
implementation either MUST support at least one implementation type standardized
by the OpenCSA Member Section or MUST comply with the following rules for
at least one other implementation type:
a. The
implementation type is defined in compliance with the SCA Assembly Extension
Model (Section 10 9 of the SCA Assembly Specification).
b. A
document describing the mapping of the constructs defined in the SCA Assembly
specification with those of the implementation type exists and is made
available to its prospective user community. Such a document describes
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). The form and content of such a document
are described in the specification "Implementation Type Documentation
Requirements for SCA Assembly Model Version 1.1 Specification" [SCA-IMPLTYPDOC].
The contents outlined in this specification template MUST be provided
in order for an SCA runtime to claim compliance with the SCA Assembly Specification
on the basis of providing support for that implementation type. An example
of a document that describes an implementation type is the "SCA POJO
Component Implementation Specification Version 1.1" [SCA-Java].
c. An
adapted version of the SCA Assembly Test Suite which uses the implementation
type exists and is made available to its prospective user community. The
steps required to adapt the SCA Assembly Test Suite for a new implementation
type are described in the specification "Test Suite Adaptation for
SCA Assembly Model Version 1.1 Specification" [SCA-TSA]. The
requirements described in this specification MUST be met in order for an
SCA runtime to claim compliance with the SCA Assembly Specification on
the basis of providing support for that implementation type..
4. The
implementation MUST support binding.sca and MUST support and conform to
the SCA Web Service Binding Specification v 1.1.
Yours, Mike.
Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014 Mobile: +44-7802-467431
Email: mike_edwards@uk.ibm.com
Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number
741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6
3AU
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]