rel-tag-issues

relTag Issues

These are externally raised issues about rel-tag with broadly varying degrees of merit. Thus some issues are REJECTED for a number of obvious reasons (but still documented here in case they are re-raised), and others contain longer discussions. Some issues may be ACCEPTED and perhaps cause changes or improved explanations in the spec. Submitted issues may (and probably will) be edited and rewritten for better terseness, clarity, calmness, rationality, and as neutral a point of view as possible. Write your issues well. — Tantek

Issues

Please use this format:

• YYYY-MM-DD raised by AUTHORNAME
  1. Issue 1: Here is the first issue I have.
  2. Issue 2: Here is the second issue I have.

• 2005-06-21 raised by Hixie
  1. Issue H-1: This specification is lacking a user agent conformance section. Does the UA simply crawl the DOM looking for all <html:a> elements with a "rel" attribute that contains a "tag" keyword (after space-separated splitting) and then grab the href="" value? How about relative links? Must they implement xml:base? <html:base>? Other things?
  2. Issue H-2: What's the point? Isn't free-text search more effective than relying on people to remember to put a particular tag?

• 2006-01-10 raised by Adam Willard
  1. Issue 1: Somewhat confused. Please either fix or elaborate the difference in the URLs in the Tag Spaces area -> is it /tag/ or /tags/ or /wiki/. Is this URI changeable or is this just showing other implementations. If this is the case I am confused on the implementation. Should /wiki/ only show tagged content of wiki? Should URIs be constructed as /definition/ /blog/ etc... to return those items? Or is it just returning pages and the webmaster just decided on /wiki/ or /tag/ or /applicationdir/?
     • ACCEPTED FAQ - We need to make this an FAQ entry. --RyanKing 14:46, 25 Jan 2006 (PST) (@TODO)
  2. Issue 2: More information on actually implementing a tag space would be helpful. I wrote a tagging system on our intranet and we run IIS. So I had to install URLrewrite (ISAPI) to create the URI /tag/tagname. We horrible Microsoft people are't as lucky to have Mod Rewrite.
     • REJECTED IRRELEVANT - Implementing a tagspace is well outside the bounds of the rel-tag specification. --RyanKing 14:46, 25 Jan 2006 (PST)

• 2006-02-09 raised by JonathanFeinberg
  1. Issue 1: It's bizarre to have the tag be denoted by the URL. The content of the a tag is a perfectly suitable place to contain the tag.
  2. Issue 2: There's no way to distinguish between an individual user's notion of a tag and a global tag (i.e., Fred's java tag versus all things tagged with java.
  3. Issue 3: It's not reasonable to restrict the host's REST implementation according to this spec's rather limited idea of a "good" tag URL. The idea of tags as query parameters is rejected without justification, for example. Query parameters are a perfectly legitimate means of denoting state.