Article — Classifications

Fields

1 required · 3 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
`headline`	string	required	The title or headline of the article. schema.org/headline
`description`	string	optional	A short summary of the article. schema.org/description
`url`	url	optional	The canonical article URL. schema.org/url
`sameAs`	string[]	optional	Canonical URLs that identify the same article. schema.org/sameAs

The canonical shape

What a Article 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": "Article",
  "headline": "Intuition Is Taking Over The World",
  "description": "Intuition, the onchain knowledge graph, is taking over the world.",
  "url": "https://example.com/article"
}

build one

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

const atomData = buildAtomData("article", {
	headline: "Intuition Is Taking Over The World",
	description: "Intuition, the onchain knowledge graph, is taking over the world.",
});

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

What a Article 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.

Article — authored by → Person proposed

Article — publisher → Company proposed

Article — has description → string value enshrined

Article — url → url value enshrined

Article — reference → schema.org/CreativeWorkorany atom proposed

Article — listed in → schema.org/Collection enshrined

Article — has category → Defined Term enshrined

Article — same as → another Article enshrined

Enrichment

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