Software Application
A software application identity with optional category and platform metadata.
Fields
1 required · 4 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 software application name. schema.org/name |
applicationCategory |
string | optional | The application category when needed. schema.org/applicationCategory |
operatingSystem |
string | optional | The target operating system when needed. schema.org/operatingSystem |
url |
url | optional | The canonical app URL. schema.org/url |
sameAs |
string[] | optional | Canonical URLs that identify the same software application. schema.org/sameAs |
The canonical shape
What a Software Application atom's data looks like. These exact bytes are what calculateAtomId hashes — shared shape is shared identity.
{
"@context": "https://schema.org/",
"@type": "SoftwareApplication",
"name": "Notion",
"applicationCategory": "Productivity",
"operatingSystem": "Web"
}
import { buildAtomData } from "@0xintuition/classifications";
import { calculateAtomId } from "@0xintuition/ids";
const atomData = buildAtomData("software-application", {
name: "Notion",
applicationCategory: "Productivity",
});
// deterministic — same bytes, same ID, offchain and on
const atomId = calculateAtomId(atomData);
What a Software Application 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.
Enrichment
Paste a bare reference and the enrichment engine fills a Software Application in from its sources (default pipeline: software-application) — titles, canonical sameAs URLs, and the fields above, merged onto the same deterministic atom.