rel-tag-feedback
rel-tag feedback
This document is for keeping track of feedback about rel-tag, one of several microformats.
Template
Consider using this format (copy and paste this to the end of the list to add your issues; replace ~~~ with an external link if preferred) to report issues or feedback, so that issues can show up in hAtom subscriptions of this issues page. If open issues lack this markup, please add it.
Please post one issue per entry, to make them easier to manage. Avoid combining multiple issues into single reports, as this can confuse or muddle feedback, and puts a burden of separating the discrete issues onto someone else who 1. may not have the time, and 2. may not understand the issue in the same way as the original reporter.
<div class="hentry">
{{OpenIssue}}
<span class="entry-summary author vcard">
<span class="published">2011-MM-DD</span>
raised by <span class="fn">~~~</span>
</span>
<div class="entry-content discussion issues">
* <strong class="entry-title">«Short title of issue»</strong>. «Description of Issue»
** Follow-up comment #1
** Follow-up comment #2
</div>
</div>
Feedback
General Questions
See the rel-tag FAQ and rel FAQ.
Issues
See rel-tag-issues.
General Comments
- Mary Hodder's published usability study with bloggers regarding tags Her conclusion: Bloggers asked for better tagging options and more licensing options.
- The heavy reliance on IMO poorly-conceived URL structures as "de facto best practice" means that some people who wish to provide a "tag here!" indicator in their markup can't play in your sandbox. A better solution would either take the content of the a tag as the tag, or would permit some sort of pattern-matching specification to point consumers of your tag to the "tag" portion of the URL. See rel-tag-issues. JonathanFeinberg 11:37, 9 Feb 2006 (PST)
- I agree with the above. I'd like to implement this tagging microformat, but am unable to because my URL's don't match the restrictions. This doesn't seem to be in the spirit of microformats either, which states that they "intend to solve simpler problems first by adapting to current behaviors and usage patterns". Better to me would be to use the class attribute to tell the browser it is a tag link and the rel attribute to specify the name of the tag, ie
class="tag" rel"xxx"PeterDaams 16:01, 18 Jan 2007 (EST)relis not available for tags; suppose an author wanted to tag a page with "bookmark", "next" "glossary", etc? Andy Mabbett 03:27, 18 Jan 2007 (PST)
- I agree with the above. I'd like to implement this tagging microformat, but am unable to because my URL's don't match the restrictions. This doesn't seem to be in the spirit of microformats either, which states that they "intend to solve simpler problems first by adapting to current behaviors and usage patterns". Better to me would be to use the class attribute to tell the browser it is a tag link and the rel attribute to specify the name of the tag, ie
- I can see value in using page anchors in the url, href="/mytags/automotive#hybrid". The label/tag differentiation seems to go against the folksonomy ethos of tagging. It is however interesting to know from which tag economy or tag scheme it came from. Taylor
UIDs
UIDs can be used as tags. For example, LSIDs for living organisms; for example the URL:
(An LSID for the Yellow-necked Spurfowl (Pternistis leucoscepus)), could be marked-up using "rel-tag" so that people could tag pages (in blogs, for example) or pictures (on, say, Flickr) of the organism concerned with a tag of:
thereby adding discoverability, without reducing or changing any of the current uses of LSIDs.
Related pages
- rel-tag
- rel-tag-faq
- See also rel-faq
- rel-tag advocacy - encourage others to use rel-tag.
- rel-tag-spaces - sites suitable as using as targets for rel-tag links.
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.
- rel-tag-feedback - general feedback (as opposed to specific issues).
- rel-tag-issues - specific issues with the specification.
- rel-tag-other-evidence - tagging schemas other than those used in rel-tag