incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Craig L Russell <Craig.Russ...@Sun.COM>
Subject Re: Jini?
Date Thu, 10 Aug 2006 02:33:38 GMT
I'd like to point out that Apache does have tolerance for "brand  
names" coming in from the outside, in particular "J-word projects"  
from Sun.

Java(TM) Data Objects a.k.a. JDO is an official Apache project [1].

JDO is not trademarked but the name is well-known in its space. The  
Apache JDO project includes the official API for both JSR-12 and  
JSR-243; and the official TCK for both JSRs.

Sun donated JDO to Apache for continued development, and Apache JDO  
released the API and TCK according to the official JCP rules, under  
the Apache license.

There is room for development of a JDO implementation as an Apache  
project, but it seems more likely that other Apache projects will  
provide a JDO implementation outside of the Apache JDO project. (e.g.  
OpenJPA or Cayenne might well provide a JDO-compliant interface, just  
as they might offer a JPA-compliant interface).

There is precedent for Apache adopting Jini as a project, regardless  
of whether you are talking about "just an implementation" or "the  
official Jini".



On Aug 7, 2006, at 11:13 AM, Jim Hurley wrote:

> On Aug 7, 2006, at 12:19 PM, Sanjiva Weerawarana wrote:
>> So whatever happened to the Jini proposal?? I just remembered that  
>> there
>> was a lot of discussion but don't recall the conclusion.
> Sorry - we hit a snag around the name, and have been working to
> try and get untangled.
> There seemed to be two discussion points around the "Jini" name on
> our Proposal:  1) trademark concerns, 2) potential confusion on
> the Jini project at Apache and other Jini Community related web
> places (,
> Part of our delay in re-engaging on this list was to get a better
> understanding of the options around the Jini trademark (that Sun
> currently owns). It seems there are two viable choices: contribute
> the trademark to Apache (along with the code), or 'abandon' the
> trademark registration. We would prefer to contribute it, but I'd
> like some discussion on this list on whether that's a viable
> option.
> As for potential confusion with other "Jini areas" (,
> -- that's a reasonable point, but we believe
> we can put context on those other sites so it's clear how they
> fit into the overall Jini Community picture and core infrastructure
> being built in the Apache Jini project.
> We did start considering alternative names, but there's a strong
> reluctance to changing names. That's primarily because of the name
> recognition we've built up around the technology and Community
> during the past number of years, as well as the difficulty (ref
> the many posts on this list in the last month on choosing names)
> with picking a new name.
> Assuming this reasoning makes sense... we'd like to proceed with
> "Jini" as the name of the Proposal and get some discussion going
> to better understand if we can contribute the TM and if it would
> be okay for those other Jini -related site (,  
> to continue to use the Jini name.
> thanks -Jim
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

Craig Russell
Architect, Sun Java Enterprise System
408 276-5638
P.S. A good JDO? O, Gasp!

View raw message