|
1 |
| -# Abstract |
2 |
| - |
3 |
| -Recent progress in machine learning and artificial intelligence promises to |
4 |
| -advance research and understanding across a wide range of fields and |
5 |
| -activities. In tandem, increased awareness of the importance of open data for |
6 |
| -reproducibility and scientific transparency is making inroads in fields that |
7 |
| -have not traditionally produced large publicly available datasets. Data sharing |
8 |
| -requirements from publishers and funders, as well as from other stakeholders, |
9 |
| -have also created pressure to make datasets with research and/or public |
10 |
| -interest value available through digital repositories. However, to make the |
11 |
| -best use of existing data, and facilitate the creation of useful future |
12 |
| -datasets, robust, interoperable and usable standards need to evolve and adapt |
13 |
| -over time. The open-source development model provides significant potential |
14 |
| -benefits to the process of standard creation and adaptation. In particular, the |
15 |
| -development and adaptation of standards can use long-standing socio-technical |
16 |
| -processes that have been key to managing the development of software, and allow |
17 |
| -incorporating broad community input into the formulation of these standards. By |
18 |
| -adhering to open-source standards to formal descriptions (e.g., by implementing |
19 |
| -schemata for standard specification, and/or by implementing automated standard |
20 |
| -validation), processes such as automated testing and continuous integration, |
21 |
| -which have been important in the development of open-source software, can be |
22 |
| -adopted in defining data and metadata standards as well. Similarly, open-source |
23 |
| -governance provides a range of stakeholders a voice in the development of |
24 |
| -standards, potentially enabling use cases and concerns that would not be taken |
25 |
| -into account in a top-down model of standards development. On the other hand, |
26 |
| -open-source models carry unique risks that need to be incorporated into the |
27 |
| -process. |
28 |
| - |
29 |
| - |
30 | 1 | {{< include sections/01-introduction.qmd >}}
|
31 | 2 | {{< include sections/02-use-cases.qmd >}}
|
32 | 3 | {{< include sections/03-challenges.qmd >}}
|
33 | 4 | {{< include sections/04-cross-sector.qmd >}}
|
34 | 5 | {{< include sections/05-recommendations.qmd >}}
|
35 | 6 | {{< include sections/06-acknowledgments.qmd >}}
|
36 |
| -{{< include sections/07-participants.qmd >}} |
37 | 7 |
|
38 |
| -# References |
| 8 | +# References |
| 9 | +:::{#refs} |
| 10 | +::: |
| 11 | + |
| 12 | +\newpage |
| 13 | + |
| 14 | +{{< include sections/07-participants.qmd >}} |
0 commit comments