I just read through this thread quickly for the first time, so please pardon my late 2 cents worth. Responding to the situation mentioned in the original post, and a few others that were related, I have to disagree with calling a violation. It simply is not a violation according to the book, and I personally don't believe we should "turn it into" a violation because we don't think the action warrants a technical. If one chooses to NOT blow the whistle on it, then warn the team not to do it again and issue a "T" the next time. Better to ignore and warn in this situation than to call it something it clearly is not. At the same time, the tactic seems to me to be clearly designed to gain an advantage, so one would probably be quite justified in calling a "T" right away. But the bottom line is that we can't (or at least shouldn't) make up our own call because we don't like the one prescribed in the book.
|