CINXE.COM
FAQ - The Principles of Open Scholarly Infrastructure
<!DOCTYPE html> <html lang="en" itemscope itemtype="http://schema.org/WebPage"> <head> <meta charset="utf-8" /> <meta http-equiv="X-UA-Compatible" content="IE=edge"> <meta name="viewport" content="width=device-width, initial-scale=1.0, maximum-scale=1.0"> <title>FAQ - The Principles of Open Scholarly Infrastructure</title> <meta name="description" content="Frequently-answered questions"><script type="application/ld+json"> { "@context": "http://schema.org", "@type": "WebSite", "name": "The Principles of Open Scholarly Infrastructure", "url": "https:\/\/openscholarlyinfrastructure.org\/" } </script><script type="application/ld+json"> { "@context": "http://schema.org", "@type": "Organization", "name": "", "url": "https:\/\/openscholarlyinfrastructure.org\/" } </script> <script type="application/ld+json"> { "@context": "http://schema.org", "@type": "BreadcrumbList", "itemListElement": [{ "@type": "ListItem", "position": 1, "item": { "@id": "https:\/\/openscholarlyinfrastructure.org\/", "name": "home" } },{ "@type": "ListItem", "position": 3, "item": { "@id": "https:\/\/openscholarlyinfrastructure.org\/faq\/", "name": "Faq" } }] } </script><script type="application/ld+json"> { "@context": "http://schema.org", "@type": "Article", "author": { "name" : "" }, "headline": "FAQ", "description" : "How do I cite POSI? Cite as Bilder G, Lin J, Neylon C (2020), The Principles of Open Scholarly Infrastructure, retrieved [date], https:\/\/doi.org\/10.24343\/C34W2H Do you have to meet all the commitments of POSI before you can adopt POSI? No. For one thing, this would make it impossible for new organisations to adopt POSI. Our experience in the founding of infrastructure services like Dryad, DataCite, ORCID, ROR, and Crossref is that one of the biggest challenges to developing any new infrastructure is gaining the trust of the community. One powerful way to address the community’s legitimate skepticism, is to adopt a set of operating principles from the start. They can then help to shape foundational decisions about governance, funding, and technology strategies. We would also like to see existing organisations adopt POSI as a statement of intent. Doing so provides their stakeholders with a set of concrete commitments against which the organisation can be measured.\n", "inLanguage" : "en", "wordCount": 1184 , "datePublished" : "2020-11-20T00:00:00\u002b00:00", "dateModified" : "2024-04-14T07:17:03\u002b00:00", "image" : "https:\/\/openscholarlyinfrastructure.org\/img\/avatar-icon.png", "keywords" : [ "" ], "mainEntityOfPage" : "https:\/\/openscholarlyinfrastructure.org\/faq\/", "publisher" : { "@type": "Organization", "name" : "https:\/\/openscholarlyinfrastructure.org\/", "logo" : { "@type" : "ImageObject", "url" : "https:\/\/openscholarlyinfrastructure.org\/img\/avatar-icon.png", "height" : 60 , "width" : 60 } } } </script> <meta property="og:title" content="FAQ" /> <meta property="og:description" content="Frequently-answered questions"> <meta property="og:image" content="https://openscholarlyinfrastructure.org/img/avatar-icon.png" /> <meta property="og:url" content="https://openscholarlyinfrastructure.org/faq/" /> <meta property="og:type" content="website" /> <meta property="og:site_name" content="The Principles of Open Scholarly Infrastructure" /> <meta name="twitter:title" content="FAQ" /> <meta name="twitter:description" content="Frequently-answered questions"> <meta name="twitter:image" content="https://openscholarlyinfrastructure.org/img/avatar-icon.png" /> <meta name="twitter:card" content="summary_large_image" /> <link href='https://openscholarlyinfrastructure.org/img/favicon.ico' rel='icon' type='image/x-icon'/> <meta name="generator" content="Hugo 0.136.4"> <link rel="alternate" href="https://openscholarlyinfrastructure.org/index.xml" type="application/rss+xml" title="The Principles of Open Scholarly Infrastructure"><link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/katex@0.16.7/dist/katex.min.css" integrity="sha384-3UiQGuEI4TTMaFmGIZumfRPtfKQ3trwQE2JgosJxCnGmQpL/lJdjpcHkaaFwHlcI" crossorigin="anonymous"> <link rel="stylesheet" href="https://use.fontawesome.com/releases/v5.5.0/css/all.css" integrity="sha384-B4dIYHKNBt8Bc12p+WXckhzcICo0wtJAoU8YZTY5qE0Id1GSseTk6S+L3BlXeVIU" crossorigin="anonymous"> <link rel="stylesheet" href="https://cdn.jsdelivr.net/npm/bootstrap@3.4.1/dist/css/bootstrap.min.css" integrity="sha384-HSMxcRTRxnN+Bdg0JdbxYKrThecOKuH5zCYotlSAcp1+c8xmyTe9GYg1l9a69psu" crossorigin="anonymous"><link rel="stylesheet" href="https://openscholarlyinfrastructure.org/css/main.css" /><link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Lora:400,700,400italic,700italic" /> <link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Open+Sans:300italic,400italic,600italic,700italic,800italic,400,300,600,700,800" /><link rel="stylesheet" href="https://openscholarlyinfrastructure.org/css/syntax.css" /><link rel="stylesheet" href="https://openscholarlyinfrastructure.org/css/codeblock.css" /><link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/photoswipe/4.1.2/photoswipe.min.css" integrity="sha384-h/L2W9KefUClHWaty3SLE5F/qvc4djlyR4qY3NUV5HGQBBW7stbcfff1+I/vmsHh" crossorigin="anonymous"> <link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/photoswipe/4.1.2/default-skin/default-skin.min.css" integrity="sha384-iD0dNku6PYSIQLyfTOpB06F2KCZJAKLOThS5HRe8b3ibhdEQ6eKsFf/EeFxdOt5R" crossorigin="anonymous"> </head> <body> <nav class="navbar navbar-default navbar-fixed-top navbar-custom"> <div class="container-fluid"> <div class="navbar-header"> <button type="button" class="navbar-toggle" data-toggle="collapse" data-target="#main-navbar"> <span class="sr-only">Toggle navigation</span> <span class="icon-bar"></span> <span class="icon-bar"></span> <span class="icon-bar"></span> </button> <a class="navbar-brand" href="https://openscholarlyinfrastructure.org/">The Principles of Open Scholarly Infrastructure</a> </div> <div class="collapse navbar-collapse" id="main-navbar"> <ul class="nav navbar-nav navbar-right"> <li> <a title="About" href="https://openscholarlyinfrastructure.org/about/">About</a> </li> <li> <a title="Posse" href="https://openscholarlyinfrastructure.org/posse/">Posse</a> </li> <li> <a title="FAQ" href="https://openscholarlyinfrastructure.org/faq/">FAQ</a> </li> <li> <a title="Discussion" href="https://openscholarlyinfrastructure.org/discussion/">Discussion</a> </li> </ul> </div> <div class="avatar-container"> <div class="avatar-img-border"> <a title="The Principles of Open Scholarly Infrastructure" href="https://openscholarlyinfrastructure.org/"> <img class="avatar-img" src="https://openscholarlyinfrastructure.org/img/avatar-icon.png" alt="The Principles of Open Scholarly Infrastructure" /> </a> </div> </div> </div> </nav> <div class="pswp" tabindex="-1" role="dialog" aria-hidden="true"> <div class="pswp__bg"></div> <div class="pswp__scroll-wrap"> <div class="pswp__container"> <div class="pswp__item"></div> <div class="pswp__item"></div> <div class="pswp__item"></div> </div> <div class="pswp__ui pswp__ui--hidden"> <div class="pswp__top-bar"> <div class="pswp__counter"></div> <button class="pswp__button pswp__button--close" title="Close (Esc)"></button> <button class="pswp__button pswp__button--share" title="Share"></button> <button class="pswp__button pswp__button--fs" title="Toggle fullscreen"></button> <button class="pswp__button pswp__button--zoom" title="Zoom in/out"></button> <div class="pswp__preloader"> <div class="pswp__preloader__icn"> <div class="pswp__preloader__cut"> <div class="pswp__preloader__donut"></div> </div> </div> </div> </div> <div class="pswp__share-modal pswp__share-modal--hidden pswp__single-tap"> <div class="pswp__share-tooltip"></div> </div> <button class="pswp__button pswp__button--arrow--left" title="Previous (arrow left)"> </button> <button class="pswp__button pswp__button--arrow--right" title="Next (arrow right)"> </button> <div class="pswp__caption"> <div class="pswp__caption__center"></div> </div> </div> </div> </div> <header class="header-section "> <div class="intro-header no-img"> <div class="container"> <div class="row"> <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1"> <div class="page-heading"> <h1>FAQ</h1> <hr class="small"> <span class="page-subheading">Frequently-answered questions</span> </div> </div> </div> </div> </div> </header> <div class="container" role="main"> <div class="row"> <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1"> <article role="main" class="blog-post"> <h2 id="how-do-i-cite-posi">How do I cite POSI?</h2> <p>Cite as <code>Bilder G, Lin J, Neylon C (2020), The Principles of Open Scholarly Infrastructure, retrieved [date], https://doi.org/10.24343/C34W2H </code></p> <hr> <h2 id="do-you-have-to-meet-all-the-commitments-of-posi-before-you-can-adopt-posi">Do you have to meet all the commitments of POSI before you can adopt POSI?</h2> <p>No. For one thing, this would make it impossible for new organisations to adopt POSI. Our experience in the founding of infrastructure services like Dryad, DataCite, ORCID, ROR, and Crossref is that one of the biggest challenges to developing any new infrastructure is gaining the trust of the community. One powerful way to address the community’s legitimate skepticism, is to adopt a set of operating principles from the start. They can then help to shape foundational decisions about governance, funding, and technology strategies. We would also like to see existing organisations adopt POSI as a statement of intent. Doing so provides their stakeholders with a set of concrete commitments against which the organisation can be measured.</p> <hr> <h2 id="isnt-adopting-posi-virtue-signalling">Isn’t adopting POSI “Virtue Signalling?”</h2> <p>Yes. This shouldn’t be surprising or contentious. Our entire scholarly communication system is based on virtue signalling. But, of course, the term “virtue signalling” (with scare-quotes) is also sometimes used to insinuate that such signalling is disingenuous and designed primarily for marketing purposes.</p> <p>The principles were drafted with a built-in safeguard against disingenuous use.</p> <p>Adoption of the principles is verifiable. You either have or don’t have broad stakeholder governance. You either have or don’t have a surplus. You either have or don’t have contingency funds. The source code for your infrastructure is either open source or it is not.</p> <p>This means that it is possible for a party to adopt the principles as an aspirational statement, even when they do not yet meet all (or even any) of the requirements. The community can then monitor progress on the individual actions and detect when no progress is being made. The reputational fallout from publicly adopting the principles and then failing to make any progress on them would be severe. Public adoption of the principles as an aspiration becomes a kind of <a href="https://en.wikipedia.org/wiki/Behavior-shaping_constraint">forcing function</a>.</p> <hr> <h2 id="what-do-you-mean-by-stakeholder-does-this-just-mean-those-who-have-made-direct-financial-investments-in-the-infrastructure-organisation">What do you mean by “stakeholder?” Does this just mean those who have made direct financial investments in the infrastructure organisation?</h2> <p>No. This narrow definition of “stakeholder” - focusing solely on those who have “invested” - is not widely held. In fact, common phrases like “<a href="https://www.lexico.com/definition/stakeholder_economy">stakeholder economy</a>” and “<a href="https://hbr.org/2020/01/making-stakeholder-capitalism-a-reality">stakeholder capitalism</a>” describe the exact opposite: systems that don’t just focus on the “investor”, but which instead balance benefits to the investor with benefits to employees, the broader community, society, and the environment.</p> <p>It is this latter, broader definition of “stakeholder” that is used in POSI. Stakeholders referenced in POSI reflect those that have a role in the global scholarly enterprise.</p> <hr> <h2 id="does-posi-exclude-commercial-organisations-from-providing-open-scholarly-infrastructure">Does POSI exclude commercial organisations from providing open scholarly infrastructure?</h2> <p>No. In fact, one of the motivations in developing POSI was to set out some guidelines that could be incorporated into the procurement rules for assessing candidates for public/private partnerships. POSI offers clear ways to compare organisational governance, sustainability and insurance practices irrespective of the organisation’s tax status. These can also be used to evaluate the practices of community-run projects that may not be a legal entity or have formal governance documents.</p> <p>We also think that wide adoption of these principles will actually help commercial organisations because it will set some clear ground-rules about how they can invest in creating services for the community in a way that respects the community’s interests and gains the community’s trust. This, in turn, minimises the financial risk of investing heavily in something that the community ultimately rejects due to concerns about enclosure, privacy, fee hikes, or other evils that are (sometimes unfairly) associated with a service just because it’s not run by a nonprofit. Equally, being a nonprofit does not make adherence to POSI automatic.</p> <hr> <h2 id="there-are-points-made-in-posi-about-open-and-available-data-why-not-refer-to-the-fair-principles">There are points made in POSI about open and available data. Why not refer to the FAIR principles?</h2> <p>First, POSI was developed before FAIR. But, more importantly, although FAIR is a relevant and useful list of principles, it doesn’t speak to core requirements of infrastructure. Nor, to many people’s surprise, does <em>FAIR</em> focus on striving for openness.</p> <hr> <h2 id="is-adoption-or-endorsement-of-posi-only-relevant-to-organisations-actually-running-or-planning-on-running-scholarly-infrastructure">Is adoption or endorsement of POSI only relevant to organisations actually running (or planning on running) scholarly infrastructure?</h2> <p>No. The entire scholarly community needs to take responsibility for ensuring that scholarly infrastructure remains open. POSI offers a way to articulate and assess this. We hope that POSI will be incorporated into institutional procurement processes, funder grant rules, and in community measurements of success.</p> <hr> <h2 id="why-not-open-science-infrastructure-instead-of-open-scholarly-infrastructure">Why not “open science infrastructure” instead of “open scholarly infrastructure?”</h2> <p>Because the research enterprise increasingly transcends disciplines. And we think this is to be encouraged.</p> <p>In some parts of the world, science and technology are increasingly seen as being out-of-touch with the ethical, social, and cultural concerns of the communities within which they operate. We are concerned that infrastructures that focus exclusively on “science” will simply further entrench the “two cultures” divide and exacerbate this trend.</p> <hr> <h2 id="why-not-open-research-infrastructure-instead-of-open-scholarly-infrastructure">Why not “open research infrastructure” instead of “open scholarly infrastructure?”</h2> <p>Because scholarship involves more than “research.” It also includes “teaching”, for example. And we think POSI is as applicable to teaching infrastructures as to research infrastructures.</p> <hr> <h2 id="do-the-posi-principles-only-apply-to-membership-organisations">Do the POSI principles only apply to membership organisations?</h2> <p>No. The principles mostly use the word “member” in the sense of “member of the community.” Although the principles were inspired by the experiences two membership organisations and the examples mentioned (particularly around sustainability) reflect that, the principles make the point that it is important that we explore other models as well. The overall goals are to ensure that the organisation is responsive to members of the community and that it is not entirely dependent on inherently brittle short-term funding cycles. So, for example, one might explore how to normalise the use of long-term grants or partial endowments as the basis for funding.</p> <hr> <h2 id="how-do-you-pronounce-posi">How do you pronounce “POSI?”</h2> <p>In the past we’ve pronounced it a number of ways, but we’ve settled on “posy”- <a href="https://en.wiktionary.org/wiki/posy">as in a small bouquet of flowers</a> 💐</p> <hr> <h2 id="can-the-rules-in-posi-be-flexible">Can the rules in POSI be flexible?</h2> <p>Absolutely. Clauses such as the “1 year of reserves” wind-down clause are meant to achieve a goal/principle, not to be treated as absolutes in themselves. If your organisation requires much less than a year to wind down (or requires much more), this should be adjusted. A good rule of thumb is that you should read POSI statements as <em>principles</em> rather than <em>rules</em>.</p> <hr> <h2 id="i-want-to-use-a-more-restrictive-license-because-i-am-worried-about-third-parties-taking-our-data-and-re-selling-it">I want to use a more restrictive license, because I am worried about third-parties taking our data and re-selling it</h2> <p>While this is a possibility, we have rarely seen it happen. Furthermore, given that the original data are open and available for free, this is not an easy challenge. Generally speaking, using more restrictive licenses merely ends up frustrating well-intentioned downstream re-users and causes problems if a rescue operation is needed for the infrastructure. An example of problematic licensing might be using CC BY-SA on data that researchers might wish to combine with proprietary datasets. This is why we recommend the public domain declaration, CC0.</p> <hr> <p>More questions? Open a <a href="https://gitlab.com/crossref/posi/-/issues">GitLab issue</a>.</p> </article> </div> </div> </div> <div class="page-meta"> (Last modified on April 14, 141414) </div> <footer> <div class="container"> <div class="row"> <div class="col-lg-8 col-lg-offset-2 col-md-10 col-md-offset-1"> <ul class="list-inline text-center footer-links"> </ul> <p class="credits copyright text-muted"> • © 2024 • <a href="https://openscholarlyinfrastructure.org/">The Principles of Open Scholarly Infrastructure</a> </p> <p class="credits theme-by text-muted"> <a href="https://gohugo.io">Hugo v0.136.4</a> powered • Theme <a href="https://github.com/halogenica/beautifulhugo">Beautiful Hugo</a> adapted from <a href="https://deanattali.com/beautiful-jekyll/">Beautiful Jekyll</a> • [<a href="false0492d9bb5d2121beae6680c705cb16840198ad52">0492d9bb</a>] </p> </div> </div> </div> </footer><script defer src="https://cdn.jsdelivr.net/npm/katex@0.16.7/dist/katex.min.js" integrity="sha384-G0zcxDFp5LWZtDuRMnBkk3EphCK1lhEf4UEyEM693ka574TZGwo4IWwS6QLzM/2t" crossorigin="anonymous"></script> <script defer src="https://cdn.jsdelivr.net/npm/katex@0.16.7/dist/contrib/auto-render.min.js" integrity="sha384-+VBxd3r6XgURycqtZ117nYw44OOcIax56Z4dCRWbxyPt0Koah1uHoK0o4+/RRE05" crossorigin="anonymous" onload="renderMathInElement(document.body);"></script> <script src="https://code.jquery.com/jquery-3.7.0.slim.min.js" integrity="sha384-w5y/xIeYixWvfM+A1cEbmHPURnvyqmVg5eVENruEdDjcyRLUSNej7512JQGspFUr" crossorigin="anonymous"></script> <script src="https://cdn.jsdelivr.net/npm/bootstrap@3.4.1/dist/js/bootstrap.min.js" integrity="sha384-aJ21OjlMXNL5UyIl/XNwTMqvzeRMZH2w8c5cRVpzpU8Y5bApTppSuUkhZXN0VxHd" crossorigin="anonymous"></script> <script src="https://openscholarlyinfrastructure.org/js/main.js"></script><script src="https://cdnjs.cloudflare.com/ajax/libs/photoswipe/4.1.2/photoswipe.min.js" integrity="sha384-QELNnmcmU8IR9ZAykt67vGr9/rZJdHbiWi64V88fCPaOohUlHCqUD/unNN0BXSqy" crossorigin="anonymous"></script> <script src="https://cdnjs.cloudflare.com/ajax/libs/photoswipe/4.1.2/photoswipe-ui-default.min.js" integrity="sha384-m67o7SkQ1ALzKZIFh4CiTA8tmadaujiTa9Vu+nqPSwDOqHrDmxLezTdFln8077+q" crossorigin="anonymous"></script><script src="https://openscholarlyinfrastructure.org/js/load-photoswipe.js"></script> </body> </html>