Don’t call me DOM

I needed today a way to create nice relative URI paths in XSLT. The point was, given a relative URI A foo/bar/toto, and another relative URI B baz/tutu supposed to be relative to the same base, calculate the URI path from A to B, in this case ../../baz/tutu.

Although it isn’t very complicated, I figured that other people may need this very same facility, since it’s a classical problem when using XSLT e.g. to build a Web site. Plus, I tried to make sure it would generate “nice” paths, for instance avoiding that the path generated to go from foo/bar/toto to foo/baz be ../../foo/baz instead of the simpler ../baz.  Read more... (144 words, estimated 35 secs reading time)

I was recently pointed to another example of important bandwidth saving due to using proper XHTML and CSS. Nothing very new, but the figure of 1M$ is pretty interesting.

The standout paper was by Brett Jackson from Fairfax Digital, detailing how they moved to validated XHTML with CSS. They deliver 164,000,000 page impressions per month for the major dailies The Sydney Morning Herald and The Age. They do day parting: different kinds of stories are emphasized at different times of day. Later in the day people want gossip, analysis and entertainment but in the morning they want breaking news and weather. He reported they save a million dollars a year on bandwidth costs by moving to validated XHTML with CSS! […]  Read more... (209 words, estimated 50 secs reading time)

Dan Connolly recently demonstrated that GRDDL could also be used as a way to tie semantics to a given XML schema, based on the namespaceTransformation property defined in GRDDL.

The only restriction is that it relies on having the said schema served at the namespace URI of the given vocabulary; in other words, it wouldn’t work through xsi:schemaLocation, but that’s probably a very acceptable restriction, especially since the XML Namespace solution scales much better, in that you don’t have to duplicate the information again and again. This very much relates to the namespaceDocument issue the TAG has in its queue…  Read more... (131 words, estimated 31 secs reading time)