From Microformats Wiki
hresume-issues /
Revision as of 04:08, 21 October 2006 by Steve Ganz (talk | contribs) (→‎Issues: Adding contact info classification issue)
Jump to navigation Jump to search

hResume issues

These are externally raised issues about hResume 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. — Tantek

See related hCalendar issues. See related hCard issues.


  • open issue! 2006-10-19 raised by User:RyanKing.
    1. There's currently no way to say 'present' in hCalendar
      • Many job experience listings will include jobs that the person is presently working at. Ciaran McNulty correctly pointed out that a blank DTEND does not indicate that the event is still ongoing. We need to find an easy way to make this work in hResume.
  • open issue! 2006-10-19 raised by Steve Ganz.
    1. There's currently no way to distinguish an hCard in hResume as the author's contact info
      • In Draft, version 0.1 it is specified that a parent element of address should be used to the distinguish an hCard as the subjects contact info. This proves problematic to implement because address is an inline element and thus cannot contain block level elements. To avoid sacrificing semantic value by restricting the child elements of an hCard to inline elements, we need to settle on an alternate method to classify a subjects hCard as thier contact info.


Please use this format (copy and paste this to the end of the list to add your issues):

  • open issue! YYYY-MM-DD raised by YOURNAME.
    1. Issue 1: Here is the first issue I have.
    2. Issue 2: Here is the second issue I have.