Letter to OpenCSA TCs on conformance and dependancies

Hi,
On behalf of the OpenCSA Liaison Subcommittee, i was asked to forward  
the following to each of the OpenCSA TCs for consideration and  
discussion.

Within the next month or so we anticipate commencing public reviews  
for many of the SCA specifications.

The TC process requires that each specification at Public Review,  
Committee Spec and OASIS Standard level, contain a conformance section  
listing one or more conformance clauses that define how to conform to  
the specification, or parts thereof.  Like any other part of a  
specification, the conformance section should be complete prior to the  
public review. Also worth noting is that substantive changes to a  
conformance section after a public review, like any other substantive  
changes to a specification, will require a subsequent public review.

Many of the SCA specifications have cross dependencies on each other,  
and in some cases it may not be possible to conform to a specification  
in its own right without reference to another “containing”  SCA  
specification. For example, it may not be possible to conform to the  
SCA Policy specification without requiring conformance to the SCA  
Assembly spec as well.

In order to build a complete picture and understand the cross  
conformance dependencies, the Liaison SC would like each TC to provide  
a list of other SCA specifications that in their opinion are required  
for conformance to each of their own specs.  We can then use this list  
to ensure that the conformance sections in each specification is  
saying the right thing.

Given that we are closing in on the public reviews we would like this  
information to be provided by 21 Jan 2009.

cheers,
  Jeff Mischkinsky, Sanjay Patil - LSC Chairs
>

--
Jeff Mischkinsky			          		
Director, Oracle Fusion Middleware 				+1(650)506-1975
	and Web Services Standards           			500 Oracle Parkway, M/S 2OP9
Oracle								Redwood Shores, CA 94065