Re: [sca-j] Issue 119: YAAP version 2

[David Booz <booz@us.ibm.com>]

I think there's a few typos below.....the first is something I thought we changed on the call.

Other than that, it looks good to me.


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:booz@us.ibm.com

Anish Karmarkar <Anish.Karmarkar@oracle.com> wrote on 03/20/2009 03:02:10 PM:

> [image removed]
>
> [sca-j] Issue 119: YAAP version 2
>
> Anish Karmarkar
>
> to:
>
> OASIS Java
>
> 03/20/2009 03:03 PM
>
> Based on today's telcon feedback, here is version 2.
>
> 1) For JCAA Spec add a new conformance section:
>
> Conformance
>
> The XML schema pointed to by the RDDL document at the namespace URI,
> defined by this specification, are considered to be authoritative and
> take precedence over the XML schema defined in the appendix of this
> document.
>
> [Move the agreed upon statement about SCA Java interface/class
> precedence from a different issue here]
>
> There are three categories of artifacts that this specification defines
> conformance for: SCA Java XML Document, SCA Java Class and SCA Runtime.
>
> SCA Java XML Document
>
> An SCA Java XML document is an SCA Composite Document, or an SCA
> ConstrainingType Document, as defined by the SCA Assembly specification
> Section 13.1 [SCA-ASM], that uses the <interface.java> element. Such an
> SCA Java XML document MUST be a conformant SCA Composite Document or a
> SCA ConstrainingType Document, as defined by [SCA-ASM], and MUST comply
> with the requirements specified in Section 3 of this specification.
>
> SCA Java Class
>
> An SCA Java Class is a Java class or interface that complies with Java
> version 1.5 and MAY include annotations and APIs defined in this
> specification. An SCA Java Class that uses annotations and APIs defined
> in this specification MUST comply with the requirements specified in
> this specification for those annotations and APIs.
>
> SCA Runtime
>
> The APIs and annotations defined in this specification are meant to be
> used by Java-based client and implementation models in either partial or
> complete fashion. A Java-based client and implementation model
> specification that uses this specification specifies which of the APIs
> and annotations defined here are used. The APIs and annotations an SCA
> Runtime has to support depends on which Java-based client and
> implementation model specification the runtime supports. For example,
> see the SCA Java Client and Implementation Specification [SCA-JCI].
>

The above text uses 'client and implementation' when I think you mean
'component implementation', i.e., what we erroneously refer to as a C&I
spec.

> An implementation that claims to conform to this specification MUST meet
> the following conditions:
> 1.The implementation MUST meet all the conformance requirements defined
> by the SCA Assembly Model Specification [SCA-ASM].
> 2.The implementation MUST support <interface.java> and MUST comply with
> all the normative statements in Section 3.
> 3. The implementation MUST reject an SCA Java XML Document that does not
> conform to the sca-interface-java.xsd schema.
> 4.The implementation MUST support and comply with comply with all the
> normative statements in Section 10.
>
typo 'and comply with comply with'

>
>
> 2) For JCI Spec add a new conformance section:
>
> Conformance
>
> The XML schema pointed to by the RDDL document at the namespace URI,
> defined by this specification, are considered to be authoritative and
> take precedence over the XML schema defined in the appendix of this
> document.
>
> There are three categories of artifacts that this specification defines
> conformance for: SCA Java Component Implementation Composite Document,
> SCA Java Component Implementation Contribution Document and SCA Runtime.
>
> SCA Java Component Implementation Composite Document
>
> An SCA Java Component Implementation Composite Document is an SCA
> Composite Document, as defined by the SCA Assembly specification Section
> 13.1 [SCA-ASM], that uses the <implementation.java> element. Such an SCA
> Java Component Implementation Composite Document MUST be a conformant
> SCA Composite Document, as defined by [SCA-ASM], and MUST comply with
> the requirements specified in Section 9 of this specification.
>
> SCA Java Component Implementation Contribution Document
>
> An SCA Java Component Implementation Contribution Document is an SCA
> Contribution Document, as defined by the SCA Assembly specification
> Section 13.1 [SCA-ASM], that uses the contribution metadata extensions
> defined in Section 10. Such an SCA Java Component Implementation
> Contribution document MUST be a conformant SCA Contribution Document, as
> defined by [SCA-ASM], and MUST comply with the requirements specified in
> Section 10 of this specification.
>
> SCA Runtime
>
> An implementation that claims to conform to this specification MUST meet
> the following conditions:
>
> 1. The implementation MUST meet all the conformance requirements defined
> by the SCA Assembly Model Specification [SCA-ASM].
> 2. The implementation MUST reject an SCA Java Composite Document that
> does not conform to the sca-implementation-java.xsd schema.
> 3. The implementation MUST reject an SCA Java Contribution Document that
> does not conform to the sca-contribution-java.xsd schema.
> 4. The implementation MUST meet all the conformance requirements,
> specified in 'Section ZZZZ Conformance', from the SCA Java Common
> Annotations and APIs Specification [JCAA].
> 5. This specification includes all the APIs and annotations defined in
> the Java Common Annotations and APIs Specification [JCAA], therefore
> the implementation MUST comply with all the statements in Appendix YYY:
> Comformance Items of [JavaCAA], notably all mandatory statements have to
> be implemented.
> 6. The implementation MUST comply with all statements related to an SCA
> Runtime, specified in 'Appendix XXX: Conformance Items' of this
> specification, notably all mandatory statements have to be implemented.
>
> -Anish
> --
>
>
> ---------------------------------------------------------------------
> 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
>