Our IPR Policy says that we have to put the following text to our specs. <div><br></div><div>I have made one sample of such as: </div><div><br></div><div><a href="http://openid.bitbucket.org/openid-connect-standard-1_0.html#anchor24">http://openid.bitbucket.org/openid-connect-standard-1_0.html#anchor24</a></div>
<div><br></div><div>As a side note, we need to put the copyright to the specs as well. </div><div>All rights reserved is the default I think, but that is not suitable for us </div><div>because it should be freely copiable, distributable, and translatable etc. </div>
<div>For making it copiable and distributable, CC-BY-ND would do. </div><div>We do not want a derivative works apart from translation, </div><div>something like CC-BY-DN with special permission to translate to </div><div>
any other languages than English seems to be what we want, I guess. </div><div><br></div><div>=nat<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Bitbucket</b> <span dir="ltr"><<a href="mailto:issues-reply@bitbucket.org">issues-reply@bitbucket.org</a>></span><br>
Date: Sun, Oct 2, 2011 at 3:46 PM<br>Subject: New issue 163 in connect: Standard - Appendix: Copyright and IPR notices should be put in place.<br>To: <a href="mailto:sakimura@gmail.com">sakimura@gmail.com</a><br><br><br>--- you can reply above this line ---<br>
<br>
New issue 163: Standard - Appendix: Copyright and IPR notices should be put in place.<br>
<a href="https://bitbucket.org/openid/connect/issue/163/standard-appendix-copyright-and-ipr" target="_blank">https://bitbucket.org/openid/connect/issue/163/standard-appendix-copyright-and-ipr</a><br>
<br>
Nat Sakimura / Nat on Sun, 2 Oct 2011 08:46:47 +0200:<br>
<br>
Description:<br>
In particular, the following MUST be included in each specs.<br>
<br>
The technology described in this specification was<br>
made available from contributions from various sources,<br>
including members of the OpenID Foundation and others.<br>
Although the OpenID Foundation has taken steps to help ensure<br>
that the technology is available for distribution, it takes<br>
no position regarding the validity or scope of any intellectual<br>
property or other rights that might be claimed to pertain to<br>
the implementation or use of the technology described in<br>
this specification or the extent to which any license under<br>
such rights might or might not be available; neither does it<br>
represent that it has made any independent effort to identify<br>
any such rights. The OpenID Foundation and the contributors<br>
to this specification make no (and hereby expressly disclaim any)<br>
warranties (express, implied, or otherwise), including implied<br>
warranties of merchantability, non-infringement, fitness for<br>
a particular purpose, or title, related to this specification,<br>
and the entire risk as to implementing this specification is<br>
assumed by the implementer. The OpenID Intellectual<br>
Property Rights policy requires contributors to offer<br>
a patent promise not to assert certain patent claims against<br>
other contributors and against implementers. OpenID invites<br>
any interested party to bring to its attention any copyrights,<br>
patents, patent applications, or other proprietary rights<br>
that may cover technology that may be required to practice<br>
this specification.<br>
<br>
<br>
<br>
Responsible:<br>
Nat<br>
<font color="#888888">--<br>
<br>
This is an issue notification from <a href="http://bitbucket.org" target="_blank">bitbucket.org</a>. You are receiving<br>
this either because you are the owner of the issue, or you are<br>
following the issue.<br>
</font></div><br><br clear="all"><div><br></div>-- <br>Nat Sakimura (=nat)<div>Chairman, OpenID Foundation<br><a href="http://nat.sakimura.org/" target="_blank">http://nat.sakimura.org/</a><br>@_nat_en</div><br>
</div>