Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frontiers licenses #40

Closed
Daniel-Mietchen opened this issue Nov 13, 2012 · 4 comments
Closed

Frontiers licenses #40

Daniel-Mietchen opened this issue Nov 13, 2012 · 4 comments

Comments

@Daniel-Mietchen
Copy link
Member

Frontiers recently switched from CC BY-NC to CC BY as their default license. However, the few files that are labeled as being CC BY normally end up recognized as "Unknown, possibly non-free license".

Examples:
10.3389/fphys.2012.00293
10.3389/fphys.2012.00414
10.3389/fmicb.2012.00338

More via https://www.google.com/search?q=10.3389+video&sugexp=chrome,mod=16&sourceid=chrome&ie=UTF-8#hl=en&tbo=d&sclient=psy-ab&q=10.3389+%22supplemental+data%22+(movie+OR+video)+%22creative+commons+attribution+license%22 .

@erlehmann
Copy link

Unfortunately, Frontiers does not distinguish its licensing via use of the <license> element href attribute:

        <license license-type="open-access" xlink:href="http://www.frontiersin.org/licenseagreement">
          <license-p>This is an open-access article distributed under the terms of the <uri xlink:type="simple" xlink:href="http://creativecommons.org/licenses/by/3.0/">Creative Commons Attribution License</uri>, which permits use, distribution and reproduction in other forums, provided the original authors and source are credited and subject to any copyright notices concerning any third-party graphics etc.</license-p>
        </license>

@erlehmann
Copy link

So, should OAMI look at <license-p> elements when <license> elements give a proprietary license?

@Daniel-Mietchen
Copy link
Member Author

probably yes.

@Daniel-Mietchen
Copy link
Member Author

Frontiers articles have worked fine for a while now - closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants