<?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"
	>
<channel>
	<title>Comments on: The problem with mail is that messages aren&#8217;t intrinsically addressable</title>
	<atom:link href="http://blog.jonmountjoy.com/the-problem-with-mail-is-that-we-have-no-permalinks/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonmountjoy.com/the-problem-with-mail-is-that-we-have-no-permalinks/</link>
	<description>Memes and Schemes from a Community Manager Consultant</description>
	<pubDate>Tue, 02 Dec 2008 12:34:41 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jon</title>
		<link>http://blog.jonmountjoy.com/the-problem-with-mail-is-that-we-have-no-permalinks/#comment-6</link>
		<dc:creator>Jon</dc:creator>
		<pubDate>Wed, 16 Aug 2006 08:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonmountjoy.com/meme/the-problem-with-mail-is-that-we-have-no-permalinks/#comment-6</guid>
		<description>Good one CotÃ©.  I just fired up GMail in the hope...I sort of drafted a URI schema document in my head, and one of the aspects was that mail messages should be addressable on the web too.  I guess it would be something like: 
mail:messageID[:xxmountjoy@gmail.com]
But you'd need a different way of processing these for every web mail implementation, unless they all provided a standard RESTian service say for calling up the desired mail message.  &lt;br /&gt;I think Leopard, the new OS X release, fixes my problem at least.  It looks like their todos allows you to embed pointers to mail messages.  I hope that they've done this "right" and that these pointers can be embedded (and recognized) in all sorts of documents.  (ie. a URI scheme of some sort)</description>
		<content:encoded><![CDATA[<p>Good one CotÃ©.  I just fired up GMail in the hope&#8230;I sort of drafted a URI schema document in my head, and one of the aspects was that mail messages should be addressable on the web too.  I guess it would be something like:<br />
mail:messageID[:xxmountjoy@gmail.com]<br />
But you&#8217;d need a different way of processing these for every web mail implementation, unless they all provided a standard RESTian service say for calling up the desired mail message.  <br />I think Leopard, the new OS X release, fixes my problem at least.  It looks like their todos allows you to embed pointers to mail messages.  I hope that they&#8217;ve done this &#8220;right&#8221; and that these pointers can be embedded (and recognized) in all sorts of documents.  (ie. a URI scheme of some sort)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cote'</title>
		<link>http://blog.jonmountjoy.com/the-problem-with-mail-is-that-we-have-no-permalinks/#comment-5</link>
		<dc:creator>Cote'</dc:creator>
		<pubDate>Tue, 15 Aug 2006 23:43:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.jonmountjoy.com/meme/the-problem-with-mail-is-that-we-have-no-permalinks/#comment-5</guid>
		<description>While this train of thought doesn't exactly address the above: I've been wishing that emails from lists that have web based archives would put the URL for the email at the bottom of the email.

That sounds confusing.

The use-case is this: I read a message I like in ScrumDevelopment (or whatever list) and want to bookmark/link to it. I have to go login to the Yahoo! Groups web archive UI, find the message, and then I have the link.

I'd much rather have just had the link in the email to click on.</description>
		<content:encoded><![CDATA[<p>While this train of thought doesn&#8217;t exactly address the above: I&#8217;ve been wishing that emails from lists that have web based archives would put the URL for the email at the bottom of the email.</p>
<p>That sounds confusing.</p>
<p>The use-case is this: I read a message I like in ScrumDevelopment (or whatever list) and want to bookmark/link to it. I have to go login to the Yahoo! Groups web archive UI, find the message, and then I have the link.</p>
<p>I&#8217;d much rather have just had the link in the email to click on.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
