<?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: Different World Views (TBox) for the same Structs (ABox)</title>
	<atom:link href="http://fgiasson.com/blog/index.php/2009/01/22/different-world-views-tbox-for-the-same-structs-abox/feed/" rel="self" type="application/rss+xml" />
	<link>http://fgiasson.com/blog/index.php/2009/01/22/different-world-views-tbox-for-the-same-structs-abox/</link>
	<description></description>
	<lastBuildDate>Tue, 15 May 2012 14:41:46 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Fred</title>
		<link>http://fgiasson.com/blog/index.php/2009/01/22/different-world-views-tbox-for-the-same-structs-abox/comment-page-1/#comment-242970</link>
		<dc:creator>Fred</dc:creator>
		<pubDate>Thu, 22 Jan 2009 21:58:16 +0000</pubDate>
		<guid isPermaLink="false">http://fgiasson.com/blog/?p=921#comment-242970</guid>
		<description>Hi Valentine!

Well, first the TBox defines the classes and properties (in RDF parlance) and their descriptions and relationships. So, the TBox is defined by these classes and properties descriptions. But As Mike put it: there is a problem with the semweb&#039;s &quot;ontology&quot; term since many people will describe everything in an &quot;ontology&quot;: classes, properties, and instances of classes. 

So, I do think the classes and properties belongs to the TBox and the instances of classes belongs to the ABox.

One of the point of this blog post is that we have to separate concerns between ABox and TBox. We do care about the ontologies at the level of the TBox. However we don&#039;t have to care about how the other system will think (tbox) about the data that is being exchanged (abox). So, sure that we care about the ontologies (at least I do) so that we can make some sense of data :)

Does this help?


Thanks!

Take care,


Fred</description>
		<content:encoded><![CDATA[<p>Hi Valentine!</p>
<p>Well, first the TBox defines the classes and properties (in RDF parlance) and their descriptions and relationships. So, the TBox is defined by these classes and properties descriptions. But As Mike put it: there is a problem with the semweb&#8217;s &#8220;ontology&#8221; term since many people will describe everything in an &#8220;ontology&#8221;: classes, properties, and instances of classes. </p>
<p>So, I do think the classes and properties belongs to the TBox and the instances of classes belongs to the ABox.</p>
<p>One of the point of this blog post is that we have to separate concerns between ABox and TBox. We do care about the ontologies at the level of the TBox. However we don&#8217;t have to care about how the other system will think (tbox) about the data that is being exchanged (abox). So, sure that we care about the ontologies (at least I do) so that we can make some sense of data <img src='http://fgiasson.com/blog/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Does this help?</p>
<p>Thanks!</p>
<p>Take care,</p>
<p>Fred</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Valentin</title>
		<link>http://fgiasson.com/blog/index.php/2009/01/22/different-world-views-tbox-for-the-same-structs-abox/comment-page-1/#comment-242957</link>
		<dc:creator>Valentin</dc:creator>
		<pubDate>Thu, 22 Jan 2009 20:54:51 +0000</pubDate>
		<guid isPermaLink="false">http://fgiasson.com/blog/?p=921#comment-242957</guid>
		<description>Really enjoyed reading this post - but still think you made a crucial mistake: you equalize the TBox with &#039;how [...] properties will be processed, understood and managed&#039;. But if you look at today&#039;s implementations of Semantic Technologies - how much of their behavior is really determined by the TBox? In the end - how much can you learn about Google&#039;s Social Graph implementation from the FOAF ontology?

Even more - if you argue that the common case will be that applications exchanging data do not commit to the same ontology and will interpret relations and properties differently - why then bother with ontologies at all?</description>
		<content:encoded><![CDATA[<p>Really enjoyed reading this post &#8211; but still think you made a crucial mistake: you equalize the TBox with &#8216;how [...] properties will be processed, understood and managed&#8217;. But if you look at today&#8217;s implementations of Semantic Technologies &#8211; how much of their behavior is really determined by the TBox? In the end &#8211; how much can you learn about Google&#8217;s Social Graph implementation from the FOAF ontology?</p>
<p>Even more &#8211; if you argue that the common case will be that applications exchanging data do not commit to the same ontology and will interpret relations and properties differently &#8211; why then bother with ontologies at all?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced (Requested URI is rejected)
Database Caching 8/16 queries in 0.009 seconds using disk: basic

Served from: fgiasson.com @ 2012-05-23 07:13:41 -->
