It has become an unfortunate trend that people start something probably useful and call it a standard. Some guys just reserve a domain name, publish a website or push a repository to GitHub. Combine this with some marketing and we have a new standard. Well, that is not how it works. At least it should be. But in our times some other guy sees the self-named standard and tells everyone he knows about it. At this point false information starts to spread like a virus.
Let's start with the HTML6 draft. But wait, there is no HTML6 draft. Calling the proposed changes a specification (it is not) and presenting them as if they would be official (it is not) is preposterous. Not only is the "specification" not really well drafted, it is also highly personal and has never been discussed in the any W3C working group. Nevertheless, I've seen countless articles from (online) magazines that actually believe in something like an HTML6 draft. "Brings us freedom" - don't confuse yourself with everyone else. Also please don't insert elements just like
<wrapper> to hide your own incompetence. One of the achievements of the recent CSS modules (starting with CSS3) was to nearly fully decouple layout from semantics. A wrapper that is only introduced for layout is therefore wrong. You should only use CSS for styling. There are enough pseudo elements, additional layers and more to style according to your needs.
These three examples have been picked more or less randomly. I could also show other examples in the C#/.NET world, but I guess its obvious that becoming a standard requires more than just a name, marketing and an idea.