<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: FOAF spec diagram</title>
	<atom:link href="http://danbri.org/words/2007/11/04/222/feed" rel="self" type="application/rss+xml" />
	<link>http://danbri.org/words/2007/11/04/222</link>
	<description>the web, the world, us, you and them</description>
	<lastBuildDate>Thu, 11 Mar 2010 21:48:30 +0000</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: danbri&#8217;s foaf stories</title>
		<link>http://danbri.org/words/2007/11/04/222/comment-page-1#comment-13149</link>
		<dc:creator>danbri&#8217;s foaf stories</dc:creator>
		<pubDate>Sun, 04 Nov 2007 13:21:00 +0000</pubDate>
		<guid isPermaLink="false">http://danbri.org/words/2007/11/04/222#comment-13149</guid>
		<description>[...] revision, after feedback from [...]</description>
		<content:encoded><![CDATA[<p>[...] revision, after feedback from [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ivan</title>
		<link>http://danbri.org/words/2007/11/04/222/comment-page-1#comment-13148</link>
		<dc:creator>ivan</dc:creator>
		<pubDate>Sun, 04 Nov 2007 12:07:08 +0000</pubDate>
		<guid isPermaLink="false">http://danbri.org/words/2007/11/04/222#comment-13148</guid>
		<description>These things are always hugely helpful... so kudos for starting this...

I was puzzled by the big &#039;Thing&#039; blob there. I looked up in the latest foaf spec to see whether there is something new there, but then I realized that you meant owl:Thing... I think everything that is _not_ foaf should be very clearly shown. Which is the case, usually, because you add a namespace stuff for others, so this may be an exception. Maybe separating the foaf blobs from the others via a background colour would even be better. 

The &#039;Thing&#039; is, actually, a bit disturbing there, because it is not clear to the casual user that, say, an Agent is a Thing, ie, it could be used as an object for, say, primaryTopic. (I must admit I do not know how to capture that either, but it is always easier to critisize:-)

Adding those extras like sioc might be good but increases the clutter. I am not sure it helps here. If this was in SVG, I would say you should make that part clickable on/off, but that might be complicated for other formats... Maybe you should have two figures, one strictly on FOAF (well, the dc properties are useful, though) and the other with some &#039;guests&#039;.

I understand to leave out a bunch of properties to avoid clutter... But listing all the chat ID-s seems to be unnecessary, too. Having 1-2 makes it clear that it is where those would be used...

I hope this helps at least a little bit...</description>
		<content:encoded><![CDATA[<p>These things are always hugely helpful&#8230; so kudos for starting this&#8230;</p>
<p>I was puzzled by the big &#8216;Thing&#8217; blob there. I looked up in the latest foaf spec to see whether there is something new there, but then I realized that you meant owl:Thing&#8230; I think everything that is _not_ foaf should be very clearly shown. Which is the case, usually, because you add a namespace stuff for others, so this may be an exception. Maybe separating the foaf blobs from the others via a background colour would even be better. </p>
<p>The &#8216;Thing&#8217; is, actually, a bit disturbing there, because it is not clear to the casual user that, say, an Agent is a Thing, ie, it could be used as an object for, say, primaryTopic. (I must admit I do not know how to capture that either, but it is always easier to critisize:-)</p>
<p>Adding those extras like sioc might be good but increases the clutter. I am not sure it helps here. If this was in SVG, I would say you should make that part clickable on/off, but that might be complicated for other formats&#8230; Maybe you should have two figures, one strictly on FOAF (well, the dc properties are useful, though) and the other with some &#8216;guests&#8217;.</p>
<p>I understand to leave out a bunch of properties to avoid clutter&#8230; But listing all the chat ID-s seems to be unnecessary, too. Having 1-2 makes it clear that it is where those would be used&#8230;</p>
<p>I hope this helps at least a little bit&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
