<?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/marks/link/768893">
<title>Public marks on http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html</title>
<description>Public marks on http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html</description>
<link>http://blogmarks.net/marks/link/768893</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058216950"/>
<rdf:li resource="http://blogmarks.net/api/user/digitalmonkey/mark/503691"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058216950">
<title>Why Is RDF The Way It Is?</title>
<link>http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;There are often many ways of serializing a complex graph into a tree. serializers can start with different objects, and split out multi-referenced things into different parts of the tree in different places. So that's just a fact about the problem space of encoding rdf's structure into xml trees.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-02-21T05:35:15Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>rdf, xml</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html"><img border="0" src="http://blogmarks.net/screenshots/2009/02/21/e6b5d3d14cd240deff2c85214a628769.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html">Why Is RDF The Way It Is?</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/768893">1 other(s)</a> 
<div class="description"><blockquote><p>There are often many ways of serializing a complex graph into a tree. serializers can start with different objects, and split out multi-referenced things into different parts of the tree in different places. So that's just a fact about the problem space of encoding rdf's structure into xml trees.</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/xml">xml</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058216950">Copy</a> | 
<a href="http://blogmarks.net/link/768893">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/digitalmonkey/mark/503691">
<title>Why Is RDF The Way It Is?</title>
<link>http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html</link>
<description></description>
<dc:date>2005-07-06T14:06:59Z</dc:date>
<dc:author>digitalmonkey</dc:author>
<dc:subject>xml, rdf</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html"><img border="0" src="http://blogmarks.net/screenshots/2009/02/21/e6b5d3d14cd240deff2c85214a628769.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.w3.org/2001/sw/Europe/200407/swintro/syntaxdesign.html">Why Is RDF The Way It Is?</a></h4>
 
by <a href="http://blogmarks.net/user/digitalmonkey">digitalmonkey</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/768893">1 other(s)</a> 
<p class="tags">
<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/rdf">rdf</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=503691">Copy</a> | 
<a href="http://blogmarks.net/link/768893">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>