hcard-issues-closed: Difference between revisions

From Microformats Wiki
hcard-issues-closed
Jump to navigation Jump to search
(sections for closed issues from other years)
(closed a resolved issue by completing FAQ and authoring related tasks as part of resolution.)
Line 6: Line 6:
=== closed 2005 ===
=== closed 2005 ===
Closed issues that were raised in 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.
*# ''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. <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.  See [[hcard-faq#How_do_you_mark_up_suffixes|hCard FAQ: marking up suffixes]] for more details.
*# ''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:
<source lang=html4strict>
<span class="adr">
<span class="type">work</span>
...
</span>
</source>
See [[hcard-faq#How_do_I_markup_multiple_addresses|hCard FAQ: multiple addresses]] for detailed examples.
 
<source lang=html4strict>
<span class="tel">
<span class="type">work</span>
<span class="value">123.555.1212</span>
<span>
</source>
See [[hcard-authoring#Phone_Numbers|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


=== closed 2006 ===
=== closed 2006 ===

Revision as of 05:01, 11 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

closed 2006

Closed issues that were raised in 2006.

  • ...

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