alexmandClaude
a09d158e16
Keys (spec/02 §2.4), the rule paperstack settled on:
- A work key is a Scholar-style citation key, a hyphen and the first four
Crockford base32 characters of SHA-256("scienting-key/1:" + identity),
where the identity is the first of doi, arxiv, isbn, pmid, pmcid and
openalex in same_as, else the folded title, year and family name. A
collision lengthens the later key by two characters; a key is minted
once and never recomputed. A document key adds .si, .v<seq> or .<type>
for versions other than the version of record.
- Every fixture key is now minted (hale2026harmonic-damb,
okafor2025solvent-acth, writer2027fixed-ynr7.v3, tiny2026tiny-j4qm), so
every node and record ID was re-minted and the docs rewritten to match.
The validator checks the document key against the work key and version
(doc.key.work) and the hash part against the identifier (doc.key.suffix).
vectors/keys.jsonl pins the cases paperstack's tests pin.
Review:
- Spot-check seeds are ECVRF-EDWARDS25519-SHA512-TAI proofs (RFC 9381),
implemented in tools/oracle/vrf.py in plain Python and reproduced
against the RFC's Example 16; the sample ranks by the VRF output. The
earlier Ed25519 seed could be ground by a dishonest checker.
- RFC 9162 inclusion and consistency proofs (crypto.inclusion_path,
verify_inclusion, consistency_proof, verify_consistency) with
scienting-proof/1, vectors/proofs.jsonl and two fixture records.
- document.json carries `history`, the root over the corrections, with
the empty-tree hash for none (spec/11 §11.5, rule doc.history).
- A provisional transparency log (spec/23): log entries, signed-note
checkpoints with key hashes as transparency logs share them, the rule
that a logged revocation beats a self-asserted time, and vectors.
- Reserved signature schemes cose and ml-dsa-65 (spec/08 §8.4).
Identifiers and text:
- urn:scienting: becomes tag:scient.ing,2026: (RFC 4151), since the URN
namespace was never registered.
- Unicode 16.0 is pinned for normalization and categories (spec/01 §1.4);
the checker refuses another version.
Checking:
- check.py: keys, proofs, VRF and checkpoint vectors; the proof and
checkpoint records; a check that every ID and hash the prose quotes
exists in the fixtures or vectors; three more broken packages
(history-wrong, key-suffix, key-work).
- stress.py: key, VRF, proof and checkpoint properties.
- Docs: a keys section in the concepts and FAQ, rationale entries for
keys, VRF, proofs, tag URIs and the Unicode pin, a "Looking ahead"
section, media-type registration and OCI distribution notes.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
1.9 KiB
15. Datasets
A dataset, scienting-dataset/1, is a Frictionless Data Package (datapackage.json with CSV or Parquet resources) with three additions.
| Addition | Meaning |
|---|---|
| Units | Every numeric field has a unit, a string Pint can parse, so a checker can test dimensions. |
| Uncertainty | A field may give uncertainty: {field?, kind}, the field that holds it and its kind, sd, se, resolution or unknown. |
| Origin | Each resource has an origin, or origin_field and origins when it varies by row. |
| Origin | Holds |
|---|---|
reported |
Values anchored to the table cells or sentences that print them, in anchors.jsonl. |
digitized |
Values read off a figure: the digitization's ID, and anchors.jsonl naming each value's series and point. |
computed |
A claim's implementation, by claim and pin. |
measured |
The team's own data, with its provenance. |
The descriptor also carries format and an id, ds- and a key.
Each line of anchors.jsonl names a resource, a row (by primary key) and a field, and either an anchor or a digitization, series and point.
A value or row is addressed as ds-…/<row>/<field>.
Values keep their digits as printed: CSV cells are never reformatted, and in JSON values are strings, so 1.526 and 1.5260 stay different.
A digitized value never passes as reported, and its uncertainty is at least the resolution of its digitization.
A dataset's content hash is SHA-256 of the canonical JSON of {"format": "scienting-dataset/1", "files": [[path, sha256, size], …]} over its files, sorted by path.
A dataset can be a source of kind dataset, so a claim can rest on a value read from a figure, with that fact visible in its evidence.
fixtures/packages/hale2026harmonic-damb/datasets/ds-hale-bond-params reports Table 1, and the suite checks that every value resolves to the cell that prints it.