RDF website screenshot

RDF

The Resource Description Framework (RDF) is a W3C standard for representing information about resources on the web. RDF is the foundation for linked data and the semantic web, providing a graph-based data model where statements are expressed as subject-predicate-object triples. It enables interoperability between systems by using IRIs to identify resources and relationships, supporting multiple serialization formats including RDF/XML, Turtle, N-Triples, N-Quads, TriG, and JSON-LD. RDF 1.1 is a W3C Recommendation (2014). RDF 1.2 is a Candidate Recommendation (2026) adding triple terms (RDF-star) and directional language-tagged strings.

RDF is profiled on the APIs.io network. Tagged areas include JSON-LD, Knowledge Graph, Linked Data, Ontology, and RDF.

The RDF catalog on APIs.io includes 1 JSON-LD context and 1 Spectral governance ruleset.

RDF’s developer surface includes code examples, documentation, GitHub presence, and 12 more developer resources.

12.9/100 emerging ▬ flat Agent 1/100 human only Full breakdown ↓
scored 2026-09-25 · rubric v0.23.0
0 APIs
JSON-LDKnowledge GraphLinked DataOntologyRDFSemantic WebSPARQLW3C

Kin Score

Kin Score Kin Score How this is scored →
scored 2026-09-25 · rubric v0.23.0
Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.
Create-or-Update Ergonomics could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.
The six quality facets above are damped to 85 points between them, because the conditional facet above carries the other 15. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 85% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/rdf: open an issue to ask a question, or submit a pull request to add artifacts. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Semantic Vocabularies 1

JSON-LD contexts and semantic vocabularies used across these APIs.

Rdf Context

0 classes · 30 properties

JSON-LD

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

RDF API Rules

6 rules · 4 warnings 2 info

SPECTRAL

JSON Schema 3

Standalone JSON Schema definitions for this provider's data models.

RDF Dataset

2 properties

JSON SCHEMA

RDF Graph

0 properties

JSON SCHEMA

RDF Triple

3 properties

JSON SCHEMA

JSON Structure 2

JSON Structure definitions describing this provider's data shapes.

Rdf Graph Structure

0 properties

JSON STRUCTURE

Rdf Triple Structure

0 properties

JSON STRUCTURE

Examples 2

Example request and response payloads for these APIs.

Rdf Graph Example

1 fields

EXAMPLE

Rdf Triple Example

4 fields

EXAMPLE

Resources

Documentation 8

Reference material describing how the API behaves

Scroll for all 8

Design & Contract 4

Pagination, idempotency, versioning, errors, and events

Build 3

SDKs, sample code, and the tooling you integrate with

Source (apis.yml)

apis.yml Raw ↑
aid: rdf
name: RDF
description: The Resource Description Framework (RDF) is a W3C standard for representing information about resources on the
  web. RDF is the foundation for linked data and the semantic web, providing a graph-based data model where statements are
  expressed as subject-predicate-object triples. It enables interoperability between systems by using IRIs to identify resources
  and relationships, supporting multiple serialization formats including RDF/XML, Turtle, N-Triples, N-Quads, TriG, and JSON-LD.
  RDF 1.1 is a W3C Recommendation (2014). RDF 1.2 is a Candidate Recommendation (2026) adding triple terms (RDF-star) and
  directional language-tagged strings.
type: Index
deliveryModel:
  model: unknown
  license_evidence:
    not_product:
    - w3c/rdf-star-wg
  open_source: unknown
  commercial: false
  callable_host: false
  label: Delivery model not determined — needs a product licence on record
  confidence: low
  source:
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source: []
  generated: '2026-07-22'
  method: derived
position: Consuming
access: 3rd-Party
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/rdf.png
url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/apis.yml
tags:
- JSON-LD
- Knowledge Graph
- Linked Data
- Ontology
- RDF
- Semantic Web
- SPARQL
- W3C
created: '2025-01-01'
modified: '2026-05-02'
specificationVersion: '0.23'
apis: []
common:
- type: JSONSchema
  name: RDF Triple Schema
  description: JSON Schema for an RDF triple (subject, predicate, object).
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/json-schema/rdf-triple.json
- type: JSONSchema
  name: RDF Graph Schema
  description: JSON Schema for an RDF graph in the RDF/JSON serialization format.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/json-schema/rdf-graph.json
- type: JSONSchema
  name: RDF Dataset Schema
  description: JSON Schema for an RDF dataset (default graph plus named graphs).
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/json-schema/rdf-dataset.json
- type: JSONStructure
  name: RDF Triple Structure
  description: Field-level structure documentation for the RDF triple object.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/json-structure/rdf-triple-structure.json
- type: JSONStructure
  name: RDF Graph Structure
  description: Field-level structure documentation for the RDF graph serialization.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/json-structure/rdf-graph-structure.json
- type: JSONLDContext
  name: RDF JSON-LD Context
  description: JSON-LD context defining core RDF, RDFS, OWL, and related vocabularies.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/json-ld/rdf-context.jsonld
- type: Examples
  name: RDF Triple Example
  description: Example RDF triple about Tim Berners-Lee using foaf:name.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/examples/rdf-triple-example.json
- type: Examples
  name: RDF Graph Example
  description: Example RDF graph in RDF/JSON serialization about Tim Berners-Lee.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/examples/rdf-graph-example.json
- type: Vocabulary
  name: RDF Vocabulary
  description: Normative vocabulary for RDF concepts, serialization formats, and related standards.
  url: https://raw.githubusercontent.com/api-evangelist/rdf/refs/heads/main/vocabulary/rdf-vocabulary.yml
- type: Specification
  name: RDF 1.1 Concepts and Abstract Syntax
  description: W3C Recommendation defining the RDF data model.
  url: https://www.w3.org/TR/rdf11-concepts/
- type: Specification
  name: RDF 1.2 Concepts and Abstract Data Model
  description: W3C Candidate Recommendation (2026) introducing triple terms and directional language-tagged strings.
  url: https://www.w3.org/TR/rdf12-concepts/
- type: Specification
  name: SPARQL 1.1 Query Language
  description: W3C Recommendation for querying RDF data.
  url: https://www.w3.org/TR/sparql11-query/
- type: Specification
  name: JSON-LD 1.1
  description: W3C Recommendation for JSON-based RDF serialization.
  url: https://www.w3.org/TR/json-ld11/
- type: Documentation
  name: W3C RDF Working Group
  description: W3C working group developing RDF and SPARQL specifications.
  url: https://www.w3.org/groups/wg/rdf-star/
- type: GitHub
  name: W3C RDF Working Group GitHub
  description: GitHub organization for the W3C RDF and SPARQL specifications.
  url: https://github.com/w3c/rdf-star-wg
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this
  • find_providersBrowse and filter every provider in the catalog.
  • get_provider_artifactsEvery artifact this provider publishes, grouped by type.
  • get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
  • get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
  • get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
  • get_provider_ratingPRO — composite, band, trend and facet scores.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This provider
curl "https://apis.io/api/v1/providers/rdf"
All providers
curl "https://apis.io/api/v1/providers?limit=25"
Every operation they expose
curl "https://apis.io/api/v1/providers/rdf/operations?limit=25"
How their score was established
curl "https://apis.io/api/v1/providers/rdf/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.