<?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/rdf,java">
<title>Public marks from user night.kame with tags rdf &amp; java</title>
<description>Public marks from user night.kame with tags rdf &amp; java</description>
<link>http://blogmarks.net/user/night.kame/marks/tag/rdf,java</link>
<items><rdf:Seq><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/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>