Further you can't even get a 'cleanroom' api design if you've downloaded
the specs. There is NO notice at their web site that the specs may only
be used 'for internal evaluation purposes only'. Only once you have
downloaded them is this information even visible!

I have spent 10 years developing Jini-like technology. To me it is
important that something like Jini become widely deployed and supported
by as many implemenations as possible. It is an enabling infrastructure
and I doubt that Sun can benefit from keeping a strangle-hold over it in
the way that MS has over other technologies they have deployed.

I hope that there is a way that classpath can undertake a meaningful
development of this type of technology. I am willing to devote my
resources to the development, but there do seem to be some legal
framework issues that need to be laid to rest.

ciao,
Christine Tomlinson

Paul Fisher wrote:

> "John Keiser" <[EMAIL PROTECTED]> writes:
>
> > We *can* create a cleanroom implementation if we wish, we just have
> > to abide by the above restrictions.
>
> Sun says we can only create a clean room implementation if we release
> the clean room version under the terms of the JTPL (see the JTPL
> licensing FAQ).
>
> Sun's taking the stance that an API can be copyrighted.  This issue
> hasn't been 100% settled in the courts.
>
> --
> Paul Fisher * [EMAIL PROTECTED]

Reply via email to