Comments on: Tags and Triples http://phildawes.net/blog/2005/02/09/tags-and-triples/ Mostly programming with a few bits of other stuff Fri, 21 Nov 2008 00:17:21 +0000 http://wordpress.org/?v=2.1.1 By: Phil Dawes' Stuff » Disambiguating tags in tagtriples http://phildawes.net/blog/2005/02/09/tags-and-triples/#comment-703 Phil Dawes' Stuff » Disambiguating tags in tagtriples Tue, 30 Nov 1999 00:00:00 +0000 http://phildawes.net/blog/2005/02/09/tags-and-triples/#comment-703 [...] ting tags in tagtriples Filed under: Semantic Web — PhilDawes @ 21:01 The <a href="http://www.phildawes.net/blog/2005/02/09/tags-and-triples/">tag triples</a> idea is going quite well. Have built a simple prototype to test the idea, [...] […] ting tags in tagtriples Filed under: Semantic Web — PhilDawes @ 21:01 The tag triples idea is going quite well. Have built a simple prototype to test the idea, […]

]]> By: Phil Dawes' Stuff » TagTriples software http://phildawes.net/blog/2005/02/09/tags-and-triples/#comment-576 Phil Dawes' Stuff » TagTriples software Tue, 30 Nov 1999 00:00:00 +0000 http://phildawes.net/blog/2005/02/09/tags-and-triples/#comment-576 [...] Semantic Web Python — PhilDawes @ 19:02 Made some software to explore the <a href="http://www.phildawes.net/blog/2005/02/09/tags-and-triples/">tag-triples idea</a> a bit further. It doesnt attempt to do anything with context yet (alt [...] […] Semantic Web Python — PhilDawes @ 19:02 Made some software to explore the tag-triples idea a bit further. It doesnt attempt to do anything with context yet (alt […]

]]> By: Max Völkel http://phildawes.net/blog/2005/02/09/tags-and-triples/#comment-568 Max Völkel Fri, 11 Feb 2005 14:42:09 +0000 http://phildawes.net/blog/2005/02/09/tags-and-triples/#comment-568 I think you should internally represent each literal as a resource. It should have e (generated) unique URI, and an rdf:value of the actual literal. This way, you can (in your model) adress different numbers for example. I think you should internally represent each literal as a resource. It should have e (generated) unique URI, and an rdf:value of the actual literal. This way, you can (in your model) adress different numbers for example.

]]>