WE'VE MOVED!
We are proud to announce our NEW community destination. Engage with resident experts and fellow entrepreneurs, and learn everything you need to start your business. Check out the new home of StartupNation Community at startupnation.mn.co
We are proud to announce our NEW community destination. Engage with resident experts and fellow entrepreneurs, and learn everything you need to start your business. Check out the new home of StartupNation Community at startupnation.mn.co
Protection for easy duplication?

Are there recommendations for protecting something that is easily duplicated? It isn`t in existance yet. It`s a series of functionalities making up a web based application, which means people can view most of the source code and figure it out. It will also have a unique layout that I`d like to protect as well. Any suggestions on what I can best do for at least validly sending, when the time comes, cease and desist letters are appreciated.
Thanks,Brett
Thanks,Brett
Sign In or Register to comment.
Comments
Someone could come along, view the source code and create their own version. How much of that can I protect?
Thanks,Brett
If I did get a patent to protect my code and find there are imitations, how do I know they are my code or different code? At what point can you say, "hey, I have to board your ship and search"?
James, that sounds correct: http://www.bitlaw.com/software-patent/why-patent.html</A>. So if you can get a design and utility patent for your web application, you are doing fairly well. Several design patents would be needed to cover different screenshots (states). Of course, there is the probably of them actually not doing so well in court. Being practical, do you have the money and time it will take to sit out of work while you defend?
Doesn`t the utility patent get into protecting at least the "feel" part of the look and feel? It`s function that is producing the feel part. There would only be a look if there were no function going on.
Starting at (24), it gets into the infringement details althought what happens before and leading up to (24) is worth reading.
To be clear, Microsoft didn`t completely duplicate Stacker. Their DoubleSpace product had its own features but also had features (read functions) identical to Stacker. Although Microsoft wrote their own "unique" source code, "some" of it resulted in providing the exact same functions as Stacker. That`s utility infringement.
Brettbrettr2007-1-20 13:18:39