<?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">
<title>Public marks from user night.kame with tag rdf</title>
<description>Public marks from user night.kame with tag rdf</description>
<link>http://blogmarks.net/user/night.kame/marks/tag/rdf</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058384924"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1058329768"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/1057946612"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/753818"/>
<rdf:li resource="http://blogmarks.net/api/user/night.kame/mark/655341"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058384924">
<title>Aligning Ontologies with Falcon - Home</title>
<link>http://iws.seu.edu.cn/projects/matching/index.jsp</link>
<description>&lt;blockquote&gt;&lt;p&gt;Falcon-AO, a prominent component of Falcon, is an automatic ontology matching system that helps actualize interoperability between (Semantic) Web applications that use different but related ontologies. Recently, it has become a very practical and popular choice for matching Web ontologies expressed by RDF(S) and OWL. Falcon-AO is implemented in Java, and presently, it is an open source project under the Apache 2.0 license.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-06-22T20:37:59Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>rdf, owl, ontologie, schema, matching</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://iws.seu.edu.cn/projects/matching/index.jsp"><img border="0" src="http://blogmarks.net/screenshots/2009/06/22/f749fcef2f708033c58b5be1cbbb6a84.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://iws.seu.edu.cn/projects/matching/index.jsp">Aligning Ontologies with Falcon - Home</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<div class="description"><blockquote><p>Falcon-AO, a prominent component of Falcon, is an automatic ontology matching system that helps actualize interoperability between (Semantic) Web applications that use different but related ontologies. Recently, it has become a very practical and popular choice for matching Web ontologies expressed by RDF(S) and OWL. Falcon-AO is implemented in Java, and presently, it is an open source project under the Apache 2.0 license.</p></blockquote></div>
<p class="tags">
<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/owl">owl</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ontologie">ontologie</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/schema">schema</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/matching">matching</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058384924">Copy</a> | 
<a href="http://blogmarks.net/link/3249110">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/1058329768">
<title>RDF Review Vocabulary</title>
<link>http://vocab.org/review/terms.html</link>
<description>Vocabulaire RDF pour les évaluations. Il semble que Google ait choisi de réinventer un autre vocabulaire pour sa fonctionnalité Rich Snippets.</description>
<dc:date>2009-05-19T15:49:17Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>rdf, owl, review, évaluation, nih, google</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://vocab.org/review/terms.html"><img border="0" src="http://blogmarks.net/screenshots/2009/05/19/b0cf9393dd43d001d09fda6b10561b70.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://vocab.org/review/terms.html">RDF Review Vocabulary</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<p class="description">Vocabulaire RDF pour les évaluations. Il semble que Google ait choisi de réinventer un autre vocabulaire pour sa fonctionnalité Rich Snippets.</p>
<p class="tags">
<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/owl">owl</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/review">review</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/%25C3%25A9valuation">évaluation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/nih">nih</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058329768">Copy</a> | 
<a href="http://blogmarks.net/link/3201481">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> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/753818">
<title>Plain Old XML - Wikipedia, the free encyclopedia</title>
<link>http://en.wikipedia.org/wiki/Plain_Old_XML</link>
<description>Quel est le problème d'une encyclopédie sans encyclopédiste ? La dissémination de fausses informations, ce qui est encore plus grave quand on devient une référence à grand coup de Pagerank...</description>
<dc:date>2006-08-06T06:42:28Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>rdf, xml, pox</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://en.wikipedia.org/wiki/Plain_Old_XML"><img border="0" src="http://blogmarks.net/screenshots/2006/08/06/bb71ebe0036844ea46776e701d44d6a6.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://en.wikipedia.org/wiki/Plain_Old_XML">Plain Old XML - Wikipedia, the free encyclopedia</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
<p class="description">Quel est le problème d'une encyclopédie sans encyclopédiste ? La dissémination de fausses informations, ce qui est encore plus grave quand on devient une référence à grand coup de Pagerank...</p>
<p class="tags">
<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/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pox">pox</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=753818">Copy</a> | 
<a href="http://blogmarks.net/link/1010527">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/night.kame/mark/655341">
<title>Interview de Iván Herman (W3C) - JDN Développeurs</title>
<link>http://developpeur.journaldunet.com/itws/060608-itw-w3c-herman.shtml</link>
<description>&quot;XHTML est un bon exemple, car ce format cherche à définir plus strictement et de manière plus évolutive les idées proposées par les gens des microformats.&quot;

Comment ça, les microformats ne sont pas la panacées ? Le pragmatisme chevrotant aurait des limites ? Ou plus simplement, les anti-RDF sont des prosélytes non-pragmatiques ?</description>
<dc:date>2006-06-25T14:16:59Z</dc:date>
<dc:author>night.kame</dc:author>
<dc:subject>sémantique, xhtml, microformat, web sémantique, rdf</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://developpeur.journaldunet.com/itws/060608-itw-w3c-herman.shtml"><img border="0" src="http://blogmarks.net/screenshots/2006/08/03/f37557582a7b95a4bf5ec849a765f60c.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://developpeur.journaldunet.com/itws/060608-itw-w3c-herman.shtml">Interview de Iván Herman (W3C) - JDN Développeurs</a></h4>
 
by <a href="http://blogmarks.net/user/night.kame">night.kame</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/939548">1 other(s)</a> 
<p class="description">"XHTML est un bon exemple, car ce format cherche à définir plus strictement et de manière plus évolutive les idées proposées par les gens des microformats."

Comment ça, les microformats ne sont pas la panacées ? Le pragmatisme chevrotant aurait des limites ? Ou plus simplement, les anti-RDF sont des prosélytes non-pragmatiques ?</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/s%25C3%25A9mantique">sémantique</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xhtml">xhtml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microformat">microformat</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bs%25C3%25A9mantique">web sémantique</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/rdf">rdf</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=655341">Copy</a> | 
<a href="http://blogmarks.net/link/939548">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>