Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
If rights are not provided, default to GBIF use and sharing agreement? #12
We are analyzing the
Option 1: Default to GBIF use and sharing agreement
Note: of course, this assessment only holds true if the data are obtained via GBIF, which is a scope we want to analyse.
Option 2: We cannot assume anything: the license is unclear
For datasets where no license is provided:
For all other datasets (even those that legally do not require attribution):
As mentioned, we will also discuss the use outside the GBIF context, for which these parameters are not overwritten.
I believe this is illogical.
Since data are not copyright protected, the only way to prevent their
You can have
but not your model
Not sure. I have no conclusion on what the GBIF license requires. I just point out that the ability to distribute it (and I assume without a confidentiality clause, i.e. distribute as in a scientific publications) makes it difficult if not impossible to enforce a "non-commercial" clause.
Neither adding permissions nor removing permissions (or the appearance of doing either) makes any sense.
You cannot add permissions (or remove conditions) such as 'distribution: true' because you do not have the legal standing to do so.
Technically you have a right to remove permissions (or add conditions) such as 'commercial: false' because a DUA can impose arbitrary requirements on signers - a DUA can insist that someone stand on their head every Tuesday, if it wants to. (A copyright license, on the other hand, can only remove permissions if there's a broader permission to remove them from, which in this scenario there isn't.) But if you remove permissions you might gratuitously take away rights that someone would have had had they not entered into the DUA. They might have been depending on those rights, in fact they may have acquired those rights from the rightsholder, in fact they might be the rightsholder, and signing them away does neither you nor them any good at all, it is meddling in a relationship that is none of your business.
To be quite graphic, suppose that someone makes an occurrence database, and releases it on the web without license, but also makes their living from it through consulting or inclusion in products that they sell. They must never sign a GBIF DUA imposing a noncommercial term, because then they would lose their livelihood! The problem is not specific to NC, but applies to any term or condition.
I'm not a lawyer but may I suggest that these sources merely be marked only "released without license statement" (which is the simple truth, the hypothesis we're considering) and let the buyer beware. I don't think you have any choice. If you're afraid this will scare people off, give a hyperlink to a brief explanation of why you considered it to be OK that the source is included in your collection - that it was publicly readable, its existence was advertised, and you looked for a statement of restriction or policy and found none - or whatever it is you believe about the situation.
Of course you're always free to give advice on how to cite sources and exercise good manners, quite independent of any legal framework. GBIF could have an influence on the community by providing a good example.
@jar398, @gmhagedorn, thanks for the feedback. I have decided that I will just present the licenses used by data publishers, and not an interpretation of those in combination with the GBIF DUA (or results based on that interpretation).
I will reference this github issue and mention that the GBIF DUA doesn't solve the situation of having no license, since it cannot add permissions to unlicensed data (it's still buyer beware), only add conditions.
If I may extend this just a little bit, I'd like to ask that GBIF be exceedingly clear about the difference between a copyright license and a DUA. The providers' copyright licenses should be grouped together and marked as such. That material enjoys the benefits of copyright such as automatic applicability without click-through, exemptions such as fair use and "facts are free", expiration, and multiple licensing. You don't get any of these with most DUAs. GBIF's DUA should only impose those conditions that GBIF's data providers require GBIF to impose, according to whatever DUA holds between the provider and GBIF. I understand that some providers require GBIF to impose a DUA, but that should not infect GBIF's treatment of material that does not require a DUA (public domain or copyright protected). In fact, GBIF should require a DUA only when a provider requires GBIF to require one. If a user is accessing non-DUA material at GBIF's site, he/she shouldn't have to sign a DUA.
Ideally every DUA should have a termination clause, too - how do I get out of the contract, once I've entered into it? It should be sufficient to, say, delete all copies of the covered material and notify GBIF.