FlowDrop Workflow Specification 1.0-draft

A property's type is a JSON Schema type, not a port lane

The two vocabularies overlap on four words, which is why a lane name written into type looks correct, derives the wrong lane, and is caught by nothing.

The rule

Normative: this is the rule
  1. A property's type is one of JSON Schema's seven type words, or an array whose every member is one.
  2. It is never a port lane.
  3. A schema that spells a lane in type is malformed, on the input side and the output side alike: the lane derivation answers the miss with the sink and reports nothing, so the only symptom is a port of the wrong lane.
  4. An implementation states this constraint where a schema is declared, so an offending schema is caught before it ships rather than after a port is drawn from it.
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-34 · changed in spec 1.0