Data & schema semantics

x-software

`x-software` appears in the info block. Its value is a string. Used by 2 providers across 5 OpenAPI documents. Observed values include `DSpace 7.6 (LYRASIS, BSD)`, `DSpace 7.6 OAI-PMH module`, `GeoNode (OSGeo, GPL-3.0)`, `Blacklight`. Consistent with data & schema semantics — this is inferred from where the key appears and what it carries, not from any published definition.

Data & schema semantics derived description
How this description was produced. It is assembled from what was measured in the corpus — where this key appears in a document, what shape its value takes, the values observed, and how many providers use it. It is not taken from a published definition, because for most extensions none exists. Read it as evidence, not as a specification. If you own this extension and want it described properly, tell us.
5 occurrences
5 documents
2 providers
purpose-named

Where it appears

Location in the documentOccurrences
info 5

What its value looks like

Value shapeOccurrences
string5

Observed values

Sampled from the specifications, most frequent first.

DSpace 7.6 (LYRASIS, BSD)DSpace 7.6 OAI-PMH moduleGeoNode (OSGeo, GPL-3.0)BlacklightDSpace 7.6

Providers publishing it

All 2.

university-of-melbourneuniversity-of-pennsylvania

Why this is not in OpenAPI

Extensions exist because a provider needed something the specification would not carry. Most of what they hold is not the API contract at all — it is operational metadata about the contract: documentation, lifecycle, policy, provenance, and now agents. That metadata is usually better placed alongside the contract, in an Overlay or an APIs.json index, than crammed inside it. See everything else doing the data & schema semantics job.