Gee... is "Sage" a trademark? Besides, I don't think a trademark is that strong... E.g. "firefox" is a trademark of mozilla. Debian doesn't want to be bound by the terms of use of said trademark, so the rename the program to "iceweasel". All visible occurrences of the name "firefox" are replaced by "iceweasel". However, I can still launch iceweasel by running "firefox" from the command line. Is this a trademark violation?
Now, if "Sage" where a trademark, then "sage-ultralight" would clearly be a trademark violation. But say the program is called "fuchsia" instead. Fuchsia is a clone of Sage, and it is meant to execute the same scripts as Sage itself. Then it's not clear that it would be a trademark violation for fuchsia to provide a "sage.py" file for compatibility purposes, i.e. just so that "import foo from sage.bar" works the same. IOW, you cannot create a GUI toolkit named "Qt", but you may be able create a GUI toolkit with a different name and provide header files using the same filenames as qt (at least wrt trademark... then there is arguing about whether interfaces are copyrightable or not...) Best, Gonzalo On Thu, May 7, 2009 at 7:09 PM, Brian Granger <ellisonbg....@gmail.com> wrote: > >>> sage-ultralight must have the same name as sage. Then you get into >>> copyright/trademark related issues (the name "sage" is already taken). >>> Just the same I could create a GUI toolkit named "Qt" that was also >>> released under the SACL license, but you can guess what would happen. >> >> Incorrect. Python doesn't care what you call your program, it only >> cares about the filename. > > Huh? Your example had two files or modules: > > foo.py > ==== > > from sage import Integer > print Integer(2)+Integer(2) > > sage.py > ====== > > # Your ultralight-sage implementation with... > # Whatever your implementation of Integer was > > Python doesn't care about the name "foo.py." But Python does care > that about the name "sage", otherwise the import of sage in foo.py > won't work. To get "from sage import Integer" to work, you *have to* > name sage.py,....well, sage.py. But as I recall there is already a > "sage" python project somewhere ;-). I think the authors of the real > sage project might have a problem with you naming your ultralight sage > module "sage.py." Just like Fernando and myself would have a problem > if another "IPython" named project came along. > >> If somebody wants to go to court about a >> filename... that'll certainly be interesting. > > This is called trademark infringement, and it happens all the time. > Remember Apple v. Apple? > > http://en.wikipedia.org/wiki/Apple_Corps_v._Apple_Computer > > Cheers, > > Brian > > >> > >> > > > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
