Which country should have exclusive jurisdiction in a simple software development contract? There's a simple contract template going around design and development communities that includes this clause: Although the language is simple, the intentions are serious and this contract is a legal document under exclusive jurisdiction of English and Welsh courts. Regardless of the rest of the template, if a contractor sends this contract to an American client: Would the American client refuse to have to potentially deal with non-American courts, in the possibility of a conflict? Should the contractor pick just one court (English OR Welsh)? What happens if there's an issue and English and Welsh laws disagree on that specific point? Could the contract stipulates that is enforceable under exclusive jurisdiction of American, English and Welsh courts, but that the Welsh one takes precedence? What is simpler and best for both parties, considering the extreme unlikeliness that such a minor project would end up in court?
Would the American client refuse to have to potentially deal with non-American courts, in the possibility of a conflict? Some might, but probably not all. Most wouldn't bother to read it; others who do won't understand what the jurisdiction provision means. Should the contractor pick just one court (English OR Welsh)? No. England and Wales is a unified legal jurisdiction. The two countries share a single court system. Could the contract stipulates that is enforceable under exclusive jurisdiction of American, English and Welsh courts, but that the Welsh one takes precedence? If US courts have jurisdiction and English-and-Welsh courts have jurisdiction, then there is no exclusive jurisdiction.
According to CENDI, yes the US government is able to claim copyright on works internationally. The law in question which makes US government works public domain in the US (17 U.S. Code § 105) only does so within the confines of US copyright. Since copyright protection is on a per-country basis, there's no reason that the US government couldn't assert IP rights under foreign copyright law (though I didn't go looking for an example). While the Berne Convention generally requires countries to provide foreign works the same protection as domestic works, I can think of two general reasons why US government works wouldn't fall under copyright protection in some countries: The country simply doesn't apply copyright protection to any government works (don't know how common this is). The country applies the rule of the shorter term. If they do, they aren't required to provide a longer term of protection than the country of origin does (which is nil in this case).
According to US law, the GPL is a license, not a contract. This means it is valid without consideration, it also means if you are in violation of the license, then you are committing copyright infringement, instead of being in breach of a contract. In Germany, the GPL is a contract. And that's fine, because German law doesn't require consideration for a contract to be valid. It's interesting in that the GPL license doesn't require you to state whether you agree to the license/contract or not. But if you don't agree to the contract then there is no contract, and you have no right to use the software.
That a company (C) has a website that can be accessed from a given county does not mean that the company operates in that country. If C is located in country A, markets and advertises to country A, offers products designed to appeal in country A, has its site only in the primary language of country A, uses servers located in country A, and has all its assets and physical offices in country A, it is not operating in country X, even if a few people from X do business with C over its web site. Country X may have laws which claim to apply to C or its web site. It will find it hard to enforce those laws, particularly if owners and officers of X do not travel to X. It will find it hard to extradite anyone for violations of the laws of X unless those actions are also crimes under the laws of A. If X is a major, powerful country such as the US, the UK, or the EU it may be able to get A to enforce its court orders, or to use its influence over the banking system to impose penalties on C. If X is North Korea, or even Brazil, it is probably out of luck. Thus the management of C needs worry primarily about the laws of A, and to a lesser extent the laws of major countries that make some effort to enforce their laws outside their own borders, such as the GDPR, or certain US laws. It probably has little reason to worry about the laws of other countries. If A is itself a major country that can easily resist any pressue from X, C has even less reason to worry. If C does significant business in countries D and E, and particularly if it opens physical offices in D or keeps assets in E, it will have much more reason to worry about the laws of D and E. If it does advertising in the D &amp; E markets, this also gives C more reason to be concerned with their laws. There is always some risk of X finding a way to enforce its laws, but the risk is small.
I can answer for the U.S., if that's helpful. The general rule, in the United States, is that covenants not to compete are enforceable as long as they are reasonable. What constitutes "reasonable" varies from state to state. Factors considered generally include: What kind of actual harm will come to the business if you go to a competitor? In other words, is this rote language they include in every contract, or did they put it in yours because you know all the secret formulas and have the customer list memorized? Is it reasonable in time, location, and scope? Something preventing you from taking any job anywhere in the United States for ten years won't be enforceable; something preventing you from taking a job with the exact same title in the same industry in the same town for the next six months might be. The general rule at common law was that covenants not to compete were unenforceable restraints of trade; the fact that they're enforceable at all is later law created by each jurisdiction, and that means it's going to vary based on your specific jurisdiction. If you want to know whether it's okay to take a specific job based on a specific non-compete you signed, you will need to talk to a legal professional licensed in your jurisdiction--and even she may not be able to tell you for sure.
I realize it has been eight months, but I believe I can offer an opinion. Given the nature of the question, please keep in mind that I am not a lawyer and my opinion is no substitute for professional legal counsel. [Preparing this post has been an educational experience and my opinion should in no way be interpreted as expert opinion] Assuming you have not infringed on any patents, the relevant legal challenges Valve could try include breach of contract, copyright infringement, and trade dress infringement. Breach of Contract The potential breach of contract occurs because the Steam client setup application requires you to accept a contract of adhesion (The License) before the software can be installed. I could not find a copy of The License online in plain text (this is separate from the Steam Subscriber Agreement, which you also agree to by accepting The License), but you can read it any time by running the Steam client setup application which is available at [redacted due to low rep - the Steam website]. These so-called "shrink wrap licenses" are of questionable legal value, depending on how the licensee assents to the contract. People often bring up Specht v. Netscape Communications Corp. In that case, the only reference to a license was on the download webpage, and it was only visible if the user scrolled down past the download button - Netscape argued unsuccessfully that clicking the download button indicated assent to the terms of the license. The Steam client setup application has a prominent dialogue box showing the terms of The License and requiring your explicit assent before installation can continue. A more relevant case may be ProCD, Inc. v. Zeidenberg, where the Seventh Circuit ruled that a license agreement was valid where the licensee had to click on a dialogue box assenting acceptance to the agreement. In short, you may be required to defend yourself under the terms of The License. If the licenses are thrown out as unenforceable, the prosecution would probably move towards copyright infringement. Section 1 Paragraph C of The License states (emphasis added): Except as expressly set forth elsewhere in this License Agreement, you may not, in whole or in part: copy, photocopy, reproduce, translate, reverse engineer (with the exception of specific circumstances where such act is permitted by law), derive source code from, modify, disassemble, decompile, or create derivative works based on the Program. Now you assert that there has been no reverse engineering, that you made yours "completely from scratch using completely different styling and images (even different website inside the client that is mine)". You may be challenged on these claims in court, for example comparison of source codes could rule out reverse engineering. I will touch on derivative work status later. Note that under Section 5, the provisions of Section 1 Paragraph C do not apply after you have uninstalled the Steam client software. This means in the case that you [can prove you had] uninstalled the Steam client software before making your own client, you would have a defense to breach of contract under Section 1 Paragraph C. However... The License also includes the terms of the "Steam Agreement", viewable online at http://www.steampowered.com/agreement. The Steam Agreement takes effect when you register for your Steam account. Section 2 Paragraph G of the Steam Agreement echoes the above referenced Section 1 Paragraph C of The License, and even survives termination of the Steam Agreement (your steam account being cancelled). Now assuming you can provide defense against reverse engineering, you may need a defense against the charge that your work is a derivative work. Your case may be pretty strong if you can show that your client was indeed written from the ground up - which rules out the possibility of deriving your program code from Steam's code as literary copyrights go. The prosecution could try saying you have copied the audiovisuals of their program, but your program was written "from scratch using completely different styling and images". Eventually prosecution may have to move into trade dress infringement. Copyright Infringement In a case of alleged copyright infringement, the first order of business is to prove there is a copyrighted work to begin with. The work in question is the Steam client by Valve Corporation. Again, I am not an expert but I could not find any copyright registration for the Steam client (http://www.copyright.gov/records/ -> Post-1978 Records -> Search by Name "Valve Corporation"). Copyright registration is required before infringement suits can be filed. Valve can register after infringement occurs but they will be limited to actual damages and profits. Nevertheless Valve does claim copyright over its product. A notice is posted on The License and Steam Agreement, and from the client itself the Help menu contains a command "Legal Info" which opens a webpage containing a copyright notice. Since 1979 it has not been necessary to post a copyright notice, but a notice helps break a defense of innocent infringement. You imply that you copied elements of the Steam client "to give customers a similar feel to what they are used to [the Steam client]". In your specific case innocent infringement may not be a valid defense. It seems you are most concerned about copyright infringement over the menus. An extremely relevant case is Lotus Development Corp. v. Borland International, Inc. In that case the First Circuit held that the menu heirarchy for Lotus 1-2-3 (the progenitor of virtually all menu heirarchies today) was uncopyrightable as a "method of operation" under U.S.C. 17 Section 102(b). We think that "method of operation," as that term is used in [U.S.C. 17 Section] 102(b), refers to the means by which a person operates something, whether it be a car, a food processor, or a computer. Thus a text describing how to operate something would not extend copyright protection to the method of operation itself; other people would be free to employ that method and to describe it in their own words. Similarly, if a new method of operation is used rather than described, other people would still be free to employ or describe that method. We hold that the Lotus menu command hierarchy is an uncopyrightable "method of operation." The Lotus menu command hierarchy provides the means by which users control and operate Lotus 1-2-3. If users wish to copy material, for example, they use the "Copy" command. If users wish to print material, they use the "Print" command. Users must use the command terms to tell the computer what to do. Without the menu command hierarchy, users would not be able to access and control, or indeed make use of, Lotus 1-2-3's functional capabilities. If specific words are essential to operating something, then they are part of a "method of operation" and, as such, are unprotectable. This is so whether they must be highlighted, typed in, or even spoken, as computer programs no doubt will soon be controlled by spoken words. The Supreme Court affirmed the decision with an even court (Judge Stevens recusing), so no national precedent was set. Nevertheless the ruling has not been overturned - the First Circuit goes into great detail explaining their decision, and I do recommend reading the ruling. We have already discussed derivative works and reverse engineering with contracts, and the same defense would apply under copyright law: source code comparison. Trade Dress Normally things like design and layout are left to patent law. A desperate prosecution, however, may claim that by copying their "look and feel" you infringe on their trade dress. The relevant text is part of U.S.C. 15 Section 1125(a) (emphasis added): (1) Any person who, on or in connection with any goods or services, or any container for goods, uses in commerce any word, term, name, symbol, or device, or any combination thereof, or any false designation of origin, false or misleading description of fact, or false or misleading representation of fact, which- (A) is likely to cause confusion, or to cause mistake, or to deceive as to the affiliation, connection, or association of such person with another person, or as to the origin, sponsorship, or approval of his or her goods, services, or commercial activities by another person, or (B) in commercial advertising or promotion, misrepresents the nature, characteristics, qualities, or geographic origin of his or her or another person's goods, services, or commercial activities, shall be liable in a civil action by any person who believes that he or she is or is likely to be damaged by such act. (2) As used in this subsection, the term "any person" includes any State, instrumentality of a State or employee of a State or instrumentality of a State acting in his or her official capacity. Any State, and any such instrumentality, officer, or employee, shall be subject to the provisions of this chapter in the same manner and to the same extent as any nongovernmental entity. (3) In a civil action for trade dress infringement under this chapter for trade dress not registered on the principal register, the person who asserts trade dress protection has the burden of proving that the matter sought to be protected is not functional. Defense against such a claim would be showing that the elements of Steam's "look and feel" were adapted because of functional reasons - see example rationale in the previously mentioned Lotus v. Borland. Overall, so long as you did write the program from scratch and there are no patent violations, you have in my opinion a strong case. There may be moral questions about unfair competition (why should you be allowed to capitalize off Valve's work put into the Steam client?), to which I would point out that your product does not appear to be in direct competition with the Steam client. Without direct competition or confidence in evidence of IP infringement it is quite unlikely Valve will file suit against you. If you would rather avoid even the possibility of legal action, you could always contact Valve directly and ask for a license.
What would be the legal validity of this behaviour? Your changes to the browser source of the website contract or license of Terms of Service (TOS) - essentially a "click-wrap" license - before agreeing to it means nothing in a legal sense, other than to void the contract. The other party (the website) can't possibly agree to those contract changes without them being submitted as contractual changes and agreeing to them, if they did agree to them. That's basic contract law. That website TOS probably has a clause that says that if you don't agree to the TOS in full, as written, without modifications, you can't use the website. And the TOS may also say that they reserve the right to prevent you from using the site by closing your account or even blocking your access. Your "witness" to the contract changes is meaningless, as your witness is not a party to the contract. And any witness to the fact that you have changed the terms of the TOS before agreeing to it would work against you in a civil proceeding as proof of your attempt at modifying the contract.
I wrote a letter to the Eclipse Foundation. The consultant pointed me to section 5 in their FAQ. My case falls under the term "linking". He warned that he isn't a lawyer, but offered the following short answer: The Eclipse Foundation does not consider linking with EPL content to be a derivative work and so you are not required to disclose your source code.