<div dir="ltr"><div>Peter</div><div>I am ok with your suggestion, thanks Ravi</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 24, 2014 at 6:09 PM, Peter Yim <span dir="ltr"><<a href="mailto:peter.yim@cim3.com" target="_blank">peter.yim@cim3.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear All,<br>
<br>
<br>
Ref. <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_IPR#nid2L0S" target="_blank">http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_IPR#nid2L0S</a><br>
<br>
The prevailing OOR Intellectual Property Rights (IPR) Policy (as<br>
adopted by the community on 17-Dec-2010) now reads:<br>
<br>
//<br>
= The Official OOR Intellectual Property Rights (IPR) Policy =<br>
<br>
Our intent is to make the OpenOntologyRepository (OOR) software and<br>
system, as well as the content hosted in the open public instance of<br>
the OOR (repository) that this OOR-team will operate and maintain, to<br>
be as free, open, and unencumbered by IPR restrictions as we possibly<br>
can, so as to allow users of the software, system, and ontology<br>
content, the maximum freedom and flexibility. As such, we shall<br>
stipulate that ... (2L0T)<br>
<br>
* software codes contributed to the OOR effort has to carry the<br>
"Simplified (two-clause) BSD License" (FreeBSD License). (2L0U)<br>
** the above will be the default position, unless it is otherwise<br>
mutually agreed in writing, between an authorized representative of<br>
the OOR team and the contributor. Such exception, even if agreed upon,<br>
needs to bind the contributing software codes to a compatible,<br>
non-reciprocal, "gift," open-source license, such as (included, but<br>
not limited to) the MIT License, the Apache License version 2.0 or the<br>
Mozilla Public License 1.1 (MPL); (2L0V)<br>
** it is, of course, also acceptable if the software contribution in<br>
question is in the public domain; (2L0W)<br>
** Software libraries, under either "gift" or "reciprocal" open<br>
software licenses, may also be used in the OOR software or system.<br>
(2L0X)<br>
<br>
* Any content contribution to OOR should specify an IPR license, as<br>
part of the OOR "gatekeeping" requirements, which will be maintained<br>
in the content contribution metadata. Each repository using the OOR<br>
software can specify its own set of acceptable IPR content licenses.<br>
(2L0Y)<br>
<br>
* That content (essentially ontologies or other "knowledge<br>
organizational structures (KOS's)") contributed to the open public<br>
instance of OOR (which the OOR team will operate and maintain) will<br>
need to be licensed under either one of the following: (2L0Z)<br>
** the "Simplified (two-clause) BSD License" (FreeBSD License), or (2L10)<br>
** the "attribution only" Creative Commons Attribution License (CC BY<br>
3.0 or its successor), or (2L11)<br>
** the content being contributed is in the public domain. (2L12)<br>
//<br>
<br>
<br>
In view of the publication of the Creative Commons CC BY 4.0 [1] in<br>
late 2013, which now does a better job in terms of<br>
Internationalization, and has made improvement to cover "data" more<br>
adequately (by properly addressing sui generis database rights and<br>
copyright-like rights) [2], I propose we update the relevant OOR IPR<br>
Policy clause (ref. "nid2L11" -<br>
<a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_IPR#nid2L11" target="_blank">http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository_IPR#nid2L11</a>)<br>
to read:<br>
//<br>
** the "attribution only" Creative Commons Attribution License (CC BY<br>
4.0 or its successor), or<br>
//<br>
[... was: ** the "attribution only" Creative Commons Attribution<br>
License (CC BY 3.0 or its successor), or ]<br>
<br>
<br>
*** I suggest we discuss any issue on this thread that OOR team<br>
members may see, for this update. Barring any objection, I move that<br>
we adopt this change at the next OOR team conference call, or<br>
automatically (by way of unanimous lack of objection), 30 days from<br>
this message, whichever comes first. ***<br>
<br>
<br>
ALL: Please second the motion, discuss, voice support, etc. ...<br>
<br>
<br>
Reference:<br>
[1] <a href="http://creativecommons.org/licenses/by/4.0/" target="_blank">http://creativecommons.org/licenses/by/4.0/</a><br>
[2] <a href="https://wiki.creativecommons.org/Version_4#Version_4.0_Policy_Decisions" target="_blank">https://wiki.creativecommons.org/Version_4#Version_4.0_Policy_Decisions</a><br>
[3] we had a discussion on the [ontoiop-forum] list when the issue<br>
of "choice of license for the OntoIOp Registry came up which may be<br>
relevant - see:<br>
<a href="https://listserv.ovgu.de/pipermail/ontoiop-forum/2014-October/000043.html" target="_blank">https://listserv.ovgu.de/pipermail/ontoiop-forum/2014-October/000043.html</a><br>
<br>
<br>
Thanks & regards. =ppy<br>
<br>
p.s. btw, will someone (Ken? Michael? Till? Todd?) step up to<br>
schedule/call the next OOR team meeting, please.<br>
<br>
--<br>
Peter P. Yim<br>
<a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?PeterYim" target="_blank">http://ontolog.cim3.net/cgi-bin/wiki.pl?PeterYim</a><br>
<br>
_________________________________________________________________<br>
Message Archives: <a href="https://listserv.ovgu.de/pipermail/oor-forum/" target="_blank">https://listserv.ovgu.de/pipermail/oor-forum/</a><br>
Subscribe: mailto:<a href="mailto:oor-forum-subscribe@ovgu.de">oor-forum-subscribe@ovgu.de</a><br>
Config/Unsubscribe: <a href="https://listserv.ovgu.de/mailman/listinfo/oor-forum" target="_blank">https://listserv.ovgu.de/mailman/listinfo/oor-forum</a><br>
Wiki: <a href="http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository" target="_blank">http://ontolog.cim3.net/cgi-bin/wiki.pl?OpenOntologyRepository</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Thanks.<br>Ravi<br>(Dr. Ravi Sharma)<br>313 204 1740 Mobile
</div>