Is there US law that can compel Apple to create software? It is my understanding that US law has jurisdiction or routinely compels corporations (BA, VZN) to: turn over customer data to law enforcement(VZN) how to build systems (in regulated products: BA aircraft) prevent products that may NOT be built \ exported Is there any US law or precedent that can compel Apple to create new software that aids law enforcement investigations?
The U.S. could pass a law directing Apple to create software for fair compensation. Similar statutes have been passed in wartime compelling companies to do all sorts of things and companies don't have all of the rights of individuals. If it can be done (not obvious in the case of existing products in the market place), it might be possible for the government to compel it to do so; if it can't be done, it can't be compelled and not all things are possible retroactively. There would also be a constitutional contracts clause issues with such a law impairing contracts between Apple and its customers when applied to existing phones retroactively. Whether it could require Apple to create a law enforcement back door depends upon whether 4th Amendment privacy rights trump the creation of a means to do so. There is an expectation of privacy in electronic records, but it is not absolute. But, there is no law on the books requiring this from Apple. It does not flow naturally from existing powers of law enforcement under existing statutes. It goes beyond what a subpoena would ordinarily require someone to do, and a subpoena is the main means by which governments compel people to provide information. In my opinion, a court faced with that question would rule that a statute requiring Apple to do this prospectively would be constitutional, but no such statute exists. However, this is currently an open legal question because there is no statute of the kind that have been litigated in a manner that produced a binding precedent.
If it is open source code, then usually the requirement is that you produce the source code for the software that you release. Exactly for the software that you release. For example if you took open source software X, and added feature Y, and distributed the combined software outside your company, anyone can request the source code for X including Y. Handing them the source code for X only wouldn't meet the open source requirements. Now all this is not illegal, but it means the copyright holder of X could sue you for copyright infringement. They will do that if they have enough reasons to do so. So let's say you are continuously developing your software and occasional hand out your compiled software. Say you built versions 100, 101, 102, 103, 104 of the software, you gave versions 100 and 103 to customers, and anyone asking for the source code is given the source code for the latest, slightly improved version 104. The copyright holder of X might sue you but: 1. They wouldn't know you are doing this. 2. A judge might side with you and decide that newer, improved source code is good enough (I don't know this, but it seems not unreasonable). 3. The copyright holder might decide that they don't want to sue you for this because you are close enough to meeting the requirements.
Is a text message legally binding? Yes, but the terms of the message need to be clear enough to ascertain the parties' intent at the formation of that contract or agreement. A contract does not even need to be in writing. There are also oral contracts and implied contracts, the latter referring to contracts which are inferred from the parties' conduct. A contract such as the agreement you describe here is binding regardless of its form. It is just easier to prove the existence of a contract if it is in writing. You did not specify your jurisdiction. If it is in the US, the price tag --rather than the downpayment-- of the object of the contract (i.e., the puppy you intend to buy) determines whether your complaint would need to be filed in Small Claims court. Generally speaking, parties to a dispute in Small Claims court have to represent themselves. Two remarks are pertinent. First, developing writing skills is utmost important not only for litigating a dispute, but also during the process of formulating the terms and conditions of a contract/agreement. Your post indicates that you seriously need to work on that. Second, the end of your post reflects that one of your managers violated labor law(s), which to most of us would be more worrisome than the controversy about the puppy. Legislation in most or all jurisdictions outlaws the act of withholding an employee's compensation regardless of its form (salary, commissions, and so forth). You might want to gain acquaintance with the labor laws of your jurisdiction so you can assess whether or how to proceed (does legislation require the employee to "exhaust administrative remedies" prior to filing in court? are administrative remedies optional? do these exist at all?), even if only to ascertain whether the deadline for filing the corresponding claim has elapsed.
It seems that you don’t understand what parody is. If you do understand, please explain how it’s even possible to parody computer code. What you can do with “open source” code depends on the licence the copyright holder(s) release it under. For some very permissive licences you can do what you suggest, for most, you can’t.
pure functionality is not copyrightable Copyright does not protect purely functional things, it only can protect the execution as Brown Bag Software v Symantec Corp established back in 1992. In fact, even before that, Data East v Epyx established in 1988 that it takes the availability of the software to be copied to even get a case, but that was refined in Capcom v Data East in 1994: There are unprotectable elements, aka Scenes a Faire, things that are just standard and have to be done. A lever that pulls on a rope is strictly functional, that the lever is pink with orange stripes is not. A button with the label &quot;save&quot; on it has no artistic choice but a purely functional one and its presence, in general, can't be copyrighted as that is standard. Even standard placements like &quot;top left corner&quot; or &quot;bottom right corner&quot; for the button are just standard enough and make that part of the UI uncopyrightable. Indeed, even the idea of a Graphic User Interface is unprotectable as Apple v Microsoft (1994) held. But if you put that save button upside down on the left edge of the screen and only visible if you mouse over it, then you have shown artistic choice beyond the mere functionality - but also very bad UI/UX design. Code can be copyrighted. Computer code can be copyright protected, but you protect only those elements that are protectable in the first place. This means only elements that are not for example mandated by the sheer functionality of the underlying programming language. If the programming language mandates that all programs start with Program launch {variable variable variables} then that part is not copyrighted by you, but your choice of variable names can be. Code can be made from functionality requirements There was a famous SCOTUS case that had pretty much this question: Can a company dissect a software and then take the determined functionality of the whole software to their own programming team? Bowers v Baystate court held an Ethical Wall will not constitute infringement, if properly executed and the EULA doesn't prohibit it. Work for hire/Employees Now employers always get pretty much all the rights to a program's code anyway. If you are contracted from the outside, it might be work-for-hire and the contract might include such a transfer. In either case, there are no rights left for the hired person to sue over. Only if the contracted outside coder does not have a work-for-hire type work and there is no transfer clause, they do have rights in the work that they can sue over at all. But Work For Hire is a very complex topic on its own - and requires you to review your contracts and get a lawyer.
If it's patented then it doesn't matter that you independently came up with it. Most software is not patented, though. Most developers do not even think about patents when writing code. In theory you could spend your time keeping up to date on software patents so that you avoid infringing. But this probably only makes sense for specialists who would want to read the latest patents in their field anyway. All software is protected by literary copyright, though. In this case they will try to prove that you did not independently created it, and did copy it. Whelan v. Jaslow in 1986 ruled that structure, sequence and organization of a computer program were protected by copyright. So you could be liable even if you did not just copy and paste sections of code. But even if you're worried the court would get things wrong and think you copied a program when you never even saw it in the first place, there is really nothing you can do about it.
Can the name of my LLC include the phrases "Software Engineer", "Software Engineering", or similar derivations thereof? No. Not based on what you've posted. Go to the definitions to see how engineer is defined. It may be they are talking about actual structural engineers or environmental engineers, where if you're wrong people die. But based on above, you can't use the word engineer unless you're licensed as such. Is there even a license for computer engineer? This seems more like it could be a term of use but not actually descriptive of what you're doing. IDK. You'd have to see the definitions and exceptions. Can my resume, curriculum vitae, or my advertising or promotional materials accurately report the subjects I studied in college as the subject matter of "Software Engineering", to the extent that this information is true and accurate? Yes, your CV is supposed to say what you have done, and learned and especially published (lest it's just a resume), but the answer as far as promotional materials, is NO. This, because you don't post your cv on your ad's and if you put that, you will likely be found to be trying to pose as a licensed professional based on a technicality. If that happens the licensing authority will probably censure you by disallowing a license when your qualify. If asked directly by a client, am I even allowed to divulge my area of study accurately,(of course, but you'd also have to divulge the fact that you are not licensed and cannot act in that capacity) Would it be a violation of the law to claim I had engineering knowledge since I have studied (and practiced) software engineering in the past (for instance, at previous places of work in states which did not have these kinds of limitations, or for corporations which did not offer my services to the general public)? It could be if the person reports that you are soliciting work as an engineer w/out a license. It's like a person who went to law school, passed the bar, but never got sworn in. They cannot solicit business as a lawyer. Unless there is a license for being a computer programer, there is nothing barring you from using that terminology. You could be, that if you look up the definition prior to the statue, that it says something like "for the purposes of this section the term engineer means…", In which case it doesn't even apply to you.
Nothing prevents firms from putting clauses like that in the disclaimer. If you're talking about goods (rather than services), much contract formation is governed by the Uniform Commercial Code, which 49 states have adopted (and which Louisiana has adopted part). However, the real question relates to whether that kind of language will be enforceable in court. A common way to attempt to avoid litigation is to insert a clause that requires arbitration of disputes (instead of litigation). The Supreme Court upheld the Federal Arbitration Act (FAA) in Southland Corp. v. Keating, 465 U.S. 1 (1984), so this can be successful. Contracts that have class-action arbitration provisions are a little dicier, but in AT&amp;T Mobility, LLC v. Conception, 563 US 333 (2011) , the court held the FAA preempts state laws that disallow class arbitration.