rel-tag-faq

From Microformats Wiki
Revision as of 22:30, 3 January 2007 by Tantek (talk | contribs) (fix close tag)
Jump to navigation Jump to search
The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

rel-tag frequently asked questions

This document serves to answer and discuss frequently asked questions specifically about the rel="tag" microformat. You may want to read the rel-faq first as it answers many common questions about the HTML4 “rel” and “rev” attributes, and their linktype values. If you have a new question to ask, first consider asking on the microformats-discuss list.

Q&A

  1. Where does a tagging link belong? Does the tagging link only need to appear in my Web feed (RSS / Atom)? Does the tagging link need to appear on the page where my specific blog entry lies? Does the tagging link need to appear everywhere that I can possibly imagine?
    • In short, tagging links belong in all the places and formats in which you published tagged content. The Web page is the primary location where users read content and where search engines index. Thus the Web page is a place where you should absolutely include your rel="tag" links. To tag your blog posts, put the rel="tag" links inside them, visibly. The Web feeds are simply alternate ways of publishing your blog posts, and thus should include the full content of your blog posts, rel="tag" links intact.
  2. Where shouldn't I use rel-tag?
  3. The format specifies that the tag must “come after the last / in the path”. Will something like http://example.com/index.php/TAG work? Or does it have to be a “real” directory or mod_rewrite? -- singpolyma 23:51, 24 Jan 2006 (PST)
    • The key is the URL. Whether that URL is generated from a database or a directory does not matter. The URL matters.
      • My question, however, was about whether that URL form ( http://example.com/index.php/TAG ) would be valid, since there is the dot in “index.php”.
        • Yes, the URL in the example is valid (or legal or conformant or whatever you want to call it to minimize confusion). The dot (period, full stop, U+002E) is free to appear in most places in a URL, even in the middle of a path-segment that is not the last path-segment. (The latest specification for URLs, “Uniform Resource Identifier (URI): Generic Syntax”, is RFC 3986.)
  4. I’m developing a web application which uses tagging, and so of course I want to use rel="tag". For this application, I want nice, clean URLs. I was planning to use mod_rewrite to map a clean URL onto my underlying scripts. How do I use Apache’s mod_rewrite to map http://example.org/~user/app/tag/car to http://example.org/~user/app/script.php?tag=car ?
    • One solution involves changing the script to inspect the path for the tag (via the variable “PATH_INFO”), rather than inspecting the query:
<Directory "/home/user/public_html/app/>
    RewriteEngine On
    RewriteRule ^tag/([^/]+)$ script.php/$1 [last]
</Directory>
    • For people who can edit the server’s main configuration file, the following untested configuration code may work. Corrections are welcome.
RewriteEngine On
RewriteMap tag int:escape
RewriteRule ^/~user/app/tag/([^/]+)$ /~user/app/script.php?tag=${tag:$1} [last]
    • The following configuration code, left over from a previous contribution to this document, does a poor job according to tests. The following code fails to enforce the rel="tag" rules about the tag corresponding to the last non-empty path-segment. The following code fails to transcode the tag for safe use in the URL query. Consider that a request on http://example.org/~user/app/tag/ would map internally to a request on http://example.org/~user/app/script.php?tag= . Consider that a request on http://example.org/~user/app/tag/not-a-tag/the-tag would map internally to a request on http://example.org/~user/app/script.php?tag=not-a-tag/the-tag . Consider that a request on http://example.org/~user/app/tag/the-tag/ would map internally to a request on http://example.org/~user/app/script.php?tag=the-tag/ . Consider that a request on http://example.org/~user/app/tag/attack&intent=destroy would map internally to a request on http://example.org/~user/app/script.php?tag=attack&intent=destroy .
<Directory "/home/user/public_html/app/>
    RewriteEngine On
    RewriteRule ^tag/(.*)$ script.php?tag=$1
</Directory>
  1. Does a rel tag still have meaning if the link redirects? If Apache returns a 302 status code, does the rel tag have meaning? Is there a formal rule that indexers should follow the link to the final, resolved destination? Or is there a formal rule that a rel tag should be ignored if URL of its link does not return a status code of 200?
    • ..next answer

CSS selector

  • How do you write a CSS selector for rel-tag?
    • a[rel~="tag"] { color: green }

Are tags case sensitive?

  • Are tags case sensitive. Is "Dog" the same tag as "dog" and "DOG"?
    • Awaiting answer

Multi-word tags

  • How should a multi-word tag be made? For instance, if using Wikipedia as a name space, a page about a Black Redstart (a bird) would be tagged Black_Redstart, with an underscore [1]. Is there any way of aliasing alternatives ("BlackRedstart", "Black-Redstart", etc.)? Is any particular format preferable?
    • Awaiting answer

Tags with file extensions

  • Is <a rel=tag href="http://example.com/cheese.htm">cheese</a> a valid tag, for "cheese"? Ditto .asp or .php variants? If not, why not?
    • Awaiting answer

Related pages

The rel-tag specification is a work in progress. As additional aspects are discussed, understood, and written, they will be added. These thoughts, issues, and questions are kept in separate pages.