Data & schema semantics

x-refdata-source

`x-refdata-source` appears on schema objects and properties. Its value is a string. Used by a single provider across 3 OpenAPI documents. Observed values include `CM-Currency`, `RT-CUSTOMER_NODE_STATUS`, `RT-perestapi.REASON`, `RT-accl.cust.statusChangeReason`. 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.
57 occurrences
3 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
parameter 7
schema 50

What its value looks like

Value shapeOccurrences
string57

Observed values

Sampled from the specifications, most frequent first.

CM-CurrencyRT-CUSTOMER_NODE_STATUSRT-perestapi.REASONRT-accl.cust.statusChangeReasonRT-api.imp.ALL_CC_CUSTOMER_TYPE|CM-Industry|||RT-COMPANY_TYPE||||||RT-accl.cust.RT-perestapi.REFERRED_TYPERT-perestapi.RELATED_PARTY_ROLE||RT-perestapi.imp.CONTACT_ROLE

Providers publishing it

All 1.

mtn-group

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.