schema-dts

JSON-LD TypeScript types for Schema.org vocabulary.

schema-dts provides TypeScript definitions for Schema.org vocabulary in JSON-LD format. The typings are exposed as complete sets of discriminated type unions, allowing for easy completions and stricter validation.

Note: This is not an officially supported Google product.

Usage

To use the typings for your project, simply add the schema-dts NPM package to your project:

1npm install schema-dts

Then you can use it by importing "schema-dts".

Examples

Defining Simple Properties

1import type {Person} from 'schema-dts';
2
3const inventor: Person = {
4  '@type': 'Person',
5  name: 'Grace Hopper',
6  disambiguatingDescription: 'American computer scientist',
7  birthDate: '1906-12-09',
8  deathDate: '1992-01-01',
9  awards: [
10    'Presidential Medal of Freedom',
11    'National Medal of Technology and Innovation',
12    'IEEE Emanuel R. Piore Award',
13  ],
14};

Using 'Context'

JSON-LD requires a "@context" property to be set on the top-level JSON object, to describe the URIs represeting the types and properties being referenced. schema-dts provides the WithContext<T> type to facilitate this.

1import type {Organization, Thing, WithContext} from 'schema-dts';
2
3export function JsonLd<T extends Thing>(json: WithContext<T>): string {
4  return `<script type="application/ld+json">
5${JSON.stringify(json)}
6</script>`;
7}
8
9export const MY_ORG = JsonLd<Organization>({
10  '@context': 'https://schema.org',
11  '@type': 'Corporation',
12  name: 'Google LLC',
13});

Graphs and IDs

JSON-LD supports '@graph' objects that have richer interconnected links between the nodes. You can do that easily in schema-dts by using the Graph type.

Notice that any node can have an @id when defining it. And you can reference the same node from different places by simply using an ID stub, for example { '@id': 'https://my.site/about/#page } below is an ID stub.

The example below shows potential JSON-LD for an About page. It includes definitions of Alyssa P. Hacker (the author & subject of the page), the specific page in this URL, and the website it belongs to. Some objects are still defined as inline nested objects (e.g. Occupation), since they are only referenced by their parent. Other objects are defined at the top-level with an @id, because multiple nodes refer to them.

1import type {Graph} from 'schema-dts';
2
3const graph: Graph = {
4  '@context': 'https://schema.org',
5  '@graph': [
6    {
7      '@type': 'Person',
8      '@id': 'https://my.site/#alyssa',
9      name: 'Alyssa P. Hacker',
10      hasOccupation: {
11        '@type': 'Occupation',
12        name: 'LISP Hacker',
13        qualifications: 'Knows LISP',
14      },
15      mainEntityOfPage: {'@id': 'https://my.site/about/#page'},
16      subjectOf: {'@id': 'https://my.site/about/#page'},
17    },
18    {
19      '@type': 'AboutPage',
20      '@id': 'https://my.site/#site',
21      url: 'https://my.site',
22      name: "Alyssa P. Hacker's Website",
23      inLanguage: 'en-US',
24      description: 'The personal website of LISP legend Alyssa P. Hacker',
25      mainEntity: {'@id': 'https://my.site/#alyssa'},
26    },
27    {
28      '@type': 'WebPage',
29      '@id': 'https://my.site/about/#page',
30      url: 'https://my.site/about/',
31      name: "About | Alyssa P. Hacker's Website",
32      inLanguage: 'en-US',
33      isPartOf: {
34        '@id': 'https://my.site/#site',
35      },
36      about: {'@id': 'https://my.site/#alyssa'},
37      mainEntity: {'@id': 'https://my.site/#alyssa'},
38    },
39  ],
40};