Skip to content

Commit 84b3aee

Browse files
committed
Typos.
1 parent 66e6177 commit 84b3aee

File tree

2 files changed

+15
-14
lines changed

2 files changed

+15
-14
lines changed

sections/03-challenges.qmd

Lines changed: 13 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -56,17 +56,6 @@ have not yet had significant adoption as tools of day-to-day computational
5656
practice. At the same time, it provides clarity and robustness for standards
5757
developers communities that are well-versed in these tools.
5858

59-
## Unclear pathways for standards success
60-
61-
Standards typically develop organically through sustained and persistent
62-
efforts from dedicated groups of data practitioners. These include scientists
63-
and the broader ecosystem of data curators and users. However, there is no
64-
playbook on the structure and components of a data standard, or the pathway
65-
that moves the implementation of a specific data architecture (e.g., a
66-
particular file format) to become a data standard. As a result, data
67-
standardization lacks formal avenues for success and recognition, for example
68-
through dedicated research grants (and see @sec-cross-sector). This hampers the long-term trajectory that is needed in order to inculcate a standard into the
69-
day-to-day practice of researchers.
7059

7160
## Cross-domain gaps
7261

@@ -141,8 +130,20 @@ cases, file formats that were once not straightforward to use in the cloud,
141130
such as HDF5 and TIFF have been adapted to cloud use (e.g., through the
142131
cloud-optimized geoTIFF format).
143132

144-
## Sustainability
145133

134+
## Unclear pathways for standards success and sustainability
135+
136+
The development of open-source standards faces similar sustainability challenges to
137+
those faced by open-source software that is developed for research. Standards
138+
typically develop organically through sustained and persistent efforts from
139+
dedicated groups of data practitioners. These include scientists and the
140+
broader ecosystem of data curators and users. However, there is no playbook on
141+
the structure and components of a data standard, or the pathway that moves the
142+
implementation of a specific data architecture (e.g., a particular file format)
143+
to become a data standard. As a result, data standardization lacks formal
144+
avenues for success and recognition, for example through dedicated research
145+
grants (and see @sec-cross-sector). This hampers the long-term trajectory that
146+
is needed to inculcate a standard into the day-to-day practice of researchers.
146147

147148

148149
## The importance of automated validation

sections/05-recommendations.qmd

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,7 +28,7 @@ Advancing the development and adoption of open-source standards requires the
2828
dissemination of knowledge to researchers in a variety of fields, but this
2929
dissemination itself may not be enough without the fostering of specialized
3030
expertise. Therefore, it is important to recognize the distinct role that *data
31-
stewards* play in contemporary research. As policy demands for openess become
31+
stewards* play in contemporary research. As policy demands for openness become
3232
increasingly high, it is crucial to truly support experts whose role will be to
3333
develop, maintain, and facilitate the adoption and use of open-source
3434
standards. This support needs to manifest in all stages of the career of these
@@ -101,7 +101,7 @@ assessment of an existing standard, or as guidelines to develop new standards.
101101
For instance, barriers to adopting a data standard irrespective of team size
102102
and technological capabilities should be considered. Meta-standards should
103103
include formalization for versioning of standards and interactions with
104-
speficic related software. Aspects of communication with potential user
104+
specific related software. Aspects of communication with potential user
105105
audiences (e.g., researchers in particular domains) should be taken into
106106
account as well. For example, in the quality of onboarding documentation and
107107
tools for ingestion or conversion into standards-compliant datasets. Relatedly,

0 commit comments

Comments
 (0)