rel-values-issues
rel Issues
These are externally raised issues about the general use of rel 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.
Issues
Please use this format:
<div class="vevent">
* {{OpenIssue}} <span class="summary vcard"><span class="dtstart">YYYY-MM-DD</span> raised by <span class="fn">~~~</span></span>
<div class="description">
*# Here is the first issue I have.
*# Here is the second issue I have.
</div>
</div>
Open issues
- open issue! 2008-01-12 raised by Andy Mabbett
- I think there is a general issue with requiring @rels where publishers normally use text, not links; contrary to microformats are not... an attempt to get everyone to change their behavior..." and the principle "adapt to current behaviors"; I see no reason why microformats should not use both, with the same value. In other words, for some microformats (rel-tag, rel-license, etc.) <foo class="value"> would have the same effect as <a rel="value">. That would also be beneficial for Wikis such this one, where rel values cannot be used by editors.
Resolved issues
- 2007-06-06 raised by Mike Kaply
- Are the rel microformats only valid on anchor tags (<A>)?
- Yes. Other elements have no subject, for there to be a relationship with. Andy Mabbett 17:50, 11 Jan 2008 (PST)
- Are the rel microformats only valid on anchor tags (<A>)?