Comments on: This Post Is Ambiguous http://www.semergence.com/2008/02/24/this-post-is-ambiguous/ Semantic Web, Ruby on Rails, and Massive Data Fri, 21 Nov 2008 17:02:11 +0000 http://wordpress.org/?v=2.2.3 By: Alexandre http://www.semergence.com/2008/02/24/this-post-is-ambiguous/#comment-517 Alexandre Mon, 25 Feb 2008 02:03:15 +0000 http://www.semergence.com/2008/02/24/this-post-is-ambiguous/#comment-517 In my opinion, the distinction is necessary. The Semantic Web was designed because machines really sucks in some tasks that humans do all the time. Unambigous resource identifiers are much more simple in some scenarios. If you have a URI that identifies both a person and a homepage, you can't say <strong>in the same context</strong> that you love the person, but hate his homepage. That's a huge problem. Even two very similar documents, like a homepage in HTML 4.01 and the same homepage written in XHTML 1.1 can lead to problems if you don't assign different URIs to them. You won't be able to create a statement determining that document being both XHTML and HTML, since the two DOCTYPES are incompatible. In my opinion, the distinction is necessary. The Semantic Web was designed because machines really sucks in some tasks that humans do all the time.

Unambigous resource identifiers are much more simple in some scenarios. If you have a URI that identifies both a person and a homepage, you can’t say in the same context that you love the person, but hate his homepage. That’s a huge problem.

Even two very similar documents, like a homepage in HTML 4.01 and the same homepage written in XHTML 1.1 can lead to problems if you don’t assign different URIs to them. You won’t be able to create a statement determining that document being both XHTML and HTML, since the two DOCTYPES are incompatible.

]]>