hCard issues

(Difference between revisions)

Jump to: navigation, search
(Issues: Christina Hope issue moved on top)
Current revision (04:59, 7 April 2013) (view source)
m (Reverted edits by ABIDEEN10 (Talk) to last version by Tantek)
 
(138 intermediate revisions not shown.)
Line 1: Line 1:
-
<h1> hCard issues </h1>
+
<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.  
+
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]] ''before'' giving any feedback or raising any issues as your feedback/issues may already be resolved/answered.
+
'''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. — [http://tantek.com/log/ Tantek]
+
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]].
For matters relating to the vCard specification itself, see [[vcard-errata]] and [[vcard-suggestions]].
-
See also related [[hcalendar-issues]].
+
== closed issues ==
 +
See: [[hcard-issues-closed]]
-
__TOC__
+
== resolved issues ==
 +
See: [[hcard-issues-resolved]]
-
== Issues ==
+
== 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.
-
* 2007-01-26 raised by James Craig on [[accessibility]] page.
+
===2010===
-
*# ''Localization of RFC2426 'type' values.  RFC2426 type values for adr, email, and tel were intended as machine-readable values. Used as real HTML content in the following example only works in English. The accessify forum discussion described on the [[accessibility]] page has asserted that reducing this problem to an abbr is not a valid, accessible solution.''<pre><nowiki>
+
* none.
-
<span class="tel" xml:lang="en">
+
===2011===
-
  <span class="type">Home</span> (<span class="type">pref</span>erred):
+
* none currently.
-
  <span class="value">+1.415.555.1212</span>
+
-
</span>
+
-
</nowiki></pre> ''Use the the class attribute for qname prefixed type values (and others such as dtstart values), AKA meta classes.'' <pre><nowiki>
+
-
<span xml:lang="en">
+
-
  Home (preferred): <span class="tel type:home type:pref">+1.415.555.1212</span>
+
-
</span>
+
-
<span xml:lang="es">
+
-
  Casa (preferido): <span class="tel type:home type:pref">+1.415.555.1212</span>
+
-
</span>
+
-
</nowiki></pre>
+
-
*#* REJECTED DUPLICATE ETC. Class attributes for type values [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was tried and rejected] and in addition, [[qnames-considered-harmful]].
+
 +
== template ==
 +
{{issues-format}}
-
* {{OpenIssue}} 2007-01-22 raised by [[User:Christina Hope|Christina Hope]].
+
== related pages ==
-
*# ''What is the easiest way to display an hCard all on one line with spacing.  Currently I am using this - but I know that there has to be an easier/ simpler way to do it. <br/>Examples: (1) <pre><nowiki><p>
+
-
<span class="vcard">
+
-
<span class="fn">Christina Hope</span>& nbsp;& nbsp;& nbsp;
+
-
<span class="department">Information Technology</span>& nbsp;& nbsp;& nbsp;
+
-
<span class="role">Website Coordinator</span>& nbsp;& nbsp;& nbsp;
+
-
<span display="none" class="region"></span>
+
-
<span class="tel"> x3408</span> & nbsp;& nbsp;& nbsp;
+
-
<span class="email"><a href="mailto:chope@example.com">chope@example.com</a></span>
+
-
</span></p></nowiki></pre>''
+
-
 
+
-
:: Try <pre><nowiki><p class="vcard">
+
-
<span class="fn">Christina Hope</span>
+
-
<span class="department">Information Technology</span>
+
-
<span class="role">Website Coordinator</span>
+
-
<abbr class="tel" title="+44123 456 7890 x 3408"> x3408</abbr>
+
-
<a class="email" href="mailto:chope@example.com">chope@example.com</a>
+
-
</p></nowiki></pre>
+
-
 
+
-
::Note: apply classes to existing elements; use abbr to give the phone number in full, in international format. Also, use CSS, not non- breaking spaces, for spacing.
+
-
 
+
-
::[[User:AndyMabbett|Andy Mabbett]] 08:34, 22 Jan 2007 (PST)
+
-
 
+
-
 
+
-
 
+
-
* {{OpenIssue}} 2006-12-15 raised ([http://microformats.org/discuss/mail/microformats-discuss/2006-December/007730.html on 2006-12-14, on the mailing list]) by Joe Andrieu.
+
-
*# (Paraphrased) By including organisations and places, as well as people, hCards have lost semantic specificity (see cited mailing list post for details).
+
-
 
+
-
* 2006-12-15 raised by [[User:WizardIsHungry|WizardIsHungry]]
+
-
*# ''[Moved from a user talk page] Hey, why is hiding semi-useful information using CSS bad? The Geo and Address stuff wouldn't be enough to contact me, but I would like there so bookmarklets, crawlers, greasemonkey etc can manipulate it. Is there a policy on using CSS hiding of fields? Thanks :)''
+
-
*#* I guess we can't rely that anything that consumes hCards is normalizing it to a particular format instead of just taking all the xml inside the hcard classed block and sticking it somewhere. If it does just store it as a string, then generating html from it will yield the same hidden fields. Perhaps hiding fields by applying a stylesheet to the relevant hcard styles is ok, but not hiding them using inline css styling. Feedback? --[[User:WizardIsHungry|Jon Williams]] 10:28, 22 Dec 2006 (PST)
+
-
*#* Furthermore, [[hcard-example1-steps]] shows using inline CSS to hide fields. What gives? I still think this is an open issue; particularly the distinction between external stylesheet hiding and inline rules though. --[[User:WizardIsHungry|Jon Williams]] 13:33, 5 Jan 2007 (PST)
+
-
*#* Should this be on [[microformats-issues]]? --[[User:WizardIsHungry|Jon Williams]] 13:37, 5 Jan 2007 (PST)
+
-
*#** The example you cite is the first of several steps, which refine and improve the first step's suboptimal hCard.
+
-
*#*** The question is: ''why is this considered suboptimal if it is ok to hide the entire card?'''
+
-
*#**** REJECTED CLOSED TOO THEORETICAL. It is not ok to hide the entire card. Without further concrete examples with real world URLs on the web, this issue is closed.
+
-
*#***** Here are a number of examples of hiding the entire card, taken from [[hcard-examples-in-wild]]: [http://www.meryl.net/] [http://www.fberriman.com/] [http://www.fberriman.com/] [http://www.last.fm/user/Crok/?scrobbling=t1]  -- Could someone link to where this was discussed and decided in the past, as it seems like this is being governed by fiat. Even if you don't care to have consensus, but could you at least justify this? This stonewalling is rather rude. --[[User:WizardIsHungry|Jon Williams]] 13:24, 9 Jan 2007 (PST)
+
-
*#* [[hcard-brainstorming#CSS_Styles]] explicitly permits this. I'm going with what they say.
+
-
 
+
-
* {{OpenIssue}} 2006-12-07 raised by RyanKing.
+
-
*# ''hCard org-fn matching should use organization-name, if given.''
+
-
*# originally [http://microformats.org/discuss/mail/microformats-discuss/2006-November/007337.html raised  on uf-discuss] by David Janes.
+
-
* 2006-11-24 raised by [[User:AndyMabbett|Andy Mabbett]]
+
-
*# ''A suggested work-around for the lack of a gender property is to represent gender implicitly in the honorific-prefix field, e.g. Mr. for male, and Ms. for female. This approach does has the limitation that "Mr." and "Ms." (or "Miss"/ "Mrs.") conflicts with a higher-ranking, gender-neutral honorific, such as "Dr." or "Rev." for the person, as it is unusual (and sometimes, outside the USA, invalid) to refer to someone as "Mr. Dr." or "Mrs. Rev." for example. Note also that some cultures or religions regard such titles as offensive, or at least disdain them.''
+
-
 
+
-
* 2006-11-23 raised by [[User:AndyMabbett|Andy Mabbett]]
+
-
*# ''The specification should be "stand alone", and not normally require reference to the vCard specification.''
+
-
*#*A: ACCEPTED PARTIAL.  Agreed that [[hcard|hCard]] should be usable by typical web authors without having to dig through the vCard specification.  Precise implementation of parsing etc. hCard properties however will likely require programmers to reference the specifics/grammars in the vCard specification which we will NOT replicate in the hCard specification in order to avoid inevitable introduction of errors due to duplication.  And that being said, ''informative'' explanations may be a good idea, while the vCard property/value definitions are kept as ''normative''.
+
-
*#** ''Yes; my meaning was with reference to hCard publishing, not parsing-into-vCards. [[User:AndyMabbett|Andy Mabbett]]''
+
-
*# ''The specification should state that "telephone numbers SHOULD adhere to [http://en.wikipedia.org/wiki/E.123 ITU-T Recommendation E.123]" (or perhaps "MUST").''
+
-
*#* ACCEPTED PARTIAL. This makes sense as an informative reference and a MAY, but since vCard makes no such SHOULD statement for TEL values, neither should/will hCard.  In addition, as a Wikipedia URL that is subject to drastic change, we cannot make that a normative reference.
+
-
*#** ''I take your point about Wikipedia - here's [http://www.itu.int/rec/T-REC-E.123-200102-I/en a more definitive ITU-E.123 URL]; but it's for a chargeable document. Using "SHOULD" or "MUST" in hCard will not affect compatibility with or conversion to vCard. [[User:AndyMabbett|Andy Mabbett]]''
+
-
 
+
-
* 2006-11-16 raised by [[User:AndyMabbett|Andy Mabbett]]
+
-
*# ''The "type" for "tel" lacks a "textphone" option (for the devices used by, e.g., people who are deaf or have speech difficulties. Example: [http://www.birmingham.gov.uk/contact Birmingham City Council (303 1119)].''
+
-
*#*A: REJECTED. This is a vCard issue, as the "type" taxonomy for "tel" is determined by vCard. We are not presently extending hCard beyond the properties and values in vCard.
+
-
*#** ''I'm not clear how you can "reject" a provably factual statement. What's the process of suggesting an update to vCard? [[User:AndyMabbett|Andy Mabbett]]''
+
-
*#***A: ACCEPTED PARTIAL RESOLVED. Unfortunately it is not clear what the process is for updating vCard. However, we can at least capture suggestions for improvement to vCard from this community which may be helpful once the process for updating vCard is understood.  I've created [[vcard-suggestions]] for this purpose and added this suggestion. - Tantek 
+
-
*#**** The vCard spec is updated by RFC, for example [http://www.rfc-editor.org/rfc/rfc4770.txt RFC 4770]. [[User:AndyMabbett|Andy Mabbett]] 06:22, 12 Jan 2007 (PST)
+
-
 
+
-
* 2006-10-21 raised by [[User:AndyMabbett|Andy Mabbett]]
+
-
*# ''There should be some way to say that the URL of an hCard or hCalendar event is the URL of the page itself, without having to include a redundant, and accessibility-damaging link to that page, on the page itself.''
+
-
 
+
-
* 2005-06-21 raised by Hixie
+
-
*# ''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.
+
-
*# ''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: ACCEPTED FAQ. By [http://suda.co.uk Brian Suda] (2005-11-08 updated by [http://tantek.com/log/ Tantek]; 2006-11-16 updated by [[User:AndyMabbett|Andy Mabbett]]) 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="[MiddleName]" 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;abbr class="honorific-suffix" title="Junior"&gt;Jr.&lt;/abbr&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
+
-
 
+
-
*2006-02-03 raised by Brian
+
-
*# We can use the [[geo]] microformat in [[hatom]] to represent GeoRSS element
+
-
 
+
-
* 2005-07-22 raised by DanConnolly
+
-
*# ''...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.''
+
-
*#*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
+
-
*# ''Are class names case sensitive or not? [[hcard]] says "If names in the source schema are case-insensitive, then use an all lowercase equivalent."''
+
-
*#* 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 RESOLVED. This 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 well.  Please 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.
+
-
*# ''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?''
+
-
*#* A: ACCEPTED FAQ. Type value.
+
-
 
+
-
* 2005-10-30 raised by [http://greenbytes.de/tech/webdav/ Julian Reschke].
+
-
*# ''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>.
+
-
*#* 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].
+
-
*# ''The specification gives no way to to declare a telephone extention, as in (800) 234-5678 ext. 101''
+
-
*#* ACCEPTED FAQ. What is the best way to declare a telephone extension in a "tel" property?  (also seems like it would be a vCard FAQ).
+
-
 
+
-
* 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!''
+
-
*#* REJECTED WORKAROUND AVAILABLE.  Either don't use definition lists in this manner (because  the description of a defintion should go completely in the DD element, and thus you should be able to put the class on that), or use separate DLs in the cases where you would otherwise have needed a DI element.
+
-
 
+
-
* {{OpenIssue}} 2006-01-28 raised by [http://rbach.priv.at/Microformats-IRC/2006-01-28#T075222 Tantek on #microformats]
+
-
*# ''Is hCard is really appropriate for a named phone bridge, or do we need something else for a named phone numbers that are neither people nor organizations (the current two precise semantics that can be defined by hCard).  For example see the "Zakim" hCard on http://www.w3.org/2005/12/allgroupoverview.html ''
+
-
 
+
-
* 2006-02-13 raised by [http://microformats.org/wiki/User:Eron_Wright Eron Wright]
+
-
*# ''Few systems contemplate the altitude component of a coordinate, yet it exists.  Altitude becomes important when working with 3D mapping software such as Google Earth. Indeed, the geocoding service that Google Earth uses returns a three-dimensional coordinate.  I suggest that hCard provide explicit support for altitude.''
+
-
*#* REJECTED POSTPONED. Not in vCard. There is no "altitude" component in vCard (RFC 2426), and thus (certainly for now) there won't be any in hCard.  If a new version of vCard were to come out with altitude, then we would add it to hCard.  At some point we may also consider adding explicit extensions beyond vCard, but if we were to do so, we would capture them first on the [[hcard-brainstorming]] page.
+
-
 
+
-
* 2006-02-19 raised by Miika Mäkinen.
+
-
*# ''Couldn't the types for tel numbers be specified in a class? Now, for a phone number one needs to add the type as "visible" text, which is not always preferred. For example, type "Work", many times more suitable label could be "Office" or similar and sometimes you might not want to display any type information at all.''
+
-
*#* REJECTED TRIED ALREADY.  Using class names for the "type" of a tel or adr [http://microformats.org/wiki/hcard-parsing#ISSUE_2 was attempted], and failed in many situations.  In addition, the "type" information is actual data, not just a property name, and thus deserves to be in the ''visible'' markup.  Note that you can use abbreviations, e.g. <code><nowiki><abbr class="type" title="work">W:</abbr></nowiki></code> in order to present the type in a way that may better fit in with the rest of your presentation.
+
-
 
+
-
* 2006-02-23 raised by [http://www.thefutureoftheweb.com/ Jesse Skinner] and [http://www.thefutureoftheweb.com/blog/2006/1/hcard#comment1 Ben Buchanan].
+
-
*# ''Are multiple URLs allowed? The [http://microformats.org/wiki/hcard#Property_List Property List] suggests not, whereas email and tel have multiple type/value pairs. However, the [http://microformats.org/wiki/hcard-parsing#finding_hCard_properties parsing page] suggests multiple URLs are OK. Either way, it seems clear that a type cannot be associated with a URL. So how exactly does hCard deal with multiple URLs?''
+
-
*#* RESOLVED FAQ: Multiple URLs are allowed. Some consuming agents (Apple's AddressBook.app among them) don't have an interface for producing multiple URLs, but they are still valid in vCard and therefore hCard. --[[User:RyanKing|RyanKing]] 17:58, 12 Jun 2006 (PDT)
+
-
 
+
-
* {{OpenIssue}} 2006-03-07 raised by [http://tantek.com Tantek].
+
-
*# ''Issue 1: In 99% of the cases I am finding the need to explicitly do "n" markup, the person has a three word fn which is in the form "given-name additional-name(or initial) family-name".  Should we make three word fn's into another shorthand notation to make this easier for authors?''
+
-
 
+
-
* 2006-04-06 raised by [[User:Evan|Evan]].
+
-
*# ''What is the relationship between the CATEGORY property and [[rel-tag]]? Can you add a tag to an hCard? How can you add a tag to a particular hcard on a page without tagging the other cards on a page?''
+
-
*#* ACCEPTED. Categories can optionally be represented as tags. The classname  'category' should always be used, but  rel="tag" can  optionally be used (in addition to the category classname). In the case that a rel-tag tag is used, the tag (as defined by [[rel-tag]]) is used for the category. Examples: (1) <code><nowiki><span class="category">food</span></nowiki></code> and (2) <code><nowiki><a class="category" rel="tag" href="http://example.com/food">Food!</a></nowiki></code>. --[[User:RyanKing|RyanKing]] 15:16, 13 Jun 2006 (PDT)
+
-
 
+
-
* {{OpenIssue}} 2006-04-10 raised by [[User:ScottReynen|Scott Reynen]].
+
-
*# ''When someone looks at the [[hcard]] pages, one sees no collection of real-world publishing of contact data nor discussion of the properties implied by such examples, I think it's far too easy to infer that microformats come from other formats more than actual behavior.  There's nothing on the [[process]] nor the hcard pages explaining this discrepancy.  I would argue that there should be an explanation, probably in both places.''
+
-
 
+
-
== Template ==
+
-
 
+
-
Please use this format (copy and paste this to the end of the list to add your issues):
+
-
* {{OpenIssue}} 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.''
+
-
 
+
-
Note: large blocks of italic text are inaccessible to many readers, including people with types of visual impairment, dyslexia, etc. [http://www.intranet.man.ac.uk/accessibility/Disabilities/dyslexia.html], [https://tritonlink.ucsd.edu/portal/site/tritonlink-preview/menuitem.b4448692267a11256ec5e210514b01ca?storyID=20896]. [http://accessites.org/], [http://tlt.psu.edu/suggestions/accessibility/font.html], [http://www.wd4a.co.uk/Guidelines.htm]
+
-
 
+
-
== Related Pages ==
+
{{hcard-related-pages}}
{{hcard-related-pages}}

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