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

Michael(tm) Smith wrote:

> Do we really want to build a special exception into the spec just
> to prevent that special set of developers from seeing that
> message? (which is effectively just a warning message)

Hi Mike, I can understand to your concerns. But W3C has created and
promoted XSLT as a very effective tool for producing HTML content from
XML source data. HTML5 should be evolution of HTML(4) and should break
existing things as less as possible. This means that HTML5 has to cope
with some sort of legacy and because of this it already contains some
things which can be designed in a much better way if HTML5 and all tools
would be developed from scratch. But we are not living in a such ideal
world, we have to cope with legacy. I think that cost of having optional
part in !DOCTYPE is very minimal, but will show that W3C is serious
about their technologies and that W3C doesn't break existing solutions
and technologies when it is not 100% necessary.

I'm teaching web technologies (including HTML, XML, XSLT) for more then
10 years. Until now, there were three !DOCTYPES in HTML and my students
were not problem to understand why there are three different !DOCTYPES
(Strict, Transitional, Frameset). Thus I think they will not have
problem understanding why there is allowed to use <!DOCTYPE HTML> and
longer variant of <!DOCTYPE HTML PUBLIC "FUBAR">. In short class you
will simply not talk about longer form, and in a longer session you can
talk about long history of HTML and its "de jure" roots in SGML.


  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 Friday, 5 September 2008 07:16:12 UTC