<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Phil Dawes' Stuff - Latest Comments in Tagtriples + identity precision</title><link>http://phildawesstuff.disqus.com/</link><description></description><language>en</language><lastBuildDate>Thu, 26 Jul 2007 07:30:57 -0000</lastBuildDate><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753104</link><description>When thinking about the general direction my (rather slow moving) Semantic Tagging stuff should head into, it became obvious pretty quickly that moving from facet-value-pairs to RDF-like subject-property-object-triples is the direction of choice. Vapou…</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Like</dc:creator><pubDate>Thu, 26 Jul 2007 07:30:57 -0000</pubDate></item><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753103</link><description>I thinking about RDF and Topic Maps See also</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">虚拟主机</dc:creator><pubDate>Thu, 29 Jun 2006 03:07:48 -0000</pubDate></item><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753102</link><description>Perhaps an appropriate, and concrete subset of the SW and open systems should be outlined.  A closed system (which controls the production of identification - by URI or any alternative means- as well as content), which does *not* automatically apply entailment rules (not even the 'simple' entailment rules as defined in RDF-MT) could be such a subset.  Then finally, simplify the model to consist only of the following parts:&lt;br&gt;&lt;br&gt;Graph&lt;br&gt;Context (or collection of statements)&lt;br&gt;Statement&lt;br&gt;Identifiers (URIs)&lt;br&gt;Literals&lt;br&gt;&lt;br&gt;voila, you have RDF-Lite (clearly distinguished from the SW).  Now the syntax for repsenting such a subset would also be much simpler, but an orthogonal issue to the underlying model.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chimezie</dc:creator><pubDate>Sun, 18 Sep 2005 13:53:09 -0000</pubDate></item><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753101</link><description>"Also, why bother with the netstring numbers? - for the sake of simplicity, why not (apple,computer) or something?"&lt;br&gt;&lt;br&gt;Because articulated text is not made of sequence of byte strings, but like you understood as *sets* of text. For instance, the sentence:&lt;br&gt;&lt;br&gt;  Steve Jobs is the creator of the Apple Computer&lt;br&gt;&lt;br&gt;may be articulated (considering "the", "is" and "of" as&lt;br&gt;articulators and with CRLF added for readability) as the Public Name:&lt;br&gt;&lt;br&gt;  15:&lt;br&gt;    5:Steve,&lt;br&gt;    4:Jobs,&lt;br&gt;    ,&lt;br&gt;  19:&lt;br&gt;    5:Apple,&lt;br&gt;    8:Computer,&lt;br&gt;    ,&lt;br&gt;  7:creator,&lt;br&gt;&lt;br&gt;Sorted sequence of netstring effectively represent the three sets of text:&lt;br&gt;&lt;br&gt;  ((Steve, Jobs) creator (Apple, Computer))&lt;br&gt;&lt;br&gt;and actually preserve the semantic between those sets expressed by the original text articulation.&lt;br&gt;&lt;br&gt;Public Names have many other interesting properties: they can be used as URI, can be used to build fast indexes and can encode any 8-bit byte strings.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Laurent Szyster</dc:creator><pubDate>Fri, 16 Sep 2005 11:23:46 -0000</pubDate></item><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753100</link><description>Hi Laurent,&lt;br&gt;&lt;br&gt;I've read your pages, but I'm afraid I'm not sure if I understand what you are getting at.&lt;br&gt;&lt;br&gt;Am I correct in thinking that you want to replace a URI with a string of associated words. Systems then disambiguate the meaning via the connected set of words?&lt;br&gt;&lt;br&gt;e.g. 5:apple,8:computer ?&lt;br&gt;&lt;br&gt;Also, why bother with the netstring numbers? - for the sake of simplicity, why not (apple,computer) or something?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PhilDawes</dc:creator><pubDate>Fri, 16 Sep 2005 05:10:09 -0000</pubDate></item><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753099</link><description>URI are not appropriate for the Semantic Web, Tim Berner Lee wrote that himself back in 2001:&lt;br&gt;&lt;br&gt;  &lt;a href="http://www.w3.org/DesignIssues/HTTP-URI.html" rel="nofollow"&gt;http://www.w3.org/DesignIssues/HTTP-URI.html&lt;/a&gt;&lt;br&gt;&lt;br&gt;  section 2.5 - Extra info with URI:&lt;br&gt;&lt;br&gt;  "Effectively, the URI scheme has now failed to identify anything by itself."&lt;br&gt;&lt;br&gt;This issue and others have since then not been addressed, although context was forced in RDF store implementation and semantic patched on RDF/XML with Named Graphs.&lt;br&gt;&lt;br&gt;As a data model for the Semantic Web, RDF triple is just broken, it is too simple.&lt;br&gt;&lt;br&gt;Have a look a:&lt;br&gt;&lt;br&gt;  &lt;a href="http://laurentszyster.be/blog/public-names/" rel="nofollow"&gt;http://laurentszyster.be/blog/public-names/&lt;/a&gt;&lt;br&gt;&lt;br&gt;and&lt;br&gt;&lt;br&gt;  &lt;a href="http://laurentszyster.be/blog/public-rdf/" rel="nofollow"&gt;http://laurentszyster.be/blog/public-rdf/&lt;/a&gt;&lt;br&gt;&lt;br&gt;then tell me what you think.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Laurent Szyster</dc:creator><pubDate>Thu, 15 Sep 2005 22:22:50 -0000</pubDate></item><item><title>Re: Tagtriples + identity precision</title><link>http://www.phildawes.net/blog/2005/09/15/tagtriples-identity-precision/#comment-2753097</link><description>This description capability even allows JAM*VAT to import RDF with no loss of information (i.e. you could export it back into RDF if required). It does this by tagging each human-readable symbol with the URI used in the RDF.&lt;br&gt;&lt;br&gt;E.g. the URI:&amp;lt;http://phildawes.net/phil&amp;gt; gets translated into the symbol 'phil', and the statement:&lt;br&gt;&lt;br&gt;&lt;br&gt;phil tag &lt;a href="http://phildawes.net/phil" rel="nofollow"&gt;http://phildawes.net/phil&lt;/a&gt;&lt;br&gt;&lt;br&gt;&lt;br&gt;(This tags the symbol 'phil' with the URI). The &lt;a href="http://phildawes.textdriven.com/jamvat/" rel="nofollow"&gt;JAM*VAT&lt;/a&gt; aggregator uses the 'tag' property to help manage identity between graphs. 'Tag' in JAM*VAT fulfils a similar role to a tag in del.icio.us - i.e. another symbol that can be used to categorise the target.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">PhilDawes</dc:creator><pubDate>Thu, 15 Sep 2005 17:55:26 -0000</pubDate></item></channel></rss>