<?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: New JSR to define a high-level REST API for Java</title>
	<atom:link href="http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/</link>
	<description>Realize your RESTful web APIs !</description>
	<lastBuildDate>Mon, 19 Dec 2011 20:51:08 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: JSR 311 approved for development &#171; Noelios Consulting</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-44</link>
		<dc:creator><![CDATA[JSR 311 approved for development &#171; Noelios Consulting]]></dc:creator>
		<pubDate>Wed, 25 Apr 2007 11:16:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-44</guid>
		<description><![CDATA[[...] can check a comprehensive list of posts following the initial announce on my updated blog post. There is a clear interest from the community for such an API. Some voiced concerns about the JCP [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] can check a comprehensive list of posts following the initial announce on my updated blog post. There is a clear interest from the community for such an API. Some voiced concerns about the JCP [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Restlet API and JSR-311 API &#171; Noelios Consulting</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-43</link>
		<dc:creator><![CDATA[Restlet API and JSR-311 API &#171; Noelios Consulting]]></dc:creator>
		<pubDate>Wed, 25 Apr 2007 11:10:03 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-43</guid>
		<description><![CDATA[[...] as underlined in this previous post, both APIs will end-up being complementary rather than competitors. To clarify the scopes of those [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] as underlined in this previous post, both APIs will end-up being complementary rather than competitors. To clarify the scopes of those [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RaymonWazerri</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-42</link>
		<dc:creator><![CDATA[RaymonWazerri]]></dc:creator>
		<pubDate>Sat, 21 Apr 2007 00:51:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-42</guid>
		<description><![CDATA[Hey, 
I love what you&#039;e doing! 
Don&#039;t ever change and best of luck. 
 
Raymon W.]]></description>
		<content:encoded><![CDATA[<p>Hey,<br />
I love what you&#8217;e doing!<br />
Don&#8217;t ever change and best of luck. </p>
<p>Raymon W.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JavaSPEKTRUM Blogosphäre &#187; Blog Archiv &#187; Blogosphäre (aus JavaSPEKTRUM 02/07)</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-41</link>
		<dc:creator><![CDATA[JavaSPEKTRUM Blogosphäre &#187; Blog Archiv &#187; Blogosphäre (aus JavaSPEKTRUM 02/07)]]></dc:creator>
		<pubDate>Tue, 06 Mar 2007 07:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-41</guid>
		<description><![CDATA[[...] erst erfolgen sollte, nachdem sich eine Lösung (z.B. auf Open Source-Basis) bereits bewährt hat. Positives Feedback kommt dagegen von Jérôme Louvel, Autor des RESTlet-Frameworks &#8212; wenig verwunderlich, ist er [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] erst erfolgen sollte, nachdem sich eine Lösung (z.B. auf Open Source-Basis) bereits bewährt hat. Positives Feedback kommt dagegen von Jérôme Louvel, Autor des RESTlet-Frameworks &#8212; wenig verwunderlich, ist er [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Pragmatic Dictator &#187; Blog Archive &#187; The Simplest API Possible</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-40</link>
		<dc:creator><![CDATA[Pragmatic Dictator &#187; Blog Archive &#187; The Simplest API Possible]]></dc:creator>
		<pubDate>Mon, 26 Feb 2007 16:12:53 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-40</guid>
		<description><![CDATA[[...] news is the proposal for a REST API in Java. Equally interesting is that various members of the community are asking for a simple API [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] news is the proposal for a REST API in Java. Equally interesting is that various members of the community are asking for a simple API [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Cave &#187; Blog Archive &#187; More JSR 311</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-39</link>
		<dc:creator><![CDATA[The Cave &#187; Blog Archive &#187; More JSR 311]]></dc:creator>
		<pubDate>Fri, 23 Feb 2007 13:31:35 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-39</guid>
		<description><![CDATA[[...] More posts about the REST JSR. [...] ]]></description>
		<content:encoded><![CDATA[<p>[...] More posts about the REST JSR. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jérôme Louvel</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-38</link>
		<dc:creator><![CDATA[Jérôme Louvel]]></dc:creator>
		<pubDate>Thu, 15 Feb 2007 07:42:06 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-38</guid>
		<description><![CDATA[The list above is only a general (and personal) list of requirements. The expert group will have to agree on those requirements before we can appreciate how well JRA solves them. Marc Hadley, one of the spec leads, has more details on the annotations plan. See the link at the end of the post. You could also apply for an Expert Group Nomination at:
http://www.jcp.org/en/jsr/egnom?id=311

Best regards,
Jerome]]></description>
		<content:encoded><![CDATA[<p>The list above is only a general (and personal) list of requirements. The expert group will have to agree on those requirements before we can appreciate how well JRA solves them. Marc Hadley, one of the spec leads, has more details on the annotations plan. See the link at the end of the post. You could also apply for an Expert Group Nomination at:<br />
<a href="http://www.jcp.org/en/jsr/egnom?id=311" rel="nofollow">http://www.jcp.org/en/jsr/egnom?id=311</a></p>
<p>Best regards,<br />
Jerome</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Diephouse</title>
		<link>http://blog.restlet.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-37</link>
		<dc:creator><![CDATA[Dan Diephouse]]></dc:creator>
		<pubDate>Wed, 14 Feb 2007 20:17:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.noelios.com/2007/02/14/new-jsr-to-define-a-high-level-rest-api-for-java/#comment-37</guid>
		<description><![CDATA[I&#039;m not sure if you&#039;re trying to say that JRA doesn&#039;t meet all those requirements, or if that is just a general requirements list. If the former, let me provide a couple clarifications on the JRA project (which I started):
1. It uses URI templates
2. They are not specific to XML, but currently CXF (the only implementation at the moment) only supports XML. I&#039;m hoping to change this in the near future though :-)
 
With that said, I&#039;m looking forward to what the JSR group comes up with. JRA is definitely just a start and I hope this JSR makes the need for JRA go away!  I would definitely like to support this in CXF once its ready.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;m not sure if you&#8217;re trying to say that JRA doesn&#8217;t meet all those requirements, or if that is just a general requirements list. If the former, let me provide a couple clarifications on the JRA project (which I started):<br />
1. It uses URI templates<br />
2. They are not specific to XML, but currently CXF (the only implementation at the moment) only supports XML. I&#8217;m hoping to change this in the near future though <img src='http://s0.wp.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>With that said, I&#8217;m looking forward to what the JSR group comes up with. JRA is definitely just a start and I hope this JSR makes the need for JRA go away!  I would definitely like to support this in CXF once its ready.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

