hcard-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(→‎2009: Implied "n" Optimization)
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(7 intermediate revisions by 3 users not shown)
Line 1: Line 1:
<entry-title> hCard issues </entry-title>
{{DISPLAYTITLE: hCard issues }}
__TOC__
 
These are externally raised issues about [[hcard|hCard]] 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.  
These are externally raised issues about [[hcard|hCard]] 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.  


Line 19: Line 19:


===2010===
===2010===
 
* none.
<div class="hentry">
===2011===
{{OpenIssue}} <span class="entry-summary author vcard"><span class="published">2010-02-03</span> raised by <span class="fn">[http://foolip.org/ Philip Jägenstedt]</span></span>
* none currently.
<div class="entry-content discussion issues">
* <strong class="entry-title">Implied "n" Optimization</strong>. The [[hcard#Implied_.22n.22_Optimization|hCard spec]] and the derived [http://www.whatwg.org/specs/web-apps/current-work/multipage/microdata.html#conversion-to-vcard microdata vCard spec] has some magic intended to derive N from FN when it is not given explicitly, as N is required by the vCard spec. The guessing employed will fail for at least Vietnamese names (e.g. Phương Thanh => N:Thanh;Phương;;;), Chinese names (e.g. 冯小刚 => N:;冯小刚;; and Feng Xiaogang => N:Xiaogang;Feng;;;) and Japanese/Korean names for the same reasons. The problem is both that family-name and given-name are reversed and that Chinese is written without space, so the whole name is interpreted as family name. If the only issue is that N is mandatory, simply outputting N:;;;; seems the safest. Although it's technically possible to add markup to avoid the guessing, that's not going to be an option when microdata/microformats are used in a template and the user isn't asked for both the full name and all of its components. This issue was previously raised on [http://microformats.org/discuss/mail/microformats-discuss/2010-February/013187.html microformats-discuss].
</div>
</div>


== template ==
== template ==

Latest revision as of 16:26, 18 July 2020


These are externally raised issues about hCard 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.

IMPORTANT: Please read the hCard FAQ and the hCard resolved issues before giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.

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

For matters relating to the vCard specification itself, see vcard-errata and vcard-suggestions.

closed issues

See: hcard-issues-closed

resolved issues

See: hcard-issues-resolved

issues

Please add new issues to the bottom of the list by copy and pasting the template. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

2010

  • none.

2011

  • none currently.

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>

related pages

The hCard 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.