We'll produce CD05 versions. A
few questions. Should these be identified as CD05 /PR03 or just CD05?
Should the markup just cover the front-matter change or full redline back
to CD03/PR01? Should the date in the front matter be the same as
CD04 (which is the date the TC approved the content) or a later date (reflecting
when we agreed on how to point to the header files)?
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:
From:
Mary McRae <>
To:
Bryan Aupperle/Raleigh/IBM@IBMUS
Cc:
,
Date:
03/03/2010 12:21 AM
Subject:
Re: [sca-c-cpp] Re: [sca-j] Publishing
Normative Java artifacts
Hi Bryan,
Since CD 04 has already been uploaded and announced
for Public Review, these changes require a new set of URIs. The cleanest
thing would be a new version (CD05) but a TC vote isn't really necessary.
As an alternative we could identify this set of files as cd04a or something,
but we can't overwrite the existing files at the cd04 location.
How would the TC like to proceed?
Mary
On Mar 1, 2010, at 1:51 PM, Bryan Aupperle wrote:
I have created new versions of the packages. The only change to the
documents is the front matter (adding the new C++ Artifacts or C Artifacts
with link). The zip files each contain the appropriate new zip containing
the header files.
Link for the updated C++ package: http://www.oasis-open.org/apps/org/workgroup/sca-c-cpp/download.php/36626/sca-cppcni-1.1-spec-cd04.zip
Link for the updated C package: http://www.oasis-open.org/apps/org/workgroup/sca-c-cpp/download.php/36629/sca-ccni-1.1-spec-cd04.zip
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:
From:
Mary McRae <>
To:
Bryan Aupperle/Raleigh/IBM@IBMUS
Cc:
,
,
David Booz/Poughkeepsie/IBM@IBMUS
Date:
02/26/2010 11:54 AM
Subject:
[sca-c-cpp] Re: [sca-j] Publishing Normative
Java artifacts
Great. Will you be creating a new version for public review then? (And
don't forget to add the resources to the appropriate namespace document(s))
Mary
On Feb 26, 2010, at 11:34 AM, Bryan Aupperle wrote:
This approach would work for C++ and C as well with the following
changes/simplifications:
- Only the zip archive of the APIs would be needed and the section would
be named C++ Artifacts or C Artifacts as appropriate.
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:
----- Forwarded by Bryan Aupperle/Raleigh/IBM on 02/26/2010 11:30 AM -----
From:
David Booz/Poughkeepsie/IBM@IBMUS
To:
Cc:
Date:
02/26/2010 11:20 AM
Subject:
[sca-j] Publishing Normative Java artifacts
Hi Mary,
Here's the proposal I mentioned in the other email thread. Some
explanation is necessary, which I've tried to provide. Speaking in
person
might be easier, so I'm happy to do it if necessary.
I've attached the first two pages of our CAA spec to illustrate, with
change marks that embody our proposal. Please ignore the line numbers,
they
are not part of the proposal.
The SCA-J TC has voted a new CD04 (which I have not sent to you yet), and
as part of that vote the SCA-J TC would also like to publish 4 additional
items:
1) A zip archive of the Java APIs. This is Java source code and is
considered normative. I've added a new section called "Java
Artifacts"
after "Declared XML Namespace(s)" which has a URI to this proposed
new zip
file.
2) A jar archive of compiled Java code. Developers and implementers of
the
spec would find this very handy. It is non-normative, so I added a URI
for
it to the "Related Work" section.
3) A zip archive of the Javadoc for the Java APIs. This is something
that
developers and implementers of the spec would find very handy. It is a
set
of HTML files that can be downloaded and exploded by developers and spec
implementers to use as reference material when writing Java code that uses
the APIs. The reason for downloading the zip is so that the material
is
available when not connected to the internet. This zip is non-normative
so
I've added a URI for it to the "Related Work" section.
4) An exploded (or online) version of the Javadoc for the API. Again,
this
is useful to developers and spec implementers, but would be hosted online
by OASIS. This material is non-normative so I've added a URI for it in
the
"Related Work" section.
(See attached file: sca-javacaa-1.1-spec-cd04_frontonly.doc)
The above is all in addition to the Word, HTML, PDF of the spec itself,
the
XML schema files for the spec, and updates to the namespace RDDL that
points to all of this stuff.
thanks
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:---------------------------------------------------------------------
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
<sca-javacaa-1.1-spec-cd04_frontonly.doc>
