<?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: open to view</title>
	<atom:link href="http://inkdroid.org/journal/2009/08/13/open-to-view/feed/" rel="self" type="application/rss+xml" />
	<link>http://inkdroid.org/journal/2009/08/13/open-to-view/</link>
	<description>$pithy_personal_mission_statement</description>
	<lastBuildDate>Wed, 10 Mar 2010 02:04:23 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: inkdroid &#8250; data.gov.uk and rdfa</title>
		<link>http://inkdroid.org/journal/2009/08/13/open-to-view/comment-page-1/#comment-81696</link>
		<dc:creator>inkdroid &#8250; data.gov.uk and rdfa</dc:creator>
		<pubDate>Wed, 27 Jan 2010 01:53:14 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=1103#comment-81696</guid>
		<description>[...] comforting about being able to crawl the open web to find the information that&#8217;s there in open to view.   This was written by ed. Posted on Tuesday, January 26, 2010, at 3:41 pm. Filed under publishing, [...]</description>
		<content:encoded><![CDATA[<p>[...] comforting about being able to crawl the open web to find the information that&#8217;s there in open to view.   This was written by ed. Posted on Tuesday, January 26, 2010, at 3:41 pm. Filed under publishing, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bibwild.wordpress.com/</title>
		<link>http://inkdroid.org/journal/2009/08/13/open-to-view/comment-page-1/#comment-81542</link>
		<dc:creator>bibwild.wordpress.com/</dc:creator>
		<pubDate>Tue, 18 Aug 2009 20:23:40 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=1103#comment-81542</guid>
		<description>Exhibitionist Data? heh.</description>
		<content:encoded><![CDATA[<p>Exhibitionist Data? heh.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: bibwild.wordpress.com/</title>
		<link>http://inkdroid.org/journal/2009/08/13/open-to-view/comment-page-1/#comment-81541</link>
		<dc:creator>bibwild.wordpress.com/</dc:creator>
		<pubDate>Tue, 18 Aug 2009 20:21:03 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=1103#comment-81541</guid>
		<description>It&#039;s definitely a &#039;better web app&#039;, but it&#039;s better in a particular way it may be useful to be descriptive of. Better in that the data and services are more easily automatically discoverable by a machine, as they are exposed in a standard(ish) way.  

Accessible Data?  An Exposed Web App?  A web app which exposes it&#039;s data in standard ways?

I am not neccesarily myself convinced that RDF is always the &#039;best&#039; way to do this -- at least not within a certain real world project where benefits and costs have to be balanced within externally set limits. But actually, I&#039;m not even convinced that RDF is always the easiest for consumers to deal with either. Although I guess in an ideal world, we&#039;d always have RDF _plus_ something else that might be easier for a consumer in a given context -- because I think RDF is an experiment well worth engaging in, although I&#039;m less convinced of the ultimate success of this experiment than some Linked Data boosters.  But, back in the real world...  we don&#039;t always have the resources to do things ideally. The important thing to me is exposing your data, not how you do it.  Exposed Data?</description>
		<content:encoded><![CDATA[<p>It&#8217;s definitely a &#8216;better web app&#8217;, but it&#8217;s better in a particular way it may be useful to be descriptive of. Better in that the data and services are more easily automatically discoverable by a machine, as they are exposed in a standard(ish) way.  </p>
<p>Accessible Data?  An Exposed Web App?  A web app which exposes it&#8217;s data in standard ways?</p>
<p>I am not neccesarily myself convinced that RDF is always the &#8216;best&#8217; way to do this &#8212; at least not within a certain real world project where benefits and costs have to be balanced within externally set limits. But actually, I&#8217;m not even convinced that RDF is always the easiest for consumers to deal with either. Although I guess in an ideal world, we&#8217;d always have RDF _plus_ something else that might be easier for a consumer in a given context &#8212; because I think RDF is an experiment well worth engaging in, although I&#8217;m less convinced of the ultimate success of this experiment than some Linked Data boosters.  But, back in the real world&#8230;  we don&#8217;t always have the resources to do things ideally. The important thing to me is exposing your data, not how you do it.  Exposed Data?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Miller</title>
		<link>http://inkdroid.org/journal/2009/08/13/open-to-view/comment-page-1/#comment-81540</link>
		<dc:creator>Paul Miller</dc:creator>
		<pubDate>Fri, 14 Aug 2009 09:54:19 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=1103#comment-81540</guid>
		<description>&quot;I had always hoped (and continue to hope) that the Linked Data effort is bigger than a particular brand, or reformulation of the semantic web effort … for me it’s a pattern for building a better web.&quot;

I would, of course, have to agree. I am convinced that RDF is almost certainly the &#039;best&#039; way to do this... but it is definitely not the &#039;only&#039; way. To suggest otherwise is unnecessary, unwise, and - ultimately - unhelpful.</description>
		<content:encoded><![CDATA[<p>&#8220;I had always hoped (and continue to hope) that the Linked Data effort is bigger than a particular brand, or reformulation of the semantic web effort … for me it’s a pattern for building a better web.&#8221;</p>
<p>I would, of course, have to agree. I am convinced that RDF is almost certainly the &#8216;best&#8217; way to do this&#8230; but it is definitely not the &#8216;only&#8217; way. To suggest otherwise is unnecessary, unwise, and &#8211; ultimately &#8211; unhelpful.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ed</title>
		<link>http://inkdroid.org/journal/2009/08/13/open-to-view/comment-page-1/#comment-81539</link>
		<dc:creator>ed</dc:creator>
		<pubDate>Thu, 13 Aug 2009 23:49:51 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=1103#comment-81539</guid>
		<description>d&#039;oh -- thanks dan :-)</description>
		<content:encoded><![CDATA[<p>d&#8217;oh &#8212; thanks dan :-)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dchud</title>
		<link>http://inkdroid.org/journal/2009/08/13/open-to-view/comment-page-1/#comment-81538</link>
		<dc:creator>dchud</dc:creator>
		<pubDate>Thu, 13 Aug 2009 21:37:46 +0000</pubDate>
		<guid isPermaLink="false">http://inkdroid.org/journal/?p=1103#comment-81538</guid>
		<description>I&#039;m sure my employers at InfoToday would prefer me to point out that I&#039;m writing for Computers in Libraries, not that other rag. :)  -Dan</description>
		<content:encoded><![CDATA[<p>I&#8217;m sure my employers at InfoToday would prefer me to point out that I&#8217;m writing for Computers in Libraries, not that other rag. :)  -Dan</p>
]]></content:encoded>
	</item>
</channel>
</rss>
