Short answer
The deterministic ZIP contains ten members at its crate root: ro-crate-metadata.json, a script-free ro-crate-preview.html, bilingual README and CC BY 4.0 attribution files, five data entities and checksums-sha256.txt. The payload covers the canonical 37-row UTF-8 CSV, equivalent JSON Lines, MLCommons Croissant 1.1 metadata, W3C CSVW metadata and the SKOS JSON-LD vocabulary. The metadata descriptor uses the required ro-crate-metadata.json identifier, points to one absolute root Dataset and declares conformance to RO-Crate 1.3. Every root hasPart File has a relative URI, name, description, media type, exact byte size and SHA-256. Validation uses the official 1.3 context pinned to an immutable public source commit, expands the graph offline and checks every path, byte, digest, checksum and deterministic ZIP property. Available third-party validator profiles currently stop at RO-Crate 1.2, so the resource does not claim third-party 1.3 certification. It also assigns no DOI, registers no repository deposit and makes no claim of external ingest or RO-Crate community endorsement.
Download the ZIP and checksums-sha256.txt, verify the ZIP bytes, extract it without changing paths, then parse ro-crate-metadata.json with an RO-Crate 1.3-aware tool. Confirm the root Dataset, seven hasPart entities, relative file paths, byte lengths and SHA-256 values before repository staging.
What to look for before choosing
- Complete U+3105 through U+3129 coverage in a canonical 37-row CSV and equivalent JSON Lines
- RO-Crate 1.3 descriptor, root Dataset and seven exact local File data entities
- Croissant 1.1, W3C CSVW and SKOS JSON-LD metadata in one attached crate
- Script-free static preview, bilingual reuse guide and CC BY 4.0 attribution
- Deterministic ten-member ZIP with byte-exact SHA-256 checksums
A practical decision process
- Open the bilingual guide and download the attached ZIP plus checksums-sha256.txt.
- Verify the published ZIP SHA-256 before extraction.
- Confirm that ro-crate-metadata.json references the official RO-Crate 1.3 context and profile.
- Check that all seven root hasPart paths exist and match their contentSize and sha256 values.
- Test the extracted crate with a 1.3-aware consumer before repository ingest.
Quick comparison
| Need | What to check | Why it matters |
|---|---|---|
| Research-object structure | RO-Crate 1.3 metadata descriptor linked to one absolute root Dataset | Consumers can find the crate root without guessing from filenames |
| Portable core data | CSV, JSON Lines, Croissant, CSVW and SKOS files use relative crate paths | The extracted ZIP remains useful without depending on an app or account |
| Fixity and reproducibility | Stable member order, fixed ZIP timestamps and SHA-256 for every member except the checksum list | A repository can reproduce and compare the exact transfer bytes |