<?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"
	>
<channel>
	<title>Comments on: Linking classes, concepts, and individuals</title>
	<atom:link href="http://openguid.net/2008/10/linking-classes-concepts-and-individuals/feed/" rel="self" type="application/rss+xml" />
	<link>http://openguid.net/2008/10/linking-classes-concepts-and-individuals/</link>
	<description>Web Identity</description>
	<pubDate>Thu, 29 Jul 2010 17:00:15 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Jason</title>
		<link>http://openguid.net/2008/10/linking-classes-concepts-and-individuals/#comment-10</link>
		<dc:creator>Jason</dc:creator>
		<pubDate>Tue, 21 Oct 2008 20:08:28 +0000</pubDate>
		<guid isPermaLink="false">http://openguid.net/?p=54#comment-10</guid>
		<description>I was just paraphrasing so the triple would fit on one line...probably not a good enough reason to be inconsistent.  Since this post was meant to be read by humans, it seemed safe to use a short hand.  An actual RDF document would look more like &lt;a href="/e694edc9-da25-102b-9a03-2db401e887ec?encoding=xml" rel="nofollow"&gt;this&lt;/a&gt;.

I actually kind of like the result.  I am looking for ways to embed references to Open GUIDs in content in a manner that is usable and resolvable.  Using an href seems like a good start...though a float over div with the keywords and description would be better.  Hopefully tools will get to the point that we have the best of both worlds.</description>
		<content:encoded><![CDATA[<p>I was just paraphrasing so the triple would fit on one line&#8230;probably not a good enough reason to be inconsistent.  Since this post was meant to be read by humans, it seemed safe to use a short hand.  An actual RDF document would look more like <a href="/e694edc9-da25-102b-9a03-2db401e887ec?encoding=xml" rel="nofollow">this</a>.</p>
<p>I actually kind of like the result.  I am looking for ways to embed references to Open GUIDs in content in a manner that is usable and resolvable.  Using an href seems like a good start&#8230;though a float over div with the keywords and description would be better.  Hopefully tools will get to the point that we have the best of both worlds.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bernard</title>
		<link>http://openguid.net/2008/10/linking-classes-concepts-and-individuals/#comment-9</link>
		<dc:creator>Bernard</dc:creator>
		<pubDate>Tue, 21 Oct 2008 12:31:15 +0000</pubDate>
		<guid isPermaLink="false">http://openguid.net/?p=54#comment-9</guid>
		<description>Two remarks on this example.

Why do you write oguid:OrganicFood instead of the actual URI 
oguid:ea434692-e2c7-102b-9532-00301b462e0a?
This does not seem consistent about what you write everywhere else about the necessary "opacity" and "ugliness" of oguid URIs.

Using so-called "multilingual" URIs such as "bar:LabelAB" or "foo:AlimentosOrganicos" would help to make the point.

Bernard</description>
		<content:encoded><![CDATA[<p>Two remarks on this example.</p>
<p>Why do you write oguid:OrganicFood instead of the actual URI<br />
oguid:ea434692-e2c7-102b-9532-00301b462e0a?<br />
This does not seem consistent about what you write everywhere else about the necessary &#8220;opacity&#8221; and &#8220;ugliness&#8221; of oguid URIs.</p>
<p>Using so-called &#8220;multilingual&#8221; URIs such as &#8220;bar:LabelAB&#8221; or &#8220;foo:AlimentosOrganicos&#8221; would help to make the point.</p>
<p>Bernard</p>
]]></content:encoded>
	</item>
</channel>
</rss>
