hresume-cheatsheet: Difference between revisions

From Microformats Wiki
Jump to navigation Jump to search
(→‎Properties (Class Names): make it clear that the classname should be lowercase)
Line 8: Line 8:
* '''hresume''' {1}
* '''hresume''' {1}
** summary?(text).
** summary?(text).
** '''contact''' {1} ([[hcard|hCard]], with [[adr]] where possible).
** '''contact''' {1} ([[hcard|hCard]], on an <code class='element'><nowiki><address></nowiki></code> where possible).
** ''experience''* ([[hcalendar|hCalendar]] with embedded hCard).
** ''experience''* ([[hcalendar|hCalendar]] with overlapping [[hCard]]).
** ''education''* (hcalendar with embedded hCard)
** ''education''* ([[hcalendar|hCalendar]] with overlapping [[hCard]])
** ''skill''* ([[rel-tag]]).
** ''skill''* ([[rel-tag]]).
** ''affiliation''* (with [[hcard]]).
** ''affiliation''* (with [[hcard|hCard]]).
** publications? (one or more <code><nowiki><cite></nowiki></code> elements)
** publications? (one or more <code><nowiki><cite></nowiki></code> elements)



Revision as of 20:09, 14 January 2008

hResume cheatsheet

Profile

  • tbc

Properties (Class Names)

  • hresume {1}
    • summary?(text).
    • contact {1} (hCard, on an <address> where possible).
    • experience* (hCalendar with overlapping hCard).
    • education* (hCalendar with overlapping hCard)
    • skill* (rel-tag).
    • affiliation* (with hCard).
    • publications? (one or more <cite> elements)

Key

Based on Perl's standard quantifiers:

bold {1} MUST be present exactly once
italic* OPTIONAL, and MAY occur more than once
+ MUST be present, and MAY occur more than once
? OPTIONAL, but MUST NOT occur more than once
[square brackets] list of common values
(parentheses) data format
# comment
! awaiting documentation

Notes

  • The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Related pages

Research

Previously

hResume is the classic microformats predecessor for h-resume. Work on hResume is documented at the following for historical purposes. Much of the general discussion and research likely still applies.

The hResume 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.