Following standard is easier if you do not want to develop your own requirements, but following because you do not know and then want to get this information for free is a little too much.
Marc got to the point when he speaks about "using the standard to make money". People should just think about the money they would have to spend if they would develop their own standard, instead of using a published one.
I agree about the "cost of developing from scratch." I frequently make the point that organizations often are better off from an economic standpoint to adopt an off-the-shelf solution to solve a problem, perhaps "tinkering or adapting to fit" rather than trying to reinvent the wheel. It seems much more efficient to spend a few minutes, hours, or days evaluating the off-the-shelf solution for utility than weeks, months, years struggling to develop a solution from scratch.
Sometimes "good enough"
IS good enough, sometimes not. My question is why not take some time to evaluate whether "good enough" is the most economic solution for your situation? Sometimes needless ego and hubris get in the way of what is best for the organization.
Mom always used a phrase that seems to fit here:
Penny wise and pound foolish!"

If your organization is the type of penny-pinching one seeking free, pirated copies of standards, software, etc., odds are it is also penny-pinching and miserable in terms of compensation, benefits, and working conditions for its employees. Employees subjected to such duress are the ones most likely to "drop a dime" on the organization just to get even. There are an entire regiment of Microsoft lawyers making a handy living going after organizations with pirated MS software, paying dandy finder's fees to disaffected current or former employees
(who have tipped off Microsoft) when those organizations ultimately settle or lose in court. Obviously, similar events occur around music and other copyright infringement (some idiotic organizations have even downloaded pirate music to play as background themes on their corporate websites! - Maybe it's the result of letting some executive's teenager design the site to save money!)
In many cases, just the threat of the bad publicity arising from such a suit that prompts organizations to FINALLY look at the situation with some common sense and rush to correct past misdeeds.