Re: ISSUE-54 (html5-doctype-vs-xslt): XSLT 1.0 can not generate HTML5 documents [HTML 5 spec]

Henri Sivonen wrote:

> If we allow a placeholder public id, cargo cultists will think that the
> more complicated syntax is somehow better because HTML 4 had similar
> cruft and cruft exists for a *reason*, will make up a rationalization
> for it that doesn't even mention XSLT (something like "it helps browsers
> better understand semantics") and will start evangelizing the more
> crufty syntax to other people who will end up wasting their time looking
> up a public id that is useless if they aren't using XSLT. Time is the
> most valuable resource people have, so inflicting time-wasting cruft on
> Web authors isn't nice.

Should be HTML5 specification based on speculations like above or on
deep analysis?

Anyway, if there are really your cargo cultists they are already using
XHTML 1.1 and they will use XML serialization of HTML5 anyway (probably
with wrong MIME type though ;-)

  Jirka Kosek      e-mail:
       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

Received on Thursday, 28 August 2008 14:39:31 UTC