sca-c-cpp message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [sca-c-cpp] Public Review of SCA Client and Implementation Model for Cand C++ Specifications - 15 day review
- From: Bryan Aupperle <aupperle@us.ibm.com>
- To: Mary McRae <mary.mcrae@oasis-open.org>
- Date: Mon, 22 Feb 2010 14:52:21 -0500
We included these files as part of what
we approved as the CD/PR. If we need to have an explicit vote for
the record, we can do so. It was the TC's intent that this PR include
the header files. A separate document seems like a bit excessive
all it would have would be a list of files that map very naturally to the
API as defined in the spec. If you think the mapping needs to be
explicitly identified, it would make much more sense to call out in the
spec the specific file(s) that apply to each part of the API as described.
Based on today's call, I believe the
Java TC will be making a specific proposal on how to package and reference
code artifacts The Java situation is a bit more complex than for C/C++
but I have no problem following a consistent model.
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:
| Mary McRae <mary.mcrae@oasis-open.org>
|
To:
| Bryan Aupperle/Raleigh/IBM@IBMUS
|
Cc:
| Jeff Mischkinsky <jeff.mischkinsky@oracle.com>,
sca-c-cpp@lists.oasis-open.org
|
Date:
| 02/22/2010 12:53 PM
|
Subject:
| Re: [sca-c-cpp] Public Review of SCA
Client and Implementation Model for C and C++ Specifications - 15 day review |
Seems like they should be included as a Normative Reference,
listed as an artifact in the namespace document, noted on the cover page
of the spec ... something. Without an explicit reference how would anyone
know where to find them?
I'm happy to work with a team of representatives from
each TC or the liaisons subcommittee to work out something that will be
applied consistently across all of the TCs.
The next question would be if that code is authoritative,
what standing does it have within the TC? Shouldn't there be a document
that describes the artifacts and that document, along with the artifacts
themselves, voted and approved at each stage? Submitted for public review?
Mary
On Feb 22, 2010, at 12:37 PM, Bryan Aupperle wrote:
They are not explicitly referenced by name or URI, but there is a statement
in the conformance section stating that there are source code artifacts
and that they are authoritative over the spec text relative to the API
definition.
If necessary, it would be reasonable to have them put in a zip and have
a link in some appropriate place in the specification.
I know the Java TC is discussing essentially the same concern.
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
Thanks Bryan.
Sorry, but more questions. Are they actually referenced in the specification
somewhere or noted in the namespace document? If not, is there some other
document that will be describing them/referencing them? How is someone
to know that they exist or should be used? Are they part of the specification
or some ancillary support material with no official standing within the
TC?
I have no objections to uploading them per se, but if they aren't part
of the specification and not referenced anywhere it doesn't make much sense.
Mary
On Feb 18, 2010, at 2:10 PM, Bryan Aupperle wrote:
It is a file in C or C++ that is used to define an API. A header
file normally has an extension of .h and is used when compiling a program.
I.e. a machine readable version of an API definition.
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
I'm going to now ask a stupid question (sorry!): What's a header file?
Mary
On Feb 18, 2010, at 1:31 PM, Bryan Aupperle wrote:
The zip packages we sent for this PR included some header files. If
I look at http://docs.oasis-open.org/opencsa/sca-c-cpp/
I do not see any of the header files. What do we need to do to get the
header files published?
Thanks.
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 OASIS members, Public Announce Lists:
The OASIS Service Component Architecture / C and C++ (SCA-C-C++) TC has
recently approved the following specifications as a Committee Draft and
approved them for public review:
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
The public review starts today, 15 February 2010, and ends 2 March 2010.
This specification was previously submitted for a 60-day public review
on 24 April 2009[1]; this 15-day review is limited in scope to changes
made from the previous review. All changes are marked.
This is an open invitation to comment. We strongly encourage feedback from
potential users, developers and others, whether OASIS members or not, for
the sake of improving the interoperability and quality of OASIS work.
More non-normative information about the specification and the technical
committee may be found at the public home page of the TC at:
http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=sca-c-cpp.
Comments may be submitted to the TC by any person through the use of the
OASIS TC Comment Facility which can be located via the button marked "Send
A Comment" at the top of that page, or directly at:
http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=sca-c-cpp.
Submitted comments (for this work as well as other works of that TC) are
publicly archived and can be viewed at:
http://lists.oasis-open.org/archives/sca-c-cpp-comment/.
All comments submitted to OASIS are subject to the OASIS Feedback License,
which ensures that the feedback you provide carries the same obligations
at least as the obligations of the TC members.
The specification documents and related files are available here:
Service Component Architecture Client and Implementation Model for C++
Specification Version 1.1
Editable Source:
http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-cppcni-1.1-spec-cd03.doc
PDF:
http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-cppcni-1.1-spec-cd03.pdf
HTML:
http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-cppcni-1.1-spec-cd03.html
Namespaces:
http://docs.oasis-open.org/ns/opencsa/sca/200903
http://docs.oasis-open.org/ns/opencsa/sca-c-cpp/cpp/200901
Service Component Architecture Client and Implementation Model for C Specification
Version 1.1
Editable Source:
http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-ccni-1.1-spec-cd04.doc
PDF:
http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-ccni-1.1-spec-cd04.pdf
HTML:
http://docs.oasis-open.org/opencsa/sca-c-cpp/sca-ccni-1.1-spec-cd04.html
Namespaces:
http://docs.oasis-open.org/ns/opencsa/sca/200903
http://docs.oasis-open.org/ns/opencsa/sca-c-cpp/cpp/200901
OASIS and the SCA-C-C++ TC welcome your comments.
Mary P McRae
Director, Standards Development
Technical Committee Administrator
OASIS: Advancing open standards for the information society
email: mary.mcrae@oasis-open.org
web: www.oasis-open.org
twitter: @fiberartisan #oasisopen
phone: 1.603.232.9090
[1] http://lists.oasis-open.org/archives/tc-announce/200904/msg00011.html
---------------------------------------------------------------------
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]