Discussion List Archives

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Assigning CC-BY-4.0 licence to CIF dictionaries

Excellent idea.  Most of my concerns relate to achieving coherence in the literature.  CC0 means anything goes and maximal chaos.  I hope Simon will want to do better than that
for the journals.

On Mon, May 13, 2024 at 8:06 PM James H via comcifs <comcifs@iucr.org> wrote:
You have reminded me, Herbert, that we have another new voting member, Simon Westrip from the IUCr Chester journals office. Let's wait for his vote before we tally them all up.

On Fri, 10 May 2024 at 00:16, Herbert J. Bernstein <yayahjb@gmail.com> wrote:
Since there seems to be a sharp divergence of opinion, and that matter is one that impacts the
IUCr journals, I would suggest trying to add the IUCr journals to the discussion.


On Thu, May 9, 2024 at 9:20 AM Bollinger, John via comcifs <comcifs@iucr.org> wrote:
On the question posed, and without further commentary,

3. CC0
2. CC-BY-4.0
1. CC-BY-SA-4.0

, where 1 is most preferred and 3 is least.


Best,

John


From: comcifs <comcifs-bounces@iucr.org> on behalf of James H via comcifs <comcifs@iucr.org>
Sent: Wednesday, May 8, 2024 9:01 PM
To: Discussion list of the IUCr Committee for the Maintenance of the CIF Standard (COMCIFS) <comcifs@iucr.org>
Cc: James H <jamesrhester@gmail.com>
Subject: Re: Assigning CC-BY-4.0 licence to CIF dictionaries
 
Caution: External Sender. Do not open unless you know the content is safe.

This topic has now had six weeks to run and I think everyone has made their position clear, and had a chance to hear everybody's opinion. I do not detect consensus, so I'm going to have to ask the four voting members (myself, Herbert, John B. and Stephen Burley) to vote on the following:

"That any CIF dictionary for which COMCIFS is the custodian be licensed under Creative Commons Licence <x>, unless and until the relevant Dictionary Management Group determines otherwise."

Where <x> is one of:
CC0
CC-BY-4.0
CC-BY-SA-4.0

Please rank your choices 1 to 3. Unless one choice gets an absolute majority of first preferences (3 or 4 votes) we're going to have to count using Condorcet (as used by Debian), as it's likely that there will be a couple each with a single vote and Single Transferable Vote won't work as  it can't break the tie.

To get the ball rolling, my vote:

CC0 3
CC-BY-4.0 1
CC-BY-SA-4.0 2

thanks,
James.

On Thu, 25 Apr 2024 at 08:02, Peter Murray-Rust <pm286@cam.ac.uk> wrote:


On Wed, Apr 24, 2024 at 7:12 AM James H via comcifs <comcifs@iucr.org> wrote:
I want to analyse Herbert's concerns about CC-BY-SA. Before doing so, what I'm proposing is that we determine a default license, but any of CC0/CC-BY/CC-BY-SA would be acceptable depending on how the dictionary authors want to jump. This is similar to Wikimedia, which allow these licenses but individual projects can choose which one they prefer.

> The CC licenses have been lawyered very carefully so that they do what the claim to do in as many jurisdictions as possible. They are used every day by thousands of organisations and individuals. Our situation (wanting to publically share documents) is precisely the one envisaged by Creative Commons. I don't think this is a situation requiring consulting a lawyer.

I would agree.
I am not a lawyer but have been variously involved (including payment) with IP (licences, copyrights, trademarks, patents, tradesecrets, i related to software, pharmaceuticals, documents, protocols and take the view that if something has to be resolved in court it's very expensive, jurisdiction-dependent and usually unpredictable. 

The major (new) issue now is not licenses of individual items but control of and restriction of access to content, whether "OA" or not . This is aggravated by the rise of aggregators and megapublishers who act as if licences do not apply to them, and AI scrapers who scrap and reuse at random. With a few others I have fought these over the years but gained little support

Some examples:
* small molecule data effectively belongs to CCDC - nominally part of the Univ od Cambridge but in practice an autonomous organization. They prohibit the re-use of more than a trivial subset of "their" content and will lawlerize "offenders". Effectively they have a near. monology on small-molecule crystallography.   They have an "agreement" with Elsevier that crystallographic data is deposited directly into CCDC and never sees the light of public. Huge kudos to Crystallography Open Database COD for creating a subset alternative (I am proud to be on the advisory board). People devloping forcefields from "CCDC data" have been lawyered. It has effectively meant that "public" data-driven research is controlled by CCDC.
* Springergate. I discovered that Springer copyrighted ALL images in "their" publications (https://blogs.ch.cam.ac.uk/pmr/2012/06/06/springergate-springerimages-for-today/) including my and Wikipedia's CC-BY (SA). They charged 60 USD and added restrictive licences. When confronted they said it was a "glitch" and withdrew the images. 
* SSRN - a preprint server https://en.wikipedia.org/wiki/Social_Science_Research_Network which the SocSci community trusted as Open for many years. It was bought for a huge sum (rumoured >>100 Million USD) and is now effectively closed and run by Elsevier
* CLOCKSS, etc. - many expired journals are now only accessible through preservation services which are incredibl;y tortuous and restrictive - maybe only access in a clean room and only pen and paper allowed. https://asistdl.onlinelibrary.wiley.com/doi/10.1002/asi.24460

One common route into this is a voluntary organization sets something up, gains res[ect and value, runs into financial trouble, is "helped" by megapublishers and ends up as a commercial arm of SpringSeverLey.

As a scientific community we generally work by "community norms" and the bioscience, astronomy, crystallography, have prospered without much explicit licensing. We should think *at the beginning* about governance. In the Shuttleworth Foundation we developed a "poison pill" licence which would deter assimilation.

The biggest effective defence is sunlight. Post CIF spec everywhere. Version. it critically . Make sure it's got multiple preservation. Add a tool  (e.g. checksums) to track integrity. Urge that all re-use, especially by company software can be verified . Make verification software universal - effectively unittests forintegrity. This can be done on a voluntary basis - e.g. pledges. We have the tools to monitor this. I would expect almot universal takeup and no pushback.


P.

--
"I always retain copyright in my papers, and nothing in any contract I sign with any publisher will override that fact. You should do the same".

Peter Murray-Rust
Reader Emeritus in Molecular Informatics
Yusuf Hamied Department of Chemistry
University of Cambridge
CB2 1EW, UK
+44-1223-336432


--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148


Email Disclaimer: www.stjude.org/emaildisclaimer
Consultation Disclaimer: www.stjude.org/consultationdisclaimer
_______________________________________________
comcifs mailing list
comcifs@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/comcifs


--
T +61 (02) 9717 9907
F +61 (02) 9717 3145
M +61 (04) 0249 4148
_______________________________________________
comcifs mailing list
comcifs@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/comcifs
_______________________________________________
comcifs mailing list
comcifs@iucr.org
http://mailman.iucr.org/cgi-bin/mailman/listinfo/comcifs

Reply to: [list | sender only]