<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.12-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Some simple examples of using Erlang&#8217;s XPath implementation</title>
	<link>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation</link>
	<description>What happens at LShift</description>
	<pubDate>Sat, 22 Nov 2008 00:14:36 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.12-alpha</generator>

	<item>
		<title>by: tonyg</title>
		<link>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-91080</link>
		<pubDate>Fri, 18 Apr 2008 15:54:03 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-91080</guid>
					<description>&lt;p&gt;@Sopwith Camel: Good point. XDM is a richer model than Infoset. I'm not sure the cost would be significantly different, but there's certainly an expressivity win. On the other hand, I don't particularly fancy implementing XPath 2.0 :-)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>@Sopwith Camel: Good point. XDM is a richer model than Infoset. I&#8217;m not sure the cost would be significantly different, but there&#8217;s certainly an expressivity win. On the other hand, I don&#8217;t particularly fancy implementing XPath 2.0 :-)</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Sopwith Camel</title>
		<link>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-91054</link>
		<pubDate>Fri, 18 Apr 2008 12:14:37 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-91054</guid>
					<description>&lt;p&gt;Why not expose the message as XDM and avoid the cost and additional transformation of going via XML Infoset?&lt;/p&gt;

&lt;p&gt;(apologies for being required to use a nom de blog)&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Why not expose the message as XDM and avoid the cost and additional transformation of going via XML Infoset?</p>
<p>(apologies for being required to use a nom de blog)</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: tonyg</title>
		<link>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-83129</link>
		<pubDate>Fri, 01 Feb 2008 15:47:36 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-83129</guid>
					<description>&lt;p&gt;We should experiment with adding it to RabbitMQ first, and making sure the design is sound - and once we have a solid, implementation-neutral proposal, we can ask the AMQP working group what they think of the idea. A proven, implemented idea has much greater chance of being accepted.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>We should experiment with adding it to RabbitMQ first, and making sure the design is sound - and once we have a solid, implementation-neutral proposal, we can ask the AMQP working group what they think of the idea. A proven, implemented idea has much greater chance of being accepted.</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: John Watson</title>
		<link>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-83097</link>
		<pubDate>Fri, 01 Feb 2008 10:22:43 +0000</pubDate>
		<guid>http://www.lshift.net/blog/2008/01/31/some-simple-examples-of-using-erlangs-xpath-implementation#comment-83097</guid>
					<description>&lt;p&gt;Tony,&lt;/p&gt;

&lt;p&gt;What do you think are the chances of getting an XPath routing exchange added to a future version of the AMQP spec?  This sort of thing is precisely what I need.&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Tony,</p>
<p>What do you think are the chances of getting an XPath routing exchange added to a future version of the AMQP spec?  This sort of thing is precisely what I need.</p>
]]></content:encoded>
				</item>
</channel>
</rss>
