Data & schema semantics

x-json-property

`x-json-property` appears on schema objects and properties. Its value is a string. Used by a single provider across 1 OpenAPI document. Observed values include `http://bibfra.me/vocab/lite/name`, `http://bibfra.me/vocab/lite/link`, `http://bibfra.me/vocab/lite/date`, `http://bibfra.me/vocab/lite/note`. 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.
185 occurrences
1 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
schema 185

What its value looks like

Value shapeOccurrences
string185

Observed values

Sampled from the specifications, most frequent first.

http://bibfra.me/vocab/lite/namehttp://bibfra.me/vocab/lite/linkhttp://bibfra.me/vocab/lite/datehttp://bibfra.me/vocab/lite/notehttp://bibfra.me/vocab/library/codehttp://bibfra.me/vocab/lite/labelhttp://bibfra.me/vocab/library/statushttp://library.link/vocab/map

Providers publishing it

All 1.

folio

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.