FlowDrop Workflow Specification 1.0-draft

How a schema property becomes a port

One mapping turns a schema property into the port an editor draws, so every schema-derived port on every node is built the same way.

The rule

Normative: this is the rule
  1. A schema-derived port takes its id from the property key; its name from the property's title, or from the key where there is no title; its lane from the type mapping; required from membership in the schema's required list; its default value from the property's default, or null where there is none; its exposed-by-default from the exposure defaults; and its display order from x-port-order, or 0 where that is absent.
  2. This is the only schema-to-port mapping.
  3. The unified input and output ports are not schema-derived: they always carry the json lane and display order 0.
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 · SCH-8 · changed in spec 1.0