Contents |
hResume cheatsheet
hResume properties and how to use them.
Profile
- tbc
Properties (Class Names)
- hresume {1}
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
- hResume
- hResume cheatsheet - hResume properties
- hResume examples - example usage of various classes within hResume.
- hResume examples in the wild - an on-going list of websites which use hResume.
- hresume-authoring
- resume-formats
- FAQ - if you have any questions about hResume, check here.
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.
- Feedback - general feedback (as opposed to specific issues).
- Brainstorming- brainstorms and other explorations relating to hResume.
- see also Skills property brainstorming.
- see also resume-brainstorming.
- Issues - specific issues with the specification.
- Other cheatsheets: hAtom cheatsheet, hCard cheatsheet (also adr cheatsheet + geo cheatsheet), hCalendar cheatsheet, hResume cheatsheet, hReview cheatsheet, PDF cheatsheet