Submission Workflow
01
Gather Verifiable Evidence
Collect immutable links, cryptographic release hashes, benchmark DOIs, and SPDX license identifiers for the target resource.
02
Author YAML Frontmatter
Create a Markdown record in _evaluations/ or _decisions/ conforming to the schema below.
03
Peer Review & Consensus
Working group reviewers validate score calculations, verify artifact hashes, and merge approved records into the public build.
Template
Evaluation Record Frontmatter Schema
---
title: "Example Open Resource"
resource_id: "RR-SW-0099"
category: "Software" # Software | Dataset | Platform | Digital Resource
version: "2.4.0"
license: "Apache-2.0"
steward: "Example Foundation"
canonical_url: "https://example.org"
assessor: "Working Group Name"
assessed_date: 2026-11-18
overall_score: 88
decision_id: "RDR-002"
decision_record: "/decisions/rdr-002-transactional-persistence/"
summary: "Concise one-sentence description of the evaluated resource."
dimensions:
- name: "Provenance & Lineage"
weight: 25
score: 90
notes: "Signed releases and clear SPDX licensing."
- name: "Empirical Evidence & Reproducibility"
weight: 30
score: 86
notes: "Public benchmark suite with reproducible instructions."
- name: "Operational Reliability & Maintenance"
weight: 25
score: 88
notes: "Active multi-maintainer governance and CI coverage."
- name: "Open Standards & Interoperability"
weight: 20
score: 88
notes: "Supports open protocols and lossless data export."
evidence:
- id: "EV-099-A"
type: "Provenance"
description: "Release SHA-256 Checksum & Provenance Attestation"
reference: "sha256:e3b0c44298fc1c149afbf4c8996fb924..."
---