Re: HTML5 Doctype - too unspecific?

Thanks for pointing me there, Jens,

but I couldn't actually find any explanation on how validators and designing 
tools are supposed to validate HTML5 and future HTML standards correctly.

How are such tools to behave if certain tags/attributes will get deprecated 
in future HTML versions? What if new tags/attributes will be added?

I'm currently developing for a customer who has just rolled out IE8. 
Developing here is a matter of try & error because Visual Studio 2010 
validates completely apart from target platform.

I believe that applications advertising to implement a versio of a standard 
should only do so if the fully do so. So validation will actually have any 
benefit.

But validation against any definitive version of a standard seems impossible 
to me if there's no version information given.

So I see a lack of definition here.

Cheers,
Axel

Received on Thursday, 26 September 2013 19:42:50 UTC