<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/user/night.kame/marks/tag/rest">
<title>Public marks from user night.kame with tag rest</title>
<description>Public marks from user night.kame with tag rest</description>
<link>http://blogmarks.net/user/night.kame/marks/tag/rest</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058352231"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1057946612"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058352231">
<title>Unboxing Web-Oriented Architecture: The 6 Aspects Of An Emergent Architectural Style</title>
<link>http://hinchcliffe.org/archive/2009/06/06/16901.aspx</link>
<description>&lt;blockquote&gt;&lt;p&gt;Transfer Methods. This is at the core of REST and ROA and is the foundation of Web-Oriented Architecture. You can read Roy Fielding's chapter on REST (he conceived of the approach originally) or you can just follow the simple guidelines here. At other times, protocols like BitTorrent can be used if the requirements warrant it, but these are exceptional scenarios that I will cover at some point in the future.&lt;/p&gt;&lt;/blockquote&gt;
&lt;p&gt;Ne pas citer XMPP dans les &quot;Transfer Methods&quot; quelque jours après l'annonce de Google Wave, et surtout le mettre dans le schéma au niveau des Microformats fait perdre toute crédibilité à l'article.&lt;/p&gt;</description>
<dc:date>2009-06-07T19:29:02Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>soa, rest, xmpp, microformats, gloubi-boulga</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://hinchcliffe.org/archive/2009/06/06/16901.aspx"><img border="0" src="http://blogmarks.net/screenshots/2009/06/07/2bc3b205bc59b5d8c3bd4a6857ce3582.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://hinchcliffe.org/archive/2009/06/06/16901.aspx">Unboxing Web-Oriented Architecture: The 6 Aspects Of An Emergent Architectural Style</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>Transfer Methods. This is at the core of REST and ROA and is the foundation of Web-Oriented Architecture. You can read Roy Fielding's chapter on REST (he conceived of the approach originally) or you can just follow the simple guidelines here. At other times, protocols like BitTorrent can be used if the requirements warrant it, but these are exceptional scenarios that I will cover at some point in the future.</p></blockquote>
<p>Ne pas citer XMPP dans les "Transfer Methods" quelque jours après l'annonce de Google Wave, et surtout le mettre dans le schéma au niveau des Microformats fait perdre toute crédibilité à l'article.</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/soa">soa</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rest">rest</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xmpp">xmpp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformats">microformats</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gloubi-boulga">gloubi-boulga</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058352231">Copy</a> | 
<a href="http://blogmarks.net/link/3220692">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1057946612">
<title>Qi4j: REST EntityStore and SPARQL EntityFinder = rich client web apps!</title>
<link>http://www.jroller.com/rickard/entry/qi4j_rest_entitystore_and_sparql</link>
<description>&lt;blockquote&gt;&lt;p&gt;For the finder part I have implemented a SPARQL backend, which internally delegates to Sesame2, which is the same default index/query that is used to find Entities in general. This in itself is pretty cool, because it means that you can write your domain model in Java, have it be automatically persisted in a store like Neo4j, and then with no extra effort expose it through SPARQL for AJAX webapps to consume (both RDF/XML and JSON output is supported today). Minimally writing a domain model only involves writing Java interfaces (no classes), so it's pretty easy to get started.&lt;/p&gt;&lt;/blockquote&gt;

Tant de choses à tester...</description>
<dc:date>2008-08-15T09:53:17Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>java, SPARQL, rdf, rest</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.jroller.com/rickard/entry/qi4j_rest_entitystore_and_sparql"><img border="0" src="http://blogmarks.net/screenshots/2008/08/15/3f043a208ec5dd021a63b401e778e762.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.jroller.com/rickard/entry/qi4j_rest_entitystore_and_sparql">Qi4j: REST EntityStore and SPARQL EntityFinder = rich client web apps!</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>For the finder part I have implemented a SPARQL backend, which internally delegates to Sesame2, which is the same default index/query that is used to find Entities in general. This in itself is pretty cool, because it means that you can write your domain model in Java, have it be automatically persisted in a store like Neo4j, and then with no extra effort expose it through SPARQL for AJAX webapps to consume (both RDF/XML and JSON output is supported today). Minimally writing a domain model only involves writing Java interfaces (no classes), so it's pretty easy to get started.</p></blockquote>

Tant de choses à tester...</div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/SPARQL">SPARQL</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rdf">rdf</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rest">rest</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057946612">Copy</a> | 
<a href="http://blogmarks.net/link/2866639">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>