Re: [sca-c-cpp] Fw: [sca-c-cpp-comment] Microsoft public review comments onSCA C/C++ implementation model specifications

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

This is my proposed response to this
PR comment.
----------------------------------

The SCA C and C++ TC thanks you for
your review of this material.  In response to your specific points:

1) After consultation with OASIS  TC-admin,
the TC process  requires a redline or detailed change log for a second
or subsequent public review.  You can see a unmarked copy by accessing
the editable source version (http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-cppcni-1.1-spec-cd04.doc
and http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-ccni-1.1-spec-cd04.doc)

2) and 3) These are problems with artifacts
owned by the SCA Assembly TC.  We have passed your comments along
to that TC to be addressed.

4)  The TC had submitted the header
files as part of the CD04 package and had already noticed that they had
not been published.  We have reached an agreement with the OASIS TC-admin
on the proper way to point to these files and have them published.  These
changes will be addressed via issues CCPP-103 (for C++) and CCPP-104 (for
C) which can be tracked via http://www.osoa.org/jira/browse/CCPP-103
and http://www.osoa.org/jira/browse/CCPP-104.
 A new Committee Draft and Public Review will be available shortly.


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

From:	Bryan Aupperle/Raleigh/IBM@IBMUS
To:	sca-c-cpp@lists.oasis-open.org
Date:	03/02/2010 08:17 AM
Subject:	[sca-c-cpp] Fw: [sca-c-cpp-comment] Microsoft public review comments on SCA C/C++ implementation model specifications

---

Forwarding to the TC list. 

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 
----- Forwarded by Bryan Aupperle/Raleigh/IBM on 03/02/2010 08:15 AM -----

From:	Michael Champion <Michael.Champion@microsoft.com>
To:	"sca-c-cpp-comment@lists.oasis-open.org" <sca-c-cpp-comment@lists.oasis-open.org>
Date:	03/01/2010 11:32 PM
Subject:	[sca-c-cpp-comment] Microsoft public review comments on SCA C/C++ implementation model specifications

---

This is Microsoft’s public comment about the following two specifications
under public review per announcement [1]: 
  
-   Service Component Architecture
Client and Implementation Model for C++ Specification Version 1.1
-   Service Component Architecture
Client and Implementation Model for C Specification Version 1.1
  
We have been attempting to review the above specifications, but have been
unable to complete our review due the following problems with the specifications
as published: 
  
1) The revised C and C++ specifications http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-ccni-1.1-spec-cd04.pdf
and http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-cppcni-1.1-spec-cd04.html
include markup to indicate changes but we could not find where the clean
versions are provided. There is enough markup in these documents to make
the document impossible to review in places. 
  
2) The RDDL document for http://docs.oasis-open.org/ns/opencsa/sca/200912
refers to at least two XML Schema documents that are not valid.  For
example the first XML schema listed (http://docs.oasis-open.org/opencsa/sca-assembly/sca-1.1-cd05.xsd)
apparently contains invalid whitespace, and the 5th item (http://docs.oasis-open.org/opencsa/sca-assembly/sca-policy-1.1-intents-definitions-cd03.xsd)returns
“HTTP 404 Not Found” error. 
  
3) The RDDL document for http://docs.oasis-open.org/ns/opencsa/sca/200912
refers to at least one XML Schema document that returns a 404. For example
the 5th XML Schema listed (http://docs.oasis-open.org/opencsa/sca-assembly/sca-policy-1.1-intents-definitions-cd03.xsd)
is not retrievable (404 error). 
  
4) But the biggest obstacle in our reviewing of the specifications is the
fact that the required C/C++ header files are missing from the specifications.
Without being able to review the C/C++ header files, it is impossible to
perform a complete and meaningful review of the specifications. 
  
Sincerely, 
Michael Champion, 
Microsoft Corporation 
  
[1] http://lists.oasis-open.org/archives/tc-announce/201002/msg00005.html