FlowDrop Workflow Specification 1.0-draft

The map from a schema type to a port lane

A port's lane is what an editor colours it by and what it checks a wire against. It is derived from the property's schema type by one closed map.

The rule

Normative: this is the rule
  1. A property's schema type maps to exactly one lane: string to string; number and integer to number; boolean to boolean; array to array; object to json; null to the sink.
  2. Any other value, and an absent type, yield the sink, never string.
  3. A property's x-data-type overrides the mapped lane whenever it names a lane the served port configuration declares; any other value is ignored and the schema type maps as usual.
  4. Every lane this derivation can return, override included, must also be declared by the served port configuration: an undeclared lane leaves the port compatible with nothing an editor can draw.
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-10 · changed in spec 1.0