hcard-issues-closed: Difference between revisions

From Microformats Wiki
hcard-issues-closed
Jump to navigation Jump to search
(: closed 2 more 2005 issues.)
(: partially accepted a previously rejected issue, resolved with adding to an FAQ entry, added more concrete reasons to reject the rest of the issue)
Line 97: Line 97:
=== closed 2006 ===
=== closed 2006 ===
Closed issues that were raised in 2006.
Closed issues that were raised in 2006.
* ...
 
* 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!''
*#* ACCEPTED PARTIAL FAQ. An example has been added for how to use a semantic DL to markup a microformat such as hCard to the [[faq#Q._Why_do_the_examples_on_the_wiki_use_.3Cspan.3E_and_.3Cdiv.3E_for_nearly_everything.3F|faq:Why do the examples use span and div]].
*#* REJECTED LACK OF REAL WORLD EXAMPLES. No URLs have been provided that publish the specific "Telephone"/"Facsimile" in DT mark up pattern mentioned in the issue.
*#* REJECTED WORKAROUND AVAILABLE.
*#*# Consider using the [[value-class-pattern]] inside the <code>&lt;dd class="tel"&gt;</code>, e.g. <code>&lt;span class="type"&gt;&lt;span class="value-title" title="fax"&gt; &lt;/span&gt;&lt;/span&gt;</code>
*#*# Don't use definition lists in this manner. The description of a definition should go completely in the DD element, and thus you should be able to put the class on that. 
*#*# Use separate DLs in the cases where you would otherwise have needed a DI element.
*#* REJECTED XHTML2 ABANDONED. The W3C is abandoning XHTML2 as of 2009-12, thus there is no need to plan for a DI element.


=== closed 2007 ===
=== closed 2007 ===

Revision as of 17:03, 17 October 2009

<entry-title>hCard closed issues</entry-title>

closed issues

hCard 1.0 closed issues that have no further actions to take..

closed 2005

Closed issues that were raised in 2005.

  • 2005-06-30 raised by Jack L. Wolfgang II. Please feel free to move these to the FAQs if they are better suited there.
    1. 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. hCard is based of the RFC2426 spec. I you want to use a middle initial it can be expanded using the abbr element. <abbr title="[MiddleName]" class="additional-name">M</abbr>. Honorific Suffixes in the RFC include Jr., Esq. and other inherited suffixes, so I would just use <abbr class="honorific-suffix" title="Junior">Jr.</abbr> etc. See hCard FAQ: marking up suffixes for more details.
    2. 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. If you want to add a type to certain elements, including address and telephone it may be done in the following manner:
<span class="adr">
<span class="type">work</span>
...
</span>

See hCard FAQ: multiple addresses for detailed examples.

<span class="tel">
 <span class="type">work</span>
 <span class="value">123.555.1212</span>
<span>

See hCard authoring: phone numbers for more detailed examples.

Note: 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
    1. ...in my cellphone/sidekick address book, I have a number of entries for companies. I wrote 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. This should at least 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:
        1. Set "fn" and "org" to the same value. E.g. <span class="fn org">W3C</span> (recommended)
        2. Set "org" as usual, and set "fn" explicitly to empty. E.g. <span class="fn"></span><span class="org">W3C</span> 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: X-ABShowAs:COMPANY
      • 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 X-ABShowAs:COMPANY
          • 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) address book:
          • Export (e.g. 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.
      • RESOLVED. hCard now specifically describes organization contact info, and there is also now an FAQ regarding this: hCard FAQ:.


  • 2005-07-23 raised by DanConnolly
    1. Are class names case sensitive or not? hCard 1.0 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. FAQ added: FAQ: Are class names case sensitive.
    2. ...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. FAQ also added: hCard FAQ: Can hCards use variants of properties like Given Name
        • A: By 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.
    3. ..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.
        • rfc2629xslt.html uses Street-Address, Family-Name, etc.
        • X2V Version 0.5.1 2005-07-08 supports Family-Name etc.
          • A: By 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.
    4. 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 1.0 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.
    5. 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. FAQ also added: hCard FAQ: Can hCards use variants of properties like Given Name
        • A: By 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 Jack L. Wolfgang II. Use of mailto transport functionality for the E-Mail address field.
    1. 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 mailtos. According to 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?
  • 2005-10-30 raised by Julian Reschke.
    1. 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. Implementations using XPath (such as XSLT or Greasemonkey scripts) should be advised to do a contains(concat(@class,' '),'vcard ').
      • REJECTED VAGUE. Which implementations? And which examples?
      • (Note: the code contains(concat(@class,' '),'vcard ') above is broken see parsing-microformats for a correct example --Robert Bachmann)
      • CLOSING DUE TO INSUFFICIENT INFORMATION. No specific implementation examples have been provided that show any problems with substring matches of "vcard". Tantek 07:00, 16 October 2009 (UTC)


  • 2005-12-08 raised by Kenny Heaton.
    1. The specification gives no way to to declare a telephone extension, 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). See hCard FAQ:.

closed 2006

Closed issues that were raised in 2006.

  • 2006-01-21 raised by Ben Boyle.
    1. 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!
      • ACCEPTED PARTIAL FAQ. An example has been added for how to use a semantic DL to markup a microformat such as hCard to the faq:Why do the examples use span and div.
      • REJECTED LACK OF REAL WORLD EXAMPLES. No URLs have been provided that publish the specific "Telephone"/"Facsimile" in DT mark up pattern mentioned in the issue.
      • REJECTED WORKAROUND AVAILABLE.
        1. Consider using the Value Class Pattern inside the <dd class="tel">, e.g. <span class="type"><span class="value-title" title="fax"> </span></span>
        2. Don't use definition lists in this manner. The description of a definition should go completely in the DD element, and thus you should be able to put the class on that.
        3. Use separate DLs in the cases where you would otherwise have needed a DI element.
      • REJECTED XHTML2 ABANDONED. The W3C is abandoning XHTML2 as of 2009-12, thus there is no need to plan for a DI element.

closed 2007

Closed issues that were raised in 2007.

  • 2007-01-26 raised by JamesCraig.
    1. Proposal to use the class attribute for qname prefixed type values (and others such as dtstart values), AKA meta classes.
<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>
  • 2007-05-08 raised by Tantek as a result of a message from Andy Mabbett on microformats-new
    1. How do you distinguish a place vs. an organization hCard, both from the perspective of a publisher (author) wishing to express the particular semantic, and from the perspective of a parser (developer) wishing to discern the difference? This is different from the 2006-12-15 issue on semantic specificity because this issue is *specifically* about place vs. org, rather than conflating that with person.
    2. Note: mailing list post cited in 2006-12-15 issue is quite clear; it says "when a spider finds an hCard, it can't tell if it is a person, company, organization, or place.".
      • DUPLICATE. See 2006-12-15 issue.

closed 2008

Closed issues that were raised in 2008.

  • 2008-02-07 raised by Andy Mabbett in microformats-discuss/2008-February/011552.html
    1. "nickname" and "fn" optimization does not work for some or all names in Asian languages. See Tom Cruise on Chinese Wikipedia, where the fn and nickname are the same. This could be partly remedied by not applying such optimization when the page's (or element's) language is set to one of a set of affected languages (may also apply to other languages, such as Greek). Comment from people fluent in such languages would be welcome.
      • REJECTED DUPLICATE. This is a duplicate of issue raised 2007-03-28 by James Craig.

closed 2009

Closed issues that were raised in 2009.

  • ...

see also