Taxonomy API Documentation

A RESTful and Linked Data interface for the Connectivity Hub Taxonomy.

Quick Start

This API lets you find terms (concepts) and retrieve their details. You don't need to know RDF or the Semantic Web. If you prefer JSON, you're covered — responses default to JSON-LD (regular JSON with extra structure for advanced use cases).

Implementation tip: Store the term IRI from the s field as your canonical identifier, and the literal value for the display label.

Look up a term by IRI

# Use the IRI returned by search
curl -i "https://connectivity-hub.com/terms/083e4731-556e-4012-810a-a961d2777362"

Search by keyword

# Finds labels starting with your keyword
curl -i -H "Accept: application/json" "https://connectivity-hub.com/search?q=agri"

Introduction

Welcome to the Connectivity Hub Taxonomy API. You can search by keyword to find a term and then request that term's IRI to retrieve its details. If you don't specify a format, responses use JSON by default.

All API endpoints are rooted at: https://connectivity-hub.com.

URIs, IRIs, and Identifiers

Each term has a unique Internationalized Resource Identifier (IRI). In this API, these IRIs are also URIs and URLs, for example: https://connectivity-hub.com/terms/083e4731-556e-4012-810a-a961d2777362. An IRI is an identifier; in our case it also functions as a web address you can dereference over HTTP to retrieve the term's details. Note: not every IRI is necessarily a URL in general, but ours are.

Typical flow

  1. Search for a keyword using /search?q=....
  2. From the results, copy the value of s (the term's IRI).
  3. Request that IRI to get the full term description (optionally add ?version=vN).
# 1) Search
curl -s -H "Accept: application/json" "https://connectivity-hub.com/search?q=agri"

# 2) Copy an "s" value from the results (it's the IRI)
# 3) Dereference the IRI
curl -i "https://connectivity-hub.com/terms/083e4731-556e-4012-810a-a961d2777362"

Get a Specific Term

Retrieve the full description of any term by making a GET request to its unique IRI.

Latest Version (Default)

By default, any request without a version parameter will query the most recent version of the taxonomy loaded into the system, and the response will be returned as JSON-LD if no Accept header is provided.

# Default: JSON-LD without specifying an Accept header
curl -i "https://connectivity-hub.com/terms/f9dbf392-d5e6-4aaf-aa32-b689581afa14"

Example response (JSON-LD, truncated):

{
  "@id": "https://connectivity-hub.com/terms/f9dbf392-d5e6-4aaf-aa32-b689581afa14",
  "@type": "skos:Concept",
  "skos:prefLabel": { "@language": "en", "@value": "Carbon dioxide (CO2) fertilization" },
  "skos:definition": { "@language": "en", "@value": "The enhancement of the growth of plants ..." },
  "skos:inScheme": { "@id": "https://connectivity-hub.com/terms/" }
}

Specific Version

To load a specific historical version, add ?version. For example, v1.

# Request the 'v1' version of the same resource
curl -i "https://connectivity-hub.com/terms/f9dbf392-d5e6-4aaf-aa32-b689581afa14?version=v1"

To request a different RDF format, set the Accept header. For example, to get Turtle:

# Request Turtle instead of JSON-LD
curl -i -H "Accept: text/turtle" "https://connectivity-hub.com/terms/f9dbf392-d5e6-4aaf-aa32-b689581afa14"
Tip: JSON-LD is standard JSON that also works with linked data tools. You can safely parse it with any JSON library.