Action/Target Pairings

[<duncan@sfractal.com>]

An issue was discussed and resolved over the last two Language
Subcommittee meetings and this note documents the resolution for the
benefit of everyone who was not able to attend. Since it impacts
actuator-profiles as well, this note is being sent to the entire TC.
Obviously if anyone has any issue with the resolution, please let us
know.

Prior to this discussion, the language specification contained many
'action/target pairings' eg action=copy, target=file. The wording could
be considered ambiguous with respect to whether those pairing were
normative in that only those pairings were allowed. Some (including one
of the author/editors) read it as the LS would contain the complete
list; and some (including a different editor) read the pairings as
informative examples but that other pairings would be legal. 

The Language Subcommittee discussed over two meetings and agreed to the
following:
- the language specification would NOT contain the complete list of
action/target pairings
- any action with any target is possible from the language specification
document view
- each actuator profiles will list the mandatory and optional pairings
for that actuator
- the language specification will contain many examples, all of which
eventually be legal in some actuator profile
- the exhaustive list currently in the language spec (in the many
property tables) will be removed from the language spec, but will be
retained for use by the subcommittee 

Those who attended, please validate I captured the points correctly.
Everyone - let us know if you disagree with any of the points.


Duncan Sparrell
sFractal Consulting LLC
iPhone, iTypo, iApologize