<?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"
	>
<channel>
	<title>Comments on: The (s&#124;S)emantic (w&#124;W)eb</title>
	<atom:link href="http://nicklothian.com/blog/2008/04/30/the-ssemantic-wweb/feed/" rel="self" type="application/rss+xml" />
	<link>http://nicklothian.com/blog/2008/04/30/the-ssemantic-wweb/</link>
	<description>My Blog, Take 4</description>
	<pubDate>Tue, 06 Jan 2009 21:39:11 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.5</generator>
		<item>
		<title>By: Sergey Mikhanov</title>
		<link>http://nicklothian.com/blog/2008/04/30/the-ssemantic-wweb/#comment-492</link>
		<dc:creator>Sergey Mikhanov</dc:creator>
		<pubDate>Mon, 20 Oct 2008 15:26:47 +0000</pubDate>
		<guid isPermaLink="false">http://nicklothian.com/blog/?p=317#comment-492</guid>
		<description>By lowercasing the Semantic Web you are taking the semantics out of it: what Google search engine is doing does not have anything to do with the real semantics of the data under analysis. It is (as well as Bayesian filtering you're putting close to it) a mere statistical analysis of the text, with regard to the internal markup structure behind the HTML, and the external structure of the web pages graph made of web pages and connected with links.

I bet you knew this already, but still.

Important thing about the semantic web being lowercased, is that there were two groups of people dealing with it: W3C comittee members, and a mere web developers.

First were saying: "HTML does not contain any semantic structure in it, only the markup, so let's create a parallel universe, where the real semantic structure for every web site is encoded in the corresponding RDF".

Second answered: "It is only part of the truth, that HTML does not contain any semantic structure; indeed it was developed with the structure in mind, while the CSS was responsible for how things looked."

The meaning here is that when a mere web developer uses ul/li tags combination this is almost always a list. And when you have a CSS class with name 'address' assigned to it, the list is almost always intended to represent an address. So, on one hand you may define the CSS version of the 'address' class to render HTML representation of address as you pleased, and on another you may extract (tada!) semantics from the ul/li combination (namely, the value of someone's address). This is what microformats (or lowercased semantic web, but NOT the Google's search) are all about.

The Semantic Web is a thing that got too much publicity. Along with semantic nets, frame hierarchies, and description logics, it tried to deal with the problem of knowledge representation and processing. (Up to date) it was unable to solve any major real-world problem, but it's OK for ongoing research initiative! As well as it is OK for a simple technical solution to the complex problem to work almost always (I am talking about semantic web/microformats now).</description>
		<content:encoded><![CDATA[<p>By lowercasing the Semantic Web you are taking the semantics out of it: what Google search engine is doing does not have anything to do with the real semantics of the data under analysis. It is (as well as Bayesian filtering you&#8217;re putting close to it) a mere statistical analysis of the text, with regard to the internal markup structure behind the HTML, and the external structure of the web pages graph made of web pages and connected with links.</p>
<p>I bet you knew this already, but still.</p>
<p>Important thing about the semantic web being lowercased, is that there were two groups of people dealing with it: W3C comittee members, and a mere web developers.</p>
<p>First were saying: &#8220;HTML does not contain any semantic structure in it, only the markup, so let&#8217;s create a parallel universe, where the real semantic structure for every web site is encoded in the corresponding RDF&#8221;.</p>
<p>Second answered: &#8220;It is only part of the truth, that HTML does not contain any semantic structure; indeed it was developed with the structure in mind, while the CSS was responsible for how things looked.&#8221;</p>
<p>The meaning here is that when a mere web developer uses ul/li tags combination this is almost always a list. And when you have a CSS class with name &#8216;address&#8217; assigned to it, the list is almost always intended to represent an address. So, on one hand you may define the CSS version of the &#8216;address&#8217; class to render HTML representation of address as you pleased, and on another you may extract (tada!) semantics from the ul/li combination (namely, the value of someone&#8217;s address). This is what microformats (or lowercased semantic web, but NOT the Google&#8217;s search) are all about.</p>
<p>The Semantic Web is a thing that got too much publicity. Along with semantic nets, frame hierarchies, and description logics, it tried to deal with the problem of knowledge representation and processing. (Up to date) it was unable to solve any major real-world problem, but it&#8217;s OK for ongoing research initiative! As well as it is OK for a simple technical solution to the complex problem to work almost always (I am talking about semantic web/microformats now).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.957 seconds -->
