<br><br><div><span class="gmail_quote">On 3/7/07, <b class="gmail_sendername">Harry Halpin</b> <<a href="mailto:hhalpin@ibiblio.org">hhalpin@ibiblio.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I'd like to draw focus onto rel-tag as a common starting place.<br><br>I might add, if we're interested in data-formats like RDF, GRDDL gives one<br>a way to bootstrap rel-tag data automatically into RDF (if we can get
<br>rel-tag to get a profile URI)..</blockquote><div><br>Could you use <br><br><code><b><a href="http://microformats.org/wiki/rel-tag-profile">http://microformats.org/wiki/rel-tag-profile</a><br><br><br></b></code></div><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Tom mentioned to me offline that there were a host of problems with<br>rel-tag. Could someone iterate through them for me?
</blockquote><div><br>yes, I'd like to hear them too<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">The main problem seems to be that there's not too much there, it's just a
<br>(a) between the page you are on and (b) the target of a link.<br><br>It's clearly missing, say, who tagged the page. However, the great thing<br>about RDF is you can just underspecify things.</blockquote><div><br>
your RDF tuple would be <br><br>[url of tagged page] <code><b><a href="http://microformats.org/wiki/rel-tag-profile">http://microformats.org/wiki/rel-tag-profile</a> <a href="http://tagspace.com/[tag]">http://tagspace.com/[tag]
</a><br>
</b></code><br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">What I'd like to do is to build a sort of "layer-cake" for tags, where at
<br>the bottom somewhere is the very basic data between between a page, a<br>tagged relationship, and it's tagged data. This could easily be put in an<br>API/RDF/XML.<br><br>Then, we can look at common services and see what else they provide, like
<br>identity of who tagged the page, time of tagging, language, etc. And then<br>add these in as "slots".<br><br>But first things first! Can we support the relationship of a tag as<br>between "one URI" and "another URI".
<br><br>Since in SemWeb world "one URI" could mean a person, then this mechanism<br>wouldn't necessarily exclude the idea of "people tagging pages" which I<br>think is much more intuitive than rel-tag's idea of "pages tagging pages".
</blockquote><div><br>no, it's pages having tags - see above. The URL defines the tag. <br> </div><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Then we can move up to deal with more complex cases like xFolk, Annotea<br>annotations, and the many issues Tom brought up in his folksonomy paper.<br></blockquote></div><br>