![]() |
Quote:
|
Quote:
The only way you get that case to mean anything different than what I'm saying is if you take it out of context. If you want to start doing that, you're going to have a lot of interesting results. If they had wanted it to mean as you seem to suggest, they would have changed the definition of a blocking foul, not the definition of LGP. |
Quote:
Yep, that's what I thought. All opinion, no rule reference, case plays or interps to support your "read between the lines" opinion. |
Quote:
|
Quote:
What I don't understand is: "It isn't intended to apply to a player who was near OOB and happens to be on the line when a player comes along and runs into them." Where can I read a rule, case play or interpretation that supports this? |
Quote:
|
Quote:
|
Quote:
Once again, you failed to answer the question. "It isn't intended to apply to a player who was near OOB and happens to be on the line when a player comes along and runs into them." Where can I read a rule, case play or interpretation that supports this? |
Quote:
The standard is that if it is not illegal, it is legal. Nowhere in the rule book says it is a foul to be contacted while OOB. It only says you don't have LGP while OOB...and the case book, in the section covering GUARDING, says it is a block when contact occurs with a defender who is GUARDING (because it is in the section defining guarding) while OOB....and the reason is that they don't have LGP. Now show me a case or rule that says a rule on guarding applies to non-guarding situations. |
Quote:
|
Quote:
The purpose of that interpretation was to address the play where a defensive guard was sliding over to cut off a baseline drive by placing one foot OOB to cut off any chance of the drive getting by. |
So you are giving players on the court and off the court the same rights?
|
All times are GMT -5. The time now is 08:33pm. |