(part of the InLOC work)
(in alphabetical order within their groups)
|Not all of this information is complete.|
- Achievement Standards Network (has worked example ASN Alaska history B)
- Common European Framework of Reference for Languages (has worked example CEFR-SI-A1)
- Curriculum Exchange Format
- Europass CV and LP
- HR-XML Competency
- UK National Occupational Standards (has worked example CFAMLB5)
- UK Qualifications and Credit Framework
- Australian Core Skills Framework
- Certificat Informatique et Internet (C2i) (has worked example C2i.C2i2md.d6.1)
- e-Competence Framework
- e-Competence Framework for ICT Users
- French Cigref IS HR nomenclature (has worked example Cigref 1.1)
- UNESCO ICT Competency Framework for Teachers
- Vitae Researcher Development Framework (has worked example Researcher Development Framework)
- eCOTOOL and the Europass CS
- IEEE Reusable Competency Definition
- IMS RDCEO
- HR-XML PositionCompetencyModel
- Personal Achieved Learning Outcomes
But they do not need a detailed model of LOCs.
- EuroLMAI and the Europass DS
- HR-XML Candidate
- HR-XML EPMResult
- HR-XML Europass CV application profile
- Metadata for Learning Opportunities
- Schools Interoperability Framework
- IPMA Competence Baseline
- LRMI Competency
- National Curriculum - Schools England
To start off a new stakeholder or source page, you can use
- the stakeholder template page (which is empty). Copy and paste this into your new page, preferably using Wiki Markup mode.
- The Example source guidance page helps you fill in the General information
- and the Features table helps you fill in the features (also check the individual features pages).
Even as a team, without the close involvement of others we cannot ensure the uptake and adoption of our outputs. This Stakeholder Liaison plan is designed to promote the adoption of our outputs, while at the same time acting as a common thread supporting the main tasks and outputs, and reducing the chance that work is duplicated.
The Information Model encompasses the models used by, developed by, or implicit in the information of interest to, the various stakeholders, gathered through this process.
The Guidelines covers topics of importance to the stakeholders, discovered and checked by us through this liaison process.
The Application Profiles are adapted more closely than the general information model to the models relevant to the particular applications, as discovered through liaison.
The Bindings that we document as outputs are those that stakeholders tell us are actually or potentially useful.
These include: tool developers; users of the structures (EC, agencies, employers, LET and awarding bodies); groups with models (including standards bodies); bodies of content; related specifications; and technical approaches.
- S1. Compile and maintain a list of stakeholders and sources. Document organisations (but not individual contacts) on wiki.
- S2. Document information from stakeholder sources. The key information about stakeholders is what they would want or need from the InLOC model, or eventual specification, to secure their adoption of InLOC outputs; and what Guidelines documentation is needed to facilitate their use. Document on wiki.
- S3. Express relevant models. Some are implicit, and to be drawn out, ensuring they are understandable by both team and owning stakeholders. Document on wiki.
- S4. Integrate model with growing core. This involves tracking the features of the models, and ensuring that the growing core model covers all important ones.
- S5. Refer the InLOC model back to relevant stakeholders. This is essential feedback, after the interim report and CWAs have been first drafted. It is aimed to convince the stakeholders to adopt the InLOC model.
The liaison process is thus in two stages. First, the requirements are gathered and models surfaced. This will enable the team to develop a good Information Model and Guidelines that is at least reasonably fit for purpose. Second, the initial Information Model and Guidelines will be carefully checked with the most significant stakeholders, making whatever improvements are needed to ensure the eventual adoption of InLOC outputs.
Page: e-Competence Framework for ICT Users
Page: Europass CV and LP
Page: Example source guidance
Page: HR-XML Candidate
Page: HR-XML Competency
Page: HR-XML EPMResult
Page: HR-XML Europass CV application profile
Page: HR-XML PositionCompetencyModel
Page: IMS RDCEO
Page: Knowledge markets
Page: LRMI Competency
Page: Mozilla Open Badges
Page: National Curriculum - Schools England
Page: stakeholder template
Page: UK NOS
Page: UK QCF
Page: UNESCO ICT-CFT
Page: Vitae RDF