OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-j message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [sca-j] Publishing Code artifacts


Big +1

AFAIK we are the first TC to do Java APIs (remember the package name 
discussions?), so this is all going to be new. But if OASIS wants Java 
API standards, these issues would have to be resolved by OASIS.

-Anish
--

On 2/19/2010 5:20 AM, David Booz wrote:
>
> The following needs to be topic of discussion for Monday.  Some of us have
> been discussing this off-list.  I've brought the jist of the discussion to
> the rest of the TC because the issues have broadened and now needs to be
> visible to the community.
>
> 1) Do we want a compiled jar of CAA API classes available publicly, hosted
> by OASIS and published alongside the spec (i.e. it has a stable URI) such
> that a developer could download the jar and use it to compile his own
> application code?
>
> 2) Do we want a source zip of CAA API Java files available publicly, hosted
> by OASIS and published alongside the spec (i.e. it has a stable URI) such
> that a runtime vendor or spec reviewer could download the jar and make
> comments on the Java API itself (since the Java source files are normative
> just like the XML schema files)?
>
> 3) Do we want an unzipped version of CAA API Javadoc available publicly,
> hosted by OASIS and published alongside the spec (i.e. it has a stable URI)
> such that a developer could view the javadoc online?
>
> 4) Do we want a zipped version of the CAA API Javadoc available publicly,
> hosted by OASIS and published alongside the spec (i.e. it has a stable URI)
> such that a developer could download the javadoc for use on his local
> machine? (FWIW, I prefer local javadoc so that I have it when I'm offline,
> which is often).
>
> I think the answer to all of these is yes, which would mean 4 new URIs (in
> addition to the spec documents) for Mary to publish.  I agree with Anish
> that once we have these URIs, we can sprinkle them where-ever we want, in
> the spec document, in the Assembly RDDL, etc.  If we agree on the above
> then it seems like we (probably me) will need to speak with Mary about our
> plan/idea.
>
> I'm mindful of the current controversy in the C/CPP TC (and also the SDO
> TC) over publishing code artifacts and am wary of overloading Mary with new
> ideas, so the TC needs to get clear on what we want to do here and should
> also work with the other TCs which are facing similar issues.
>
> 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:booz@us.ibm.com
>
>
> ---------------------------------------------------------------------
> 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]