superfluous language in 9.3.3 synchronic flow processing

I was just re-reading the final (current) language in 9.3.3, and notice
that the phrase "to be equivalent to" was added to rules 3, 4, 5, 7, 8, 9.
This phrase adds no semantics to the process, and further complicates an
already complex formulation. I would suggest these additions be removed,
and, if necessary, a general note be added indicting that "map X to" means
"map X to be the equivalent to".

Received on Friday, 10 February 2012 21:40:37 UTC