<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Advent Digerati &#187; Rant</title>
	<atom:link href="http://blog.adventdigerati.com/tag/rant/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.adventdigerati.com</link>
	<description>Where Life meets Geek</description>
	<lastBuildDate>Mon, 26 Jul 2010 00:49:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>MS Slices X-Path to Ribbons</title>
		<link>http://blog.adventdigerati.com/2009/04/ms-slices-x-path-to-ribbons/</link>
		<comments>http://blog.adventdigerati.com/2009/04/ms-slices-x-path-to-ribbons/#comments</comments>
		<pubDate>Tue, 14 Apr 2009 04:31:32 +0000</pubDate>
		<dc:creator>Zack</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Rant]]></category>

		<guid isPermaLink="false">http://blog.adventdigerati.com/?p=53</guid>
		<description><![CDATA[Microsoft has a history of creating things that are one-off mainstream, (or Open Source), in what they call an effort of efficiency or a claim to sticking to standards. In reality, they&#8217;ve just muddied the waters for developers looking to make the web more ubiquitous. IE8 continues this misguided charge with Web Slices, a particular [...]]]></description>
			<content:encoded><![CDATA[<p>Microsoft has a history of creating things that are one-off mainstream, (or Open Source), in what they call an effort of efficiency or a claim to sticking to standards. In reality, they&#8217;ve just muddied the waters for developers looking to make the web more ubiquitous.</p>
<p>IE8 continues this misguided charge with <a href="http://msdn.microsoft.com/en-us/library/cc304073(VS.85).aspx">Web Slices</a>, a particular element of a page which the browser can selectively update asynchronous to the rest of your behavior. In lamens terms, consider it to be RSS on crack. The idea is kind of cool and interesting as a developer: Provide desktop and web apps a <a href="http://en.wikipedia.org/wiki/Uniform_Resource_Identifier">URI</a> to a manageable piece of information that can be parsed relatively frequently for updates.</p>
<p>My issue is two fold: (1) the URI Microsoft defines is nonstandard and trivial; and (2), why should we learn another set of proprietary syntax for what should be defined elsewhere in the page or headers?</p>
<p>As for the URI, <a href="http://en.wikipedia.org/wiki/XPath">XPath</a> is a much stronger and cleaner way to identify what is subscribable. Why should I be limited to just one element at a time? XPath would allot me several subscriptions all at once. A URI like <code>http://blog.adventdigerati.com//*[@class="story"]:first</code> would give you my the snippet to my latest blog post, and omitting <code>:first</code> would give you all the posts on the front page. Why is that so hard?</p>
<p>Secondly, most of Slices&#8217; API is defined using bastardized (X)HTML elements and attributes. Even I learned that text content should not be used to define semantic meaning in a document; it&#8217;s a corruption of XML standard, one of the best directions in web standardization so far. How hard would it be to include a custom <a href="http://www.w3schools.com/html/html_meta.asp"><code>&lt;meta></code></a> tag in the <code>&lt;head></code>? Namespacing a custom tag would be sufficient, and you could even achieve the same effects MS wants via these methods. <code>&lt;meta name="ms-slice-title" content="/absolute/path/from/slice/root/to/title/tag"/></code> would give a consistent way to retrieve the titles for each slice with one line of code! Or, if need be that the slices be drastically different, <code>&lt;meta name="ms-slice-ttl" content="//*[@class='entry-content']"/></code> would parse slower but achieve the same goals, and be standards-compliant.</p>
<p>In all, everything Microsoft wanted to get out of their new Web Slices feature could already be done using existing tools; let&#8217;s not clutter what could be an awesome new tool for developers with sub-par requisites that somehow shoehorn their way into standards by just being left to fester.</p>
]]></content:encoded>
			<wfw:commentRss>http://blog.adventdigerati.com/2009/04/ms-slices-x-path-to-ribbons/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
