I was reading over the document of changes from 4 and came across datalist, http://www.w3.org/TR/2008/WD-html5-d.../#new-elements which seems to be replacing select? Then I came across the new input types. Oh man, that's the biggest hit to security. I'd still confirm the input, because a cracker would be able to fake those. It'd be really simple to fake the get of course. The ping attribute seems useless and would hinder tracking if used. The target attribute coming back is cool, but it's problematic for now in that it's deprecated currently and makes the pages invalid if we were to test, so I know I'll get so use to not using it I'll forget about it in the next few years. ol start and li value coming back is awesome and I can't wait for it. One thing which I think is bad is the charset attribute for meta, since it can only be used on one meta tag. I think that if you have something like that you should just make a new tag. Autofocus I'd turn off, but I think is a great accessibility feature. The form attribute is a blessing. The required attribute is useful, but is a security issue we'll have to face. Link's size attribute seems quite pointless, but I'm not sure. Ol's reversed attribute is great.
The data-* attribute seems useless, what's the point of it if user-agents aren't allowed to use them?
About the removing of accesskey, I've never used it, but don't see why it's going away. Name is finally going away on a, so ids it is.
So any thoughts?

The new elements: <header>, <footer>, <nav>, <section>, <article>, <aside>, and <dialog> are definitely positive developments, because they are more semantic. They don't, however, seem like they are dramatically different than elements that already exist. The <dialog> element, for example, is basically just a definition list, but it's semantics is meant to indicate a conversation. Semantic HTML is a very positive evolution, IMO, because when Google looks at a page, it is more clear what each element is meant to represent.

As for the security issues, that will become more clear as the standard become more finalized, and supported by browsers.

HTML 5 may be an attempt to break from the XHTML standard, which has failed in its original intent, which was to make XML the standard for data interpretation (JSON is a more elegant solution). XHTML did do some positive things, however, such as enforcing tag closing, which HTML lets go in a loose manner. Does anyone know if HTML 5 is going to enforce this?

Overall, I think it is a positive improvement to the standard. As designers and coders, we are free of course to style all of the elements in any manner we wish, and we, as developers, as usual, will make the real innovations.

It would look like you have to close them from their examples given of it that I've seen. You will also be able to use HTML5 with XML parsing instead.

I think some of what they've done is a step BACKWARDS, rather than forwards. It'll be years before it's even close to even recommendation phase and implementation by the browser makers.

And a previous one:

http://www.webmaster-talk.com/html-f...xhtml-2-a.html