Re: [sca-assembly] ISSUE 237: Remove sca-1,1.xsd content

[Bryan Aupperle <aupperle@us.ibm.com>]

During the discussion to open this issue
last week, there were some comments towards potential resolutions.

Martin suggested removing all of Appendix
A (copies of the schema files) since it is neither normative or authoritative.
 The only drawback I see to this is that it forces a reader to open
an external file to lookt at any schema specifics.  This could be
a problem if the reader is disconnected and has not downloaded the schemas.
 It does have the advantage of not having to duplicate the application
of any schema changes during editing.  I really do not have strong
feelings either way (but if we remove Appendix A completely, we should
formally communicate this to the other TCs for consideration of a similar
action).

Anish, pointed out that this is only
a partial fix to the problem.  I agree, but I was only truing to limit
the impact of spec text changes caused by new CDs from the other TCs (i.e.
fewer things to forget).  We still have to work out an acceptable
solution to updating sca-1.1-cdxx.xsd as needed.  We could use rev
levels of the schema as needed and keep what is posted internally consistent
and then suggest using an extension of the Designated Cross Reference process
when the set of specs go to CS.  But if anyone has a better suggestion,
please put it on the table.

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of
Excellence Application Integration Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com

From:	Bryan Aupperle/Raleigh/IBM@IBMUS
To:	sca-assembly@lists.oasis-open.org
Date:	07/19/2010 08:59 AM
Subject:	[sca-assembly] NEW ISSUE: Remove sca-1,1.xsd content

---

Target: Assembly Spec. CD05 Rev 1

Description: TC Admin. has noted that our current manner of handling schema
revisions has problems (i.e. artifacts appearing publically with a CDXX
destination before the appropriate TC has approved that CD).  One
of the reasons we have been using the current procedure is that the Assembly
spec lists the contents of sca-1.1-cdxx.xsd in Appendix A.  This particular
schema  simply includes all the other schema in the main SCA namespace.
 But this means that since the Assembly TC tends to approve a CD of
the Assembly spec before the other SCA TCs vote CDs of the specs they own
that impact the main SCA namespace, if we follow the direction for work-in-progress
schema file naming that TC Admin. suggests, the Assembly spec would be
quickly out of data. 

Proposal: Remove the content of sca-1.1-cdxx.xsd from Appendix A and replace
it with:  sca-1.1-cdxx.xsd is provided for convenience.  It  contains
<include/> elements for each of the schema files that contribute
to the http://docs.oasis-open.org/ns/opencsa/sca/200912
namespace. 

Bryan Aupperle, Ph.D.
STSM, WebSphere Enterprise Platform Software Solution Architect
WW Center of Excellence for Enterprise Systems & Banking Center of
Excellence Application Integration Architect

Research Triangle Park,  NC 
+1 919-254-7508 (T/L 444-7508)
Internet Address: aupperle@us.ibm.com