Data & schema semantics · Naming & aliasing

x-sd-openapi-service-name-zh_cn

`x-sd-openapi-service-name-zh_cn` appears at the root of the document. Its value is a string. Used by a single provider across 29 OpenAPI documents. Observed values include `分析模型`, `渠道追踪`, `概览`, `业务集市`. Consistent with naming & aliasing — 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.
29 occurrences
29 documents
1 providers
purpose-named

Where it appears

Location in the documentOccurrences
root 29

What its value looks like

Value shapeOccurrences
string29

Observed values

Sampled from the specifications, most frequent first.

分析模型渠道追踪概览业务集市事件元数据属性元数据智能预警基础服务-通道

Providers publishing it

All 1.

sensors-data

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.