What is a technical standard from a Copyright law standpoint? Take for example a technical standard, that covers some communication protocol or any arbitrary mathematical algorithm. It is an idea of some kind. Could this technical standard be patented? Licensed? What is the legal status of such a standard? Could fixing this standard in any tangible form change anything in its patent-ability? As far as I understand, should somebody implement the aforementioned communication protocol or algorithm in software or hardware, then this implementation becomes a separate entity and could in turn be patented and licensed. Am I correct? Could initial standard somehow prohibit creating such implementations? Could it require a license of some sorts for this?
Copyright and patents are two very very different things. Copyrighting a standard means the wording of the standard can not be copied without the copyright holders permission. It does not protect the ideas expressed in the document, just the way those ideas are expressed. IEEE standards, for example, are copyrighted by the IEEE and therefore you can't make a copy of the Ethernet specification, you need to buy it from them. That has nothing to do with implementing an Ethernet device. To implement something described in a technical specification might or might not require one or more patent licenses. The authors of the standard may not even be aware that something they require for the standard has already been invented and patented by someone else. Many standard bodies do impose a requirement on participants in the standard's creation that they offer licenses to any patents they own that are needed to implement the standard on a fair and equal basis to all. It is called FRAND - the acronym for fair, reasonable and non-discriminatory licensing.
1) I saw that no where during registration you actually tell what your work does, you only fill up details, how exactly is it protecting you if you don't specify? For example I have a computer program/website that do something, how exactly the copyright protects you if you did not specify about it? A copyright protects a particular single expression of an idea and versions that are derived from that particular expression. When you copyright software you have to provide approximately 50 pages of printed code so as to make it possible to distinguish your code from someone else's and you generally deposit a full copy with the Library of Congress. The ideas in the computer program are not protected. You only protect the exact language of the code in the computer program and other programs that use that exact language as a starting point. If someone reverse engineers a way to achieve the same process or outcome with different code language (or even comes up with exactly the same code language without ever looking at the language used in your code) then their software does not infringe on your copyright. To protect the ideas in a computer program you need a patent. 2) If I am a non-us citizen, do I need to select in State "Non-US", or leave it blank on "Select"? Because it allows me to complete registration with either. State "Non-US" refers to where you are located, not to your citizenship. If you are located outside the U.S., then you select "Non-US" and if you are located in a U.S. state, but are a non-citizen, you select the state where you are located. The answer does not affect the validity of your copyright. It is used for economic statistics and to determine where the copyright office should locate its own offices to be maximally useful to the public.
Legally, such services have no special status. They're not necessary for copyright to exist, and their status as evidence is not in any way special. This is one of those rare cases where a blockchain actually does make sense. Recently the idea of Non-Fungible Tokens has come up in the context of blockchains, and typically these are very accurately dated. NFT's can be sold, but that is not necessary for them to be created.
Exactly the same way it works over all other content There are no special classes of copyright, there’s just copyright. What a user of a service may do with copyright materials will be spelled out in the licence. If there is no licence, then they are left with fair use/fair dealing.
In my opinion, you are totally free to publish the information. There are two areas of law that can be cosidered - private and public law. In the private law area, you can be liable for revealing trade secrets, but only if you agreed to keep them by a contract. Trade secrets do not exist by themselves (there are minor exceptions, eg. in competition law, but those do not concern us), they must be protected by contracts. Another private limitations, like libel laws, won't apply here. This is not uncommon, but not in cars - you can find clauses like these in software license agreements. Then there is the public area. Is there any regulation, any policy of the state, that prevents you from publishing it? I am not aware you whole legal code of your state, but I doubt there is. It would be a harsh limitation of freedom of speech. Even if the modification could lead to illegal effect (like, modifying toy weapon to kill by rising its power...) it would be only illegal under very rare circumstances. To conclude it - freedom of speech can be limited only if there is sufficient public interest to do so, and I don't see any.
A proof can be protected by copyright. The underlying facts of math cannot. But if one has copied details of the order of the proof, or of the selection of theorems to use, and if several other choices would have been possible, then the new proof may constitute a trivially modified copy, or a derivative work, and in either case making of it might be copyright infringement. However, making and distributing a copy, even with no changes at all, for purposes of comment and criticism, might be fair use in the US, fair dealing in the UK or some other parts of the Commonwealth, or fall under an exception to copyright in other countries (these generally vary significantly by country). This is usually a very fact-driven question.
In my opinion, this should be enough. The GDPR regulation is general - it does not attempt to address these issues directly, precisely for the reasons we see here: You can never predict how the technology will develop. When interpreting the GDPR, we must keep the intended goal in mind. What is the purpose of the "right to erasure"? To prevent anyone from further processing the personal data. If you "crypto-shred" it, it can't be processed anymore, not even theoretically. The encryptec file cannot be used to identify the subject, therefore it is not even personal data anymore. In case it can be decrypted in the future... Well, that is just a speculation. The courts can go to great lengths in interpreting what personal data is (dynamic IP address is considered personal data, since it can be linked to a person by the police with a court order), but i am pretty sure that "it can be theoretically possible in some distant future" is beyond the limit. As for the second question, I am not aware of any applicable case-law, but I guess that current security and technological standards will be used to assess the delay. You have a right to protect your data, the subject has a right to erase them. Those rights must be balanced, neither fully overrules the other. The delay should be short enough so the right to erasure is effective, and it should not extremely long compared to other (economically viable) backup solutions available, in line with current industrial standards.
If you aren't including those libraries, then yes because it's entirely your own work. If you are publishing those libraries, then no because their licenses will limit how you can do that. GPL's and MIT's main features are restricting how you can distribute software that includes the licensed code, and they don't allow the &quot;do whatever you want&quot; of public domain.