hCard issues

(Difference between revisions)

Jump to: navigation, search
m
Current revision (04:59, 7 April 2013) (view source)
m (Reverted edits by ABIDEEN10 (Talk) to last version by Tantek)
 
(196 intermediate revisions not shown.)
Line 1: Line 1:
-
= hCard issues =
+
<entry-title> hCard issues </entry-title>
-
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-21 raised by Hixie
+
For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].
-
*# ''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?
+
-
*#*A: ACCEPTED RESOLVED.  See [[hcard-parsing]] for how hCards must be parsed.  For errors/unexpected content/missing content, please provide specific examples.
+
-
* 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
+
== closed issues ==
-
*# ''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.)?''
+
See: [[hcard-issues-closed]]
-
*#*A: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]) hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. <code>&lt;abbr title="Middle Name" class="additional-name"&gt;M&lt;/abbr&gt;</code>. Honorific Suffixes in the RFC include Jr. Esq. and other inherited suffixes, so i would just use <code>&lt;span  class="honorific-suffix"&gt;Jr.&lt;/span&gt;</code> etc.
+
-
*# ''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: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]) If you want to add a type to certain elements, including address and telephone it may be done in the following manner:
+
-
<pre><nowiki>
+
-
&lt;span class="adr"&gt;
+
-
&lt;span class="type"&gt;work&lt;/span&gt;:
+
-
...
+
-
&lt;/span&gt;
+
-
</nowiki></pre>
+
-
<pre><nowiki>
+
-
&lt;span class="tel"&gt;
+
-
&lt;span class="type"&gt;work&lt;/span&gt;:
+
-
&lt;span class="value"&gt;123.456.7890&lt;/span&gt;
+
-
&lt;/span&gt;
+
-
</nowiki></pre>
+
-
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
+
-
* 2005-07-22 raised by DanConnolly
+
== resolved issues ==
-
*# ''...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.''
+
See: [[hcard-issues-resolved]]
-
*#*A: ACCEPTED FAQ. 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> (recommended)
+
-
*#*# 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> or
+
-
*#*#* Simply have no "fn", and on the parsing side, if there is no "fn" present, but there is an "org" property, then duplicate the "org" value as "fn"
+
-
*#*The last two options are effectively the same and are both not explicit and easily confusable with a "missing data" condition.  Thus option 1 is preferred.  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>
+
-
*#*We are looking for descriptions of how other vCard supporting applications treat "company" vCards differently from "person" vCards.  Please provide descriptions here:
+
-
*#** Address Book / MacOSX.3:
+
-
*#*** Export (e.g. drag & drop to desktop, view in text editor)
+
-
*#**** Sets "FN" and "ORG" to the name of the company
+
-
*#**** Sets proprietary <code>X-ABShowAs:COMPANY</code>
+
-
*#*** Import (e.g. edit in text editor, drag & drop from desktop)
+
-
*#**** By setting "FN" and "ORG' to the same name (e.g. Banana Computers Inc.)
+
-
*#**** And removing any proprietary properties (e.g. X-ABShowAs)
+
-
*#**** Address Book user interface showed new vCard as a "company" contact rather an a person
+
-
*#** Address Book MacOSX.4:
+
-
*#*** same results as above -RyanKing
+
-
*#** The Danger Hiptop (aka T-Mobile Sidekick) addressbook:
+
-
*#*** Export (e.g. [http://lists.w3.org/Archives/Public/www-archive/2005Sep/0007.html email to a mailing list])
+
-
*#**** Sets "FN" to the empty string and puts the company name in "ORG".
+
-
*#*** Import - could not find a way to import a .vcf, by email, IM, or other means into the Sidekick.
+
-
*#** Contacts / Outlook 2003 Windows
+
-
*#*** Export (e.g. Highlight contact, File, Save As, vcard)
+
-
*#**** Sets "N" and "ORG to the name of the company
+
-
*#**** Sets "FN" to value in "File as:"
+
-
*#** Add another vCard app here.
+
-
* 2005-07-23 raised by DanConnolly
+
== issues ==
-
*# ''Are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
+
<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 issuesDuplicate issue additions will be reverted.
-
*#* A: ACCEPTED FAQ. 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"''
+
-
*#* A: ACCEPTED RESOLVED. That is from an older preliminary 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.
+
-
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the lower-case style, this is a hold-over from the original design, X2V has been updated.
+
-
*# ''..and code that supports it [data with class="Given-Name"].''
+
-
*#* A: ACCEPTED RESOLVED. 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.
+
-
*#** [http://greenbytes.de/tech/webdav/rfc2629xslt/rfc2629xslt.html rfc2629xslt.html] uses Street-Address, Family-Name, etc.
+
-
*#*** A: By [http://greenbytes.de/tech/webdav/ Julian Reschke] Fixed rfc2629.xslt (2005-10-29)
+
-
*#** [http://suda.co.uk/projects/X2V/ X2V] Version 0.5.1 2005-07-08 supports Family-Name etc.
+
-
*#*** A: By [http://suda.co.uk Brian Suda] I agree that the upper-case class names can be removed from the code, this was a hold-over and will be trimmed.
+
-
*# ''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.''
+
-
*#* A. ACCEPTED RESOLVEDThis needs to be added to the spec.  2005-11-08 Update: the way multiple values has been updated to work much better and not require ul/ol.
+
-
*# ''the [[hcard-profile]] says country-name but X2V and lots of the data I've seen says country''
+
-
*#* A. ACCEPTED RESOLVED.  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 wellPlease note which examples (URLs) are using the class name "country" and hopefully we can get them fixed.
+
-
*#** A: By [http://suda.co.uk Brian Suda] I have fixed all the references in the [[hcard-brainstorming]] page to reflect the proper country-name, X2V will support this in the next iteration when i fix several bugs at once.
+
-
* 2005-08-12 raised by [http://home.alltel.net/jackwolfgang/contact/ Jack L. Wolfgang II].  Use of mailto transport functionality for the E-Mail address field.
+
===2010===
-
*# ''As stated in the [[hcard-brainstorming]] document, mailto is abused by spammers. As a result, many organizations have moved to form-based contacts as opposed to mailto's.  According to [http://www.ietf.org/rfc/rfc2426.txt RFC 2426], Section 3.3.2, "A non-standard value can also be specified."  Does this refer to a non-standard e-mail address value or type value?''
+
* none.
-
*#* A: ACCEPTED FAQ. Type value.
+
===2011===
 +
* none currently.
-
* 2005-10-30 raised by [http://greenbytes.de/tech/webdav/ Julian Reschke].
+
== template ==
-
*# ''Several implementations'' '''(Which ones? Please provide links.)''' ''seem to assume that any class attribute that contains the substring "vcard" indeed signals the presence of vcard information. Not so: there are examples'' '''(What examples? Please provide links.)''' ''of where a token in the class attribute indeed only ''starts with'' "vcard", in which it should be ignored.  Implemenations using XPath (such as XSLT or Greasemonkey scripts) should be advised to do a <code>contains(concat(@class,' '),'vcard ')</code>.
+
{{issues-format}}
-
*#* REJECTED VAGUE. Which implementations?  And which examples?
+
-
*#*''(Note: the code <code>contains(concat(@class,' '),'vcard ')</code> is broken see [[parsing-microformats#Parsing_class_values]] for a correct example --[[User:RobertBachmann|Robert Bachmann]])''
+
-
* 2005-12-08 raised by [http://www.heatonarts.com Kenny Heaton].
+
== related pages ==
-
*# ''The specification gives no way to to declare a telephone extention, as in (800) 234-5678 ext. 101''
+
{{hcard-related-pages}}
-
*#* ACCEPTED FAQ.  What is the best way to declare a telephone extension?
+
-
 
+
-
* 2006-01-21 raised by [http://inspire.server101.com/ben/resume/ Ben Boyle].
+
-
*# ''Have run into issues trying to use definition lists with hCard, specifically around nesting requirements for tel where the DT element takes a class "type" (e.g. Telephone, Facsimile) and the DD element marks the value. It is invalid to place any other elements within a DL that wrap around the DT/DD pairs so there is no available element to assign the class "tel" to. XHTML2 proposes a DI element that will resolve this issue. I am hoping for an interim solution for those that wish to use definition lists, perhaps that "any class that would be placed on the DI parent (in XHTML2) must instead be placed on the first DT element". I realise this will cause headaches for those implementing hCard parsers. I'd also like to note this may affect other (current or future) microformats and relates to the general hassle of definition lists in current (X)HTML recommendations. For your consideration - thanks!''
+
-
 
+
-
== Template ==
+
-
 
+
-
Please use this format (copy and paste this to the end of the list to add your issues):
+
-
* YYYY-MM-DD raised by [http://yourhomepage.example.com YOURNAME].
+
-
*# ''Issue 1: Here is the first issue I have.''
+
-
*# ''Issue 2: Here is the second issue I have.''
+

Current revision


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.

Contents

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

2011

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.

hCard issues was last modified: Sunday, April 7th, 2013

Views