You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: sections/03-challenges.qmd
+13-12Lines changed: 13 additions & 12 deletions
Original file line number
Diff line number
Diff line change
@@ -56,17 +56,6 @@ have not yet had significant adoption as tools of day-to-day computational
56
56
practice. At the same time, it provides clarity and robustness for standards
57
57
developers communities that are well-versed in these tools.
58
58
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.
70
59
71
60
## Cross-domain gaps
72
61
@@ -141,8 +130,20 @@ cases, file formats that were once not straightforward to use in the cloud,
141
130
such as HDF5 and TIFF have been adapted to cloud use (e.g., through the
142
131
cloud-optimized geoTIFF format).
143
132
144
-
## Sustainability
145
133
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.
0 commit comments