Data & schema semantics

x-ms-odata

`x-ms-odata` appears on path items and on operations. Its value is a string. Used by 3 providers across 35 OpenAPI documents. It sits in the `x-ms-` namespace, so its meaning is defined by ms tooling rather than by OpenAPI. Observed values include `#/definitions/Schedule`, `#/definitions/MetricFilter`, `#/definitions/JobFilter`, `#/definitions/Lab`. 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-ms- 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.
220 occurrences
35 documents
3 providers
vendor-named

Where it appears

Location in the documentOccurrences
operation 79
path 141

What its value looks like

Value shapeOccurrences
string217
object3

Observed values

Sampled from the specifications, most frequent first.

#/definitions/Schedule#/definitions/MetricFilter#/definitions/JobFilter#/definitions/Lab#/definitions/User#/definitions/DeploymentExtendedFilter#/definitions/WorkflowFilter#/definitions/ManagementLockObject

Providers publishing it

All 3.

azure-logic-appsazure-test-labsmicrosoft-azure

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.