Forum Moderators: LifeinAsia
In my own terms I state that underlying code and functionality remains my property except where elements are public domain or attributed to other programmers.
The client argues that there would be no functionality without his original idea so the site is therefore jointly owned - including code and functionality.
How does one separate the two without there being grey areas? Yes the concept may be his but how do I retain my rights here. After all, I have to sit down and convert his ideas into a working model and the last thing I need is for him to replicate it or sell it on. Anyone else hit this problem?
As a compay, when we hire an individual to do work for us, we make sure there is a contract that we own the rights to the work once it's completed, as we paid that individual for their time and expertise - and don't want any future issues with someone claiming ownership of something we paid for.
As an individual, when I go into work for someone, I make sure that there is a contract stating what rights, if any, I want from the project, in case there is something I'll develop that I'll want to use again.
Sometimes an agreement can't be reached, and you are best to walk away.
FYI - Here's an article that explains a bit about this:
ht*p://www.bitlaw.com/copyright/ownership.html#software
The latest findings from what I understand are that webpages are currently being considered software as they are coded to run in a browser - although, that could change in the future.
If you get financially compensated for your work, what's the problem with him reselling it afterwards?
Normally, I think the client owns the code once the money lands in your bank account.
Hope I helped.
//ZS
Ford may own the copyright on the Ford Escort but do they own copyright on the pneumatic tyre, the combustion engine? Its far from simple.
Ford may own the copyright on the Ford Escort but do they own copyright on the pneumatic tyre, the combustion engine?
You're confusing copyright with patent.
1. We want a working relationship with the designer for any future specific changes which they could implement easier than someone working to understand the program.
2. If we found them good enough to work for us in the 1st place, we will probably contract with them again, and will get a bit of priority because they were well compensated and treated fairly in the first place.
In addition, remember, if they want changes to a finalized product to be made in the future, that should be stated if it's in the contract, or if that will be a seperate negotiation.
Many companies expect free or cheap changes to a product - make sure that's worth your time before entering into an agreement.
If you build a complex site, in essence its an application. In most cases there is just the one site and I have no problem with that. The problem comes when he clones 100s of them or sells it as a boxed product.
According to the link Ewhisper gave me, you either say its 'for hire' or else negotiate a price and draw up a contract that allows the client to do as he wishes - in which case the final price is obviously higher.
On that basis I can only stick with the "we own the code" clause. Its a tight profit margin on the contract and this small point is using up time. Maybe its a case of saying "Look lets forget the idea".
Jim
You had the expertise to build it once, so you should be allowed to build it again.
The client argues that there would be no functionality without his original idea so the site is therefore jointly owned - including code and functionality.
IANAL. However as I understand it in the US the issue of ownership would have to be determined by contract. Unless there is a patent on the idea it doesn't matter that the client had the original idea. You can't copywrite an idea.
As an example say I have an idea for a new way of swinging on a swing and I tell my friend Fred. Now Fred goes to the local playground and tries it out; in effect using my idea. Even though it is my idea it does not mean that Fred now owes me a fee for using that idea. However, if I had patented my idea, as a Mr. Steven Olson has for inventing a method for swinging sideways on a swing(patent #6,368,227), I would be able to charge Fred for swinging, if I wanted to do so.
Although, now that I think about it, I'm not sure where the provisions of a "work for hire" would come into this.
[webmasterworld.com...]
[ivanhoffman.com...]
>>You're confusing copyright with patent.<<
You’re getting copyright, and trademark confused. Ford and Escort are trademarks, which are stronger than copyrights. And a patent could have something to do with it if one filed and the idea is unique enough to get one. I have filed my own copyrights and have been the witness for Motorola patents.
jdMorgan is right. You find out up front what the deal is. Since about 1985 I have at least 2 people a year tell me that they have an idea that is the best idea since sliced bread and want me to code it for a percentage of the profits. I always tell them the same thing. You keep all the profits and I get my coding fees upfront.
I’m not even convinced that an entire web site is a ‘program’ unless it uses PHP or PERL, etc. for literally every output. In every programming book I have ever read, a program requires 3 things, input, output and loops. It could be a work of art easily though, but that would be a copyright. You should go to The Library of Congress [loc.gov...] for additional information on copyrights and ownership. The form you fill out to file for a copyright is very specific about ownership and whom the work was done for.
The_Hitcher, my bet is without a contract stating you own the work, you are out of luck.
One of my clients came up with a good idea for a product which they required. I quoted for the web based product and they couldn't afford it.
I agreed with the client, followed up with a contract, that we would provide the product to them at a large discount (a price they could afford) and in return we would retain total ownership, marketing & intellectual rights to the product. Thereby allowing us to resell the product to similar companies and make a profit from the venture.
A lot depends upon the client. In this instance they have been a client for several years and we have a mutual "trust" of each other. However, we still both wanted the relationship in contractual form. Something I recommend to anyone getting involved in anything where ownership or marketing rights may ever be questioned.....which is just about everything ;)
You're getting confused - I'm referring to The_Hitchers example of copyright on the pneumatic tyre and the combustion engine, which are patented items - please read the message.
Except, right now my edit message button doesn’t seem to be visible.
On a semi ridiculous analogy - when you build a website for a client - say, a simple 3 pager. What would your take be if he had a friend to whom he sold a copy of the site as a template, and with minor tweaks in the header and copy, that friend set up his own site?
On the other side, there's of course the cases of software packages. Buying Office does not give you reselling rights. But I don't think contract work falls under that category.
Of course, if you know your client's intention is to resell the product, you may quote him accordingly, or establish royalties. But even as you quote him, the simple fact is that technology implementation can always be bought elsewhere.
What's your client's name and contact info?:)
To put it in context, in this particular case I seemed to be investigating the legalities involved for several days before we even reached the point of deposits and final agreement and however you look at it, this is all valuable time - and unpaid at that. Therefore it seems fair to include a general clause on copyright ownership if only to stop this kind of thing. The buck stops here. If one feels its ok to lift such a clause then fine, but if you look around, most webdesigners have such a clause and for good reasons.........
I guess for a simple three page site, ownership is not an issue. The complication comes when you build something on a much bigger scale (as in this case)with a comprehensive database that as far as I can see is a unique project and I can see it doing very well indeed.
my 2 cents *s*
3 pages or 30,000 pages, its all relative. the quantity does not determine the ownership or the gray areas of ownership. there are many if-else statements in the legalities, but certainly a written statement upfront helps to sort it out. when you can, read back over the urls posted in this thread.
In this business we try to be competitive on the basis that theres always a 'Jim' somewhere who can do it cheaper.
amen. and janes too.
Theres only one way IMO, agree it up front with detailed contract termsand get paid accordingly. Suggest terms, modify terms etc until you reach agreement.
If the code is really so inovative, patent it beforehand :)
My contracts always specify that markup, code and copy developed by me belong to me and that the client is given rights to their use.
When you buy software, you buy the right to use the software only. Some programmer was paid once, but the company gets paid over and over and over.
I'd rather be the company.
WBF
