hcard-issues: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
m (Replace <entry-title> with {{DISPLAYTITLE:}})
 
(221 intermediate revisions by 44 users not shown)
Line 1: Line 1:
= hCard issues =
{{DISPLAYTITLE: hCard issues }}


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. 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. — [http://tantek.com/log/ Tantek]
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.  


See related [[hcalendar-issues]].
'''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.


== Issues ==
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]]


* 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].
*# Handling middle names and suffixes:  How does one handle middle initials/names in the hCard format and suffixes that are not honorific suffixes (e.g. Jr., Sr., II, III, etc. as opposed to Ph.D., Esq., M.D., etc.)?
*#*A: By [http://suda.co.uk Brian Suda] hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. &lt;abbr title="Middle Name" class="additional-names"&gt;M&lt;/abbr&gt;. Honorific Suffixes in the RFC include Jr. Esq. and other inherited suffixes, so i would just use &lt;abbr title="Junior" class="honorific-suffixes"&gt;Jr.&lt;/abbr&gt;
*# Handling different types of addresses:  How does one handle the TYPE (e.g. postal, work, etc.) specification for addresses as specified in RFC 2426 Section 3.2.1?
*#* A: By [http://suda.co.uk Brian Suda] If you want to add a type to certain elements, including address and telephone it will be done in the following manner:


&lt;span class="adr"&gt;
== closed issues ==
&lt;span class="work"&gt;
See: [[hcard-issues-closed]]
...
&lt;/span&gt;
&lt;/span&gt;


&lt;span class="tel"&gt;&lt;span class="work"&gt;123.456.7890&lt;/span&gt;&lt;/span&gt;
== resolved issues ==
See: [[hcard-issues-resolved]]


the TYPE needs to be a sub-element of the property (adr, tel, etc) NOTE: EMAIL does NOT have many TYPE attributes, only INTERNET and X400
== 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.


* 2005-06-21 raised by Hixie
===2010===
*# ''Issue H-1: This specification is lacking a user agent conformance section. There's basically nothing that says how hCards must be parsed, how to handle errors, and so forth. Is it defined in terms of the DOM? Is it defined in terms of a serialisation? How do you handle unexpected content or missing content?
* none.
===2011===
* none currently.


== template ==
{{issues-format}}


* 2005-07-22 raised by DanConnolly
== related pages ==
*# ''in my cellphone/sidekick address book, I have a number of entries for companies. I wrote [http://dev.w3.org/cvsweb/2001/palmagent/asHCard.xsl asHCard.xsl] to convert the data from RDF to hCard, but I don't know what to do with entries for companies, since FN is mandatory in hCard.''
{{hcard-related-pages}}
*#*A: This should be an FAQ.  "How do I write an hCard for a company?"  The vCard specification is silent on this point (entries for companies).  Thus there are two options as far as the hCard standard is concerned:
*#*# Set "fn" and "org" to the same value.  E.g. <code>&lt;span class="fn org"&gt;W3C&lt;/span&gt;</code>
*#*# Set "org" as usual, and set "fn" explicitly to empty. E.g. <code>&lt;span class="fn"&gt;&lt;/span&gt;&lt;span class="org"&gt;W3C&lt;/span&gt;</code>
*#*For converting applications (hCard to vCard), they ''may'' consider using proprietary extensions to make the distinction explicit in generated vCards, based on either case 1 or 2 above.  E.g. Apple's Address Book application supports the property: <code>X-ABShowAs:COMPANY</code>
 
* 2005-07-23 raised by DanConnolly
*# ''are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
*#* Class names are case sensitive per the HTML4 specification.  Hence hCard explicitly specifies the case of class name to use for source schema names that are case-insensitive.
*# ''...but I find example data with class="Given-Name"''
*#* That is from an older version of the hCard spec which used mixed case class names.  Such class names are no longer valid hCard.  Please note which examples (URLs) are using the older class names and hopefully we can get them fixed.
*# ''..and code that supports it [data with class="Given-Name"].''
*#* Any code supporting the older class name(s) is for backward compatibility only, and should be phased out.  Any new hCard code SHOULD NOT support such mixed case class names.
*# ''The ul/ol stuff for multiple values of a property seems to be in the X2V code and in [[hcard-brainstorming]] but not in the [[hcard]] spec.''
*#* ACCEPTED.  This needs to be added to the spec.
*# the [[hcard-profile]] says country-name but X2V and lots of the data I've seen says country
*#* RFC 2426 clearly says "country name" in both the prose and the grammar, thus "country-name" is the correct class name to use.  If X2V uses just "country", it needs to be fixed to use "country-name", and any such examples as well.  Please note which examples (URLs) are using the class name "country" and hopefully we can get them fixed.
 
== Template ==
 
Please use this format:
* YYYY-MM-DD raised by AUTHORNAME
*# ''Issue 1: Here is the first issue I have.''
*# ''Issue 2: Here is the second issue I have.''

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.