How important is the &#169; symbol in copyright notices? Many years ago, probably some time around 1990, a lawyer was sent around my employer (in the UK) to brief all the programmers about the need to include a proper copyright notice at the top of every source code file, including the &quot;©&quot; c-in-a-circle copyright symbol. We programmers tried to explain that the ASCII character set did not include the copyright symbol, and hence our practice was to use &quot;(c)&quot; c-in-brackets. The lawyer replied that this was not acceptable, it had to be a proper c-in-a-circle, and it was up to us techies to figure out how to do it. Needless to say we let him go on his way and carried on using &quot;(c)&quot; because there was nothing else we could do. According to Wikipedia the US Copyright office has always accepted &quot;(c)&quot;, but it says nothing about other countries. And there are still some countries that are not signatories to the Berne Convention. These days of course putting the proper symbol in source code is not a problem as long as your programming tools can handle Unicode. But I have always wondered: why was the © symbol so important then, and is it still important now?
The exact timing of this story makes a bit of a difference, as you're placing the story right around the time of the Berne Convention Implementation Act of 1988, which changed the rules for works first published after March 1, 1989. Before then, most copyrightable works were only treated as protected if they included a proper copyright notice, which required the copyright symbol (or &quot;copyright&quot; or &quot;copr.&quot;), the year of first publication, and the original copyright owner. So if this happened in February 1989, the lawyer was correct that you needed to include &quot;a proper copyright notice.&quot; But he was probably mistaken to think that your rendering was problematic. The copyright symbol required was the same circled C that you mentioned, but the Copyright Office will also recognize a variant on the symbol if it &quot;resembles the © closely enough to indicate clearly that the variant is intended to be the copyright symbol.&quot; The office's current guidance makes clear that your variant would be sufficient: Acceptable variants include: The letter c with a parenthesis over the top. The letter c with a parenthesis under the bottom. (c c) (c) The letter c with an unenclosed circle around it. Examples of unacceptable variants on the © symbol include the following: CO C C/O @ (i.e., the letter a in a circle). The letter c with a circle attached to the bottom of the letter. The letter c in a square. [c] The same was true under the guidance that would have been in effect at the time. See section 1005.01(c)(6). If the advice came after March 1, 1989, the notice would not have been strictly necessary, regardless of how you rendered it.
Provided you are in one of the 170+ countries signatory to the Berne Convention (the current 10 non-signatories are, exhaustively: Eritrea, Marshall Islands, Nauru, Palau, San Marino, Iran, Iraq, Ethiopia, Somalia, and South Sudan), then copyright comes into existence at the moment a work is fixed in a tangible medium, not when it is published. The initial copyright owner is the author of the work. In cases of employment, the "author" might be the natural person who authored the work, or the corporate person who employed the natural author. To clarify your thinking about registration: copyright registration is a public record of authorship (or copyright ownership). Registration does not create a copyright, but is merely a recording of the copyright that was automatically created at the moment of original authorship. Depending on circumstances and jurisdiction, Alan might have a legitimate claim to copyright on his own work. However, he will be quite hard-pressed to find a convincing theory of law that allows him to publish the unpublished copyrighted work of other people without their permission. This leaves him either to admit defeat -- he cannot possibly own the copyright of his coworkers' code, so he cannot have legally reproduced it -- or else make the baldfaced lie that the code has no other authors other than Alan himself. For your company to disprove such a claim, you may employ sworn testimony of your coworkers, you may employ code analysis to show differing coding styles (suggestive of multiple authors), or you may show code backups or version control history showing the progressive authorship of the work over time by many people. (Sure, a Git history is possible to fake, but a realistic history with feature branches, "whoops, undid the typo in the last commit" messages, etc. would lend significant weight to your company being the original authors.)
No for the U.S. There is no criteria for graphic complexity in the United States. A signature can still be the historical &quot;X&quot;. If it is some representation of your name, as it ordinarily is, it not need to be remotely legible or a representation of your full name. From FindLaw Usually, a signature is simply someone's name written in a stylized fashion. However, that is not really necessary. All that needs to be there is some mark that represents you. It can be -- as many signatures end up -- a series of squiggles, a picture, or historically, even the traditional &quot;X&quot; for people who couldn't read and write. As long as it adequately records the intent of the parties involved in a contractual agreement, it's considered a valid signature.
Copyright exists whether they make that statement or not. Giving such notice informs the public that the work is copyrighted, who owns it, and when it was published. If the work is infringed, the defendant will not be able to use an innocent infringement defense. There's nothing special about using the domain name, as it's probably the name or DBA of the business that owns the domain.
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.
Can I sign legal documents with a smiley face? Yes, that is lawful. A person's signature does not necessarily have to include the person's name or initials. What matters is that the signature reliably and unequivocally identifies the person who produces it, which apparently you have been able to prove by showing your driver's license. The Black's Law Dictionary (4th Edition) states in its entry for signature that "whatever mark, symbol, or device one may choose to employ as representative of himself is sufficient". It directs to the entry for sign, which likewise speaks in terms of "any mark, as upon a document, in token of knowledge, approval, acceptance or obligation". Accordingly, your signature qualifies as mark or symbol that fits these purposes. Your history of signing other legally binding documents that way further reinforces the authenticity of your signature. If it is legal, is it a bad idea? It is a bad idea to the extent (if any) that (1) others can easily forge your signature (notwithstanding that forgery or identity theft might be proved circumstantially); and (2) verifying your identity may cause hassle or annoyance to you and/or third parties. But this paragraph obviously is applicable to any and all signatures, not just those which at first glance may seem to be a joke.
It is not required. The companies undoubtedly prefer that you include those designations, and they may even write to say that you should, but that is just them doing their due diligence in policing their brands. In the instances you cited, there is probably some agreement between those companies to include those markers. If you don't have such an agreement, there is no obligation to notify the users of your website that some third party has trademarked a name that you mention.
"Pastiche" is a literary, not a legal term, and as a professional coder, I would not use it to describe code that to some extent imitated other code. The legal question here is: is your code a derivative work of the code it is based on, and if it is, did you have permission to make that work. Copyright, in an Berne Convention country, which includes the EU, does not protect ideas and concepts, it protects expression. It protects the choices of words and symbols, and other forms of expression. If all you did was study example code, presented for educational purposes, and then write code that performs a similar function, using the same general techniques, then I don't think you have infringed copyright. That, after all, is why people post code to Stack Overflow and similar sites, to allow them to learn how to use specific coding techniques, including in commercial projects. I have used techniques posted to SO to do coding as part of my paid job. The usual test for copying under US law is "substantial similarity". This takes into account cases where there is essentially only one way to say or code something. I don't know the exact tests under the various laws of various EU countries, and they will not all be the same. But I suspect that on this point they are, well, substantially similar :). I can't advise on your specific situation. But if it is as described, I don't think you have a problem.