Event — 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
`name`	string	required	The name of the event. schema.org/name
`startDate`	iso-date	optional	The event start date. schema.org/startDate
`location`	string	optional	The location name when needed. schema.org/location
`sameAs`	string[]	optional	Canonical URLs for the same event. schema.org/sameAs

The canonical shape

What a Event 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": "Event",
  "name": "ETHDenver 2026",
  "startDate": "2026-01-01",
  "location": "Denver, Colorado"
}

build one

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

const atomData = buildAtomData("event", {
	name: "ETHDenver 2026",
	startDate: "2026-02-26",
});

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

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

Event — organizer → PersonorCompany proposed

Event — performer → PersonorMusic GrouporCompany proposed

Event — sponsored by → Company proposed

Event — sub event → Event proposed

Event — super event → Event proposed

Event — located in → Location proposed

Event — same as → another Event enshrined

Enrichment

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