The development programme for the custom CV builder plugin follows 10 design principles: user-centric, interoperable, recognised, flexible, multi-lingual, multimedia, secure, portable, accessible and open, all described in detail here:

  1. User-centric. The CV builder employs a user-centric approach to personal data management by allowing individuals to control their personal information and digital self-representation. Individuals can decide where to store their data and have administrator rights to manage it. In this way data is not held with third-party web CV repositories or Job Board administered applications. The Europass CV Builder is fully integrated with WordPress, as a plugin application.
  2. Interoperable. CVs are compliant with the latest HR-XML Staffing Exchange Protocol specification. By using a standards compliant CV format, individuals are able to establish a fluid exchange of personal information with eRecruitment, eLearning and Human Resources bodies.
  3. Recognised. The builder produces CVs that comply with the widest European and internationally recognised standards for representation of personal data, qualifications and competencies. This allows the edition of a complete CV following the official Europass template and latest Europass XML specifications, recognised by audiences not limited by sector or geography.
  4. Flexible. The CV Builder can produce flexible and fully modifiable views of CV content. Individuals can customise their CVs and target them according to their personal or professional needs and goals. To create a targeted CV, the user selects relevant content from the Master CV (the vault for personal information) and creates a View. This can be built using out-of the box templates or by creating new templates that can be customised with the addition of extra sections and fields as required. These fields may be outside of the Europass template but present in the HR-XML specification and therefore HR-XML compatibility is maintained. Allowing user-created fields will break standards compliance but this option is being considered to enhance customisability.
  5. Multi-lingual. The entire interface is multilingual and content can be filled in by the user in any of the official languages of the European Union.
  6. Multimedia. Text fields within the CV can be linked to any media (pictures, certificate, video or audio record); these can be added as evidence of performance alongside the tagging and aggregation of content from distributed locations. Support for WordPress ‘short codes’ allows content integration within blog posts and pages, adding ePortfolio-like capabilities.
  7. Portable. Individual CVs are accessible via Internet and can be packaged, exported and moved from physical locations e.g. hosting services compliant with HR-XML specifications.  Users can also select the publishing format of their choice for each targeted CV or View, including: XHTML and HTML (integrated in blog pages), PDF, ODT, HR-XML feed and Europass XML feed.
  8. Accessible. CVs are ergonomic, usable and any user, through compliance with accessibility standards such as WAI, can readily access content.
  9. Secure. Stored personal data and CVs are secured for personal access via the WordPress authentication protocol. Individuals can set access permissions and the builder is granular enough such that portions personal data can be cordoned off. Publishing rights are available to allow both public versions of a CV for open consultation via the Internet and protected CVs held in a secure location. Each export of a targeted CV or View can be protected by an access code defined by the user.
  10. Open. The CV is open and not related to any proprietary technology. Its online forms are built using XForms.

No Comments on “Design principles for the custom CV Builder plugin for WordPress compliant with Europass and HR-XML specifications”

You can track this conversation through its atom feed.

No one has commented on this entry yet.

Leave a Reply

XHTML: You can use these tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>