rel-tag-spaces dilemma
Since I started using the Operator Firefox extension a couple of week ago, I’ve found it to be a useful tool – to quickly access microformatted content; such as Contact details and Tagspaces.
Whilst I was testing it out on ReadySteadyBook, I noticed that the only tagspace was “Blog.aspx“, which seemed a bit weird. When I found the same problem on other websites, such as Amazon (example here) where the tagspace was “ref=tag_dpp_cust_itdp_t“. I thought this was a bug, so I raised a ticket on Bugzilla.
… however, I was wrong! Michael Kaply (the Operator developer) pointed me towards the Tagspaces spec.
It seems that for a rel-tag to be recognised as a tagspace it needs to have a specific URI structure:
Tags are embedded in HTTP URIs in a well-defined manner so that the tag embedded in an HTTP URI can be mechanically extracted from that URI. Specifically, the last segment of the path portion of the URI (after the final “/” character) contains the tag value. For example, the URI: http://www.example.com/tags/foo contains the tag “foo”.
This causes an issue for me. On ReadySteadyBook, the site is built using ASP.NET (1.1) on a shared web hosting environment. This means that I have no control over how the web-server (IIS) handles the page requests. For legacy reasons, IIS is configured to only map URI that have ASP.NET extensions (e.g. .aspx, .ascx, .ashx, .asmx, etc) to handled by the .NET Framework. So any “fancy permalinks” that I want to use must have one of those extensions.
At present, an example of a tagspace on ReadySteadyBook is: http://www.readysteadybook.com/Blog.aspx?tag=poetry
(The “Blog.aspx” page is quite complex, it can take all sorts of parameter to filter out it’s content – hence my reason to use the querystring)
Even if I did pretty up the URI structure to not use the querystring, at most I could get it to this: http://www.readysteadybook.com/blog/tag/poetry.aspx
Unfortunately, that still wouldn’t pass the grade with the “Masters of the Microformats”! As the tag would be defined as “poetry.aspx“, rather than “poetry“. See my dilemma?
Should I keep the rel-tag attribute on my tag links? or remove them because it conflicts with the current version of the rel-tag specification? (For other issues with the rel-tag spec, go here.)
Alternatively, I could link them to an external tagspace, such as Technorati?