Published schemas carry the flag only where the default is hidden
The rule
Normative: this is the rule
- Where a node type's stored default exposure for a port is false, the schema it publishes carries
x-exposed-by-default: false. - Where it is anything else, the key is absent from the published schema rather than present and true.
- A processor's own value for the key is overwritten either way, so the published schema states the node type's decision and only where it diverges from the exposed default (CFG-2).
What it means
What a node type publishes states only its own decision, and only where that decision diverges from the default. A processor's own schema for the same port is never consulted at publication time and never survives into what ships — even where the node type's stored value agrees with the processor, or contradicts it outright, the published schema is built from the stored value alone.
Example
{ "connectable": true, "exposed_by_default": false }{ "x-exposed-by-default": false }Where the node type's own stored value is anything else — unset, or an
explicit true even against a processor schema that itself declares
x-exposed-by-default: false for that port — the published schema carries
no such key at all. A processor's own value for the key never reaches what
publishes; only the node type's stored word does.
Rule identifiers are permanent and are never renumbered. Each implementation publishes its own standing against these rules; this specification does not.spec 1.0-draft · EXPO-7 · changed in spec 1.0