Use Advanced Search to search the entire archive.
[jsr363-experts] Re: Specification not ready for a release today
- From: Werner Keil <
>
- To: "
" <
>
- Subject: [jsr363-experts] Re: Specification not ready for a release today
- Date: Thu, 18 Dec 2014 12:05:21 +0100
First and foremost it would confuse members of the EC or others that think
in "Spec" and "RI/TCK";-)
Several JSRs like Servlets, Portlets or others call the artifact that
manifests the spec "-api.jar" so do we, it doesn't matter, that some also
provide an SPI, since we currently don't fine grain it like MEEP 8 or most
OSGi driven projects.
So API stands for the manifestation of the Spec, thus calling it "another
API" (we define) in the spec would irritate especially those familiar with
the JCP.
There's a chapter "Other API" that refers to external projects and JSRs,
there it is OK. So it's called "Other RI elements" now.
All references to EG Members are also in the mentioned introduction chapter.
Those to 275 and 108 were always there.
Until PMO publishes the official access point on jcp.org, please check
https://java.net/projects/unitsofmeasurement/downloads there's one frozen
download with the EDR file and a "Snapshot" that could change more
frequently.
Werner
On Thu, Dec 18, 2014 at 3:47 AM, Martin Desruisseaux <
>
wrote:
>
>
Le 18/12/14 04:51, Werner Keil a écrit :
>
> A few phrases like "non-standard API" are wrong, as there is just one
>
> API, so I'll change that to "...Reference Implentation" or where it
>
> was a separate headline call it appropriately, something like "other
>
> RI elements".
>
>
Okay for changing the sentence. But I'm not sure two understand "there
>
is just one API"... To me there is two API: the standardized one in
>
javax.measure packages, and an other API (the RI one) extending the
>
standard one.
>
>
Martin
>
>