InLOC — Application Profile of
Europass Curriculum Vitae and Language Passport
for Integrating Learning Outcomes and Competences

This draft document was prepared by the InLOC team:
Simon Grant, Mike Collett, Marc Van Coillie, Jan Górecki, Jad Najjar, Cleo Sgouropoulou, Christian M. Stracke.

2013-04-22

Contents

In this document, "Application Profile" is abbreviated to "AP".

Introduction

Application Profiles for InLOC

Application profiles ("APs") have been discussed and used for well over a decade. For example:

• the ARIADNE Web Magazine issue 25 from September 2000 has an article, "Application Profiles: Mixing and Matching Metadata Schemas"; [1]
• the Dublin Core Metadata Initiative has published "Guidelines for Dublin Core Application Profiles" in 2009; [2]
• the relevant Wikipedia article was initiated in 2006. [3]

APs for InLOC are much simpler than the more complex cases envisaged in these cited documents. APs for InLOC may include both small modifications to an existing specification, and recommendations within that specification on how to use the existing structures to refer to InLOC information, but there is no reason to change the main functional requirements of the existing specification, and this is not attempted. The purpose of APs for InLOC is simply to fulfill an extra requirement, which is to refer effectively to one or more definitions of learning outcome or competence (LOC), in a way that enables identification of and cross-reference between LOCs across different application, specifically (but not exclusively) allowing reference to InLOC-formatted information.

In the Guidelines [4] to InLOC, there is a general explanation of how Integrating InLOC can work, referring to the particular European Learner Mobility specifications of particular interest in the context of InLOC. The job of the APs for InLOC documentation here is to provide technical details of how this can be done.

There is no need for any profiling of the InLOC Information Model [5] itself, at least for InLOC to work well together with other European Learner Mobility specifications. Profiles may be desired for specific applications of InLOC, e.g. for the consistent creation of a set of competence standards by a particular authority, but this is understood as beyond the scope of the InLOC project.

Europass

The Europass initiative [6] comprises five documents, available in 26 languages. Europass is managed and presented by Cedefop. Europass helps:

• citizens communicate their skills and qualifications effectively when looking for a job or training;
• employers understand the skills and qualifications of the workforce;
• education and training authorities define and communicate the content of curricula.

"Five documents to make your skills and qualifications clearly and easily understood in Europe" is how the Europass web site presents itself.

Two of the five documents are completed by European citizens:

• the Curriculum Vitae (CV) [7] gives an overview of personal skills; and
• the Language Passport (LP) [8] provides a self-assessment of language skills using standardised levels.

In addition, the European Skills Passport (ESP) was launched together with the new CV. The ESP is an easy-to-use electronic folder to help students, workers or job-seekers build up a personal, modular inventory of personal skills and qualifications acquired throughout life. It can contain a range of documents (Language Passport, copies of degrees, attestations of employment, etc.). When attached to a Europass CV, the European Skills Passport will reinforce the CV by bringing evidence of skills and qualifications listed.

The remaining three documents are issued by national education and training authorities or institutions:

• the Europass Mobility [9] shows work and education experience in other European countries;
• the Certificate Supplement [10] gives the content of vocational qualifications; and
• the Diploma Supplement [11] details the achievements of holders of diplomas or degrees, including the subjects studied and the grades achieved.

Working closely with the European Commission and a network of National Europass Centres (NECs), Cedefop

• drafted and revises Europass documents;
• designed and maintains the multilingual web site, providing expertise on content, language processing and IT;
• supports the NECs that implement Europass at national level.

Europass and InLOC

The relationship of InLOC to four of the five Europass documents (excluding the Europass Mobility) is discussed in the Integrating InLOC section of the Guidelines. For the purposes of InLOC APs, Europass is treated as outlined in the three short subsections following.

The CV and LP

The is the topic of the main part of this present document, "InLOC — Application Profile of Europass Curriculum Vitae and Language Passport for integrating Learning Outcomes and Competences". The full AP given here shows how a Europass CV or Language Passport could refer or link to InLOC information. The proposal is in tune with the new concept of a European Skills Passport, and extends it to allow clearer, and more complete and fully functional, references to related to learning outcomes or competences described or mentioned in a CV or LP.

This AP work is based on the latest officially published XML schema from Cedefop (v3.0 RC7, dated December 2012) http://europass.cedefop.europa.eu/xml/EuropassSchema_V3.0-rc7.xsd used by their online CV/LP editor. It also takes into consideration Cedefop work in progress towards their next Europass Schema release (V3.1-rc1).

The InLOC AP, detailed below, extends the official XSD so that it can represent links to InLOC formatted LOC information effectively. The associated XSD file is available at http://purl.org/net/inloc/EuropassSchema_V3.0-InLOC-AP2.xsd.

A full example with LP and computer skills is available on the InLOC project wiki.

The Diploma Supplement

Practical implementation of the Diploma Supplement is covered by the ELMO project. Following consultation with the ELMO team, the ELMO CWA will incorporate the requirements of InLOC directly. This is highly preferable to having a separate AP for the Diploma Supplement.

Early draft InLOC project materials for the ELMO Application Profile are available.

The Certificate Supplement

In the Integrating InLOC section of the Guidelines, the general approach to this integration is explained. The technical details of one possible integration, and the reasoning about why it is not yet suitable for any standardization, is explained in the separate document, InLOC and the Europass Certificate Supplement.

Proficiency levels in the Europass LP

The foreign language skills section of the Europass CV/LP is extended in order to allow reference to a language competencies framework defined externally using InLOC, such as the CEFR. An optional URI to reference the LOCdefinition or LOCstructure is placed in a new resourceRef attribute, and an optional value/number related to its level of competency is placed in a new number attribute.

This has similarities to the Europass v3.1 drafts.

• The resourceRef is present in the draft v3.1 Europass schema, so the InLOC AP uses the same name for the attribute to be as close as possible.
• There is no equivalent of the number attribute in the Europass v3.0 or v3.1 release (together referred to as 3.x in the rest of this document). The number is an important feature of the InLOC Information Model, but this has not yet been comprehended in Europass.

The ProficiencyLevel element is already present in the Europass schema v3.x, but InLOC extends it.

Definition of the InLOC ProficiencyLevel feature

Each ProficiencyLevel element is redefined as:

• a string (as originally) with two new attributes:
  • resourceRef that indicates the URI of the related LOCdefinition or LOCstructure
  • number that indicates the level of the skill as a decimal number.

Linguistic skills example XML

Here is some example XML for linguistic skills, first following the original Europass format, then following the InLOC AP.

Example XML as for original v3.0 Europass

This first illustration of a Skills sub-tree with a ProficiencyLevel element shows the original version without any modification. The validity of this XML is unaffected by the InLOC AP.

<Skills>
    <Linguistic>
        <ForeignLanguageList>
            <ForeignLanguage>
                <Description>
                    <Code>en</Code>
                    <Label>English</Label>
                </Description>
                <ProficiencyLevel>
                    <Listening>A1</Listening>
                    <Reading>B1</Reading>
                    <SpokenInteraction>C1</SpokenInteraction>
                    <SpokenProduction>C2</SpokenProduction>
                    <Writing>B2</Writing>
                </ProficiencyLevel>
            </ForeignLanguage>
        </ForeignLanguageList>
    </Linguistic>
</Skills>

Example XML as for InLOC AP

This second illustration contains the two new InLOC attributes. A link to the full LP XML example is given in the resources section.

Here, and elsewhere below, the indentation has been modified to allow for print media.

<Skills>
    <Linguistic>
        <ForeignLanguageList>
            <ForeignLanguage>
                <Description>
                    <Code>en</Code>
                    <Label>English</Label>
                </Description>
                <ProficiencyLevel>
  <Listening resourceRef="http://example.org/cefr/cefr-listening-A1" number="10">A1</Listening>
  <Reading resourceRef="http://example.org/cefr/cefr-reading-B1" number="30">B1</Reading>
  <SpokenInteraction resourceRef="http://example.org/cefr/cefr-interaction-C1" number="50">C1</SpokenInteraction>
  <SpokenProduction resourceRef="http://example.org/cefr/cefr-production-C2" number="60">C2</SpokenProduction>
  <Writing resourceRef="http://example.org/cefr/cefr-writing-B2" number="40">B2</Writing>
                </ProficiencyLevel>
            </ForeignLanguage>
        </ForeignLanguageList>
    </Linguistic>
</Skills>

Proficiency level modifications on XML Schema

The XSD fragments below shows the related modifications on the Europass base schema in order to add resourceRef and number attributes for ProficiencyLevel for each Language skills:

ForeignLanguageSkillType

The first modification is in the type "ForeignLanguageSkillType" which contains the ProficiencyLevel element which is extended for all its sub-competencies (Listening, Reading, Writing...) . The related type "CEFLanguageLevelType" is changed to a new one "InLOCCEFLanguageLevelType" that contains the extensions.

<xsd:complexType name="ForeignLanguageSkillType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            Restricts the generic skill type by specifying the data type of the elements that describe
            the level of knowledge of the language and related linguistic diplomas and/or experiences.
        </xsd:documentation>
        <xsd:documentation>
            InLOC Application Profile modification (moving CEFLanguageLevelType to
            InLOCCEFLanguageLevelType in order to add new attributes resourceRef and number)
        </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
        <xsd:restriction base="SkillType">
            <xsd:sequence>
                <xsd:element name="Description" type="ForeignLanguageType" minOccurs="1"/>
                <xsd:element name="ProficiencyLevel" minOccurs="0">
                    <xsd:complexType>
                        <xsd:complexContent>
                            <xsd:restriction base="xsd:anyType">
                                <xsd:sequence>
<!-- Modification: type of sub-elements changed from "CEFLanguageLevelType" to "InLOCCEFLanguageLevelType" -->
                                    <xsd:element name="Listening" type="InLOCCEFLanguageLevelType" minOccurs="0"/>
                                    <xsd:element name="Reading" type="InLOCCEFLanguageLevelType" minOccurs="0"/>
                                    <xsd:element name="SpokenInteraction" type="InLOCCEFLanguageLevelType" minOccurs="0"/>
                                    <xsd:element name="SpokenProduction" type="InLOCCEFLanguageLevelType" minOccurs="0"/>
                                    <xsd:element name="Writing" type="InLOCCEFLanguageLevelType" minOccurs="0"/>
                                </xsd:sequence>
                            </xsd:restriction>
                        </xsd:complexContent>
                    </xsd:complexType>
                </xsd:element>
<!-- elements "AcquiredDuring", "VerifiedBy" and "Documentation" are unchanged, and omitted for brevity -->
            </xsd:sequence>
        </xsd:restriction>
    </xsd:complexContent>
</xsd:complexType>

InLOCCEFLanguageLevelType

The second modification introduces a new type – "InLOCCEFLanguageLevelType" – which extends the existing "CEFLanguageLevelType" with two new attributes resourceRef and number.

<!-- no change on the CEFLanguageLevelType itself, it has just been extended -->
<!-- in a new type InLOCCEFLanguageLevelType provided below -->
<xsd:simpleType name="CEFLanguageLevelType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            The CEF language level is comprised of one letter 
            (either A, B or C) and one digit (either 1 or 2).
            E.g. A1, B2, C1. The levels are defined by the 
            Common European Framework of Reference for Languages (CEFR)
        </xsd:documentation>
    </xsd:annotation>
    <xsd:restriction base="xsd:string">
        <xsd:pattern value="([A-C][12])?"/>
    </xsd:restriction>
</xsd:simpleType>


<!-- here is the new type InLOCCEFLanguageLevelType it extends CEFLanguageLevelType -->
<!-- by adding the two InLOC new attributes "resourceRef" and "number" -->
<xsd:complexType name="InLOCCEFLanguageLevelType">
    <xsd:annotation>
        <xsd:documentation>
            InLOC Application Profile type addition (add attribute resourceRef and number)
        </xsd:documentation>
    </xsd:annotation>
    <xsd:simpleContent>
        <xsd:extension base="CEFLanguageLevelType">
            <xsd:attribute name="resourceRef"  type="xsd:anyURI" use="optional"/>
            <xsd:attribute name="number"  type="xsd:decimal" use="optional"/>
        </xsd:extension>
    </xsd:simpleContent>
</xsd:complexType>

Generic skills in the Europass CV

The InLOC AP extends the Europass skills section in order to allow:

• multiple Skill sub-elements for each basic skill type (Communication, Organisation, JobRelated, Computer and Other) so that each skill could have specific content and references (attachment files to add evidence);
• a reference linking to an external competency framework, using the resourceRef attribute with a URI value;
• multiple ProficiencyLevel elements to allow links with other competency frameworks;
• with resourceRef (URI) and number (decimal) attributes for defining the level, and a string Label (called Evaluation) to detail or explain this in a human readable perspective.

Definition of the InLOC Skills feature

Each Skills sub-element that is based on "GenericSkillType" is set to multiple (unbounded in the XML schema) with :

• one additional attribute resourceRef that indicates the URI of the related LOC definition
• additional ProficiencyLevel sub-elements that could be multiple (unbounded in the XML schema)
  • supports a textual description (string)
    • using a Evaluation (string) sub-element
  • and two optional attributes:
    • resourceRef — a URI pointing to the LOC definition for the specific level
    • number — a decimal number referred to the numbers defined in the framework, giving the claimed level of the user

Generic skills example XML

The example XML given here relates to computer skills, a Europass CV "GenericSkillType".

Example XML as for original Europass

The first version shows the way in which the original XML might be represented. Note that there is only one Computer element, into which a text list must be placed.

<Skills>
    <Computer>
        <Description>
Information searching and aggregation 
Communication with skype 
Online participation with conference meeting tool 
OpenOffice, Word and Excel 
Powerpoint multimedia document creation using existing content (sound, picture, text) 
        </Description>
    </Computer>
</Skills>

Example XML as for InLOC AP

The second version follows the InLOC AP, which has been extended to allow reference to a European competency framework (eSkills). The eSkills competency framework is based on EQF European levels and so a number (level) is associated. Note how each separate skill is now represented separately, and how each skill has references into potential frameworks that define it, along with optional levels within the defining frameworks.

Again, this is similar to Europass v3.1 work in progress.

• The draft work in progress for the next Europass schema allows multiplicity of skills within each main generic skills sections (Communication, Organisational, JobRelated, Computer, Other) as well as a resourceRef attribute for each Skill and ProficiencyLevel.
• The number attribute is still missing. The Evaluation sub-element for ProficiencyLevel has no specific type associated (anyType), and the InLOC AP restricts it to be a string.

<Skills>
    <Computer>
        <Skill resourceRef="http://purl.cen.eu/ecf/E.4">
            <Description>Relationship Management</Description>
            <ProficiencyLevel resourceRef="http://purl.cen.eu/ecf/E.4_L2" number="2">
                <Evaluation>Positively interacts with clients.</Evaluation>
            </ProficiencyLevel>
        </Skill>
        <Skill resourceRef="http://purl.cen.eu/ecf/E.2">
            <Description>Project and Portfolio Management</Description>
            <ProficiencyLevel resourceRef="http://purl.cen.eu/ecf/E.2_L2" number="2">
                <Evaluation>Understands and applies the principles of project management and
                applies methodologies, tools and processes to manage simple projects.</Evaluation>
            </ProficiencyLevel>
            <ProficiencyLevel resourceRef="http://purl.cen.eu/ecf/E.2_L3" number="3">
                <Evaluation>
                Accounts for own and others activities, 
                working within the project boundary, making choices and giving instructions; 
                manages and supervises relationships within the team; 
                plans and establishes team objectives and outputs and documents results.
                </Evaluation>
            </ProficiencyLevel>
        </Skill>
    </Computer>
</Skills>

Generic skills modifications on XML Schema

The code below shows the 4 related modifications on the Europass base schema:

• GenericSkillType elements may be multiple;
• GenericSkillType elements may have multiple ProficiencyLevel sub-elements;
• GenericSkillType elements may have a resourceRef attribute;
• ProficiencyLevel elements for generic skills may have resourceRef and number attributes and Label sub-elements.

Modification 1: multiplicity of new "Skill" element within "GenericSkillType"

The main type used for generic skills, "GenericSkillType", is modified, in order to support multiplicity of sub-competency associated with its generic competency elements (Communication, Organisational, JobRelated, Computer, Other) a new sub-element Skill is introduced with unbounded multiplicity (maxOccurs = "unbounded"), which means that all these Skill elements could be present multiple times in the same generic skill element (Communication, Organisational...).

<!-- Skills -->
<xsd:complexType name="GenericSkillType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            Defines a generic skill, which is modelled with  one unstructured (free text)
            Description element. It may also accept Documentation information.
        </xsd:documentation>
        <xsd:documentation>
            InLOC Application Profile modification, introducing new element Skill with multiplicity set to unbounded
        </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:element name="Skill" minOccurs="1" maxOccurs="unbounded">
          <xsd:complexType>
            <xsd:complexContent>
              <xsd:restriction base="SkillType">
                <xsd:sequence>
                  <xsd:element name="Description" type="xsd:string" minOccurs="1"/>
                  <xsd:element name="ProficiencyLevel" type="InLOCLevelType" minOccurs="0" maxOccurs="unbounded"/>
                  <xsd:element name="Documentation" type="DocumentationType" minOccurs="0"/>
                </xsd:sequence>
              </xsd:restriction>
            </xsd:complexContent>
          </xsd:complexType>
        </xsd:element>
    </xsd:sequence>
</xsd:complexType>

For comparison, here is the original Europass version of the complexType definition.

<xsd:complexType name="GenericSkillType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            Defines a generic skill, which is modelled with one unstructured (free text)
            Description element. It may also accept Documentation information.
        </xsd:documentation>
    </xsd:annotation>
    <xsd:complexContent>
        <xsd:restriction base="SkillType">
            <xsd:sequence>
                <xsd:element name="Description" type="xsd:string" minOccurs="1"/>
                <xsd:element name="Documentation" type="DocumentationType" minOccurs="0"/>
            </xsd:sequence>
        </xsd:restriction>
    </xsd:complexContent>
</xsd:complexType>

Modifications 2 and 3: contents of "SkillType" elements

• "SkillType" elements may have multiple ProficiencyLevel sub-elements.
• "SkillType" elements may have a single resourceRef attribute.

<xsd:complexType name="SkillType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            Defines a skill. A Skill has a description and may be accompanied by suitable documentation.
            Morever a Skill may be acquired during one or more experience periods,
            and be verified by one or more certificates
        </xsd:documentation>
        <xsd:documentation>
            InLOC Application Profile modification (attribute resourceRef, unbounded ProficiencyLevel)
        </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:element name="Description" type="xsd:anyType" minOccurs="1"/>
<!-- the multiplicity of ProficiencyLevel is set to maxOccurs="unbounded" -->
<!-- which means could be present multiple times in a same parent element -->
        <xsd:element name="ProficiencyLevel" type="InLOCProficiencyLevelType" minOccurs="0" maxOccurs="unbounded"/>
<!-- other elements remain unchanged -->
        <xsd:element name="AcquiredDuring" type="ExperienceListType" minOccurs="0"/>
        <xsd:element name="VerifiedBy" type="CertificateListType" minOccurs="0"/>
        <xsd:element name="Documentation" type="DocumentationType" minOccurs="0"/>
    </xsd:sequence>
<!-- a new "resourceRef" attribute is added: -->
    <xsd:attribute name="resourceRef"  type="xsd:anyURI" use="optional"/>
</xsd:complexType>

Again, here is the original Europass version, for comparison.

<xsd:complexType name="SkillType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            Defines a skill. A Skill has a description and may be accompanied by sutiable documentation.
            Morever a Skill may be acquired during one or more experience periods,
            and be verified by one or more certificates.
        </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence>
        <xsd:element name="Description" type="xsd:anyType" minOccurs="1"/>
        <xsd:element name="ProficiencyLevel" type="xsd:anyType" minOccurs="0"/>
        <xsd:element name="AcquiredDuring" type="ExperienceListType" minOccurs="0"/>
        <xsd:element name="VerifiedBy" type="CertificateListType" minOccurs="0"/>
        <xsd:element name="Documentation" type="DocumentationType" minOccurs="0"/>
    </xsd:sequence>
</xsd:complexType>

Modification 4: ProficiencyLevel contents

For ProficiencyLevel within "Generic" skills, a new type "InLOCProficiencyLevelType" is created, in order to allow two new attributes resourceRef and number, together with an Evaluation sub-element, used as a string label.

<xsd:complexType name="InLOCProficiencyLevelType">
    <xsd:annotation>
        <xsd:documentation xml:lang="en">
            InLOC Application Profile addition
        </xsd:documentation>
    </xsd:annotation>
    <xsd:sequence minOccurs="0">
        <xsd:element name="Evaluation" type="xsd:string"></xsd:element>
    </xsd:sequence>
    <xsd:attribute name="resourceRef"  type="xsd:anyURI" use="optional"/>
    <xsd:attribute name="number"  type="xsd:decimal" use="optional"/>
</xsd:complexType>

There is no direct equivalent in the original XSD v3.0. The Evaluation element and resourceRef attribute are based on the draft v3.1 XSD as presented below.

    <xsd:complexType name="ProficiencyLevelType">
        <xsd:sequence>
            <xsd:element name="Evaluation" type="xsd:anyType" minOccurs="1"/>
        </xsd:sequence>
        <xsd:attribute name="resourceRef" type="xsd:anyURI">
            <xsd:annotation>
                <xsd:documentation xml:lang="en">
                    Describes a URI under which specific information 
                    about the proficiency level scale can be found.
                </xsd:documentation>
            </xsd:annotation>
        </xsd:attribute>
    </xsd:complexType>

Resources

Supporting this AP

The replacement EuropassSchema v3.0 AP XSD is available at http://purl.org/net/inloc/EuropassSchema_V3.0-InLOC-AP2.xsd. This XSD file itself is not substantially changed, but imports the other ones needed, including the substantially changed EuropassLearnerInformation XSD.

A full example with LP and computer skills is available on the InLOC project wiki.

Other APs

Europass is not the only interoperability specification dealing with competence-related information. InLOC has also worked on an HR-XML Application Profile.

References

The web pages for all the following references were accessed in April 2013.

• [1] Rachel Heery & Manjula Patel (2000) Application profiles: mixing and matching metadata schemas. Ariadne Web Magazine, Issue 25. Available at http://www.ariadne.ac.uk/issue25/app-profiles.
• [2] Karen Coyle & Thomas Baker (2009) Guidelines for Dublin Core Application Profiles. Dublin Core Metadata Initiative. Available at http://dublincore.org/documents/profile-guidelines/.
• [3] Wikipedia (2006--2012) Application profile. Available at http://en.wikipedia.org/wiki/Application_profile.
• [4] InLOC project (2013) InLOC — Guidelines including the integration of Learning Outcomes and Competences into existing specifications. Available from this site.
• [5] InLOC project (2013) InLOC — Information Model for Learning Outcomes and Competences. Available from this site.
• [6] Europass (2013) Web site: http://europass.cedefop.europa.eu/en/home.
  • [7] Europass (2013) Europass: Curriculum Vitae. Web pages: http://europass.cedefop.europa.eu/en/documents/curriculum-vitae.
  • [8] Europass (2013) Europass: Language Passport. Web pages: http://europass.cedefop.europa.eu/en/documents/european-skills-passport/language-passport.
  • [9] Europass (2013) Europass: Europass Mobility. Web pages: http://europass.cedefop.europa.eu/en/documents/european-skills-passport/europass-mobility.
  • [10] Europass (2013) Europass: Certificate Supplement. Web pages: http://europass.cedefop.europa.eu/en/documents/european-skills-passport/certificate-supplement.
  • [11] Europass (2013) Europass: Diploma Supplement. Web pages: http://europass.cedefop.europa.eu/en/documents/european-skills-passport/diploma-supplement.