What

First developed in a 2015 blog post, POSI offers a set of guidelines by which open scholarly infrastructure organisations and initiatives that support the research community can be run and sustained. Others have since built on the foundation of POSI to discuss and propose how all those that support scholarly communications can use these principles to hold each other accountable. This includes the following:

Why

This site codifies POSI as a community resource. Many open infrastructure organisations are at different stages of their journeys toward compliance with POSI. As more attention is paid to open infrastructure, we’ve missed having a place where POSI can be more closely integrated into the community’s vision for scholarly research.

This site therefore provides a reference point for organisations that are discussing and striving to meet POSI. It also aims to address some commonly-heard misconceptions around what is “open” and what is “infrastructure” via the FAQs.

Who

Any organisation that provides open infrastructure for research and scholarly communications is welcome; this is not an exclusive club. The site was set up by the original blog post authors and collaborators who have contributed to and built upon POSI. While the website is hosted by Crossref, individuals from California Digial Library, DataCite, eLife, and Dryad have so far been involved in this site. To contact us, please open a GitLab issue.

How

Any initiative can self-identify as open infrastructure and pointing to this site allows anyone to make a public statement of intent and to invite community appraisal. If you would like to cite POSI, please use: Bilder G, Lin J, Neylon C (2020), The Principles of Open Scholarly Infrastructure, retrieved [date], https://doi.org/10.24343/C34W2H

For now this website is simply a home for the principles. In the future, it could be a place where the community records POSI adopters or even measures progress. If you’d like to share experiences with POSI or ideas about what this site could achieve more broadly, please open a GitLab issue for others to comment on.