Bryan,
Very good proposal.
Two comments:
1) The definition of SCA runtime,
"· SCA runtime, which provides a container for SCA components and
potentially tools for authoring SCA artifacts, component descriptions
and/or runtime operation."
I think, would make sense to have it be defined in the assembly spec and
be pointed to from other specs.
2) I don't quite see tools/artifacts claiming conformance to the common
annotations and API spec, which contains functionality available for C&I
specs to include-by-reference a-la-carte. It is specific C&Is such as
Java C&I that tools would conform to.
-Anish
--
David Booz wrote:
> http://www.osoa.org/jira/browse/JAVA-119
>
> Dave Booz
> STSM, BPM and SCA Architecture
> Co-Chair OASIS SCA-Policy TC and SCA-J TC
> "Distributed objects first, then world hunger"
> Poughkeepsie, NY (845)-435-6093 or 8-295-6093
> e-mail:
>
> Inactive hide details for Bryan Aupperle---01/09/2009 11:35:23
> AM---Target: Java CAA Description: The CAA specification is misBryan
> Aupperle---01/09/2009 11:35:23 AM---Target: Java CAA Description: The
> CAA specification is missing a conformance section which
>
>
> From:
> Bryan Aupperle/Raleigh/IBM@IBMUS
>
> To:
>
>
> Date:
> 01/09/2009 11:35 AM
>
> Subject:
> [sca-j] NEW ISSUE: JAA Conformance Section
>
> ------------------------------------------------------------------------
>
>
>
>
> Target: Java CAA
>
> Description: The CAA specification is missing a conformance section
> which should identify conformance targets and make conformance claims
> for each target.
>
> Proposal: Add as section 11:
>
> *1 Conformance*
>
> This section specifies the conformance targets of this specification and
> the requirements that apply to each of them.
>
> *1.1 Conformance Targets*
>
> The conformance targets of this specification are:
>
> · *SCA runtime*, which provides a *container* for SCA components and
> potentially *tools* for authoring SCA artifacts, component descriptions
> and/or runtime operation .
> · *SCDL documents*, which describe SCA artifacts, and specific
> *elements* within these documents. (This is dependent on Java-60)
>
> *Conformance Claims*
>
> A claim of conformance with this specification MUST meet the following
> requirements:
>
> · It MUST state which conformance targets it implements.
>
> *SCA Runtime*
>
> An implementation conforms to this specification if it meets the
> following conditions:
>
> It MUST conform to the SCA Assembly Model Specification *[ASSEMBLY]* and
> the SCA Policy Framework *[POLICY]*
>
> It MUST implement the SCA Java API defined in section Java API.
>
> It MUST implement the mapping between Java and WSDL 1.1 [WSDL11] as
> described in WSDL to Java and Java to WSDL.
>
> It MUST support Java contributions as defined in XXX. (This is dependent
> on Java-60)
>
> It MUST support source file annotations as defined in Java Annotations
> and Policy Annotations for Java.
>
> *1.2 SCDL Documents* (This is dependent on Java-60)
>
> A SCDL file conforms to this specification if it meets the following
> conditions:
>
> It MUST conform to the SCA Assembly Model Specification *[ASSEMBLY]*.
>
> It conforms to the requirements in section [Contributions].
>
> *1.3 Extensions*
>
> [What extention points do we want to identify?].
>
>
> Bryan Aupperle, Ph.D.
> STSM, WebSphere Enterprise Platform Software Solution Architect
>
> Research Triangle Park, NC
> +1 919-254-7508 (T/L 444-7508)
> Internet Address:
>
