On Apr 10, 2006, at 11:20 AM, Tantek Çelik wrote:
One poor job does not deserve another - this line of argument NEVER justifies poor behavior.
I intentionally avoided making any line of argument, as I thought simply asking for clarification would be more productive. Apparently I was wrong about that, as the inferred line of argument (don't use the process) is pretty much the opposite of the one I avoided making (encourage use of the process through clarification). So here's my line of argument:
Exceptions to the process should be clearly identified and explained to avoid confusion between the exception and the rule. It's nice to keep pointing people to the process page, but that's analogous to pointing people to the HTML spec. People imitate examples more than we follow rules. When someone looks at the hcard pages and sees no collection of real-world publishing of contact data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior. There's nothing on the process nor the hcard pages explaining this discrepancy. I would argue that there should be an explanation, probably in both places. If design patterns don't follow the process, I would argue that this distinction should be clearly documented and explained.
Peace, Scott _______________________________________________ microformats-discuss mailing list [email protected] http://microformats.org/mailman/listinfo/microformats-discuss
