Mario Mommer mommer@igpm.rwth-aachen.de writes:
Yes, I think that would be ok. Google returns (not NIL) for hslookup, but it seems to be no danger.
I didn't feel comfortable waiting so I went a head and changed it to hyperspec-lookup. I think that will be ok as I see hyperspec.el etc on my filesystem. Is hyperspec-lookup ok with you?
Erik.
Erik Enge eenge@prium.net writes:
Mario Mommer mommer@igpm.rwth-aachen.de writes:
Yes, I think that would be ok. Google returns (not NIL) for hslookup, but it seems to be no danger.
I didn't feel comfortable waiting so I went a head and changed it to hyperspec-lookup. I think that will be ok as I see hyperspec.el etc on my filesystem. Is hyperspec-lookup ok with you?
With me personally yes, but I'm not a lawyer, so I don't know if (tm) issues are out of the world like this. My intuition tells me that naming a file somesuch has a different degree of relevance for such things than a project name...
Regards, Mario.
On Thu, Nov 13, 2003 at 02:22:53PM -0500, Erik Enge wrote:
I didn't feel comfortable waiting so I went a head and changed it to hyperspec-lookup. I think that will be ok as I see hyperspec.el etc on my filesystem. Is hyperspec-lookup ok with you?
Fine with me. Also, looking at LispWorks site I see that "Common Lisp Hyperspec" is trademarked, not Hyperspec.
IANAL, but:
* Yes, trademarks need to be defended in order for them to remain.
* This is why very often you see it mentioned the Foo is a registered trademark of Foobar Co., and use of it should not be construed as a challenge or infringement.
* Since hypersec-lookup *refers* to the "Common Lisp Hyperspec" I cannot for the life of me see how it could be considered a challenge of the trademark. But add a small-print disclaimer, and there really should be no worries.
Cheers,
-- Nikodemus
-
Erik Enge -
Mario Mommer -
Nikodemus Siivola