<?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/"
	xmlns:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Hosted lifebits meets infobus</title>
	<atom:link href="http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/</link>
	<description>Strategies for Internet citizens</description>
	<lastBuildDate>Tue, 16 Mar 2010 08:48:27 +0000</lastBuildDate>
	<generator>http://wordpress.com/</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: CameronNeylon.Net &#187; Blog Archive &#187; Pub-sub/syndication patterns and post publication peer review</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-131235</link>
		<dc:creator>CameronNeylon.Net &#187; Blog Archive &#187; Pub-sub/syndication patterns and post publication peer review</dc:creator>
		<pubDate>Wed, 30 Dec 2009 15:31:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-131235</guid>
		<description>[...] In a sense, when the Web 2.0 world was built it was got nearly precisely wrong for personal content. For me Jon Udell has written most clearly about this when he talks about the publish-subscribe pattern for successful frameworks. In essence I publish my content and you choose to subscribe to it. This works well for me, the blogger, at this site, but it is not so great for the commenter who has to leave their comment to my tender mercies on my site. It would be better if the commenter could publish their comment and I could syndicate it back to my blog. This creates all sorts of problems; it is challenging for you to aggregate your own comments together and you have to rely on the functionality of specific sites to help you follow responses to your comments. Jon wrote about this better than I can in his blog post. [...]</description>
		<content:encoded><![CDATA[<p>[...] In a sense, when the Web 2.0 world was built it was got nearly precisely wrong for personal content. For me Jon Udell has written most clearly about this when he talks about the publish-subscribe pattern for successful frameworks. In essence I publish my content and you choose to subscribe to it. This works well for me, the blogger, at this site, but it is not so great for the commenter who has to leave their comment to my tender mercies on my site. It would be better if the commenter could publish their comment and I could syndicate it back to my blog. This creates all sorts of problems; it is challenging for you to aggregate your own comments together and you have to rely on the functionality of specific sites to help you follow responses to your comments. Jon wrote about this better than I can in his blog post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Seb</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-128911</link>
		<dc:creator>Seb</dc:creator>
		<pubDate>Tue, 30 Jun 2009 20:23:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-128911</guid>
		<description>Leaving this comment in your blog&#039;s care, partly for my future reference ...

1) Backtype does a nice job of automagically gathering copies of the comments I leave on various blogs: http://www.backtype.com/sebpaquet

It features (local) revocation and fake/spam marking. It links to the original conversations; sadly but obviously, that link is one-way.

2) I haven&#039;t seen anyone do it, but one way to get pretty close to what you describe, by hand, would be to start a &quot;comment blog&quot; and dual-post every comment there, making sure to include reciprocal links. Somewhat tedious...</description>
		<content:encoded><![CDATA[<p>Leaving this comment in your blog&#8217;s care, partly for my future reference &#8230;</p>
<p>1) Backtype does a nice job of automagically gathering copies of the comments I leave on various blogs: <a href="http://www.backtype.com/sebpaquet" rel="nofollow">http://www.backtype.com/sebpaquet</a></p>
<p>It features (local) revocation and fake/spam marking. It links to the original conversations; sadly but obviously, that link is one-way.</p>
<p>2) I haven&#8217;t seen anyone do it, but one way to get pretty close to what you describe, by hand, would be to start a &#8220;comment blog&#8221; and dual-post every comment there, making sure to include reciprocal links. Somewhat tedious&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Science in the open &#187; Pub-sub/syndication patterns and post publication peer review</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-128514</link>
		<dc:creator>Science in the open &#187; Pub-sub/syndication patterns and post publication peer review</dc:creator>
		<pubDate>Sat, 20 Jun 2009 18:35:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-128514</guid>
		<description>[...] In a sense, when the Web 2.0 world was built it was got nearly precisely wrong for personal content. For me Jon Udell has written most clearly about this when he talks about the publish-subscribe pattern for successful frameworks. In essence I publish my content and you choose to subscribe to it. This works well for me, the blogger, at this site, but it is not so great for the commenter who has to leave their comment to my tender mercies on my site. It would be better if the commenter could publish their comment and I could syndicate it back to my blog. This creates all sorts of problems; it is challenging for you to aggregate your own comments together and you have to rely on the functionality of specific sites to help you follow responses to your comments. Jon wrote about this better than I can in his blog post. [...]</description>
		<content:encoded><![CDATA[<p>[...] In a sense, when the Web 2.0 world was built it was got nearly precisely wrong for personal content. For me Jon Udell has written most clearly about this when he talks about the publish-subscribe pattern for successful frameworks. In essence I publish my content and you choose to subscribe to it. This works well for me, the blogger, at this site, but it is not so great for the commenter who has to leave their comment to my tender mercies on my site. It would be better if the commenter could publish their comment and I could syndicate it back to my blog. This creates all sorts of problems; it is challenging for you to aggregate your own comments together and you have to rely on the functionality of specific sites to help you follow responses to your comments. Jon wrote about this better than I can in his blog post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim Yates</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-126918</link>
		<dc:creator>Jim Yates</dc:creator>
		<pubDate>Sat, 07 Mar 2009 17:43:47 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-126918</guid>
		<description>ehud says, &quot;...Interesting discussion. One nitpick: Not all information is the same. I don’t think the analogy between a comment made in the context of a discussion and medical records hold. ...&quot;
I agree and this is very very important.  Who is the owner of the information.  What are the conditions surrounding the information has to be taken into account.  It is not clear that you (Jon) are the owner of the X-ray (probably not the physical X-ray just the part that it is of your body - complex stuff).  Consider Music you have bought on CD (you, of course, do not get files from your friends ;-) ).  It has a copyright agreement associated with it that must be properly handled in any transfer.
While I believe that the Twitter type of activity has some value I do not think that it is game-changing.  There is a lot more to this area than has even begun to be thought about let alone executed in code.</description>
		<content:encoded><![CDATA[<p>ehud says, &#8220;&#8230;Interesting discussion. One nitpick: Not all information is the same. I don’t think the analogy between a comment made in the context of a discussion and medical records hold. &#8230;&#8221;<br />
I agree and this is very very important.  Who is the owner of the information.  What are the conditions surrounding the information has to be taken into account.  It is not clear that you (Jon) are the owner of the X-ray (probably not the physical X-ray just the part that it is of your body &#8211; complex stuff).  Consider Music you have bought on CD (you, of course, do not get files from your friends ;-) ).  It has a copyright agreement associated with it that must be properly handled in any transfer.<br />
While I believe that the Twitter type of activity has some value I do not think that it is game-changing.  There is a lot more to this area than has even begun to be thought about let alone executed in code.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jon Udell</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-126910</link>
		<dc:creator>Jon Udell</dc:creator>
		<pubDate>Fri, 06 Mar 2009 22:10:33 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-126910</guid>
		<description>&gt; Whether this is the right model for 
&gt; social activities such (like discussion
&gt; threads), I am not sure.

There is no singular right model, but it is /a/ right model. Example why: My conversation with Timo Hannay at Nature Publishing. 

http://blog.jonudell.net/2007/07/06/a-conversation-with-timo-hannay-about-the-scientific-web/

The issue here: Scientists would collaborate better, and science would advance faster, if scientists could participate more freely in loosely-coupled online discussion: blogging, commenting on other blogs, etc.

Many still don&#039;t, and observers closer to that scene than me invariably report that it&#039;s partly because they can&#039;t take credit for contributions in that realm, or measure the influence that accrues to them from such contributions.

The architecture I&#039;m proposing would support measurement of contribution and influence, so that scientists could more easily justify contributing to, and influencing, a loosely-coupled network.</description>
		<content:encoded><![CDATA[<p>&gt; Whether this is the right model for<br />
&gt; social activities such (like discussion<br />
&gt; threads), I am not sure.</p>
<p>There is no singular right model, but it is /a/ right model. Example why: My conversation with Timo Hannay at Nature Publishing. </p>
<p><a href="http://blog.jonudell.net/2007/07/06/a-conversation-with-timo-hannay-about-the-scientific-web/" rel="nofollow">http://blog.jonudell.net/2007/07/06/a-conversation-with-timo-hannay-about-the-scientific-web/</a></p>
<p>The issue here: Scientists would collaborate better, and science would advance faster, if scientists could participate more freely in loosely-coupled online discussion: blogging, commenting on other blogs, etc.</p>
<p>Many still don&#8217;t, and observers closer to that scene than me invariably report that it&#8217;s partly because they can&#8217;t take credit for contributions in that realm, or measure the influence that accrues to them from such contributions.</p>
<p>The architecture I&#8217;m proposing would support measurement of contribution and influence, so that scientists could more easily justify contributing to, and influencing, a loosely-coupled network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ehud</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-126905</link>
		<dc:creator>Ehud</dc:creator>
		<pubDate>Fri, 06 Mar 2009 18:22:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-126905</guid>
		<description>Interesting discussion. One nitpick: Not all information is the same. I don&#039;t think the analogy between a comment made in the context of a discussion and medical records hold. We want to be able to revoke, withdraw etc. for the latter, you are damn right that the architecture should support this. Whether this is the right model for social activities such (like discussion threads), I am not sure.</description>
		<content:encoded><![CDATA[<p>Interesting discussion. One nitpick: Not all information is the same. I don&#8217;t think the analogy between a comment made in the context of a discussion and medical records hold. We want to be able to revoke, withdraw etc. for the latter, you are damn right that the architecture should support this. Whether this is the right model for social activities such (like discussion threads), I am not sure.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mitch Garnaat</title>
		<link>http://blog.jonudell.net/2009/03/06/hosted-lifebits-meets-infobus/#comment-126900</link>
		<dc:creator>Mitch Garnaat</dc:creator>
		<pubDate>Fri, 06 Mar 2009 16:42:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.jonudell.net/?p=1215#comment-126900</guid>
		<description>Another interesting article.  I love this topic!  I think you are on the right track in asserting that the lifebits service is more about providing clarity of ownership and syndication than trying to enforce it.  True enforcement would lead you down an RIAA rathole that would just irritate people and provide no real value.  Clear communication of your intent regarding your content will achieve the desired affect in the vast majority of situations.

Mitch</description>
		<content:encoded><![CDATA[<p>Another interesting article.  I love this topic!  I think you are on the right track in asserting that the lifebits service is more about providing clarity of ownership and syndication than trying to enforce it.  True enforcement would lead you down an RIAA rathole that would just irritate people and provide no real value.  Clear communication of your intent regarding your content will achieve the desired affect in the vast majority of situations.</p>
<p>Mitch</p>
]]></content:encoded>
	</item>
</channel>
</rss>
