hresume-issues

From Microformats Wiki
hresume-issues /
Revision as of 18:39, 23 October 2006 by Fantasai (talk | contribs) (→‎Issues: address is not an inline element)
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.

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 different hCard types in hResume
      • In Draft, version 0.1 it is specified that a parent element of address should be used to the distinguish an hCard as the subject's contact info. This proves problematic to implement because address 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 subject's hCard as thier contact info.
      • In any given experience there may be one or more hCards. One which would be the subject's hCard for that experience and the other for a supervisor or manager, etc. We need a way to distinguish different hCards in a given experience.

Template

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.