<?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: There&#8217;s Not Yet Enough Backbone</title>
	<atom:link href="http://www.mkbergman.com/367/theres-not-yet-enough-backbone/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mkbergman.com/367/theres-not-yet-enough-backbone/</link>
	<description>Mike Bergman on the semantic Web and structured Web</description>
	<lastBuildDate>Mon, 06 Feb 2012 00:15:33 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Seeking a Semantic Web Sweet Spot &#187; AI3:::Adaptive Information</title>
		<link>http://www.mkbergman.com/367/theres-not-yet-enough-backbone/comment-page-1/#comment-78540</link>
		<dc:creator>Seeking a Semantic Web Sweet Spot &#187; AI3:::Adaptive Information</dc:creator>
		<pubDate>Mon, 21 Feb 2011 08:31:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=367#comment-78540</guid>
		<description>[...]  [...]</description>
		<content:encoded><![CDATA[<p>[...]  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Where are the Road Signs for the Structured Web? &#187; AI3:::Adaptive Information</title>
		<link>http://www.mkbergman.com/367/theres-not-yet-enough-backbone/comment-page-1/#comment-45150</link>
		<dc:creator>Where are the Road Signs for the Structured Web? &#187; AI3:::Adaptive Information</dc:creator>
		<pubDate>Tue, 29 May 2007 22:19:37 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=367#comment-45150</guid>
		<description>[...] As I discussed in an earlier posting, there&apos;s not yet enough backbone to the structured Web. I believe this structure should firstly be built around a lightweight subject- or topic-oriented reference layer. [...]</description>
		<content:encoded><![CDATA[<p>[...] As I discussed in an earlier posting, there&apos;s not yet enough backbone to the structured Web. I believe this structure should firstly be built around a lightweight subject- or topic-oriented reference layer. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike</title>
		<link>http://www.mkbergman.com/367/theres-not-yet-enough-backbone/comment-page-1/#comment-44958</link>
		<dc:creator>Mike</dc:creator>
		<pubDate>Wed, 02 May 2007 19:10:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=367#comment-44958</guid>
		<description>Hi Sherman,

I&#039;m glad you like the vertebrae analogy.  In some subsequent pieces I&#039;m working on I extend the analogy to also relate to how other specific domains -- the many other body parts in the organism -- also tie into (&quot;hang off of&quot;) this backbone structure.  What I&#039;m really thinking about is a simple, &lt;strong&gt;lightweight binding structure&lt;/strong&gt; to which any and all third-party ontologies and structures can reference in relation to their &lt;strong&gt;subject coverage&lt;/strong&gt;.  This would greatly aid such things as guiding queries to SPARQL endpoints, collaborative P2P frameworks such as DBin, prompting vocabularies and structures for newly developed ontologies, etc.

I also totally concur with your views on context.  But even in the case of an ambiguous term such as &quot;driver&quot;, an appropriate subject structure could have many placements related to golf, printers, automobilies. screws, NASCAR, whatever.  In fact, such structure itself helps guide the context by virtue of which branches in the subject tree are of primary interest (i.e., enables disambiguation).  (I&#039;m also not ignoring relatedness, one reason why I like SKOS as reference schema.)

I&#039;d be curious to know how we could direct the NLP tool you have written, Cypher, to Wikipedia, Cyc, and WordNet to make this happen.  Interested?

Mike</description>
		<content:encoded><![CDATA[<p>Hi Sherman,</p>
<p>I&#8217;m glad you like the vertebrae analogy.  In some subsequent pieces I&#8217;m working on I extend the analogy to also relate to how other specific domains &#8212; the many other body parts in the organism &#8212; also tie into (&#8220;hang off of&#8221;) this backbone structure.  What I&#8217;m really thinking about is a simple, <strong>lightweight binding structure</strong> to which any and all third-party ontologies and structures can reference in relation to their <strong>subject coverage</strong>.  This would greatly aid such things as guiding queries to SPARQL endpoints, collaborative P2P frameworks such as DBin, prompting vocabularies and structures for newly developed ontologies, etc.</p>
<p>I also totally concur with your views on context.  But even in the case of an ambiguous term such as &#8220;driver&#8221;, an appropriate subject structure could have many placements related to golf, printers, automobilies. screws, NASCAR, whatever.  In fact, such structure itself helps guide the context by virtue of which branches in the subject tree are of primary interest (i.e., enables disambiguation).  (I&#8217;m also not ignoring relatedness, one reason why I like SKOS as reference schema.)</p>
<p>I&#8217;d be curious to know how we could direct the NLP tool you have written, Cypher, to Wikipedia, Cyc, and WordNet to make this happen.  Interested?</p>
<p>Mike</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sherman Monroe</title>
		<link>http://www.mkbergman.com/367/theres-not-yet-enough-backbone/comment-page-1/#comment-44957</link>
		<dc:creator>Sherman Monroe</dc:creator>
		<pubDate>Wed, 02 May 2007 17:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.mkbergman.com/?p=367#comment-44957</guid>
		<description>I really like the use of a vertbrae analogy, because if you think about a backbone, each disc is seperately very ridge and provides alot of strength, but the loose links between the discs is what gives the backbone its flexibility. Likewise, the ultimate solution will need to provide a lot of (formal) structure and consistency, but be flexible enough to encompass all the different ways people will use and apply knowledge in the Semweb. Open collaboration of ontology development, e.g. a &lt;em&gt;Wikitology&lt;/em&gt;, is one way to bring ontologies out of the silos and vacuums in which they are currently being created. Wikipedia is an example that such an approach can provide the consensus and the mass needed, both in bredth, and dept of this backbone. I also think one thing missing from your analysis is context. Take your Automobile example. In some contexts and for some users, for instance a user looking up an automobile&#039;s history, a nameplate would be a &quot;natural&quot; property of a car, and the interface should mold around that and other properties. But for other contexts and users, for example a metal scrap yard owner looking up vehicles in his inventory, other &quot;views&quot; of car are more appropriate (weight for example). So the backbone (e.g. wikitology) will need to account for this kind of context, allowing and allow users to switch from one context to another as they transverse the data in this structured web.</description>
		<content:encoded><![CDATA[<p>I really like the use of a vertbrae analogy, because if you think about a backbone, each disc is seperately very ridge and provides alot of strength, but the loose links between the discs is what gives the backbone its flexibility. Likewise, the ultimate solution will need to provide a lot of (formal) structure and consistency, but be flexible enough to encompass all the different ways people will use and apply knowledge in the Semweb. Open collaboration of ontology development, e.g. a <em>Wikitology</em>, is one way to bring ontologies out of the silos and vacuums in which they are currently being created. Wikipedia is an example that such an approach can provide the consensus and the mass needed, both in bredth, and dept of this backbone. I also think one thing missing from your analysis is context. Take your Automobile example. In some contexts and for some users, for instance a user looking up an automobile&#8217;s history, a nameplate would be a &#8220;natural&#8221; property of a car, and the interface should mold around that and other properties. But for other contexts and users, for example a metal scrap yard owner looking up vehicles in his inventory, other &#8220;views&#8221; of car are more appropriate (weight for example). So the backbone (e.g. wikitology) will need to account for this kind of context, allowing and allow users to switch from one context to another as they transverse the data in this structured web.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

