What field of law would I specialize in for cases dealing with technology? I am considering getting into the field of law. I am currently an engineer and technologist. What field of law would I need to specialize in to get cases that deal with technology?
Patent law, especially patent prosecution (writing patent applications and working with the US Patent &amp; Trademark Office to get those applications granted), is the most common area of law for scientists and engineers to enter. Patent prosecution does not require a law degree, but does require a science or engineering undergraduate degree. On the other hand, patent litigation (going to court over alleged infringement of granted patents) and other technology-focused areas of law (e.g., IP transactions) do generally require a law degree (and not a technical degree), and so you would have to spend a good deal of time and money on law school.
Most advice that a lawyer gives is subjective; facts are objective but opinions are always subjective. What a lawyer does when they advise a client is typically called a "legal opinion". The reason it is subjective is that, as Dale M said, there are numerous variants that go into an opinion, and reasonably trained professionals (attorneys) can disagree as to the outcome of a specific factual predicate. Often times, case outcomes will differ based on the application of the facts to the law, so much so that the case outcome can differ based on the choice of words a witness uses, or even the way a judge interprets the law. This is why unlike truly objective discipline such as mathematics, where there is a right and wrong answer, no lawyer can ever say a case will definitely go one way or another. It will always be dependent on perception, which is the very definition of subjective. So, whoever indicated that lawyers don't give subjective advice was simply misinformed. They do. What they try not to do is make value-judgments, saying that things are good or bad; rather, they are trained to indicate whether something is illegal or not, or likely to get you sued or not. However, these are all legal opinions.
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.
The solicitor is allowed not to accept a case. If your ex-wife asked him to prepare papers, and he feels that she is getting ripped off, it is absolutely understandable that he won't prepare these papers for her, because he doesn't want to be sued or badmouthed when the deal goes wrong. "We would also reserve the right to take our own professional advice as to our efforts on your behalf." means simply he is not specialised in some subject, and will prefer to ask someone who is. Like a medical doctor asking for a second opinion before going ahead and cutting your leg off. Now I would have preferred if the solicitor had said concretely what exactly is wrong with the contract. Also, it would be obvious that you would be very comfortable with anything that he would advice her against. If he thinks that it is a good deal for you but not for her, he should advice against it. (Your comment to another question seems to indicate that she should be paid a lot more than you offered, so her solicitor seems to have been perfectly right).
Are there any underlying reasons behind the nonsensical structure of U.S.C. titles? Is it simply a case of "This is how it's been for awhile, don't fix what isn't broken." or is there more to it than that? First of all, the United States Code is generally not designed to be used by non-lawyers. Second, one of the main ways to research case law interpreting a statute is by doing a boolean search on the code section of that statute. Every time you change a title or section number, you impair the ability of people doing legal research (both judges and lawyers) to find previous case law interpreting the meaning of the statute. Third, you make it much harder to determine when the substance of the provision was originally enacted (e.g. if you want legislative history or to determine which of two conflicting statutory provisions was enacted first) since an annotated statute will often show when the current section was enacted but will not explain what it was derived from. Fourth, the location of a statute within the context of other statutory sections often informs its meaning. Machine gun may have one definition in two or three laws, and a different one in two or three other laws, and there may be yet other laws where machine gun is an undefined term. Moving a statutory section from one part of the code to another could influence the default definition that one uses for an undefined term changing substantive law. Fifth, usually a new codification will also involve some drafting standards, for example, to add gender neutrality or to avoid notoriously ambiguous constructions (like 250 word sentences). But, it isn't at all uncommon for very slight changes like the position of a comma or the formatting of a section with multiple indents, to result in a change of the likely meaning of a somewhat ambiguous statute and it is pretty much impossible to know a priori when a statutory section is ambiguous until you are confronted with a fact pattern that makes the ambiguity in that context clear. This isn't confined to obscure laws of little importance. For example, the question of whether Obamacare applied in states that hadn't set up their own exchanges hinged on these kinds of issues. None of this is to say that you should never recodify the statutes. But, a basically aesthetic motivation that mostly matters to people who make up a tiny portion of the main users of the product (non-lawyers) that poses multiple threats to how statutes will be located using legal research tools, and how it will be interpreted once located, means that reorganizing statutes is not something to be done lightly. In short, there are a lot of serious, substantive costs that can accompany a recodification of a law. As a result, re-codification is most often done only as part of an overall omnibus reform of an area of law on the merits where the interest in being able to track prior interpretive caselaw and determine the original meaning of a statute enacted long ago is at its lowest. Barring the even more ridiculous case of Congress repealing everything and passing the exact same laws again, just under different Titles/Chapters/etc, This is not so ridiculous. Most states have done exactly that one or two times in their history (sometimes more for older states). Also, many newly admitted to the union states also do something similar. For example, the basic template for the statutes in Colorado was the statutes of the state of Illinois. Basically, the first time around, somebody started with an Illinois statute book, eliminated Illinois specific laws and laws that they didn't like, rearranged them and adopted them as the original statutes of the State of Colorado (it may have actually been version 2.0 after a stopgap set of statutes, I don't recall which). Also, most states completely repeal and readopt all of their statutes in codified form on the recommendation of the codifier to a legislative committee, to reflect the acts passed in the previous session, every year. This doesn't involve overhauls really, but in principle is a complete repeal and reenactment. While the federal government has never overhauled the entire U.S. Code in this manner, it has been done at the level of individual titles of the U.S. Code. For example, the most recent major reorganization and overhaul of the structure of the Internal Revenue Code (Title 26) was in 1986. The copyright laws were overhauled in the late 1970s. Both of those accompanied major substantive changes in those areas of law. Another major recodification of many parts of the U.S. Code took place following 9-11 in connection with the creation of the Department of Homeland Security, which reorganized both the bureaucracy and the associated U.S. Code language associated with dozens of federal agencies. would it be possible for Congress to arbitrarily merge, combine, and delete Titles, and to rearrange the location of laws, definitions, etc? Are there laws/regulations governing this? Yes. Congress can do so any time it wants by passing a bill (it would be the longest bill ever - dozens of volumes long) doing so, and getting the President to sign it. The legislative process would be exactly the same as any other bill.
It's virtually never going to be as complex as you're imagining. First, because in the vast majority of cases, the vast majority of lawyers will only be dealing with one body of law: either federal law or the law of the state in which they practice. A lawyer in Maine, for example, is likely to deal almost exclusively with contracts, torts, crimes, etc. that are controlled only by the laws of the United States or Maine. In the vast majority of the remaining cases, lawyers will only be dealing with two bodies of law: those of their home state and federal law. There may be conflicts between the two, but the law has developed a variety of doctrines for determining which rules control -- most notably the Erie Doctrine -- and they will have learned both bodies of law before passing the bar. And even when there are multiple parties from multiple jurisdictions, the lawyers will still rarely need to know the substantive law of more than one. To use your example, a contract dispute involving parties from multiple states will rarely require a lawyer to understand the contract law of every jurisdiction involved. Before the court ever gets to interpreting the contract, it will first consider the &quot;choice of law&quot; question, meaning that it must determine which state's laws control the contract. Once that question is answered, the court will proceed to determine the questions of formation, breach, and damages using the laws of the jurisdiction it has selected. So in your hypothetical, the court may conclude that because the contract was signed in New York, New York law controls. So it applies New York law, and the other states' laws become largely irrelevant. Second, the choice-of-law question may not even come up, because well-drafted contracts will include a choice-of-law provision, where the parties simply agree that the contract should be interpreted using the laws of California, or New York, or Delaware, or wherever. Third, even when there is a need to apply the law of multiple jurisdictions, it is often not as difficult as you're imagining, because so much of law is largely harmonized across the states. Much of the work in this area is spearheaded by the Uniform Law Commission, which has drafted widely adopted legislation governing, for example, sales of goods, leases, negotiable instruments,bank deposits, letters of credit, title documents, investment securities, secured transactions, trusts, trade secrets, partnerships, child custody, and arbitration. Undoubtedly, there are occasions where strange circumstances or bad legal advice lead to incredibly thorny procedural questions about choice of law, but only a very small share of lawyers will need to know many seriously divergent bodies of substantive law from multiple jurisdictions, and even then, it will likely be limited to two or three jurisdictions at the most.
None The contractual chain is you &lt;-> warranty company &lt;-> (potentially others you don’t know about) &lt;-> service provider. Should something go wrong, you would sue your warranty company who might (it is up to them) then sue the service provider. Notwithstanding, it’s likely the service company owes you a duty of care and would be directly liable to you for a negligence claim.
Florida bar membership is something that can be determined from public records to see if he is an attorney or not. I would be stunned if he was not. It could be that he was an enrolled patent agent prior to being admitted to the practice of law and has never updated the record. Alternatively, it could simply be that there was a data entry error. No large database is 100% accurate. For most purposes, the rights of an enrolled patent agent and an attorney admitted to patent law practice are the same in PTO practice, so correcting this error (assuming that it is one), even if it was discovered, wouldn't be an urgent priority.