Service — 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 service name. schema.org/name
`provider`	string	optional	The provider name when needed. schema.org/provider
`areaServed`	string	optional	The served geography or audience when needed. schema.org/areaServed
`sameAs`	string[]	optional	Canonical URLs for the same service. schema.org/sameAs

The canonical shape

What a Service 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": "Service",
  "name": "ENS Name Service",
  "provider": "ENS Labs",
  "areaServed": "Global"
}

build one

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

const atomData = buildAtomData("service", {
	name: "ENS Name Service",
	provider: "ENS Labs",
});

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

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

Service — provider → PersonorCompany proposed

Service — area served → Location proposed

Service — has category → Defined Term enshrined

Service — url → url value enshrined

Service — same as → another Service enshrined

Enrichment

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