Re: Bug 7034

Henri Sivonen wrote:

> It's not clear that the validity definition is the right place to address the case where the author wants to avoid cruft to make the markup maintainable. I definitely want to have tools that help with that case, though.

I think that such cases are best served by custom Schematron schema
defining additional constraints on top of the normal HTML5 validator. In
Schematron you can very easily prohibit or mandate presence of
elements/attributes.

Maybe validator.nu could provide interface for specifying such custom
additional schemas and even can provide few predefined ones like: "ban
all presentational stuff", "ban HTML5 elements/attributes not supported
in browser X, version Y", ...

				Jirka

-- 
------------------------------------------------------------------
  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
------------------------------------------------------------------
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
------------------------------------------------------------------
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member
------------------------------------------------------------------