Skip to main content

JSON-LD and knowledge graphs

JSON-LD is JSON with linked-data semantics. It keeps the payload readable for normal API clients, while adding stable identifiers, typed nodes, and relationship names that graph tools can understand.

In practice, JSON-LD lets an API response behave both like JSON and like a graph. A client can read fields such as title, language, and hasSection directly, while a graph processor can expand the same document into nodes and edges using the @context.

Why this fits standards​

Standards are already structured as connected knowledge:

  • a standard has editions, languages, identifiers, classifications, and status
  • a clause is part of a standard and can contain provisions
  • a provision can be a requirement, recommendation, permission, or statement
  • a term can be defined once and referenced from many places
  • related documents can amend, replace, cite, or adopt each other
  • projects, mandates, directives, and stages can explain why a standard is changing

JSON-LD lets the API express those links directly instead of forcing clients to infer meaning from plain text fields.

What you can do with it​

With JSON-LD, consumers can:

  • render a table of contents and jump between clauses, provisions, terms, and related projects
  • build search or AI retrieval indexes where each node keeps its source identity
  • trace why a provision belongs to a clause and which standard edition it came from
  • combine SIS data with internal systems that already use RDF, graph databases, or semantic search
  • keep normal JSON processing while gradually adopting graph-aware tooling

Current preview​

The knowledge graph endpoint is currently a preview. That means the shape is available for exploration and feedback, but field names, vocabulary terms, and graph coverage may change before launch.

The current preview endpoint is part of the Content Preview API:

GET /api/content/preview/knowledge-graph/standards/{id}
Accept: application/ld+json

The response includes a JSON-LD @context and an @graph containing the standard, sections, provisions, terms, ICS codes, relations, and related project information where available.

The demo can run against the preview API by pasting a bearer token. It uses the Content API standards list to show only standards available to that token, then calls the preview graph endpoint for the selected standard.

Continue to the interactive demo to click from a standard to clauses, provisions, terms, and related documents.