<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: xml-stylesheet and the World of Warcraft home page</title>
	<atom:link href="http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/feed" rel="self" type="application/rss+xml" />
	<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page</link>
	<description>It's all spinning wheels and self-doubt until the first pot of coffee.</description>
	<lastBuildDate>Thu, 11 Mar 2010 12:23:09 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0-alpha</generator>
	<item>
		<title>By: Mike Riley</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-399120</link>
		<dc:creator>Mike Riley</dc:creator>
		<pubDate>Wed, 15 Apr 2009 06:41:42 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-399120</guid>
		<description>&lt;p&gt;I&#039;m really confused as to why they have gone with this particular implementation, from the standpoint of separating content from design, using XML as the data layer and XSL as the display layer is completely beautiful.  But if you really look closely at the source of WOW&#039;s homepage, they actually have a lot of the content served up INSIDE THE XSL.  The XSL sheets are specific to each page, and it drives me insane trying to understand the logic behind doing this.&lt;/p&gt;

&lt;p&gt;If you have any insight into it, please, drop me a line, because I&#039;m at a loss.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I&#8217;m really confused as to why they have gone with this particular implementation, from the standpoint of separating content from design, using XML as the data layer and XSL as the display layer is completely beautiful.  But if you really look closely at the source of WOW&#8217;s homepage, they actually have a lot of the content served up INSIDE THE XSL.  The XSL sheets are specific to each page, and it drives me insane trying to understand the logic behind doing this.</p>
<p>If you have any insight into it, please, drop me a line, because I&#8217;m at a loss.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. David Peterson</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30627</link>
		<dc:creator>M. David Peterson</dc:creator>
		<pubDate>Tue, 01 Aug 2006 01:00:54 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30627</guid>
		<description>&lt;blockquote&gt;
  &lt;/blockquote&gt;&lt;blockquote&gt;
    &lt;p&gt;Yeah, but DOM scripting sucks so bad. :( I like Javascript, but I hate DOM scripting. (My kingdom for widespread adoption of E4X.)&lt;/p&gt;
  &lt;/blockquote&gt;

&lt;p&gt;We do it because there’s no other way. But I really want a better way…
 &lt;&lt;&lt;/p&gt;

&lt;p&gt;Amen to that!&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote></blockquote>
<blockquote>
<p>Yeah, but DOM scripting sucks so bad. :( I like Javascript, but I hate DOM scripting. (My kingdom for widespread adoption of E4X.)</p>
</blockquote>
<p>We do it because there’s no other way. But I really want a better way…<br />
 &lt;&lt;</p>
<p>Amen to that!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30605</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Mon, 31 Jul 2006 20:21:28 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30605</guid>
		<description>&lt;blockquote&gt;
  &lt;p&gt;if you use it that way, you might as well throw in some unobtrusive JS to wrangle the DOM into desired shape&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Yeah, but DOM scripting sucks so bad. :&lt;b&gt;&lt;/b&gt;( I like Javascript, but I hate DOM scripting. (My kingdom for widespread adoption of E4X.)&lt;/p&gt;

&lt;p&gt;We do it because there’s no other way. But I really want a better way…&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<blockquote>
<p>if you use it that way, you might as well throw in some unobtrusive JS to wrangle the DOM into desired shape</p>
</blockquote>
<p>Yeah, but DOM scripting sucks so bad. :<b></b>( I like Javascript, but I hate DOM scripting. (My kingdom for widespread adoption of E4X.)</p>
<p>We do it because there’s no other way. But I really want a better way…</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eby</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30588</link>
		<dc:creator>Eby</dc:creator>
		<pubDate>Mon, 31 Jul 2006 16:20:06 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30588</guid>
		<description>&lt;p&gt;The change was recent. I think there are some posts around about the change. Before it was a table-based tag soup that took forever to load. It still is some soup but it looks much lighter then it did back then. They most likely did the change to save on bandwidth and/or make things easier to change. I postponed my account awhile back though.&lt;/p&gt;

&lt;p&gt;They don&#039;t seem to advertise it but they now appear to finally have RSS for the news:&lt;/p&gt;

&lt;p&gt;www.worldofwarcraft.com/rss.xml&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>The change was recent. I think there are some posts around about the change. Before it was a table-based tag soup that took forever to load. It still is some soup but it looks much lighter then it did back then. They most likely did the change to save on bandwidth and/or make things easier to change. I postponed my account awhile back though.</p>
<p>They don&#8217;t seem to advertise it but they now appear to finally have RSS for the news:</p>
<p><a href="http://www.worldofwarcraft.com/rss.xml" rel="nofollow">http://www.worldofwarcraft.com/rss.xml</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: M. David Peterson</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30584</link>
		<dc:creator>M. David Peterson</dc:creator>
		<pubDate>Mon, 31 Jul 2006 15:48:14 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30584</guid>
		<description>&lt;p&gt;Hi Leslie,&lt;/p&gt;

&lt;p&gt;This has been an area of keen interest, and in particular, specialized research and development[1], for over three years now.  Opera was the last of the major browser vendors to add XSLT support  -- while there are still a few broken areas[2, 3], things are getting better.  In short, IE 5.x+, Mozilla, and Safari &lt;em&gt;ALL&lt;/em&gt; support XSLT 1.0, with Opera only a few functions short of full support.&lt;/p&gt;

&lt;p&gt;Theres a lot that can be done in this area, and dependent on a few factors that may boost its arrival, expect to see a TON more in this area from my direction in regards to OSS software projects released that build and extend from this in a BIG way.&lt;/p&gt;

&lt;p&gt;[1] http://www.xsltblog.com/archives/2005/12/finally&lt;em&gt;someone&lt;/em&gt;1.html
[2] http://www.oreillynet.com/xml/blog/2006/06/opera&lt;em&gt;90&lt;/em&gt;final&lt;em&gt;released.html
[3] http://www.oreillynet.com/xml/blog/2006/07/no&lt;/em&gt;sign&lt;em&gt;of&lt;/em&gt;document&lt;em&gt;function&lt;/em&gt;b.html&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Hi Leslie,</p>
<p>This has been an area of keen interest, and in particular, specialized research and development[1], for over three years now.  Opera was the last of the major browser vendors to add XSLT support  &#8212; while there are still a few broken areas[2, 3], things are getting better.  In short, IE 5.x+, Mozilla, and Safari <em>ALL</em> support XSLT 1.0, with Opera only a few functions short of full support.</p>
<p>Theres a lot that can be done in this area, and dependent on a few factors that may boost its arrival, expect to see a TON more in this area from my direction in regards to OSS software projects released that build and extend from this in a BIG way.</p>
<p>[1] <a href="http://www.xsltblog.com/archives/2005/12/finally" rel="nofollow">http://www.xsltblog.com/archives/2005/12/finally</a><em>someone</em>1.html<br />
[2] <a href="http://www.oreillynet.com/xml/blog/2006/06/opera" rel="nofollow">http://www.oreillynet.com/xml/blog/2006/06/opera</a><em>90</em>final<em>released.html<br />
[3] <a href="http://www.oreillynet.com/xml/blog/2006/07/no" rel="nofollow">http://www.oreillynet.com/xml/blog/2006/07/no</a></em>sign<em>of</em>document<em>function</em>b.html</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: George Hotelling</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30578</link>
		<dc:creator>George Hotelling</dc:creator>
		<pubDate>Mon, 31 Jul 2006 14:38:53 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30578</guid>
		<description>&lt;p&gt;I suspect that WoW&#039;s audience consists of earlier-than-average adopters, so they can expect the latest browser versions.  The only way to know whether or not you can pull it off (from a business perspective) is by looking at your user agent headers in your logs.&lt;/p&gt;

&lt;p&gt;That said, I am in love with the idea of replacing most of my DOM scripting with XSL.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>I suspect that WoW&#8217;s audience consists of earlier-than-average adopters, so they can expect the latest browser versions.  The only way to know whether or not you can pull it off (from a business perspective) is by looking at your user agent headers in your logs.</p>
<p>That said, I am in love with the idea of replacing most of my DOM scripting with XSL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: l.m.orchard</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30574</link>
		<dc:creator>l.m.orchard</dc:creator>
		<pubDate>Mon, 31 Jul 2006 14:04:05 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30574</guid>
		<description>&lt;p&gt;Aristotle:  Of course, if you use it that way, you might as well throw in some unobtrusive JS to wrangle the DOM into desired shape.  I wonder which is more efficient to run, and which would be smoother to write?  JS and DOM scripting leads to all sorts of uncomfortable loops that make me wish for XSL&#039;s XPath matches...&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Aristotle:  Of course, if you use it that way, you might as well throw in some unobtrusive JS to wrangle the DOM into desired shape.  I wonder which is more efficient to run, and which would be smoother to write?  JS and DOM scripting leads to all sorts of uncomfortable loops that make me wish for XSL&#8217;s XPath matches&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aristotle Pagaltzis</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30561</link>
		<dc:creator>Aristotle Pagaltzis</dc:creator>
		<pubDate>Mon, 31 Jul 2006 09:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30561</guid>
		<description>&lt;p&gt;It’s a fine idea, as long as you remember that the untransformed markup must be able to pass for HTML that is navigable as is, lest you shut out search engines, speech browsers etc.&lt;/p&gt;

&lt;p&gt;If I made use of this, I’d serve up actual XHTML and use the stylesheet only to insert repetitious bits of markup. Now that I think about that, it might in fact be a sweet way to inject the extra non-semantic markup required by the easy techniques for rounded corners or sliding doors, without actually touching the document. Oh, oh! Zebra tables! Hmmmm, now I’m thinking.&lt;/p&gt;

&lt;p&gt;Gotta investigate.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>It’s a fine idea, as long as you remember that the untransformed markup must be able to pass for HTML that is navigable as is, lest you shut out search engines, speech browsers etc.</p>
<p>If I made use of this, I’d serve up actual XHTML and use the stylesheet only to insert repetitious bits of markup. Now that I think about that, it might in fact be a sweet way to inject the extra non-semantic markup required by the easy techniques for rounded corners or sliding doors, without actually touching the document. Oh, oh! Zebra tables! Hmmmm, now I’m thinking.</p>
<p>Gotta investigate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John Resig</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30515</link>
		<dc:creator>John Resig</dc:creator>
		<pubDate>Sun, 30 Jul 2006 21:23:33 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30515</guid>
		<description>&lt;p&gt;Wow, that&#039;s really interesting - I wonder if they serve things up based upon the user agent that&#039;s used. If not, I wonder how they deal with search engine indexing.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Wow, that&#8217;s really interesting &#8211; I wonder if they serve things up based upon the user agent that&#8217;s used. If not, I wonder how they deal with search engine indexing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brett O'Connor</title>
		<link>http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page/comment-page-1#comment-30514</link>
		<dc:creator>Brett O'Connor</dc:creator>
		<pubDate>Sun, 30 Jul 2006 21:00:28 +0000</pubDate>
		<guid isPermaLink="false">http://decafbad.com/blog/2006/07/30/xml-stylesheet-and-the-world-of-warcraft-home-page#comment-30514</guid>
		<description>&lt;p&gt;If you go to &lt;a href=&quot;http://www.worldofwarcraft.com/index.xml&quot; rel=&quot;nofollow&quot;&gt;http://www.worldofwarcraft.com/index.xml&lt;/a&gt; it works.&lt;/p&gt;

&lt;p&gt;And yea, they made that change just last month. I&#039;ve seen the parsing errors like that at least three times since then.  All of them have had to do with the non-&quot;www&quot; hostname. I wonder why?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>If you go to <a href="http://www.worldofwarcraft.com/index.xml" rel="nofollow">http://www.worldofwarcraft.com/index.xml</a> it works.</p>
<p>And yea, they made that change just last month. I&#8217;ve seen the parsing errors like that at least three times since then.  All of them have had to do with the non-&#8221;www&#8221; hostname. I wonder why?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
