Do these terms contradict each other for who owns work created by contractor? These two sentences are literally side by side and seem to be saying opposite things. All deliverables and associated documents...developed by Contractor during the term of this Agreement shall belong to Agents or its clients for whom work is being performed by Contractor. Contractor retains all rights to source code or content, pre-existing code or content...or other methods it may employ in the course of creating deliverables for Agent. With Deliverables defined as Software provided in object and/or source format or documentation or any other materials required by Contractor by Agent... In this scenario would it be interpreted in favor of the person who did not draft the terms? In general, does position in contract matter where a term occurs? For example if term A) is written on line 10 and term B) is written on line 11, is it reasonable to assume term B) takes precedence or modifies term A?
would it be interpreted in favor of the person who did not draft the terms? Yes, provided that the interpretation is reasonable. That is known as the doctrine of contra proferentem. Here, the term "deliverables and associated documents" might entail a contradiction if that term [allegedly or literally] encompasses "source code or content". That depends on what definition(s) of "deliverables and associated documents" can be adduced from the contract. The term could refer to items that are not "source code or content", such as the binary files (i.e., executables and DLLs), instructions &amp; documentation on how to operate and troubleshoot the application, and so forth. In that case, there would be no contradiction because there is no overlap between these items and the source code. if term A) is written on line 10 and term B) is written on line 11, is it resonable to assume term B) takes precedence or modifies term A? No. The sequence of clauses/terms itself does not determine which one outweighs or qualifies the other. Instead, the language used in the contract is indicative of the parties' intent and therefore how the terms of that contract relate to each other.
Does "in the course of providing services" mean "during the same time as providing services" or "for the purpose of providing services" or something else? I ask because I am a programmer who will be working on my own project during the same period as I am providing services to this Client, but after-hours and not for the same purpose or business. I want to make sure that what I create for myself I will own. The best definitions that come to mind off the cuff are "related to" and "in connection with", and both of those phrases appear in the same sentence, so that is quite close to the mark. Black's Law Dictionary (5th edition 1979) (from my hard copy edition) defines "in the course of employment" as follows (citation omitted): The phase "in the course of" employment, as used in worker's compensation acts, related to time, place and circumstances under which accident occurred, and means injury happened while worker was at work in his or her employer's service. Dictionary.com defines "in the course of" as: during the course of. In the process or progress of The best definition I gleaned from relevant case law is as follows: [A]n invention made or conceived in performing, or as a result of performing, the work required by a contract is made or conceived "in the course of" that contract. That would be true even though the invention was not specifically sought in the terms of the contract. An invention is made or conceived "under" a contract when it is made or conceived during the life of the contract and the invention is, in whole or in part, specifically provided for by that contract. Fitch v. Atomic Energy Commn., 491 F.2d 1392, 1395 (Cust. &amp; Pat. App. 1974). The law which forms the background against which the contract term in question is drafted is discussed in the following language from a Federal Circuit patent law case: The general rule is that an individual owns the patent rights to the subject matter of which he is an inventor, even though he conceived it or reduced it to practice in the course of his employment. There are two exceptions to this rule: first, an employer owns an employee's invention if the employee is a party to an express contract to that effect; second, where an employee is hired to invent something or solve a particular problem, the property of the invention related to this effort may belong to the employer. Both exceptions are firmly grounded in the principles of contract law that allow parties to freely structure their transactions and obtain the benefit of any bargains reached. Banks v. Unisys Corp., 228 F.3d 1357, 1359 (Fed. Cir. 2000). A similar contact is applied in the case Greene v. Ablon, 794 F.3d 133, 142 (1st Cir. 2015), but the term was not defined or disputed in that case. This case is still useful, however, for purposes of seeing the kind of issues that are typically raised in a case like this one and to assure yourself that the contract probably is enforceable. For the purposes of this question, the difference between an employee and an independent contractor is immaterial.
Am I contractually obligated to follow that old handbook? Yes. Consider this: your employer gave you a copy of the handbook saying, "here is a copy of the staff handbook." Because of this, you know that the document in question is the staff handbook of your company, regardless of the fact that it bears an old name, and that the policies it expresses are part of the terms of your employment contract. If you were truly concerned that the document in question had no validity as the staff handbook, you perhaps should have expressed that concern by telling the person giving you the document that they appear to have given you the wrong document, because it bears a different name. By not doing this, you accept the terms in the document. On the other hand, if you do do that, you'll just irritate the people who have to produce a rebranded staff handbook so they can give you a copy.
Recall the basic principle of copyright law, as detailed in 17 USC 106: The copyright holder has the exclusive right to make copies; prepare derivative works; or distribute copies by sale, rental, lease, or lending. Other people can legally do these things only if they are given permission by the copyright holder, typically via a license. (Remember, the literal meaning of the word license is permission.) Often, the copyright holder will require a prospective licensee to accept various terms and conditions before the license will be granted. If there is &quot;no EULA&quot;, or if there is one but the purchaser has not agreed to its terms, then the purchaser has not been granted any such license, hence does not have permission to do any of the things listed above. If they do so anyway, it is illegal copyright infringement and they will be liable for damages. To use a firewall analogy, copyright law is &quot;default deny&quot;. So let's take your questions one by one: Do they own the software? US law has no concept of literally owning software. The closest thing is owning the copyright, which the purchaser certainly does not. It still belongs to the vendor that wrote the software (or whoever they may have later transferred it to). Can they legally alter the code of the program they purchased? No, that would be preparing a derivative work. The copyright holder has not granted them a license to do that. (There are some exceptions for purposes such as reverse engineering and interoperability, see 17 USC 1201(f)). Can they legally redistribute it No; again, that is the exclusive right of the copyright holder, and the purchaser has not received their permission. or transfer ownership? Maybe, if the first sale doctrine applies. Its application to software is complicated. The user has a better case for being able to sell the software if it exists as some tangible object which is transferred (physical media, pre-installed on hardware, etc). Can they legally modify the code of the program for others who have also purchased the same package? No, that would be preparing a derivative work. Can they take that software and install it on a secondary machine? No, that would be making a copy.
Let me start by saying that real estate contracts are some of the most heavily regulated contracts and details vary enormously by jurisdiction. That said ... To vary a contract, the contract must actually contain provisions that allow for it to be varied and variations must be in accordance with those. These sorts of clauses are common in long-term contracts (building, mining, logistics etc) but are less common (but not unknown) in transactional contracts like real estate sales. If the contract does not contain such provisions then it can only be varied by a collateral contract which has the same basic requirements of any contract - in this particular case, were you offered something in return for agreeing to delay settlement? If you weren't you do not have a collateral contract that varies the original contract. Notwithstanding, even though the other party delaying settlement from the 11th to the 18th is a breach of the contract by them, by agreeing to it you would be prevented from enforcing your rights under the contract by the doctrine of promissory estoppel. This presumes that they actually settle by the 18th - if they don't all bets are off and you can enforce the rights you have from their breach by failing to settle on or before the 11th - just don't agree to any more extensions. What you remedies are will be detailed in the contract. These would normally include issuing a notice for them to settle by a given date - if they don't do that you can terminate the contract and keep the deposit. You could also sue for damages. Don't do any of this (or anything else) without getting legal advice first. Edit The OP has put in a comment a rather vital piece of information: there is a clause making settlement contingent on the buyer selling their condo. If the delay is in accordance with that clause then the vendor is stuck, even if settlement takes 10 years.
I'm going to focus on one part of your question, because I think it is informative to the entire question: "By publishing those data in a copyrighted book are they now in the public domain?" Insofar as copyright is concerned, the "facts" are simply never copyrightable. What is copyrightable is the expression of the fact. So you publish a book and it contains many facts. You retain copyright over how you expressed the facts, meaning the word choice, format of presentation and so on. The discussion of this point always leads people to ask the following two questions: What if the "facts" are closely related to the way they are expressed? For example, a phonebook contains "facts" about phone numbers. The individual numbers are not subject to copyright. But if the way they were organized was clever (i.e. not merely alphabetical) the presentation may be copyrighted. Doesn't that line get blurred? Why doesn't "the presentation order" count as a "fact?" It does get blurred! And courts use nuanced case law and judgment to figure out which side of the line a given thing is. However, one backstop is that if AN EXPRESSION is so closely related to the IDEA BEING EXPRESSED that the IDEA cannot be otherwise expressed, then then the EXPRESSION is not subject to copyright protection. To answer your specific questions: The book is subject to copyright. The facts in the book are not. Someone else could publish a book with the same measurements so long as they are expressing the facts with sufficient difference from the original. I'm not familiar with CUSIP numbers. However, there are two things to say here. (A) it sounds like you are describing a contractual relationship between the people who have the numbers. This is not governed by copyright; it is governed by contract between the parties. If these numbers could be treated as a "trade secret" they might be protected IP in that way. But given that they are likely circulated at least a bit, they don't seem like candidates for "trade secret" protection. To your question, "what is the effect of one person leaking?" If "trade secret" law was doing any "work" here... then yes, the trade secret would be undone once the information was public. But like I said, its likely this is actually all about contracts not intellectual property protection. (B) The "facts" of "which number is associated with which instrument" is likely NOT subject to copyright at any time. The specific numbering code COULD BE copyrighted, but in reality is almost certainly TOO CLOSELY tied to the IDEA being expressed to be copyrighted. Could the number be expressed otherwise? If not, then its likely not protected by copyright. -- Big take away here: You seem to be confused about the concept of "facts" getting into the public domain. That's not exactly what copyright is about. Copyright would protect the expression of facts. An expression can become public domain if it is sufficiently old or if the creator designates it as public domain work. But simply "putting something out there" does nothing to alter the copyright status of the thing.
Depends on the NDA Just like any other contract, it does what it says it does. You could draft the NDA either way.
Absolutely it is. If a contract contains void provisions then, in general, the contract itself is void for uncertainty. A void contract never existed so you couldn't use this to terminate a contract because there never was a contract. Contracts of employment are typically heavily regulated and the regulations may tell you to deal with void provisions in a different way. However, for common law contracts a void provision can sink the whole thing.