Data & schema semantics

x-fds-dh

`x-fds-dh` appears on schema objects and properties. Its value is a string. Used by a single provider across 2 OpenAPI documents. It sits in the `x-fds-` namespace, so its meaning is defined by fds tooling rather than by OpenAPI. Observed values include `REGIONAL_FDS_ID`, `EVENT_ID`, `EVENT_TYPE_CODE`, `EVENT_TYPE`. 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 x-fds- namespace 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.
160 occurrences
2 documents
1 providers
vendor-named

Where it appears

Location in the documentOccurrences
schema 160

What its value looks like

Value shapeOccurrences
string160

Observed values

Sampled from the specifications, most frequent first.

REGIONAL_FDS_IDEVENT_IDEVENT_TYPE_CODEEVENT_TYPEANNDATERECORD_DATEPAYDATEEFFECTIVE_DATE

Providers publishing it

All 1.

factset

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.