<?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 for uberblic.org</title>
	<atom:link href="http://uberblic.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://uberblic.org</link>
	<description></description>
	<lastBuildDate>Tue, 20 Jul 2010 19:15:23 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>Comment on uberblic Search API &#8211; just enough semantics by Julius</title>
		<link>http://uberblic.org/2010/07/uberblic-search-api-just-enough-semantics/#comment-11</link>
		<dc:creator>Julius</dc:creator>
		<pubDate>Tue, 20 Jul 2010 19:15:23 +0000</pubDate>
		<guid isPermaLink="false">http://uberblic.org/?p=446#comment-11</guid>
		<description>Georgi, that indirect autocomplete by specifying criteria blows my mind. I tried it and it even works with partial names, like:

  starring:[Ewan] starring:[Scarlett]

Very awesome.</description>
		<content:encoded><![CDATA[<p>Georgi, that indirect autocomplete by specifying criteria blows my mind. I tried it and it even works with partial names, like:</p>
<p>  starring:[Ewan] starring:[Scarlett]</p>
<p>Very awesome.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Feedback by Bob Ferris</title>
		<link>http://uberblic.org/feedback/#comment-4</link>
		<dc:creator>Bob Ferris</dc:creator>
		<pubDate>Tue, 06 Jul 2010 17:01:56 +0000</pubDate>
		<guid isPermaLink="false">http://wordpress3.uberblic.org/#comment-4</guid>
		<description>Hi,

Congrats to your 1.0 release of Uberblic. You federated an interesting mix of web information services. However, I do not really understand, why you also follow they way of DBpedia by creating an own ontology specification as T-Box basis. Why didn&#039;t you reuse specific, more or less well established domain ontologies and additionally reinforce thereby their integration in the whole distributed database of the Linked Data project? I don&#039;t see an added value, if everyone is using his/her own ontology specification, which describes at the end the same things. I know one could still match A-Boxes. However, we also know that T-Box matching is faster than A-Box matching and if we make use of the same (domain) ontologies, then we even don&#039;t need T-Boxes matchings (or save at least many T-Box matchings). What you&#039;ve done (from my point of view), is that you&#039;ve created a nice federated knowledge base on important and well established information service - however, with an smaller reuse effect, because you used your own ontology specification, where ontology reutilization (and mapping/alignment) could be applied. 

Cheers,

Bob</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>Congrats to your 1.0 release of Uberblic. You federated an interesting mix of web information services. However, I do not really understand, why you also follow they way of DBpedia by creating an own ontology specification as T-Box basis. Why didn&#8217;t you reuse specific, more or less well established domain ontologies and additionally reinforce thereby their integration in the whole distributed database of the Linked Data project? I don&#8217;t see an added value, if everyone is using his/her own ontology specification, which describes at the end the same things. I know one could still match A-Boxes. However, we also know that T-Box matching is faster than A-Box matching and if we make use of the same (domain) ontologies, then we even don&#8217;t need T-Boxes matchings (or save at least many T-Box matchings). What you&#8217;ve done (from my point of view), is that you&#8217;ve created a nice federated knowledge base on important and well established information service &#8211; however, with an smaller reuse effect, because you used your own ontology specification, where ontology reutilization (and mapping/alignment) could be applied. </p>
<p>Cheers,</p>
<p>Bob</p>
]]></content:encoded>
	</item>
</channel>
</rss>
