OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-j] ISSUE 119: JAA Conformance Section



Your first suggestion is a good one, but we would need to raise an issue there.

If we consider tools as including anything that either helps author document including annotations or deploy contributions, then these tools could claim to enforce annotation restrictions and thus conform with the spec.  As far as artifacts conforming with the spec., this will depend on the resolution with Java-60 which might define import.java and export.java.

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



Anish Karmarkar <Anish.Karmarkar@oracle.com>

01/12/2009 01:35 AM

To
David Booz/Poughkeepsie/IBM@IBMUS
cc
sca-j@lists.oasis-open.org
Subject
Re: [sca-j] ISSUE 119: JAA Conformance Section





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:booz@us.ibm.com
>
> 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:                
> sca-j@lists.oasis-open.org
>
> 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: aupperle@us.ibm.com
>

---------------------------------------------------------------------
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




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]