Dataset — Classifications

Fields

1 required · 2 recommended. Every field points at its schema.org property — the definition lives in one place, so nothing drifts. The full inherited superset stays available through @0xintuition/schema-org.

Field	Type		Description
`name`	string	required	The name of the dataset. schema.org/name
`url`	url	optional	The canonical dataset URL. schema.org/url
`sameAs`	string[]	optional	Canonical references such as DOI links. schema.org/sameAs

The canonical shape

What a Dataset atom's data looks like. These exact bytes are what calculateAtomId hashes — shared shape is shared identity.

atom data · canonical JSON-LD

{
  "@context": "https://schema.org/",
  "@type": "Dataset",
  "name": "Global Surface Temperature",
  "url": "https://example.org/datasets/global-surface-temperature",
  "sameAs": [
    "https://doi.org/10.1234/example-dataset"
  ]
}

build one

import { buildAtomData } from "@0xintuition/classifications";
import { calculateAtomId } from "@0xintuition/ids";

const atomData = buildAtomData("dataset", {
	name: "Global Surface Temperature",
	url: "https://example.org/datasets/global-surface-temperature",
});

// deterministic — same bytes, same ID, offchain and on
const atomId = calculateAtomId(atomData);

What a Dataset can say

The recommended triple vocabulary for this classification — each row is a claim shape the graph already understands, with the kind of atom expected on the other end.

Dataset — created by → PersonorCompany enshrined

Dataset — publisher → Company proposed

Dataset — reference → schema.org/CreativeWorkorany atom proposed

Dataset — url → url value enshrined

Dataset — same as → another Dataset enshrined

Enrichment

Paste a bare reference and the enrichment engine fills a Dataset in from its sources (default pipeline: dataset) — titles, canonical sameAs URLs, and the fields above, merged onto the same deterministic atom.