Data & schema semantics

x-operator-evidence

`x-operator-evidence` appears in the info block. Its value is a structured object. Used by 33 providers across 93 OpenAPI documents. 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.

93 occurrences

93 documents

33 providers

purpose-named

Where it appears

Location in the document	Occurrences
info	82
root	10
other	1

What its value looks like

Value shape	Occurrences
object	81
string	12

Observed values

Sampled from the specifications, most frequent first.

host datashare.ed.ac.uk is under ed.ac.uk, Domain Owner: University of Edinburghhost era.ed.ac.uk is under ed.ac.uk, Domain Owner: University of Edinburgh (Nomieidf.ac.uk Domain Owner: University of Edinburgh (Nominet whois); Registered Foredina.ac.uk Domain Owner: University of Edinburgh (Nominet whois); Registered FoAll 16 APIs are served from https://api.data.um.edu.mo, a host under the Univers

Providers publishing it

All 33.

anu carnegie-mellon-university columbia cornell curtin hanyang imperial-college-london keio kyoto lse massey mcgill mcmaster nycu peking politecnico-di-milano tokyo-institute-of-technology tu-delft ucsf universite-de-montreal universiti-teknologi-petronas university-of-edinburgh university-of-leeds university-of-lisbon university-of-macau university-of-michigan-ann-arbor university-of-oxford university-of-pittsburgh university-of-southampton university-of-tokyo unsw-sydney uq ustc

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.