Skip to toolbar

Community & Business Groups



The purpose of the CV 2.0 – Global Resume Community Group is to move the current textual and graphical resumes to a well-formed and accessible resume format that supports applicants as well as recruiters.

Scope of Work

Group participants should have an understanding of one or more of the following:

  • recruiting process
  • technologies and markup languages
    • CSS
    • HTML
    • SVG
    • WCAG (Accessibility)
  • interaction/graphic design
  • marketing
  • user experience research


Global Resume Specification

The specification includes a best practice recommendation and a clear syntax for a new resume format based on the skills and technologies mentioned above.

Community Group Reports that are not Specifications

The group may produce other Community Group Reports within the scope of this charter that are not specifications, such as use cases, templates, design recommendations, style guides, APIs, etc.


All software, if any, developed by this group is Open Source and subject to the MIT license.


Although this group’s work is independent, we will incorporate information from existing specifications where applicable. The following groups’ efforts are a guideline for our work:


Incorporating some of the syntax of these specifications allows for easier import and extensions in the future.

Contribution Mechanics

Contributions can only be made by Community Group Participants (so all contributors have agreed to the CLA). Particular care must be taken by Chairs and Editors to ensure contributions of content that is implementable come from Community Group Participants.

How to make a Contribution

Community Group Participants agree that all technical contributions will be documented in pull requests and commits in the group’s GitHub repository or on the mailing list, if the contribution was not documented on GitHub.

If you are not the sole contributor to a contribution, please identify all contributors in the commit message or e-mail.


The group will conduct all of its technical work in public via the group’s public mailing list and GitHub. Any contributions made are therefore visible and documented.

Meetings may be restricted to group participants, but a public summary will be posted to the group’s public mailing list.

Decision Process

This group will seek consensus decisions. After public discussion and due to consideration of different opinions, the Chair will record a decision and any objections.

If no consensus can be reached, a 2/3 majority vote is needed, otherwise the decision topic will be postponed consecutively every 7 days until consensus or 2/3 majority are reached or until the topic becomes obsolete.

Call for Consensus

A common way to determine consensus for important decisions is to conduct a Call for Consensus where the Chair puts a proposal to the group on the public mail list and asks for feedback from the Participants within some period of time that is at least 7 days. Silence implies consent. Direct feedback is encouraged, especially to weigh the degree of consensus when there is dissent.


Votes are public and any decision needs 2/3 of voting participants to come into effect. Voting lasts for 14 days or until all Participants have voted.

Decisions at Meetings (F2F, telcon)

When the group reaches a decision at a meeting, the decision is tentative. Any group participant may object to a decision reached at a meeting within 7 days of publication of the decision on the mailing list. That decision must then be confirmed on the mailing list.

Community and Business Group Process

Terms in this charter that conflict with those of the Community and Business Group Process are void.

No Comments |