The Principles of Open Scholarly Infrastructure

peter.suber's bookmarks 2020-12-03

Summary:

"

  • Open source – All software required to run the infrastructure should be available under an open source license. This does not include other software that may be involved with running the organisation.
  • Open data (within constraints of privacy laws) – For an infrastructure to be forked it will be necessary to replicate all relevant data. The CC0 waiver is best practice in making data legally available. Privacy and data protection laws will limit the extent to which this is possible
  • Available data (within constraints of privacy laws) – It is not enough that the data be made “open” if there is not a practical way to actually obtain it. Underlying data should be made easily available via periodic data dumps.
  • Patent non-assertion – The organisation should commit to a patent non-assertion covenant. The organisation may obtain patents to protect its own operations, but not use them to prevent the community from replicating the infrastructure...."

Link:

https://openscholarlyinfrastructure.org/

From feeds:

Open Access Tracking Project (OATP) » peter.suber's bookmarks

Tags:

oa.new oa.infrastructure oa.posi oa.principles oa.academic_led oa.sustainability oa.floss oa.data oa.privacy oa.patents oa.best_practices oa.recommendations oa.economics_of

Date tagged:

12/03/2020, 10:29

Date published:

12/03/2020, 05:29