Skip to content

Commit 6e722ce

Browse files
committed
A bit more about the cross-sector piece.
1 parent 2581b15 commit 6e722ce

File tree

1 file changed

+38
-7
lines changed

1 file changed

+38
-7
lines changed

sections/xx-cross-sector.qmd

Lines changed: 38 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -52,19 +52,50 @@ executive director, Brian Nosek, entitled "Strategy for Culture Change"
5252
science requires an alignment of not only incentives and values, but also
5353
technical infrastructure and user experience. A sociotechnical bridge between
5454
these pieces, which makes the adoption of standards possible, and maybe even
55-
easy, and the policy goals, arises from a community of practice that makes
55+
easy, and the policy goals, arises from a community of practice that makes the
5656
adoption of standards *normative*. Once all of these pieces are in place,
5757
making adoption of open science standards *required* through policy becomes
5858
more straightforward and less onerous.
5959

6060
## Funding
6161

62-
While government-set policy is primarily directed towards research that is
63-
funded through governmental funding agencies, there are other ways in which
64-
funding relates to the development of open-source standards. One way is in
65-
funding the development of these standards. For example, the National
66-
Institutes of Health have provided some of the funding for the development of
67-
the Brain Imaging Data Structure standard in neuroscience. Where large governmental funding agencies may not have
62+
Government-set policy intersects with funding considerations. This is because
63+
it is primarily directed towards research that is funded through governmental
64+
funding agencies. For example, high-level policy guidance boils to practice in
65+
guidance for data management plans that are part of funded research. In
66+
response to the policy guidance, these have become increasingly more detailed
67+
and, for example, NSF- and NIH-funded researchers are now required to both
68+
formulate their plans with more clarity and increasingly also to share data
69+
using specified standards as a condition for funding.
70+
71+
However, there are other ways in which funding relates to the development of
72+
open-source standards. For example, through the BRAIN Initiative, the National
73+
Institutes of Health have provided key funding for the development of the Brain
74+
Imaging Data Structure standard in neuroscience. Where large governmental
75+
funding agencies may not have the resources or agility required to fund nascent
76+
or unconventional ways of formulating standards, funding by non-governmental
77+
philanthropies and other organizations can provide alternatives. One example
78+
(out of many) is the Chan-Zuckerberg Initiative program for Essential Open
79+
Source Software, which funds foundational open-source software projects that
80+
have an application in biomedical sciences. Distinct from NIH funding, however,
81+
some of this investment focuses on the development of OSS practices. For
82+
example, funding to the Arrow project that focuses on developing open-source
83+
software maintenance skills and practices, rather than a specific biomedical
84+
application.
85+
86+
87+
## Industry
88+
89+
Interactions of data and meta-data standards with commercial interests may
90+
provide specific sources of friction. This is because proprietary/closed
91+
formats of data can create difficulty at various transition points: from one
92+
instrument vendor to another, from data producer to downstream recipient/user,
93+
etc. On the other hand, in some cases cross-sector collaborations with
94+
commercial entities may pave the way to robust and useful standards. One
95+
example is the DICOM standard, which is maintained by working groups that
96+
encompass commercial imaging device vendors and researchers.
97+
98+
6899

69100

70101

0 commit comments

Comments
 (0)