Do these two Microsoft Excel patents prevent anyone from shipping similar features? Considering these two patents describing two features: User defined spreadsheet functions Customizable spreadsheet table styles If anyone were to build some spreadsheet software, what would these entail in terms of restrictions if they would want to develop the same features? Is there a difference between commercial software and open source/free in that case?
If you want to implement this or a similar feature, you'd look up the patents, and either get a license (unlikely that Microsoft would give you a license), or figure out how to implement the feature without violating the patent. An example how a company I worked for worked around a patent: In order to compress data. in the best possible way, the idea was to try eight different methods to compress the data and pick the best compressed data. There was a patent for that (even though to me, this was quite obvious). Workaround: The software tried eight different methods and reported a number from 1 to 8 indicating which method gave the best result (unlike the patent, which actually gave the best result). Then the data was compressed once using the best method. No patent violation. You'd probably want a patent lawyer to check if your idea how to implement the feature violates the patent or not, and how to get around it. It takes a specific mindset that you and I don't have. And even good lawyers who are not patent lawyers might not be able to help you there. Commercial vs. open source/free software makes no difference, except that Microsoft might not bother suing you if there is no money to be made. Unless the intent is to prevent you from implementing the feature, in which case the would sue companies without money as well.
Before the AIA in 2012 both companies could apply for a patent and if one of the applicants thought they were both trying to patent the same thing they could initiate an interference proceeding. In that proceeding before the board, they each present their evidence as to date of conception and diligent effort from that point to the date of the first filing. The board decided which application went forward. Now the U.S. is with the rest of the world in first-to-file. It doesn’t matter who conceived first unless one actually stole the idea from the other. There is a new derivation procedure to try to prove that. I don’t think it has ever yet happened. One of the &quot;simultaneous&quot; inventors could publish the invention, putting into the public domain. If published before the other's filing date, it would theoretically prevent the other from getting a patent. In any case a patent owner can stop the other from making their product or charge a royalty. There is a narrow case under the AIA where one company has been using a process that another later patents and can retain a limited right to keep using that process but can’t move or expand operations. This is called Prior User Rights.
Person A has to have created the data to hold copyright; for most kinds of data this has no legal effect because facts are not protected by copyright. A mineable database probably does not have the necessary creative elements for copyright. An algorithm is not protected by copyright (it might be patented). Person C's program is copyrighted. The product created by D is probably copyrighted, depending on what degree of creativity is involved in their transformation. If the transformation is automatic then no, but if creative judgments are applied to the output of the program then maybe. Though the resulting product is another database of facts, and the facts cannot be protected. In terms of "using the model", only C and possibly B have any control. If it is necessary to validate the software using A's data and A has kept the data secret, C might negotiate with A to use the data, in order to complete his program, and that could give A some interest in the program.
Copyright doesn't protect methods, only particular fixed expressions. 17 USC 102 Some methods (but not algorithms) may be protected by patent. Diamond v. Diehr 450 U.S. 175 (1981) More exactly, "an algorithm, or mathematical formula, is like a law of nature, which cannot be the subject of a patent". However, in Diamond, the respondents here do not seek to patent a mathematical formula. Instead, they seek patent protection for a process of curing synthetic rubber. Their process admittedly employs a well-known mathematical equation, but they do not seek to preempt the use of that equation. Rather, they seek only to foreclose from others the use of that equation in conjunction with all of the other steps in their claimed process. Said another way: the algorithm cannot be protected, but if you are using the algorithm as part of a method or process that as a whole is patented, you would be infringing the patent. The paper does not have to disclose the patent - you could email the authors to see if they have any patent that protects any particular methods using the algorithm in the paper, but that doesn't rule out patents that the paper author is unaware of.
The difference between commercial and non-commercial software use is about as clear as it gets, outlined by the definitions in the license above. One makes money, the other doesn't. There is no gray area. Your intent or expectations for a project may seem to alter the difference between the two and add a gray area in your mind, but they don't. Once you are a commercial user, buy a commercial license and/or upgrade the non-commercial license to commercial. That's the legal angle; and what is illegal and what is unethical are not always the same. If you still feel like your intent does make a difference and you feel unethical about using a non-commercial license - because you are building a community and hoping/planning on making money - buy the commercial license to begin with.
Yes, you can. To be precise, I claim that one can take BSD-licensed code and distribute it under the combined terms of both the BSD and the GPL licences. We know that, if I receive someone else's code under a BSD licence, I may redistribute it to you under those same terms. This is common practice, and not (I hope) in any way contentious. We also know that I may not redistribute it to you without the conditions that the BSD licence imposes; that is, I may not place less onerous conditions on you than BSD requires (that is, requiring the inclusion of the original copyright notice, the disclaimer, this list of conditions, and a prohibition on claiming the original author's endorsement on any modified version). So the question becomes whether I can distribute that code whilst adding more onerous terms than the BSD licence itself imposes. It is clear that I can. As the question notes, Microsoft is known to have taken code which it received under a BSD licence and used it in proprietary products. These come with very onerous conditions on the the use, modification, and redistribution of the derived code (usually, they permit one instance of it to be run, and no modifications nor redistributions of any kind). For clarity: if I were to seek from Microsoft permission to modify and/or redistribute the derived code, and they were to grant it, they would not be able to free me from the BSD requirements as they applied to the derived code; I would still need to comply with those. But they are perfectly capable of applying new, onerous requirements of their own. The GPL imposes conditions on redistribution that are more onerous than BSD's, but less onerous than those of most proprietary licences. I am therefore perfectly entitled to receive code under a BSD licence, and - with or without making modifications of my own - redistribute it, adding in the GPL's requirements, if I choose to. If I haven't modified the code, those added requirements are probably pointless; if you don't wish to be bound by them, you will go and get the code from the original author, who presumably will happily distribute it to you under the BSD licence. But if I have modified the code, and you wish to use those modifications, then you will need to abide by the requirements of both the BSD and the GPL licences, since both will apply to this new, combined work (the original code + my changes).
Whether this is considered a trade secret (at least in the US) depends partly on whether you've taken reasonable action to keep it secret. If an employee thought it was OK to publish the algorithm, that's evidence that you didn't try very hard to keep it from getting out. Even if nobody's noticed it yet, getting the blog post taken down in't going to get it off the internet. You may as well try to do it anyway. If nobody has noticed the algorithm by now, you want to make it harder for them to find. You need an IP lawyer pronto. Depending on where you are, you might be able to get a patent on the algorithm still, but patents are hard to enforce, and it appears to be getting harder in the US to patent algorithms. (There's a Stack Exchange site so people can look at patent applications and see if they can invalidate the application with prior art.) You can't license out the algorithm without having some legal way of stopping other places from just using it. If you have more proprietary algorithms or things that aren't generally known that give you a competitive advantage, it would be a good idea to inform employees that they aren't supposed to reveal them. Check with your IP lawyer to see what you should do.
This is unlikely to be a problem. There are many companies that have already registered software-related trademarks prominently involving an X or the name Xcom. That Twitter has changed to X branding does not substantially change this general situation. With trademarks, the general question is whether similar branding causes confusion. It is unlikely that someone would confuse the X display server / X.Org project / X.Org Foundation with the social media service now being branded as X or x.com. Of course, anyone can sue anyone, the real question is whether that's possible successfully. Here, I have my doubts that x.com could successfully demonstrate confusion in its favour. It is worth noting that the X.Org Foundation does not seem to hold any relevant trademark registrations at all. This is not unusual for Open Source software projects and doesn't mean that X.Org has no rights, but does make a defense a bit more difficult. However, there also doesn't seem to be a relevant registration by the ex-Twitter company or by the X Corp. The x.org domain name is unlikely to be threatened. If the x.org domain name was being used in bad faith it could maybe be seized, but the X.Org Foundation has a pretty strong claim on this name. For historical context, both x.com and x.org were among the six single-letter .org/.net/.com domain names when such registrations were stopped in 1993. But while x.com has been pretty much dormant since that company was renamed to PayPal, x.org has (I think) always been associated with the display server software, and has been used continuously by the X.Org Foundation since its establishment in 2004.