Data & schema semantics

x-path

`x-path` appears on schema objects and properties. Its value is a string. Used by 3 providers across 6 OpenAPI documents. Observed values include `/tapi-common:context/tapi-connectivity:connection/tapi-connectivity:uuid`, `/tapi-common:context/tapi-topology:topology/tapi-topology:node/tapi-topology:own`, `/tapi-common:context/tapi-connectivity:connectivity-service/tapi-connectivity:uu`, `/tapi-common:context/tapi-topology:topology/tapi-topology:uuid`. 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.
139 occurrences
6 documents
3 providers
purpose-named

Where it appears

Location in the documentOccurrences
operation 20
schema 119

What its value looks like

Value shapeOccurrences
string139

Observed values

Sampled from the specifications, most frequent first.

/tapi-common:context/tapi-connectivity:connection/tapi-connectivity:uuid/tapi-common:context/tapi-topology:topology/tapi-topology:node/tapi-topology:own/tapi-common:context/tapi-connectivity:connectivity-service/tapi-connectivity:uu/tapi-common:context/tapi-topology:topology/tapi-topology:uuid/tapi-common:context/tapi-common:service-interface-point/tapi-common:uuid/tapi-common:context/tapi-connectivity:connection/tapi-connectivity:route/tapi-c/tapi-common:context/tapi-connectivity:connection/tapi-connectivity:switch-contr/tapi-common:context/tapi-path-computation:path/tapi-path-computation:uuid

Providers publishing it

All 3.

centrapaymefxero

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.