Data & schema semantics

x-xsd-source

`x-xsd-source` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `schemas/iso-new-england-web-services-ns0.xsd#type_forecast_capacity_analysis_rep`, `schemas/iso-new-england-web-services-ns0.xsd#type_ActualFifteenMinInterchange`, `schemas/iso-new-england-web-services-ns0.xsd#type_ActualFifteenMinInterchanges`, `schemas/iso-new-england-web-services-ns0.xsd#type_ActualInterchange`. 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.
217 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 217

What its value looks like

Value shapeOccurrences
string217

Observed values

Sampled from the specifications, most frequent first.

schemas/iso-new-england-web-services-ns0.xsd#type_forecast_capacity_analysis_repschemas/iso-new-england-web-services-ns0.xsd#type_ActualFifteenMinInterchangeschemas/iso-new-england-web-services-ns0.xsd#type_ActualFifteenMinInterchangesschemas/iso-new-england-web-services-ns0.xsd#type_ActualInterchangeschemas/iso-new-england-web-services-ns0.xsd#type_ActualInterchangesschemas/iso-new-england-web-services-ns0.xsd#type_CapacityScarcityConditionschemas/iso-new-england-web-services-ns0.xsd#type_CapacityScarcityConditionsschemas/iso-new-england-web-services-ns0.xsd#type_CombinedHourlyDemand

Providers publishing it

All 1.

iso-new-england

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.