Warning, technical argot ahead.
Well, my last post, that contains tags embedded into the post body (thanks to ecto, see below), actually got folksonomified smoothly.
So I raised an eyebrow and dived into my templates, just to find out that, after converting keywords to tags in html pages, I forgot to add them to feed templates. Oh my!
That's probably why my post were not handled correctly on technorati.
I've corrected this, even if I'm now considering using domain enhanced categories, instead of or in addition to embedded links.
Nothing would change in the blog's onsite taxonomy, but the feed could benefit from this little semantic enhancement.
On the implementation side, as for RSS2, this simply means adding, for each would-be tag, a category entry within the RSS feed with an extra domain attribute pointing to either to technorati or wikipedia or any site meaningful for that item, like this:
I'll do some experiments.
On the other hand, ecto, the blog client I'm proudly using these days, now features a very comfortable way of tagging a post and even merges available tags from flickr, delicious, and technorati in a single pool. This rocks!
...and could eventually push me back to simply keep tags declaration in the post's body (as almost everyone does) and live happy with that.
Well, my last post, that contains tags embedded into the post body (thanks to ecto, see below), actually got folksonomified smoothly.So I raised an eyebrow and dived into my templates, just to find out that, after converting keywords to tags in html pages, I forgot to add them to feed templates. Oh my!
That's probably why my post were not handled correctly on technorati.
I've corrected this, even if I'm now considering using domain enhanced categories, instead of or in addition to embedded links.
Nothing would change in the blog's onsite taxonomy, but the feed could benefit from this little semantic enhancement.
On the implementation side, as for RSS2, this simply means adding, for each would-be tag, a category entry within the RSS feed with an extra domain attribute pointing to either to technorati or wikipedia or any site meaningful for that item, like this:
<category domain="http://www.technorati.com/tag">foo</category>
I'll do some experiments.
On the other hand, ecto, the blog client I'm proudly using these days, now features a very comfortable way of tagging a post and even merges available tags from flickr, delicious, and technorati in a single pool. This rocks!
...and could eventually push me back to simply keep tags declaration in the post's body (as almost everyone does) and live happy with that.
I've been meaning to get Ecto. However, since I often post at work (pc), I often resort to having to use my blog's web interface. However, at home it would be nice to use Ecto since I have a Mac.
I'm still trying to understand the tagging and how it pings technorati. Sometimes the tags embedded in my post hit technorati, and at other times it appears they do not. Are you saying Ecto resolves this?
Rob: well I don't know why is it that some posts hit technorati and others do not, and I'm actually experiencing the same problem in this very moment. I suppose TR indexing takes some time, or maybe just fails on some occasions. I'm still experimenting on this. Ecto doesn't solve the problem, it simply makes it really natural to use tags, gathering your "usual" tags not only from technorati, but also from del.icio.us and flickr!
And... well, there's also a Windows version ;)
Agylen: I've a similar problem with a wordpress blog hidden in a subdirectory of codewitch: http://www.codewitch.org/it