Researcher Development Framework

This is a worked example of the Vitae RDF as rendered by InteropAbility, compared with a possible InLOC rendering.
In this page, the InteropAbility spec is abbreviated as "IA".

Two versions of the IA XML are given as the attached XML files

Analysis of the containing structure – the Researcher Development Framework as a whole

The RDF as a whole is a LOCstructure for InLOC, and an interopAbility element rather than an ability element for IA.

Direct properties

property value IA treatment
language would be assumed to be "en" no place given in spec
id (suggested) http://www.vitae.ac.uk/researchers/uri/vitaerdf

constructed for the purpose
abbr (suggested) "VitaeRDF" none given
title "Researcher Development Framework" same
rights http://www.vitae.ac.uk/researchers/274251/RDF-conditions-of-use.html no place given in spec
description "The Researcher Development Framework (RDF) is a major new approach to researcher development, to enhance our capacity to build the UK workforce, develop world-class researchers and build our research base.

The RDF is a professional development framework for planning, promoting and supporting the personal, professional and career development of researchers in higher education. It articulates the knowledge, behaviours and attributes of successful researchers and encourages them to realise their potential."
"The knowledge, intellectual abilities and techniques to do research." suggested
furtherInformation follow through http://www.vitae.ac.uk/researchers/430901-291181/Researcher-Development-Framework-RDF.html

This is handled differently. The interopAbility element XML tree may contain the ability elements, which then provide some kind of further information. There is no explicit place for extended information.
created   2011-05-24 (Nottingham)
modified   2011-05-24 (Nottingham)
issued 2010 2011-05-25T16:53:06 (Nottingham)
validityStart   dcterms:valid 2011-05-24 (Nottingham)
validityEnd   expiry 2015-04-04 (Nottingham)

InLOC LOCassociation instances with the whole RDF as subject

The Researcher Development Framework as a whole includes all its domains, sub-domains, descriptors and phases. In InLOC, the top level concepts are related with the LOCassociation "hasLOCpart".

type scheme.id scheme.label object.id object.label number IA treatment
by creator   http://www.vitae.ac.uk/ "VITAE"   "test test" (Pebble) "University of Nottingham" (Nott)
by publisher   http://www.crac.org.uk/ "CRAC: The Career Development Organisation"   "University of Nottingham" (Nott)
by rightsHolder "©" http://www.crac.org.uk/ "CRAC: The Career Development Organisation"   "VITAE" (Nott)
topic            
LOCrel hasLOCpart   A     hasSubAbility
LOCrel hasLOCpart   B     hasSubAbility
LOCrel hasLOCpart   C     hasSubAbility
LOCrel hasLOCpart   D     hasSubAbility

IA uses separate elements for each property containing just one text field, whereas the LOCassociation structure also allows identifiers as well as names for the agents, somewhat like the Atom person construct (which also has an e-mail element).

For IA, the Pebble representation nests each element within its parent using the relationship "hasSubAbility"; while the Nottingham representation has each ability element directly stemming from the main interopAbility element, and both reciprocal relationships "hasSubAbility" and "isSubAbilityOf" are used, with no distinction made between ability and interopAbility elements. The Framework only has the Domains as sub-abilities; the Domains have the sub-domains; and the sub-domains have the descriptors. The actual relations are equivalent in both representations: it is only the layout of the XML that is different.


Analysis of Domain B: Personal effectiveness

This is a LOCdefinition.

Direct properties

property value IA treatment
language    
id "B" "B" (Nottingham) / an opaque URI (Pebble)
title "Personal effectiveness" "Personal effectiveness"
description "This domain contains the personal qualities, career and self-management skills required to take ownership for and control of professional development." "The personal qualities and approach to be an effective researcher."
furtherInformation not needed in the context of the framework – if separate, could give the complete formatted section  
created (from container) (given by Pebble)
modified (from container) (given by Pebble)

InLOC LOCassociation instances with B as subject

type scheme.id scheme.label object.id object.label number IA treatment
LOCrel hasLOCpart   B1     hasSubAbility
LOCrel hasLOCpart   B2     hasSubAbility
LOCrel hasLOCpart   B3     hasSubAbility

Pebble give creator as text field, the same as for the Framework as a whole.


Analysis of B2 Self-management

This is a LOCdefinition.

Direct properties

property value IA treatment
language "en" (from container)
id "B2" "B-2" (Nottingham) / another opaque URI (Pebble)
title "Self-management" "Self-management"
description (none) (none: Pebble) / new XHTML "Sub-domain summary" supplied (Nottingham)
furtherInformation not needed in the context of the framework – if separate, could give the formatted section (none)
created (from container) (given by Pebble)
modified (from container) (given by Pebble)

InLOC LOCassociation instances with B2 as subject

type scheme.id scheme.label object.id object.label number IA treatment
LOCrel hasLOCpart   B     isSubAbilityOf
LOCrel hasLOCpart   B2-1     hasSubAbility
LOCrel hasLOCpart   B2-2     hasSubAbility
LOCrel hasLOCpart   B2-3     hasSubAbility

Pebble give creator as text field, the same as for B.


Analysis of B2 2 Commitment to research

This is a LOCdefinition.

Direct properties

property value IA treatment
language "en" (from container)  
id "B2-2" "B-2-2" (Nottingham) / another opaque URI (Pebble)
title "Commitment to research" "Commitment to research"
description (none) Text of all phases in plain text (Pebble) / in XHTML (Nottingham)
furtherInformation not needed in the context of the framework – if separate, could give the formatted section (none)
created (from container) (given by Pebble)
modified (from container) (given by Pebble)

InLOC LOCassociation instances with B2-2 as subject

type scheme.id scheme.label object.id object.label number IA treatment
LOCrel isLOCpartOf   B2     isSubAbilityOf
LOCrel hasDefinedLevel   B2-2_Ph1 "Phase 1" 1  
LOCrel hasDefinedLevel   B2-2_Ph2 "Phase 2" 2  
LOCrel hasDefinedLevel   B2-2_Ph3 "Phases 3 and 4" 3  
LOCrel hasDefinedLevel   B2-2_Ph5 "Phase 5" 5  

Pebble give creator as text field, the same as for B2.

Note that within "Commitment to research" Stages 3 and 4 are merged. It is not clear what the most helpful way of handling this is. However, it could be said that the descriptor belongs more to Stage 3 than Stage 4, as this is the earliest stage it is assigned to. Hence no LOC association is defined with 4 as its number.

Similar merging of stages occurs throughout the Framework.


Analysis of B2 2 Phase 2

(This layer of the model is not given separately in IA)

In InLOC terms, this is another LOCdefinition.

property value
language "en" (from container)
id "B2-2_Ph2"
title (none)
description "Evaluates and manages potential distractions. Dedicated: has purposeful and determined focus on developing own research and research credentials."
furtherInformation (none)

InLOC LOCassociation instances with B2 2 Phase 2 as subject

type scheme.id scheme label object id object label number IA treatment notes
LOCrel isDefinedLevelOf   B2-2 "Phase 2" 2    
topic              
level   "EQF" eqf#5 "EQF Competence Level 5" 5   might be helpful cross-reference

The Researcher Development Framework does not specify topics or level assignments, however it would be highly plausible to add them to this kind of definition.
The assignment to EQF level 5 is a personal estimate, not an official position.