Martin on ThoughtWorks: Our belief is that an organization with the right social model can jump business models.

I'm far from an xslt expert, (those should know even better tricks and tools), but I've found the simple templates below a help at the bottom of any stylesheet under development.

Come to think of it, this might do very well as the first 30' of any XSLT course. Allowing people to just comment in/out these lines and watch/question/understand the effect should give some foundation to build the rest of the course upon.

Maybe a tip for Belgian ICT school teachers sending off their students into the big bad world to a training that actually requires the proclaimed XSLT knowledge.

 5
 6    <xsl:template match="text()" >
 7        TEXT: <xsl:value-of select="." />
 8    </xsl:template>
 9
10    <xsl:template match="@*">
11        ATTR: <xsl:value-of select="name(.)" /> = <xsl:value-of select="." />
12    </xsl:template>
13
14    <xsl:template match="*">
15      ELM:  <xsl:value-of select="name(.)" />
16      <xsl:apply-templates select="@*"/>
17      <xsl:apply-templates select="*"/>
18      <xsl:apply-templates select="text()"/>
19    </xsl:template>
20

It really just started out as helping out the kids a bit...

Some recent wow-experiences in the web-browser:

• bookmarklets at work in relation to googlemaps. (via Sam)
• ajax (via tomk)
• And closer to home the fine HTMLArea wysiwyg editing experience integrated with the features of our daisy cms and related to it: Bruno's recent work on the nav-tree editor.

The web continuous to be a cradle for technological innovation. People knowing me can easily guess that I account the free information sharing attitude on the web as the main enabler for this. However the mere fact that the simplicity of the web-model forces/challenges people to think out of the box sounds like a decent additional explanation. (which is probably why I keep giving the hard core ReST-addicts some slack in their continued stress on the-way-the-web-works... the border with starting to be a block on innovation is probably thin as Sam seems to be hinting...)

The downside of fast change isn't as romantic though: Every now and then the high change rate itself is characterised by a decent amount of chaos: (warning: incomplete list)

• URI-encoding dillema's (Sam again)
• Backgrounder and outcome on the recent IDN spoofing.
• on the common wrong (according to spec) practice of nesting <ul> directly (recently learned from Bruno)
• or some grab out of the common user agent problems