knowledge-database (beta)

Current group: pgsql.advocacy

Re: Pervasive PostgreSQL Announcement

Re: Pervasive PostgreSQL Announcement  
Robert Bernier (by way of Robert Bernier
 Re: Pervasive PostgreSQL Announcement  
Joshua D. Drake
From:Robert Bernier (by way of Robert Bernier
Subject:Re: Pervasive PostgreSQL Announcement
Date:Tue, 11 Jan 2005 08:15:02 -0500
On January 11, 2005 07:42 am, Robert Treat wrote:
> Whose trademark would it infringe upon? Berkely's ? After all this
> community has no hold over the name Postgres. I also think that as long as
> they continue to use the terms "pervasive postgres" for thier product and
> "postgresql" for the community on a consistent basis, there should be much
> issue. Certainly no more than companies like postgresql inc and postgresql
> international and that company that sells mammoth postgresql and other
> examples... we're a mixing pot on that end, and I think pervasive looks
> like they are trying to approach things above board, so I think we should
> give them as much helpful feedback as we can and be proud that an
> established player wants to be a part of this community.

You're right of course, why be critical of Pervasive when so many others
already do it? Except for the small matter that I'm right too. Somebody in
the community currently controls the PostgreSQL trademark name and should
get off his duff and make out the correct paper work by explicitly assigning
permission. Does anybody remember that goof in california that sued Linus of
using 'his' trademark'?

robert b

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
From:Joshua D. Drake
Subject:Re: Pervasive PostgreSQL Announcement
Date:Tue, 11 Jan 2005 08:08:40 -0800
This is a multi-part message in MIME format.
--------------090205040603010909080008
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit


>>issue. Certainly no more than companies like postgresql inc and postgresql
>>international and that company that sells mammoth postgresql and other
>>examples... we're a mixing pot on that end, and I think pervasive looks
>>like they are trying to approach things above board, so I think we should
>>give them as much helpful feedback as we can and be proud that an
>>established player wants to be a part of this community.
>>
>>
>
>You're right of course, why be critical of Pervasive when so many others
> already do it? Except for the small matter that I'm right too. Somebody in
> the community currently controls the PostgreSQL trademark name and should
> get off his duff and make out the correct paper work by explicitly assigning
> permission. Does anybody remember that goof in california that sued Linus of
> using 'his' trademark'?
>
>
Well one major problem with the PostgreSQL trademark is that it
isn't enforced, and thus unenforceable. There is also no indication
that the trademark would ever be enforced. Trademarks must be enforced
vigorously in order to protect them.

As there have been several large corporations (and small ones) who
have used the PostgreSQL trademark without permission, and without
enforcement... We can probably forget enforcing in general.

Sincerely,

Joshua D. Drake




>robert b
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>


--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL


--------------090205040603010909080008
Content-Type: text/x-vcard; charset=utf-8;
name="jd.vcf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="jd.vcf"

YmVnaW46dmNhcmQNCmZuOkpvc2h1YSBEcmFrZQ0KbjpEcmFrZTtKb3NodWEN
Cm9yZzpDb21tYW5kIFByb21wdCwgSW5jLg0KYWRyOjs7UE8gQm94IDIxNSA7
Q2FzY2FkZSBMb2NrcztPUjs5NzAxNDtVUw0KZW1haWw7aW50ZXJuZXQ6amRA
Y29tbWFuZHByb21wdC5jb20NCnRpdGxlOkNvbnN1bHRhbnQNCnRlbDt3b3Jr
OjUwMy02NjctNDU2NA0KdGVsO2ZheDo1MDMtMjEwLTAzMzQNCngtbW96aWxs
YS1odG1sOkZBTFNFDQp1cmw6aHR0cDovL3d3dy5jb21tYW5kcHJvbXB0LmNv
bQ0KdmVyc2lvbjoyLjENCmVuZDp2Y2FyZA0KDQo=

--------------090205040603010909080008
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
MIME-Version: 1.0


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

--------------090205040603010909080008--
   

Copyright © 2006 knowledge-database   -   All rights reserved