hcard-issues

2010-02-03T09:35:31Z

Foolip: /* 2009 */ Implied "n" Optimization

<entry-title> hCard issues </entry-title>
__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.

'''IMPORTANT''': Please read the [[hcard-faq|hCard FAQ]] and the [[hcard-issues-resolved|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. — [[User:Tantek|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 ==
<span id="Issues">Please add new issues</span> to the '''bottom''' of the list by copy and pasting the [[#template|template]]. Please follow-up to resolved/rejected issues with new information rather than resubmitting such issues. Duplicate issue additions will be reverted.

===2010===

<div class="hentry">
{{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>
<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 ==
{{issues-format}}

== related pages ==
{{hcard-related-pages}}

Microformats Wiki - User contributions [en]

hcard-issues