Use symbol nomenclature instead of requires, provides...

Registered by Joshua Harlow on 2014-06-28

Instead of referring to the [provided, requires] inputs and outputs of atoms by various names including:

- Argument mappings
- Output mappings
- Input mappings
- ...
- http://docs.openstack.org/developer/taskflow/arguments_and_results.html

Lets start to follow more standard *compiler* like naming and just refer to these using existing nomenclature where a atom produces symbols that are bound to some value (bound symbols) and an atom may declare symbols (not bound to a value, aka free variables, aka unbound symbols) that it needs for execution (at execution time they will be bound to a value produced by some other atom). This creates a single well-known nomenclature that is more understandable to those who have used or created compilers or languages, or other similar tools previously.

See: http://www.slideshare.net/Tech_MX/symbol-table-design-compiler-construction/ (and other search results for information on what symbols mean, https://en.wiktionary.org/wiki/bound_variable and https://en.wiktionary.org/wiki/free_variable for what bound symbols/free variables are...)

Blueprint information

Status:
Not started
Approver:
Joshua Harlow
Priority:
Medium
Drafter:
Joshua Harlow
Direction:
Approved
Assignee:
None
Definition:
Approved
Series goal:
None
Implementation:
Unknown
Milestone target:
None

Related branches

Sprints

Whiteboard

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.