<?xml version="1.0" encoding="UTF-8"?><!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Publishing DTD v1.2 20190208//EN" "http://jats.nlm.nih.gov/publishing/1.2/JATS-journalpublishing1.dtd"><article xmlns:mml="http://www.w3.org/1998/Math/MathML" xmlns:xlink="http://www.w3.org/1999/xlink" article-type="other" dtd-version="1.2" xml:lang="en">
    <front>
        <journal-meta>
            <journal-id journal-id-type="pmc">F1000Research</journal-id>
            <journal-title-group>
                <journal-title>F1000Research</journal-title>
            </journal-title-group>
            <issn pub-type="epub">2046-1402</issn>
            <publisher>
                <publisher-name>F1000 Research Limited</publisher-name>
                <publisher-loc>London, UK</publisher-loc>
            </publisher>
        </journal-meta>
        <article-meta>
            <article-id pub-id-type="doi">10.12688/f1000research.128167.1</article-id>
            <article-categories>
                <subj-group subj-group-type="heading">
                    <subject>Policy Brief</subject>
                </subj-group>
                <subj-group>
                    <subject>Articles</subject>
                </subj-group>
            </article-categories>
            <title-group>
                <article-title>The road to success: drawing parallels between 'road' and 'research data' infrastructures to foster understanding between service providers, funders and policymakers</article-title>
                <fn-group content-type="pub-status">
                    <fn>
                        <p>[version 1; peer review: 2 approved]</p>
                    </fn>
                </fn-group>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author" corresp="yes">
                    <name>
                        <surname>Hooft</surname>
                        <given-names>Rob W.W.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Conceptualization</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0001-6825-9439</uri>
                    <xref ref-type="corresp" rid="c1">a</xref>
                    <xref ref-type="aff" rid="a1">1</xref>
                </contrib>
                <contrib contrib-type="author" corresp="no">
                    <name>
                        <surname>Martin</surname>
                        <given-names>Corinne S.</given-names>
                    </name>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Original Draft Preparation</role>
                    <role content-type="http://credit.niso.org/">Writing &#x2013; Review &amp; Editing</role>
                    <uri content-type="orcid">https://orcid.org/0000-0002-5428-2766</uri>
                    <xref ref-type="aff" rid="a2">2</xref>
                </contrib>
                <aff id="a1">
                    <label>1</label>Dutch Techcentre for Life Sciences, Utrecht, 3521 AL, The Netherlands</aff>
                <aff id="a2">
                    <label>2</label>ELIXIR Hub, Hinxton, Cambridge, CB10 1SD, UK</aff>
            </contrib-group>
            <author-notes>
                <corresp id="c1">
                    <label>a</label>
                    <email xlink:href="mailto:rob.hooft@dtls.nl">rob.hooft@dtls.nl</email>
                </corresp>
                <fn fn-type="conflict">
                    <p>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>23</day>
                <month>1</month>
                <year>2023</year>
            </pub-date>
            <pub-date pub-type="collection">
                <year>2023</year>
            </pub-date>
            <volume>12</volume>
            <elocation-id>ELIXIR-88</elocation-id>
            <history>
                <date date-type="accepted">
                    <day>13</day>
                    <month>12</month>
                    <year>2022</year>
                </date>
            </history>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Hooft RWW and Martin CS</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access article distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <self-uri content-type="pdf" xlink:href="https://f1000research.com/articles/12-88/pdf"/>
            <abstract>
                <p>
                    <bold>Background:</bold> The work of data research infrastructure operators is poorly understood, yet the services they provide are used by millions of scientists across the planet.</p>
                <p>
                    <bold>Policy and implications:</bold> As the data services and the underlying infrastructure are typically funded through the public purse, it is essential that policymakers, research funders, experts reviewing funding proposals, and possibly even end-users are equipped with a good understanding of the daily tasks of service providers.</p>
                <p>
                    <bold>Recommendations:</bold> We suggest drawing parallels between research data infrastructure and road infrastructure. To trigger the imagination and foster understanding, this policy brief contains a table of corresponding aspects of the two classes of infrastructure.</p>
                <p>
                    <bold>Conclusions:</bold> Just as economists and specialist evaluators are typically brought in to inform policies and funding decisions for road infrastructure, we encourage this to also be done for research infrastructures.</p>
            </abstract>
            <kwd-group kwd-group-type="author">
                <kwd>Research Data</kwd>
                <kwd>Research Infrastructure</kwd>
                <kwd>Infrastructure Funding</kwd>
                <kwd>Sustainability</kwd>
            </kwd-group>
            <funding-group>
                <award-group id="fund-1" xlink:href="http://dx.doi.org/10.13039/501100007601">
                    <funding-source>Horizon 2020</funding-source>
                    <award-id>871075</award-id>
                </award-group>
                <award-group id="fund-2">
                    <funding-source>ELIXIR</funding-source>
                </award-group>
                <funding-statement>This work was supported by ELIXIR, the research infrastructure for life-science data, including the ELIXIR-funded Strategic Implementation Study &#x201c;Impact evaluation at Node-level - getting it done&#x201d;. This work also received funding from the European Union&#x2019;s Horizon 2020 research and innovation programme under grant agreement No 871075 (ELIXIR-CONVERGE).</funding-statement>
                <funding-statement>
                    <italic>The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.</italic>
                </funding-statement>
            </funding-group>
        </article-meta>
    </front>
    <body>
        <sec id="sec1" sec-type="intro">
            <title>Introduction</title>
            <p>Data-intensive research depends on data and data services, such as databases, software and tools, and standards. These are often made available to end-users through research infrastructure. Such a research infrastructure for biological data and bioinformatics service in Europe is 
                <ext-link ext-link-type="uri" xlink:href="https://elixir-europe.org/">ELIXIR</ext-link>.
                <sup>
                    <xref ref-type="bibr" rid="ref1">1</xref>
                </sup>
            </p>
            <p>As is common for many types of infrastructure&#x00a0;(especially&#x00a0;those that are free at the point of use), the existence of research infrastructure, like the services provided by ELIXIR, is often taken for granted by their users. Their importance is only noticed when they are (temporarily) unavailable, or worse, 
                <ext-link ext-link-type="uri" xlink:href="http://gigasciencejournal.com/blog/imicrobe-qa-bonnie-hurwitz/">could disappear due to discontinued funding</ext-link>.
                <sup>
                    <xref ref-type="bibr" rid="ref2">2</xref>
                </sup>
                <sup>,</sup>
                <sup>
                    <xref ref-type="bibr" rid="ref3">3</xref>
                </sup> In the 
                <ext-link ext-link-type="uri" xlink:href="https://en.wikipedia.org/wiki/Kano_model">Kano model</ext-link>, infrastructure services are must-be qualities: their proper functioning does not make the users happy, but service disruptions are strong dissatisfiers.</p>
            <p>As research infrastructures and their services are typically funded through the public purse, it is essential that policy makers, research funders, experts reviewing funding proposals, and possibly even end-users are equipped with a good understanding of the daily tasks of service providers. We have noticed that this is not often the case, and this becomes an issue when this lack of understanding affects the funding of research infrastructures. To foster better understanding, this policy brief provides a comparison table of features of data infrastructure and their relatable counterparts in road infrastructure. We believe that using this approach can help, first because the change in mind frame makes it possible to see consequences of certain choices more clearly, especially those linked to funding of research infrastructures. Second, many people, even those working in research, are much more accustomed to road infrastructure setup and road infrastructure disruptions than to research infrastructure setup and research infrastructure disruptions; this increased familiarity increases the chances that consequences of policy decisions are foreseen.</p>
            <p>For the actual feature comparison, see 
                <xref ref-type="table" rid="T1">Table 1</xref>.</p>
            <table-wrap id="T1" orientation="portrait" position="float">
                <label>Table 1. </label>
                <caption>
                    <title>Comparable concepts in research data infrastructure and road infrastructure.</title>
                </caption>
                <table content-type="article-table" frame="hsides">
                    <thead>
                        <tr>
                            <th align="left" colspan="1" rowspan="1" valign="top">Data infrastructure</th>
                            <th align="left" colspan="1" rowspan="1" valign="top">Road infrastructure</th>
                        </tr>
                    </thead>
                    <tbody>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Data service</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Road</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">User of a data service/Researcher</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Car driver</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Research project</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Car</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Cutting edge research project</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Expensive car</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Project</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Trip, journey</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">The one who develops and operates a service, service provider</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Road construction and maintenance&#x00a0;company</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Flexible data service</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Road suitable for cargo and people</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Hack something together yourself</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Driving your own Jeep from Manchester to Cambridge, possibly off-road</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Using a well-documented and well-maintained existing service</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Driving the motorway from Manchester to Cambridge in a mid-class comfortable car</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Services that the user pays for</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Toll road</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Centrally financed service that therefore is oversubscribed/abused (e.g. free repository where someone dumps 1TB of data)</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Traffic Jam</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Services that can be used by anyone, the user does not need to be part of the infrastructure that provides them</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Public roads</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Interoperable services</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Road intersections, motorway interchanges</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Non-interoperable services</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Crossing roads without intersections</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Efficiency of a well-thought-out service</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Speed of a Ferrari on an asphalt road</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Efficiency of letting everyone figure things out themselves</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Speed of a Jeep on rough terrain</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Thinking data infrastructure is too expensive (or lacking sufficient accommodation of one's specific needs) and preferring to build everything yourself to exact specifications; underestimating the value of services (e.g. 24/7 support) and underestimating the real cost of building everything yourself (excluding e.g. energy bills, and the fact that the postdoc employed for the task is not productive for work while making weekly backups)</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Not being willing to pay road taxes or to pay another centralised tax system (or complaining that you have to walk the last bit from the parking lot), underestimating the value provided (to its users) by the road infrastructure and underestimating the cost incurred to get exactly from A-&gt;B without roads (i.e. using an all-terrain car), e.g. forgetting that there won't be any gas stations along the way either</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">What can be realistically achieved in a scientific project</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">How far you can travel in a day</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">ELIXIR's visibility (i.e. prominence)&#x00a0;in biology</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Public knowledge about the companies building&#x00a0;and maintaining&#x00a0; roads</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">ELIXIR's visibility in bioinformatics</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Knowledge in the government about the companies building and maintaining&#x00a0;roads</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Not knowing whether the infrastructure will live long enough to serve your entire project (and its successor), and therefore being coerced into building it yourself</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Not knowing whether the roads will be maintained for 10 years, and therefore better off buying a Jeep than either a Ferrari or a Volkswagen</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Infrastructure investing in services based on community needs</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Government prioritising road investments based on transport needs</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Asking a research infrastructure provider what scientific breakthroughs the infrastructure will be making. An RI facilitates/enables breakthroughs (as well as enabling more routine research to be carried out) but does not make them itself nor predict what they will be</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Asking a road construction/maintenance company how much faster the distance will be travelled. The road enables road users to travel at average and perhaps faster speeds, but the road construction/maintenance company cannot predict what cars they will use and what they will carry</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Making the requirement that a funding proposal for "infrastructure" includes scientific breakthroughs to happen within a set timeline, instead of enabling routine and breakthrough research as long as the infrastructure is useful</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">Asking a road company to deploy a combination of a very fast asphalt depositing machine, a Ferrari, and a system to clean up the road immediately afterwards</td>
                        </tr>
                        <tr>
                            <td align="left" colspan="1" rowspan="1" valign="top">Asking top scientists to review proposals for research infrastructure funding. The services that would be offered by the infrastructure would be "competing" with what they (and only similar top scientists) can get done in their own labs</td>
                            <td align="left" colspan="1" rowspan="1" valign="top">To ask those who have expensive Jeeps whether they approve the construction of a public road. They and others with off-road cars do not see the need for roads, they can get along just fine without them</td>
                        </tr>
                    </tbody>
                </table>
            </table-wrap>
        </sec>
        <sec id="sec2">
            <title>Policy outcomes and implications</title>
            <p>The comparison between research data infrastructure and road infrastructure has many hooks to support productive discussions, and decisions, on research infrastructure funding and sustainability governance. Given that we, the co-authors, all work in research infrastructures, there is an inherent bias in the approach presented, just like when Sutherland 
                <italic toggle="yes">et al.</italic>
                <sup>
                    <xref ref-type="bibr" rid="ref4">4</xref>
                </sup> published their &#x201c;20 things politicians need to know about science&#x201d;. Yet, we also do not intend to be counterproductive: policymaking is complex and multifaceted, as astutely explained in &#x201c;
                <ext-link ext-link-type="uri" xlink:href="https://www.theguardian.com/science/2013/dec/02/scientists-policy-governments-science">20 things scientists need to know about policy</ext-link>&#x201d;. The comparison table is simply our contribution to fostering longer-term sustainability of infrastructures that already exist, that are widely used across the world, and that have typically received significant public financing over the years.</p>
            <p>Furthermore, the comparison table is likely to support efforts of both research infrastructure operators and policymakers in 
                <ext-link ext-link-type="uri" xlink:href="https://www.theguardian.com/science/political-science/2013/dec/04/12-things-policy-makers-and-scientists-should-know-about-the-public">more accurately conveying to taxpayers</ext-link> the public value of research infrastructures, in addition to their role as enablers of scientific discovery and applications of societal benefit. The word &#x2018;enablers&#x2019; is perhaps the most important message to convey: just like a road enables travel (and a research infrastructure enables research), it is questionable whether it is right to ask the road construction/maintenance company (and the research infrastructure operator) whether the road (and the research infrastructure) bring(s) value to society. Economists and evaluation specialists are very well placed and qualified (and likely unbiased) to answer 
                <ext-link ext-link-type="uri" xlink:href="https://www.embl.org/documents/document/embl-ebi-impact-report-2021/">complex</ext-link> 
                <ext-link ext-link-type="uri" xlink:href="https://www.icos-cp.eu/sites/default/files/2018-09/ICOS_Impact_Assessment_Report_2018.pdf">questions</ext-link> around the public value of financing roads and research infrastructures.
                <sup>
                    <xref ref-type="bibr" rid="ref5">5</xref>
                </sup>
                <sup>,</sup>
                <sup>
                    <xref ref-type="bibr" rid="ref6">6</xref>
                </sup>
            </p>
        </sec>
        <sec id="sec3">
            <title>Actionable recommendations</title>
            <p>
                <bold>
                    <italic toggle="yes">Recommendation 1</italic>
                </bold>: When formulating opinions and decisions on research data infrastructure funding and sustainability governance, compare them with that of road infrastructure. The change of frame may bring new insights.</p>
            <p>
                <bold>
                    <italic toggle="yes">Recommendation 2</italic>
                </bold>: Consider informing policies and funding decisions relating to existing and future research infrastructure with support from economists and specialist evaluators.</p>
        </sec>
        <sec id="sec4" sec-type="conclusion">
            <title>Conclusion</title>
            <p>We welcome any additional rows for the comparison as well as discussion on improving the existing table in 
                <ext-link ext-link-type="uri" xlink:href="https://bit.ly/RoadDataInfra">the original Google Document</ext-link>. We have found it difficult to broaden the set of comparisons to also include a sustainable travel angle (e.g. examples covering public transport versus private car travel). Considering the climate emergency, this would be a useful and still relatable expansion of the approach.</p>
        </sec>
    </body>
    <back>
        <sec id="sec7" sec-type="data-availability">
            <title>Data availability</title>
            <p>No data are associated with this article</p>
        </sec>
        <ref-list>
            <title>References</title>
            <ref id="ref1">
                <label>1</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Harrow</surname>
                            <given-names>J</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Drysdale</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Smith</surname>
                            <given-names>A</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>ELIXIR: providing a sustainable infrastructure for life science data at European scale.</article-title>
                    <source>

                        <italic toggle="yes">Bioinformatics.</italic>
</source>
                    <year>15 August 2021</year>;<volume>37</volume>(<issue>16</issue>):<fpage>2506</fpage>&#x2013;<lpage>2511</lpage>.
                    <pub-id pub-id-type="pmid">34175941</pub-id>
                    <pub-id pub-id-type="doi">10.1093/bioinformatics/btab481</pub-id>
                    <pub-id pub-id-type="pmcid">PMC8388016</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref2">
                <label>2</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Merali</surname>
                            <given-names>Z</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Giles</surname>
                            <given-names>J</given-names>
                        </name>
</person-group>:
                    <article-title>Databases in peril.</article-title>
                    <source>

                        <italic toggle="yes">Nature.</italic>
</source>
                    <year>2005</year>;<volume>435</volume>:<fpage>1010</fpage>&#x2013;<lpage>1011</lpage>.
                    <pub-id pub-id-type="doi">10.1038/4351010a</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref3">
                <label>3</label>
                <mixed-citation publication-type="journal">
                    <comment>

                        <italic toggle="yes">E.g. Figure 6 in&#x00a0;</italic>
</comment>
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Drysdale</surname>
                            <given-names>R</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Cook</surname>
                            <given-names>CE</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Petryszak</surname>
                            <given-names>R</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>The ELIXIR Core Data Resources: fundamental infrastructure for the life sciences.</article-title>
                    <source>

                        <italic toggle="yes">Bioinformatics.</italic>
</source>
                    <year>15 April 2020</year>;<volume>36</volume>(<issue>8</issue>):<fpage>2636</fpage>&#x2013;<lpage>2642</lpage>.
                    <pub-id pub-id-type="pmid">31950984</pub-id>
                    <pub-id pub-id-type="doi">10.1093/bioinformatics/btz959</pub-id>
                    <pub-id pub-id-type="pmcid">PMC7446027</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref4">
                <label>4</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Sutherland</surname>
                            <given-names>W</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Spiegelhalter</surname>
                            <given-names>D</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Burgman</surname>
                            <given-names>M</given-names>
                        </name>
</person-group>:
                    <article-title>Policy: Twenty tips for interpreting scientific claims.</article-title>
                    <source>

                        <italic toggle="yes">Nature.</italic>
</source>
                    <year>2013</year>;<volume>503</volume>:<fpage>335</fpage>&#x2013;<lpage>337</lpage>.
                    <pub-id pub-id-type="pmid">24273799</pub-id>
                    <pub-id pub-id-type="doi">10.1038/503335a</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref5">
                <label>5</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Martin</surname>
                            <given-names>CS</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Repo</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Arenas M&#x00e1;rquez</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>Demonstrating public value to funders and other stakeholders&#x2014;the journey of ELIXIR, a virtual and distributed research infrastructure for life science data.</article-title>
                    <source>

                        <italic toggle="yes">Ann. Public Coop. Econ.</italic>
</source>
                    <year>2021</year>;<volume>92</volume>(<issue>3</issue>):<fpage>497</fpage>&#x2013;<lpage>510</lpage>.
                    <pub-id pub-id-type="doi">10.1111/apce.12328</pub-id>
                </mixed-citation>
            </ref>
            <ref id="ref6">
                <label>6</label>
                <mixed-citation publication-type="journal">
                    <person-group person-group-type="author">

                        <name name-style="western">
                            <surname>Vignetti</surname>
                            <given-names>S</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Pezzati</surname>
                            <given-names>L</given-names>
                        </name>

                        <name name-style="western">
                            <surname>Striova</surname>
                            <given-names>J</given-names>
                        </name>

                        <etal/>
</person-group>:
                    <article-title>E-RIHS PP D6.1 Cost Benefit Analysis and socioeconomic impact assessment.</article-title>
                    <source>

                        <italic toggle="yes">Zenodo.</italic>
</source>
                    <year>2020</year>.
                    <pub-id pub-id-type="doi">10.5281/zenodo.3946205</pub-id>
                </mixed-citation>
            </ref>
        </ref-list>
    </back>
    <sub-article article-type="reviewer-report" id="report161289">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.140729.r161289</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Vignetti</surname>
                        <given-names>Silvia</given-names>
                    </name>
                    <xref ref-type="aff" rid="r161289a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r161289a1">
                    <label>1</label>CSIL, Milan, Italy</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>I hereby declare that, in reviewing the article 'The road to success: drawing parallels between 'road' and 'research data' infrastructures to foster understanding between service providers, funders and policymakers' by Hooft RWW and Martin CST, no conflict of interest applied.&#13;
&#13;
In the interest of full transparency, I report herewith the non-financial relationships I have with one of the authors of the paper, Martin C.S.:&#13;
&#13;
- During the period 01/01/2018-01/06/2020, on behalf of our own institutes (CSIL and ELIXIR) we were both members of the research team of the project &#x2018;Charting Impact Pathways of Investment in Research Infrastructure&#x2019; a research project granted by H2020 programme aimed at developing a model describing the socio-economic impact of research infrastructures and of their related financial investments. In the context of this project, we co-authored the report Deliverable 5.1 of the RI-PATHS Project.&#13;
&#13;
- Since the 1st of September 2022, we are both part of the PathOS project, a Horizon Europe programme aiming to collect concrete evidence of Open Science effects and study the pathways of Open Science practices. The project will last four years and we will collaborate to develop a joint case study. We work on PathOS for two different institutions, being partners in the project. They are supposed to be one of the case studies and we are supposed to perform an analysis of impacts generated by one of the open resources they have. Two people are working from their side and three experts are working from our side, in addition to all the other project partners (8 institutions for a total of more than 30 people involved). However, both Martin and I have a more supervising role, while the other colleagues are more hands-on.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>13</day>
                <month>4</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Vignetti S</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport161289" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.128167.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This article sheds light on the important and often poorly understood world of research infrastructures providing data and other research services to scientific communities around the world to perform excellent science. It does so by showing the features a research infrastructure has with a road infrastructure, with the aim of making clear why and how public funding must be understood and justified.</p>
            <p> The article is well-written and to some extent illuminating. The parallel with road infrastructures is fitting quite well with&#x00a0;the purpose of the authors. The parallel may go even further in depicting the parallels with other infrastructures delivering public services such as water supply, sewage system and so on. The article however does not fully exploit the potential of this parallel and remains a bit open and generic in the explanations.</p>
            <p> </p>
            <p> First, the table, which is pretty much the core of the article, presents some elements that should be better qualified, explained and perhaps even reconsidered in a few cases (e.g. "
                <italic>data service</italic>" corresponds perhaps more to 'transport service' than to "
                <italic>road</italic>"; it is not clear why "
                <italic>research project</italic>" corresponds to "
                <italic>car</italic>" and "
                <italic>project</italic>"&#x00a0;to "
                <italic>trip, journey</italic>"; "
                <italic>oversubscribed service</italic>" may be 'crowded road' more than "
                <italic>traffic jam</italic>"), so it would be better to add a short explanation or a narrative section where the content of the table is described, justified and put in context.</p>
            <p> </p>
            <p> Second, the policy options and implications do not come immediately from the description of the main common features, especially for those who are not familiar with both research and more traditional infrastructures. Perhaps the table could be split in two to distinguish the key features (first half) from the policy implications on their funding and public justification (second half more or less).&#x00a0;</p>
            <p> </p>
            <p> Overall, the article is very interesting and well-conceived, but it would benefit from a small additional effort to better explain the main claim and its implications.</p>
            <p>Does the paper provide a comprehensive overview of the policy and the context of its implementation in a way which is accessible to a general reader?</p>
            <p>Yes</p>
            <p>Is the discussion on the implications clearly and accurately presented and does it cite the current literature?</p>
            <p>Partly</p>
            <p>Are the recommendations made clear, balanced, and justified on the basis of the presented arguments?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Public policy analysis and evaluation, infrastructure appraisal, economic evaluation</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
        <sub-article article-type="response" id="comment9982-161289">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Hooft</surname>
                            <given-names>Rob</given-names>
                        </name>
                        <aff>Health-RI, The Netherlands</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>28</day>
                    <month>7</month>
                    <year>2023</year>
                </pub-date>
            </front-stub>
            <body>
                <p>We thank you very much for this accurate and positive description of our work. You make a very good suggestion relating to expanding the analogies to other public service infrastructures. Along this line and during the writing process, we had actually been tempted to introduce a climate change element to some of the analogies, e.g. how mass transit (train) may not satisfy all the specific transportation needs of all users, just like an international database might not either, yet these are far more cost-effective and climate-friendly than the proliferation of 100s of very specific databases and 1,000s of jeeps on the roads. We have added your suggestions at the end of the article.</p>
                <p> </p>
                <p> We agree with your suggestions on the table. We have split the table as you suggested in version 2 of the article, and have added relevant text in the [now two] tables, which are more readily understandable as a result. We have also invited an additional co-author (Elaine Harrison), with science communications specialism, to reformulate and strengthen the text, in line with the your comments.</p>
            </body>
        </sub-article>
    </sub-article>
    <sub-article article-type="reviewer-report" id="report164512">
        <front-stub>
            <article-id pub-id-type="doi">10.5256/f1000research.140729.r164512</article-id>
            <title-group>
                <article-title>Reviewer response for version 1</article-title>
            </title-group>
            <contrib-group>
                <contrib contrib-type="author">
                    <name>
                        <surname>Sgard</surname>
                        <given-names>Fr&#x00e9;d&#x00e9;ric</given-names>
                    </name>
                    <xref ref-type="aff" rid="r164512a1">1</xref>
                    <role>Referee</role>
                </contrib>
                <aff id="r164512a1">
                    <label>1</label>OECD, Paris, France</aff>
            </contrib-group>
            <author-notes>
                <fn fn-type="conflict">
                    <p>
                        <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                </fn>
            </author-notes>
            <pub-date pub-type="epub">
                <day>28</day>
                <month>3</month>
                <year>2023</year>
            </pub-date>
            <permissions>
                <copyright-statement>Copyright: &#x00a9; 2023 Sgard F</copyright-statement>
                <copyright-year>2023</copyright-year>
                <license xlink:href="https://creativecommons.org/licenses/by/4.0/">
                    <license-p>This is an open access peer review report distributed under the terms of the Creative Commons Attribution Licence, which permits unrestricted use, distribution, and reproduction in any medium, provided the original work is properly cited.</license-p>
                </license>
            </permissions>
            <related-article ext-link-type="doi" id="relatedArticleReport164512" related-article-type="peer-reviewed-article" xlink:href="10.12688/f1000research.128167.1"/>
            <custom-meta-group>
                <custom-meta>
                    <meta-name>recommendation</meta-name>
                    <meta-value>approve</meta-value>
                </custom-meta>
            </custom-meta-group>
        </front-stub>
        <body>
            <p>This policy brief addresses a very important element of research policy, which is the understanding by decision-makers of the role, relevance, and impact of research infrastructures. In this particular case, of research data infrastructure, by using a comparison with a much well known type of infrastructures: roads. This comparison with a much more mundane example (roads) is aptly supported by a strong argument regarding the usefulness of the infrastructure mostly appears when its activity is disrupted, as normal operation is often taken for granted and thus invisible. The comparison between data research infrastructures and roads is clearly and convincingly argumented. This brief is also timely as funders are increasingly stretched to provide support to existing and new research infrastructures and have to make selective choices in their investments.</p>
            <p>Does the paper provide a comprehensive overview of the policy and the context of its implementation in a way which is accessible to a general reader?</p>
            <p>Yes</p>
            <p>Is the discussion on the implications clearly and accurately presented and does it cite the current literature?</p>
            <p>Yes</p>
            <p>Are the recommendations made clear, balanced, and justified on the basis of the presented arguments?</p>
            <p>Yes</p>
            <p>Reviewer Expertise:</p>
            <p>Science policy</p>
            <p>I confirm that I have read this submission and believe that I have an appropriate level of expertise to confirm that it is of an acceptable scientific standard.</p>
        </body>
        <sub-article article-type="response" id="comment9981-164512">
            <front-stub>
                <contrib-group>
                    <contrib contrib-type="author">
                        <name>
                            <surname>Hooft</surname>
                            <given-names>Rob</given-names>
                        </name>
                        <aff>Health-RI, The Netherlands</aff>
                    </contrib>
                </contrib-group>
                <author-notes>
                    <fn fn-type="conflict">
                        <p>
                            <bold>Competing interests: </bold>No competing interests were disclosed.</p>
                    </fn>
                </author-notes>
                <pub-date pub-type="epub">
                    <day>28</day>
                    <month>7</month>
                    <year>2023</year>
                </pub-date>
            </front-stub>
            <body>
                <p>We are very grateful for your kind words on the usefulness of this policy brief, especially to funders of research infrastructures. We hope that version 2 has strengthened the brief.</p>
            </body>
        </sub-article>
    </sub-article>
</article>
