However, this article is around the physical rules and design of the proposal feature (what abilities the features give you by design). As an Asker/OP, it is not mandated that you're able to read the answers before someone else proposes them. Actually marking an answer is what your priviledge should be, as the Asker. Anyone can propose an answer, which is basically just saying, "Hey, I think this is the answer. Is this the answer? If so, then a Moderator or the Original Asker should confirm that by marking it as the answer." (Whether or not you should propose answers is a separate discussion and is often determined case by case.)
That's all a proposed answer is: someone thinks they saw what could be the answer, and they want the Asker to verify that. The feature of proposing an answer actually does nothing until it's confirmed. Once it's confirmed, it counts as marks toward Achievement Medals, but still no Recognition Points are involved (in the proposal part).
So if you see proposed answers, and they aren't the answers, then go ahead and dismiss them (unpropose them). That's what they're there for... someone thinks they're the answer and they want you to verify or dismiss. It's also perfectly in the rules to propose your own answer (the feature is enabled to allow it). However, there are several reasons not to propose your own answer, so you'll need to make the decision for yourself. See Whether or Not You Should Self Propose an Answer in an MSDN or TechNet Forum. If you are the Asker/OP, I recommend that you do not leave proposed answers without either marking them (as the answer) or unproposing them. Or else eventually a Moderator might think you've skipped out on reviewing the proposed answers. This article is part of the Wiki series: MSDN/TechNet Forums.
I agree.