Person — Classifications

Fields

2 required · 1 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
`givenName`	string	required	The person’s given or first name. schema.org/givenName
`familyName`	string	required	The person’s family or last name. schema.org/familyName
`sameAs`	string[]	optional	Canonical URLs that identify the same person. schema.org/sameAs

The canonical shape

What a Person 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": "Person",
  "givenName": "Vitalik",
  "familyName": "Buterin",
  "sameAs": [
    "https://example.com/canonical"
  ]
}

build one

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

const atomData = buildAtomData("person", {
	givenName: "Vitalik",
	familyName: "Buterin",
	sameAs: ["…"],
});

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

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

Person — member of → Company proposed

Person — employed by → Company proposed

Person — affiliated with → Company proposed

Person — alumni of → schema.org/EducationalOrganization proposed

Person — same as → another Person enshrined

Person — url → url value enshrined

Enrichment

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