infoof? Don't toy with my emotions there, bud
The point I was making is that the final implementation should match the characteristics of what would be built with it. In Rx's case, Sum-as-sequence makes perfect case as you adequately explain. In IE's case, Sum-as-scale fits well with what people almost certain end up doing. In any event, a user-study would reveal this (albeit too late to change the established SQO specifications if I'm proven wrong).