W3C home > Mailing lists > Public > public-html@w3.org > September 2008

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

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 2 Sep 2008 20:16:19 +0000 (UTC)
To: Dean Edridge <dean@dean.org.nz>
Cc: Julian Reschke <julian.reschke@gmx.de>, HTML WG <public-html@w3.org>
Message-ID: <Pine.LNX.4.62.0809022013380.7044@hixie.dreamhostps.com>

On Wed, 3 Sep 2008, Dean Edridge wrote:
> Julian Reschke wrote:
> > 
> > ...
> > I just checked my last project where I needed to produce HTML from Java --
> > turns out that it falls into the same category, as it uses
> > javax.xml.transform just for the purpose of serializing to HTML. Note that
> > this is *not* XSLT, just usage of a standard JDK method to produce HTML.
> > 
> > So, which standard libraries do people use on other platforms (such as
> > .NET), and can *those* produce the HTML5 header?
> I think that's totally irrelevant. It's one thing to make a special case 
> for a W3C standard (XSLT), but if you're suggesting we go changing the 
> spec to suit various web frameworks I think that's going too far. If we 
> go down that path we'd be making exceptions for every web framework that 
> pops up over the next 5 years, this would compromise the quality of the 
> spec and we might never get it finished.

The key point here being that XSLT is a standard, so software that 
implements it may be restricted in its options, whereas Java, libxml2, and 
other libraries are just software, and can be updated. In fact most of 
these libraries can even just be patched locally or locally extended to 
handle HTML5.

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 2 September 2008 20:16:16 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 10:15:37 UTC