- Some CMSs (including vanilla MediaWiki) allow neither the use of rel or class on links.
- Possible solution - allow
class="representative vcard"or similar. Andy Mabbett 15:54, 2 Feb 2008 (PST) - ACCEPTED FAQ. Update MediaWiki install with a version that allows the use of rel or class on links or use one of the MediaWiki plugins that does so.
- Possible solution - allow
- Some CMSs (including vanilla MediaWiki) allow neither the use of rel or class on links.
representative-hcard-issues
Jump to navigation
Jump to search
Representative hCard Issues
These are externally raised issues about representative hCards 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.
open issues
Add open issues here:
- ...
resolved issues
closed issues
- Translated content. "Work" in Finnish is "Työ", "Preferred" is "suositeltava", how am I supposed to do that?
I propose following syntax, btw "content" attribute is used commonly elsewhere for this too:
<span class="tel"><span class="type" content="work">Työ</span>
(<span class="type" content="pref">suositeltava</span>):
<span class="value">+1.415.555.1212</span>
</span>
- CLOSED DUPLICATE. This is an hCard issue not a representative hCard issue, and is a duplicate of an issue raised by James Craig in 2007. The summary of the resolution is: The use of
abbrandtitleattribute to provide an alternate language representation rather than an abbreviation expansion falls outside the semantics ofabbr. The value-class-pattern has been devised as a solution to this problem, to avoid the semantic mis-use of abbr for this instance. E.g. see the first example in the value class pattern: using value-title section.
- CLOSED DUPLICATE. This is an hCard issue not a representative hCard issue, and is a duplicate of an issue raised by James Craig in 2007. The summary of the resolution is: The use of
- There are accessibility and usability issues with linking a page to itself (to be expanded). Note prior discussion at hcard-issues-resolved#resolved_2006 dated 2006-10-21
- Possible solution - allow
class="representative vcard"or similar. Andy Mabbett 15:44, 2 Feb 2008 (PST) - REJECTED THEORETICAL AND MISCONCEPTION same as resolution to the hCard issue.
- Possible solution - allow
- There are accessibility and usability issues with linking a page to itself (to be expanded). Note prior discussion at hcard-issues-resolved#resolved_2006 dated 2006-10-21
- hCards will not always include a URL (to be expanded)
- Possible solution - allow
class="representative vcard"or similar. Andy Mabbett 15:44, 2 Feb 2008 (PST) - REJECTED THEORETICAL. Links to a real world example of an hCard without a URL are required to devise an appropriate solution, otherwise solutions may be (overly) addressing a theoretical problem.
- Possible solution - allow
- hCards will not always include a URL (to be expanded)
- Not all representative hCards are about people; some are about organisations or venues, so cannot use
rel="me"(see, for example that for the BBFO, one of several on http://www.westmidlandbirdclub.com/bardsey- Possible solution - allow
class="representative vcard"or similar. Andy Mabbett 16:03, 2 Feb 2008 (PST) - REJECTED UNNECESSARY. The url=uid=source option works for representing hCards about organizations and venues.
- Possible solution - allow
- Not all representative hCards are about people; some are about organisations or venues, so cannot use
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>