<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>Paul Mison’s random stuff that doesn’t go elsewhere. Is it microblogging, or microactivity?

(Previously known as ‘tumblr is my sock drawer’, for reasons that are somewhat unclear.)</description><title>notes.husk.org</title><generator>Tumblr (3.0; @blech)</generator><link>http://notes.husk.org/</link><item><title>Annotations and Machines Tags</title><description>&lt;p&gt;I&amp;#8217;m at &lt;a href="http://warblecamp.org/"&gt;Warblecamp&lt;/a&gt; (unsurprisingly, they also have a &lt;a href="http://twitter.com/warblecamp"&gt;Twitter account&lt;/a&gt;), where I gave a short talk about Flickr&amp;#8217;s &lt;a href="http://www.flickr.com/groups/api/discuss/72157594497877875/"&gt;machine tags&lt;/a&gt; and possible lessons for Twitter&amp;#8217;s upcoming &lt;a href="http://groups.google.com/group/twitter-api-announce/browse_thread/thread/fa5da2608865453"&gt;annotations&lt;/a&gt; feature. You can &lt;a href="http://husk.org/talk/annotations_machine_tags.pdf"&gt;download the slides&lt;/a&gt; (6MB PDF), but they&amp;#8217;re very much from the &amp;#8220;big word / big picture&amp;#8221; school, so feel free not to bother.&lt;/p&gt;
&lt;p&gt;The idea was to breeze through Flickr&amp;#8217;s implementation of tags, machine tags, machine tag extras, and exploring hierarchies via both URLs and the API, and point out the features I liked and how, perhaps, Twitter might learn from them.&lt;/p&gt;
&lt;p&gt;The discussion afterwards was interesting. One point, which was well worth making, was that Twitter&amp;#8217;s stream of text is very different from Flickr&amp;#8217;s archive of photographs. (One more difference is that tags (and machine tags) are editable later; annotations are set in stone at post create time.) Aral Balkan suggested a registry of Twitter annotation namespaces, along the lines of his &lt;a href="http://twitterformats.org/"&gt;Twitter Formats proposal&lt;/a&gt;. Personally, I prefer the &amp;#8220;pave the cowpaths&amp;#8221; approach of discovering what&amp;#8217;s actually in use in the wild (and is also why I built the &lt;a href="http://husk.org/code/machine-tag-browser.html"&gt;machine tag browser&lt;/a&gt;). I didn&amp;#8217;t mention this at the time, but there was an attempt at a Flickr machine tags wiki, which failed, perhaps colouring my view.&lt;/p&gt;
&lt;p&gt;There was also a question about size limits for annotations (turns out it&amp;#8217;s 512 bytes) and a discussion on the more RDF-ish aspects of triple tags (and how you say what a thing is, which also touched on establishing concordances). Generally I don&amp;#8217;t get hung up on the semantics of machine tags, but I&amp;#8217;m sure there are people who do, and they might be reassured by the points (mentioned in the Twitter preview post) about the use of schemas:&lt;/p&gt;
&lt;blockquote&gt;People could add some agreed upon &amp;#8220;meta-annotation&amp;#8221; that points to something which *describes* the annotation or annotations that person is using. Think something sort of like XML DTD, though not necessarily machine readable.&lt;/blockquote&gt;
&lt;p&gt;For a few slides knocked up the evening before, I&amp;#8217;m vaguely happy with both the talk but very happy with the response and the way it&amp;#8217;s made me think more about the idea.&lt;/p&gt;</description><link>http://notes.husk.org/post/581324250</link><guid>http://notes.husk.org/post/581324250</guid><pubDate>Sat, 08 May 2010 14:43:31 +0100</pubDate><category>post</category><category>flickr</category><category>twitter</category><category>conference</category><category>talk</category><category>rdf</category><category>husk:front</category></item></channel></rss>
