Bibliographic record
Abstract
In many ways, a precondition to realizing the promise of open government data is the standardization of that data. Open data standards ensure interoperability, establish benchmarks in assessing whether governments achieve their goals in publishing open data, can better ensure accuracy of the data. Interoperability enables the use of off-the shelf software and can ease third party development of products that serves multiple locales. Our project aims to determine which standards for civic data are “best” to open up government data. We began by disambiguating the multiple meanings of what constitutes a data standard by creating a standards stack. The empirical research started by identifying twelve “high value” open datasets for which we found 22 data standards. A qualitative systematic review of the gray literature and standards documentation generated 18 evaluation metrics, which we grouped into four categories. We evaluated the metrics with civic data standards. Our goal is to identify and characterize types of standards and provide a systematic way to assess their quality.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Direct model labels (unvalidated)
Per-model category and study-design labels from the labeling rounds. They are machine output, unvalidated, and the disagreement between models ships as data. No study design here is MEDLINE-validated yet.
| Model arm | Categories | Study design | Confidence |
|---|---|---|---|
| gemma | Open science Domain: not available · Genre: Empirical About the Canadian research system: no · About a Canadian topic: no | Not applicable | low |
| gpt | no category Domain: not available · Genre: Empirical About the Canadian research system: no · About a Canadian topic: no | Other design | low |
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.288 | 0.505 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.002 |
| Bibliometrics | 0.026 | 0.029 |
| Science and technology studies | 0.004 | 0.006 |
| Scholarly communication | 0.011 | 0.018 |
| Open science | 0.003 | 0.010 |
| Research integrity | 0.003 | 0.003 |
| Insufficient payload (model declined to judge) | 0.002 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedLabeled directly by 2 models reading the full record.
The models disagree on parts of this classification; every voice is preserved in the section at the end of the page.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".