<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/1.5.1.3" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: The OPS Blog Sample Application, Part I</title>
	<link>http://www.orbeon.com/blog/2005/03/28/the-ops-blog-sample-application-part-i/</link>
	<description>XForms Everywhere</description>
	<pubDate>Fri, 29 Aug 2008 23:43:25 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1.3</generator>

	<item>
		<title>by: Erik Bruchez</title>
		<link>http://www.orbeon.com/blog/2005/03/28/the-ops-blog-sample-application-part-i/#comment-160</link>
		<pubDate>Fri, 01 Apr 2005 15:05:48 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/28/the-ops-blog-sample-application-part-i/#comment-160</guid>
					<description>That's partly what I have started doing when using the terms &quot;title&quot; and &quot;description&quot; from RSS for posts. But I am not very happy with this, because heck, where does that &quot;description&quot; term come from? It appears that they have a better terminology in Atom, and that's probably the format to follow (&lt;a href=&quot;http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-06.txt&quot;&gt;http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-06.txt&lt;/a&gt;). So far I hadn't looked at Atom, but I believe after a first look that I am more inclined to like what they are doing than all the mess we've had so far with RSS and the Blogger API.

Converting from one format to another is going to be trivial anyway, but I agree that if we can follow an existing format, we'll be better off.</description>
		<content:encoded><![CDATA[	<p>That&#8217;s partly what I have started doing when using the terms &#8220;title&#8221; and &#8220;description&#8221; from RSS for posts. But I am not very happy with this, because heck, where does that &#8220;description&#8221; term come from? It appears that they have a better terminology in Atom, and that&#8217;s probably the format to follow (<a href="http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-06.txt"><a href='http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-06.txt' rel='nofollow'>http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-06.txt</a></a>). So far I hadn&#8217;t looked at Atom, but I believe after a first look that I am more inclined to like what they are doing than all the mess we&#8217;ve had so far with RSS and the Blogger API.</p>
	<p>Converting from one format to another is going to be trivial anyway, but I agree that if we can follow an existing format, we&#8217;ll be better off.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Stephan H. Wissel</title>
		<link>http://www.orbeon.com/blog/2005/03/28/the-ops-blog-sample-application-part-i/#comment-159</link>
		<pubDate>Fri, 01 Apr 2005 14:41:34 +0000</pubDate>
		<guid>http://www.orbeon.com/blog/2005/03/28/the-ops-blog-sample-application-part-i/#comment-159</guid>
					<description>Hi Eric,
Excellent idea. My thought to make the storage of the Weblog entry easier... Why not use RSS2.0 tags directly (or Atom). This way the RSS Feed would be very resource effective (either a XSLT or a SAX processor that filters out the not needed elements). A good into can be found here: http://blogs.law.harvard.edu/tech/rss
Of course the format need to have additional fields since RSS doesn't contain the full text or comments. What do you think?
;-) stw</description>
		<content:encoded><![CDATA[	<p>Hi Eric,<br />
Excellent idea. My thought to make the storage of the Weblog entry easier&#8230; Why not use RSS2.0 tags directly (or Atom). This way the RSS Feed would be very resource effective (either a XSLT or a SAX processor that filters out the not needed elements). A good into can be found here: <a href='http://blogs.law.harvard.edu/tech/rss' rel='nofollow'>http://blogs.law.harvard.edu/tech/rss</a><br />
Of course the format need to have additional fields since RSS doesn&#8217;t contain the full text or comments. What do you think?<br />
;-) stw
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
