In the abstract, I like the idea of HTML namespacing. However, their proposed implementation gives me a nasty feeling in the pit of my stomach.
It seems that this proposal would contort HTML to better accomodate XML data, just as other interchange formats like YAML and JSON are taking the stage. Also, a lot of the scripting advantages are already taken care of with HTML 5 custom data attributes. I just don't see the need.
Plus, some of these changes would seriously break compatibility with legacy parsers. The only purpose for this proposal seems to be making life easier for Microsoft programmers.
Comments
In the abstract, I like the idea of HTML namespacing. However, their proposed implementation gives me a nasty feeling in the pit of my stomach.
It seems that this proposal would contort HTML to better accomodate XML data, just as other interchange formats like YAML and JSON are taking the stage. Also, a lot of the scripting advantages are already taken care of with HTML 5 custom data attributes. I just don't see the need.
Plus, some of these changes would seriously break compatibility with legacy parsers. The only purpose for this proposal seems to be making life easier for Microsoft programmers.