[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: how to apply trademark symbols to Apache Subversion

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Wed, 17 Nov 2010 10:59:39 -0500

On 11/17/2010 10:35 AM, Greg Stein wrote:
> On Wed, Nov 17, 2010 at 09:08, C. Michael Pilato <cmpilato_at_collab.net> wrote:
>> On 11/17/2010 08:56 AM, Greg Stein wrote:
>>> Hi Legal peeps,
>>>
>>> The Subversion community updated the website to conform to the new
>>> guidelines, but we have a question on how to apply the appropriate
>>> trademark symbols. The guideline says to put a (tm) at the end of the
>>> first use of "Apache Subversion", however, "Subversion" (alone) is a
>>> *registered* trademark. Should we just put an (r) after the first use
>>> of Subversion and leave it at that? And if that first use is "Apache
>>> Subversion(r)", would that still be fine? Maybe we should put an (r)
>>> after the first "Apache Subversion" and the first "Subversion" to
>>> clarify what is registered?
>>
>> I would expected that the common practice would be to, for the first use of
>> "Apache Subversion", display as "Apache(tm) Subversion(r)".
>
> Well, we have three terms/phrases in play here:
>
> * Apache(tm)
> * Subversion(r)
> * Apache Subversion ... ??
>
> The first two are easy. But we also want to reserve "Apache
> Subversion", much like we have "Apache Tomcat(tm)" (where the (tm) is
> implied for the two-word phrase)

I see your point, but you can't use "Apache Subversion" without running into
the marks for each (both!) of those words. Is there any value in trying to
distinguish between

   tm("Apache Subversion")

and:

   tm("Apache") + r("Subversion")

?

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand

Received on 2010-11-17 17:00:22 CET

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.