spec5-reserved-names Legal Notice?
Folks, Considering the spec5-reserved-names<https://github.com/centralnic/spec5-reserved-names> github repo that Gavin organized. I was wondering if the repo should have some kind of legal disclaimer saying essentially that folks should use it at their own risk. The community has done their best job of interpreting the ICANN guidelines, but it’s up to users to implement things in a way that meets their own contractual obligations. May be this isn’t necessary. Thoughts? -- John John Colosi Senior Manager of Product Development JColosi@Verisign.com m: 703-967-4062 t: 703-948-3211 12061 Bluemont Way, Reston VA 20190 VerisignInc.com<http://www.verisigninc.com/> [Verisign™] “This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”
Hi John, The LICENSE file contains the 2-clause BSD license which states that "this software is provided by the copyright holders and contributors "as is" and any express or implied warranties, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose are disclaimed" (lowercased to avoid shouting). I have also copied that into the README.md file so it's more obvious. G. On 17/04/2014 23:14, Colosi, John wrote:
Folks,
Considering the spec5-reserved-names <https://github.com/centralnic/spec5-reserved-names> github repo that Gavin organized. I was wondering if the repo should have some kind of legal disclaimer saying essentially that folks should use it at their own risk. The community has done their best job of interpreting the ICANN guidelines, but it’s up to users to implement things in a way that meets their own contractual obligations. May be this isn’t necessary. Thoughts?
-- John
Verisign
*John Colosi* Senior Manager of Product Development JColosi@Verisign.com
m: 703-967-4062 t: 703-948-3211 12061 Bluemont Way, Reston VA 20190
VerisignInc.com <http://www.verisigninc.com/>
Verisign™
“This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed, and may contain information that is non-public, proprietary, privileged, confidential and exempt from disclosure under applicable law or may be constituted as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this message in error, notify sender immediately and delete this message immediately.”
-- Gavin Brown Chief Technology Officer CentralNic Group plc (LSE:CNIC) Innovative, Reliable and Flexible Registry Services for ccTLD, gTLD and private domain name registries https://www.centralnic.com/ CentralNic Group plc is a company registered in England and Wales with company number 8576358. Registered Offices: 35-39 Moorgate, London, EC2R 6AR.
participants (2)
-
Colosi, John -
Gavin Brown