<?xml version="1.0" encoding="UTF-8" ?>
<rss version="2.0">
<channel>

<title>What do people have against URLs or URIs? (Updated)</title><link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388</link><description>Stumbled across a nice post titled: What do people have against URLs?. My answer: Everything, if they don&#39;t understand the inherent power of URLs when incorporated into the &amp;quot;Data Source Naming&amp;quot; mechanism of the Web called: URIs :-)
URIs are simple to use i.e you simply click on them via a user agents UI. However, URLs when incorporated into Data Source Naming en route to constructing HTTP based Identifiers, that deliver HTTP based pointers to the location / address of a Resource Descriptions, another matter.
I touched on this issue in my Linked Data Planet keynote last week, and I must say, it did set off a light.
I believe, we can only get the broader Web community to comprehend the utility of URIs (Web Data Source Names) by exposing said utility via the Web&#39;s Universal Client (Web Browser). For instance, how do URN based Identity / Naming schemes help in a world dominated by Web Browsers that only grok &amp;quot;http://&amp;quot;? From my vantage point, the practical solution is for data providers who already have &amp;quot;doi&amp;quot;, &amp;quot;lsid&amp;quot; and other Handle based Identifiers in place, to embark upon http-to-native-naming-scheme-proxying.
In my usual &amp;quot;dog-fooding&amp;quot; and &amp;quot;practice what you preach&amp;quot; fashion, this is exactly what we do in the new Linked Data Web extension that we&#39;ve decided to reveal to the public (albeit late beta). Thus, when you use an existing browser to view pages with &amp;quot;lsid&amp;quot; or &amp;quot;doi&amp;quot; URNs, you still enjoy the utility of getting at the &amp;quot;Raw Linked Data Sources&amp;quot; that these names expose.</description><pubDate>Sun, 22 Jun 2008 22:36:14 GMT</pubDate><generator>Virtuoso Universal Server 08.03.3334</generator><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Kingsley Uyi Idehen</dc:creator><image><title>What do people have against URLs or URIs? (Updated)</title><url>http://www.openlinksw.com:443/weblog/public/images/vbloglogo.gif</url><link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388</link><description>I have seen the future and it&#39;s full of Linked Data! :-)</description><width>88</width><height>31</height></image>
<item><title>Kingsley Uyi Idehen</title><guid>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4580</guid><link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4580</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kidehen@openlinksw.com</dc:creator><pubDate>Mon, 23 Jun 2008 13:37:57 GMT</pubDate><description>Simon,&lt;br&gt;&lt;br&gt;Very nice meeting and chatting with you at Linked Data Planet :-) &lt;br&gt;&lt;br&gt;Yes, there is a role for tools to play re. URIs deployment from a corpus of URLs. This is a pretty sizable opportunity for Linked Data Deployment middleware (imho) i.e wrapping URIs around URLs that basically connects the Document and the Things (Named Entities and Subject Matter) that the Document is about. I also see RDFa, when used in conjunction with the &lt;a href=&quot;http://bibliontology.com/&quot;&gt;Biblogrphic Ontology&lt;/a&gt;, as a pretty neat route for resolving some of these matters.&lt;br&gt;&lt;br&gt;Kingsley&lt;br&gt;&lt;br /&gt;

</description></item><item><title>Kingsley Uyi Idehen</title><guid>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4579</guid><link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4579</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">kidehen@openlinksw.com</dc:creator><pubDate>Mon, 23 Jun 2008 13:11:52 GMT</pubDate><description>Dave,&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Truly ironic :-)  Especially as this was the result of a cut &amp;amp; paste job from my internal post about the same subject (even longer story).&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Anyway, the link is fixed. &lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Thanks,&lt;/div&gt;&lt;div&gt;&lt;br&gt;&lt;/div&gt;&lt;div&gt;Kingsley&lt;/div&gt;</description></item><item><title>Simon Gibbs</title><guid>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4578</guid><link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4578</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">simon.gibbs@cantorva.com</dc:creator><pubDate>Mon, 23 Jun 2008 09:49:49 GMT</pubDate><description>Hi Kingsley, I did enjoy your keynote at Linked Data Planet, and thank you for your advice IRL re licencing of DBpedia data.&lt;br&gt;&lt;br&gt;I think one issue with adoption of URIs is that people feel the need to create the URL as a web document, analagous to a namespace document i.e. to make a GET on the URI dereferencable with a 200 status code and a meaningful representation in the response. &lt;br&gt;&lt;br&gt;We see this a ludicrously low barrier (and I tend to feel is actually not necessary as a theoretically dereferencable URL in still better than a URN, IMHO) but if your an application developer working on a minor project inside a large corporate bureauocracy then you face the need to justify creating a space on a web server for the namespace documents, vocabulary documentation, OWL, RDFS and XSD documents etc. Unfortunately a lot of data processing tasks are very minor projects.&lt;br&gt;&lt;br&gt;Project managers will probably support documentation for end users, but this kind of development documentation is often overlooked anyway and the requirement to explain - at length - what it is you are doing, what RDF is, what RDFS and OWL are, what a predicate is, why you aren&#39;t just using a database etc mean you&#39;re unlikely to get anywhere fast. Unless a developer has bought into the Linked Data concept and is willing and able to proselytise then they will prefer to just use an inverse fucntional property and stick to public vocabs - or hell - just to use a database.&lt;br&gt;&lt;br&gt;There is a role for tools here I think...&lt;br&gt;&lt;br&gt;&lt;br /&gt;

</description></item><item><title>Dave Beckett</title><guid>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4577</guid><link>http://www.openlinksw.com:443/blog/kidehen@openlinksw.com/blog/?id=1388#4577</link><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dave@dajobe.org</dc:creator><pubDate>Mon, 23 Jun 2008 06:00:23 GMT</pubDate><description>Your first link to http://blogs.usnet.private:8893/weblog/kidehen@openlinksw.com/127/?id=13781 is broken/not public.&amp;nbsp; Ironic in a post about URLs&lt;br&gt;&lt;br /&gt;

</description></item>
</channel>
</rss>
