Skip to content

Commit 83d99e0

Browse files
authored
Merge pull request #1 from vanitech/day1updates
feat: Drafted a few more challenges with headings and brief descriptions
2 parents 7eed4ca + 63c77d3 commit 83d99e0

File tree

2 files changed

+20
-1
lines changed

2 files changed

+20
-1
lines changed

_metadata.yml

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,5 +6,10 @@ authors:
66
corresponding: true
77
orcid: 0000-0003-0679-1985
88
# Add your name and metadata here:
9+
- name: Vani Mandava
10+
affiliation: University of Washington
11+
roles: writing
12+
corresponding: true
13+
orcid: 0000-0003-3592-9453
914

1015
bibliography: references.bib

sections/02-challenges.qmd

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ of a new standard [^1].
1111
been devoted to it.
1212

1313
Another failure is the mismatch between developers of the standard and users.
14-
There is an iherent gap in both interest and ability to engage with the
14+
There is an inherent gap in both interest and ability to engage with the
1515
technical details undergirding standards and their development between the
1616
developers of the standard and their users. In extreme cases, these interests
1717
may be at odds, as developers implement sophisticated mechanisms to automate
@@ -20,6 +20,20 @@ mechanisms for evolving the standard, leaving potential users sidelined in the
2020
development of the standard, and limiting their ability to provide feedback
2121
about the practical implications of changes to the standards.
2222

23+
## Unclear pathways for standards success
24+
25+
Standards typically develop organically through sustained and persistent efforts from dedicated
26+
groups of data practitioneers. These include scientists and the broader ecosystem of data curators and users. However there is no playbook on the structure and components of a data standard, or the pathway that moves a data implementation to a data standard.
27+
As a result, data standardization lacks formal avenues for research grants.
28+
29+
## Cross domain funding gaps
30+
31+
Data standardization investment is justified if the standard is generalizable beyond any specific science domain. However while the use cases are domain sciences based, data standardization is seen as a data infrastrucutre and not a science investment. Moreover due to how science research funding works, scientists lack incentives to work across domains, or work on infrastructure problems.
32+
33+
## Data instrumentation issues
34+
35+
Data for scientific observations are often generated by proprietary instrumentation due to commercialization or other profit driven incentives. There islack of regulatory oversight to adhere to available standards or evolve Significant data transformation is required to get data to a state that is amenable to standards, if available. If not available, there is lack of incentive to set aside investment or resources to invest in establishing data standards.
36+
2337
## Sustainability
2438

2539
## The importance of automated validation

0 commit comments

Comments
 (0)