Hacker News Reader

HNHacker News

Top New Best Ask Show Jobs

Comment by MattPalmer1086 | Hacker News Reader

Parent Full thread

MattPalmer1086·

Was there ever a good reason for XSLT to be an XML document itself? It was painful writing it.

View on HN

Is XSLT not an XML document itself?

I’m confused by your comment. My XSLT stylesheets are like this:

``` <?xml version="1.0"?> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> ```

Yes it is, I was asking why it needed to be. Sorry if that wasn't clear.

Once upon a time HTML was a kind of XML, which is why the current version is very similar to XML and hence painful to write. This in turn is why we tend to use programmatic tools to handle the HTML, and you should if you work with XML too.

In fact, HTML predates XML. Both can be seen as types of SGML.

HTML5 is unlike XML in very important regards, which makes it actually quite difficult for tools to handle. But easier than XML. XHTML was quite annoying to write as far as I remember.

This way you can manipulate XSLT using XSLT. A common case is to generate XSLT.

Clearly that would be possible, but I never actually saw anyone doing that though.

Any pointers to tech that did this, if it was a common case?

I doubt it was common. But, for example, there is such thing as Schematron: this is a special notation that checks that an XML document follows business rules and the final tool that it produces is a custom XSLT that transforms the document into the report.

(I'm also doing this currently; I need to prepare a sort of an annotated patch to an XML document, so I concocted a notation that describes edits and use it to generate both the documentation that highlights differences and also the patch itself; the patch comes out as XSLT.)

Yo dawg, I heard you like xml … so I made you an xml-based language to turn xml into other xml!

Reply on news.ycombinator.com