JRutledge |
Sun Oct 11, 2015 05:17pm |
Quote:
Originally Posted by BryanV21
(Post 967867)
Doesn't that POE history make you think that the error was excluding it from rules? I really don't believe that this is a case of a POE creating anything.
I'm not saying anybody should just assume the violation, but I'm not going to be surprised if I'm told to call it one.
|
Rules changes are voted on and accepted. So if it was intended to be a rules change, they should have simply stated their intention. They had months before last year to do just that. Then this year they could have changed the wording like they do other things and they didn't.
Again, when you look in the actual rules, this is not a violation anywhere in the actual rules. That is a problem no matter how you want to minimize that fact. That is what you they should have done if they suggest they want consistency. As I have said before, we're just a small sample size to all the officials. I know there are officials that have noticed this inconsistency and will either not go along with the POE's wording or go only with what is in the rulebook. If you want inconsistency, stay the course and say nothing. At this point without clarification I am not calling a violation for this. I will call a foul if needed because nothing in the rule contradicts calling a foul when appropriate.
Peace
|