The current plan is not to present this separately for CWA, but to rely on the ELMO CWA to include the proposals made here.

Application Profile of ELMO for InLOC information

(See also the relevant section of Integrating InLOC in InLOC's Guidelines)

MLO section of ELMO

New learningOutcome element to reference LOC Definition or LOCStructure

This new element has been called learningOutcome (following the XCRI UK standard), and is based on that work.

It allows reference to a LOCdefinition or LOCstructure using:

  • a URI to a LOCdefinition (may be multiple)
  • a URI to a LOCstructure (should be single only)

and supports a textual description with the attribute xml:lang that indicates the language used.

Definition of the learningOutcome element

learningOutcome is a child of either the learningOpportunitySpecification element or (exceptionally) the learningOpportunityInstance element. It is optional and could be multiple (unbounded in the xml schema). It is defined as:

  • a string
    with two attributes:
    • xml:lang that indicates the language of the string
    • href that indicates the URI of the related LOCdefinition or LOCstructure

Note that this may follow BS 8581 with the attribute name "href". Alternatively, href could be substituted with "locref", which would bring consistency with internal InLOC attributes, and also because the contents of "locref" may be a URI that is not of an information resource.

XML Example

Example of the proposed learningOutcome element
		<learningOpportunitySpecification>
			<description/>
			<title xml:lang="no">Ph.d</title>
			<title xml:lang="en">PhD</title>
			<type>Degree</type>
			<url/>
			<qualification>
				<identifier type="fs">PHD</identifier>
				<identifier type="nus">801199</identifier>
				<identifier type="subjectArea">11.3</identifier>
				<title xml:lang="no">Philosophiae Doctor</title>
				<title xml:lang="en">Doctor of Philosophy</title>
				<educationLevel xml:lang="no">Doktorgrad, tidsnormert</educationLevel>
				<educationLevel xml:lang="en">Doctoral degree with normal length of study</educationLevel>
				<qualificationHolderTitle>PHILOSOPHIAE DOCTOR</qualificationHolderTitle>
				<qualificationMainStudyField/>
			</qualification>
			<credit>
				<scheme>ECTS</scheme>
				<value>180</value>
			</credit>
<!-- here is the overall learning outcome, referring to an imagined InLOC LOC structure  -->
			<learningOutcome xml:lang="en" href="http://www.vitae.ac.uk/uri/rdf">
(here would be a description of the Researcher Development Framework.
The actual Framework documentation is at http://www.vitae.ac.uk/researchers/428241/Researcher-Development-Framework
but we imagine here that they also have a more persistent URI standing for the Framework as a Semantic Web concept,
which could be the base for identifiers within it.)</learningOutcome>
<!-- end of the overall learning outcome -->
			<specifies>
                                 <!-- ............. -->
                        </specifies>
		</learningOpportunitySpecification>

Related modifications on XML Schemas to support the feature

Related modifications on the XML Schemas elmo_MLO.xsd and types.xsd in order to allow a new multiple learningOutcome element within the parent learningOpportunitySpecification element:

Modification on XML schema elmo_MLO.xsd (addition of a new multiple learningOutcome element)
	<xs:complexType name="LearningOpportunitySpecification">
		<xs:complexContent>
			<xs:extension base="LearningOpportunityObject">
				<xs:sequence>
					<xs:element name="qualification" type="Qualification" minOccurs="0" maxOccurs="1"/>
					<xs:element name="credit" type="Credit" minOccurs="0" maxOccurs="unbounded"/>
					<xs:element name="level" type="SimpleLiteral" minOccurs="0" maxOccurs="unbounded"/>
<!------------------------------------------------------------------------------------------------------------------------------------>
					<!-- InLOC addition, related type define in types.xsd -->
					<xs:element name="learningOutcome" type="InLOCLearningOutcome" minOccurs="0" maxOccurs="unbounded"/>
<!------------------------------------------------------------------------------------------------------------------------------------>
					<xs:element name="specifies" type="Specifies" minOccurs="1" maxOccurs="unbounded"/>
					<xs:element name="hasPart" type="LearningOpportunitySpecificationAssociation" minOccurs="0" maxOccurs="unbounded"/>
					<xs:element name="objective" type="Description" minOccurs="0" maxOccurs="unbounded"/>
					<xs:element name="prerequisite" type="Description" minOccurs="0" maxOccurs="unbounded"/>
				</xs:sequence>
			</xs:extension>
		</xs:complexContent>
	</xs:complexType>
Modification on XML schema types.xsd (addition of a new type for the new learningOutcome element)
<!------------------------------------------------------------------------------------------------------------------------------------>
        <!-- InLOC addition, related element learningOutcome define in elmo_MLO.xsd -->
	<xs:complexType name="InLOCLearningOutcome">
		<xs:simpleContent>
			<xs:extension base="xs:string">
				<xs:attribute ref="xml:lang"/>
				<xs:attribute name="href" type="xs:anyURI" use="optional" />
			</xs:extension>
		</xs:simpleContent>
	</xs:complexType>
<!------------------------------------------------------------------------------------------------------------------------------------>

Result distribution category referencing InLOC level definition

This has been proposed by the ELMO team. The idea is to add an extra explanatory element to a Learning Opportunity Instance, to give context to someone's result. It includes a list of category which describes the distribution of the result.

Definition of the InLOC feature

The category element is a child of a resultDistribution, is optional and may be multiple (unbounded in the xml schema). The current ELMO definition uses two attributes:

  • label which tells what the category is
  • count that indicates the number of people concerned for each category within the resultDistribution.

InLOC proposes a third attribute for category:

  • locref indicates the URI of the related LOC definition, which is a level in a LOC structure.

XML Example

Example of the modified resultDistribution element
	<learningOpportunityInstance>
		<start>2009 Vår</start>
		<duration>1 semester</duration>
		<result scheme="http://www.uio.no/locrefs/NO30" number="60">B</result>
		<gradingScheme xml:lang="no"/>
<!-- resultDistribution not in the original example, imagined here -->
<!-- locref attributes are added to the category elements -->
		<resultDistribution>
			<category locref="http://www.uio.no/locrefs/NO30/A" label="A" count="10"/>
			<category locref="http://www.uio.no/locrefs/NO30/B" label="B" count="30"/>
			<category locref="http://www.uio.no/locrefs/NO30/C" label="C" count="60"/>
			<category locref="http://www.uio.no/locrefs/NO30/D" label="D" count="30"/>
			<category locref="http://www.uio.no/locrefs/NO30/E" label="E" count="10"/>
		</resultDistribution>
	</learningOpportunityInstance>

Related modification on the XML Schema to support the feature

Related modification on the XML Schema elmo_result.xsd to add a number attribute to the result element and a locref attribute to the category element:

Modification on XML schema elmo_result.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"
	targetNamespace="http://purl.org/net/elmo"
	xmlns="http://purl.org/net/elmo"
	elementFormDefault="qualified">

	<xs:include schemaLocation="types-InLOC-AP1.xsd"/>

    <!-- Defined as a separate type to allow extension -->
	<xs:complexType name="Result">
		<xs:simpleContent>
			<xs:extension base="SimpleLiteral">
				<xs:attribute name="scheme" use="optional"/>
				<!-- level related to LOC definition level -->
				<xs:attribute name="number"  type="xs:decimal" use="optional"/>
			</xs:extension>
		</xs:simpleContent>
	</xs:complexType>

	<xs:complexType name="ResultDistribution">
	   <xs:sequence>
	       <xs:element name="category" type="Section"  minOccurs="0" maxOccurs="unbounded"/>
	       <xs:element name="description" type="Description" minOccurs="0" maxOccurs="1"/>
	   </xs:sequence>
	</xs:complexType>


	<!-- potential to add in a link here to LOC info for an interval -->
	<xs:complexType name="Section">
<!------------------------------------------------------------------------------------------------------------------------------------>
		<xs:attribute name="locref"  type="xs:anyURI" use="optional"/> <!-- here is the link to the LOC info -->
<!------------------------------------------------------------------------------------------------------------------------------------>
		<xs:attribute name="label" use="required"/>
	        <xs:attribute name="count" use="required"/>
	</xs:complexType>
</xs:schema>

EuroLMAI: Europass DS and transcripts section of ELMO

The "result" element

The ELMO team have proposed extending the result element, currently just text, with a scheme attribute.

InLOC proposes to use this scheme attribute for the URI of the appropriate LOCdefinition and introduce a number attribute for the related user's level.

Definition of InLOC result feature

The result element is a child of a learningOpportunityInstance, is optional and could be multiple (unbounded in the xml schema), it is define using two attributes:

  • scheme that could indicates the URI of the related LOCdefinition or LOCstructure
  • number (decimal type) which gives the level of the user

XML Example

Example of the modified result element
						<learningOpportunityInstance>
							<start>2009 Vår</start>
							<duration>1 semester</duration>
<!-- 2012-12-04 imagine that uio.no keeps a proper catalogue of result scheme URIs - also added an InLOC number attribute -->
<!-- 2012-12-04 NO30 has been replaced throughout by the corresponding invented URI  -->
							<result scheme="http://www.uio.no/locrefs/NO30" number="60">B</result>
						</learningOpportunityInstance>

Related modification on the XML Schema to support the feature

Related modification on the XML Schema elmo_result.xsd to add a number attribute in the result element:

Modification on XML schema elmo_result.xsd
<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
	xmlns:xml="http://www.w3.org/XML/1998/namespace"
	targetNamespace="http://purl.org/net/elmo"
	xmlns="http://purl.org/net/elmo"
	elementFormDefault="qualified">

	<xs:include schemaLocation="types-InLOC-AP1.xsd"/>

    <!-- Defined as a separate type to allow extension -->
	<xs:complexType name="Result">
		<xs:simpleContent>
			<xs:extension base="SimpleLiteral">
				<xs:attribute name="scheme" use="optional"/>
<!------------------------------------------------------------------------------------------------------------------------------------>
				<!-- level related to LOC definition level -->
				<xs:attribute name="number"  type="xs:decimal" use="optional"/>
<!------------------------------------------------------------------------------------------------------------------------------------>
			</xs:extension>
		</xs:simpleContent>
	</xs:complexType>

	<xs:complexType name="ResultDistribution">
	   <xs:sequence>
	       <xs:element name="category" type="Section"  minOccurs="0" maxOccurs="unbounded"/>
	       <xs:element name="description" type="Description" minOccurs="0" maxOccurs="1"/>
	   </xs:sequence>
	</xs:complexType>


	<!-- potential to add in a link here to LOC info for an interval -->
	<xs:complexType name="Section">
		<xs:attribute name="locref"  type="xs:anyURI" use="optional"/> <!-- here is the link to the LOC info -->
		<xs:attribute name="label" use="required"/>
	        <xs:attribute name="count" use="required"/>
	</xs:complexType>
</xs:schema>

Overall XML Example

Example including all modifications
<?xml version="1.0" encoding="UTF-8"?>
<!-- 2012-12-04 Simon Grant added possible InLOC information and references, with some ideas from the Vitae RDF -->
<elmo xmlns="http://purl.org/net/elmo" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
	<report>
		<learner>
			<identifier type="nationalIdentifier">30535890168</identifier>
			<identifier type="studentIdentifier">531</identifier>
			<fullName>Test Testesen</fullName>
			<givenNames>Test</givenNames>
			<familyName>Testesen</familyName>
			<bday dtf="yyyy-MM-dd">1958-03-30</bday>
		</learner>
		<issuer>
			<identifier type="fs">219</identifier>
			<identifier type="database">FSSBKURS</identifier>
			<title xml:lang="no">Universitetet i Oslo</title>
			<title xml:lang="en">University of Oslo</title>
			<type>University receiving state support</type>
			<url>http://www.uio.no/</url>
		</issuer>
		<learningOpportunitySpecification>
			<description/>
			<title xml:lang="no">Ph.d</title>
			<title xml:lang="en">PhD</title>
			<type>Degree</type>
			<url/>
			<qualification>
				<identifier type="fs">PHD</identifier>
				<identifier type="nus">801199</identifier>
				<identifier type="subjectArea">11.3</identifier>
				<title xml:lang="no">Philosophiae Doctor</title>
				<title xml:lang="en">Doctor of Philosophy</title>
				<educationLevel xml:lang="no">Doktorgrad, tidsnormert</educationLevel>
				<educationLevel xml:lang="en">Doctoral degree with normal length of study</educationLevel>
				<qualificationHolderTitle>PHILOSOPHIAE DOCTOR</qualificationHolderTitle>
				<qualificationMainStudyField/>
			</qualification>
			<credit>
				<scheme>ECTS</scheme>
				<value>180</value>
			</credit>
<!-- 2012-12-04 added an overall learning outcome framework here, close to BS 8581, the UK's MLO compatible version of XCRI -->
			<learningOutcome xml:lang="en" href="http://www.vitae.ac.uk/uri/rdf">
(here would be a description of the Researcher Development Framework.
The actual Framework documentation is at http://www.vitae.ac.uk/researchers/428241/Researcher-Development-Framework
but we imagine here that they also have a more persistent URI standing for the Framework as a Semantic Web concept,
which could be the base for identifiers within it.)</learningOutcome>

<!-- 2012-12-04 end of whole degree learning outcome framework -->
			<specifies>
				<learningOpportunityInstance>
					<date dtf="yyyy-MM-dd">2010-11-28</date>
					<start>2007</start>
					<duration interval="unknown">0</duration>
					<languageOfInstruction xml:lang="no">Engelsk</languageOfInstruction>
					<languageOfInstruction xml:lang="en">English</languageOfInstruction>
				</learningOpportunityInstance>
			</specifies>
			<hasPart>
				<learningOpportunitySpecification>
					<description/>
					<identifier type="fs">VITTEORI1</identifier>
					<subject xml:lang="no">Vitenskapsteori</subject>
					<subject xml:lang="en">Scientific theory</subject>
					<title xml:lang="no">Vitenskapsteori</title>
					<title xml:lang="en">Scientific theory</title>
					<type>Module</type>
					<url/>
					<qualification>
						<educationLevel xml:lang="no">Doktorgrads nivå</educationLevel>
						<educationLevel xml:lang="en">Doctoral degree level</educationLevel>
					</qualification>
					<credit>
						<scheme>ECTS</scheme>
						<value>15</value>
					</credit>
<!-- 2012-12-04 including a learning outcome here -->
					<learningOutcome xml:lang="en" href="http://www.vitae.ac.uk/uri/rdf/A1.1">Subject knowledge</learningOutcome>
<!-- 2012-12-06 end of this learning outcome example - - this is single, but could be multiple -->
					<specifies>
						<learningOpportunityInstance>
							<start>2009 Vår</start>
							<duration>1 semester</duration>
<!-- 2012-12-04 imagine that uio.no keeps a proper catalogue of result scheme URIs - also added an InLOC number attribute -->
<!-- 2012-12-04 NO30 has been replaced throughout by the corresponding invented URI  -->
							<result scheme="http://www.uio.no/locrefs/NO30" number="60">B</result>
<!-- 2012-12-04 do we also want a locref to the definition of the particular level, as in the resultDistribution below? -->
<!-- 2012-12-04 or should that scheme rather be a locref attribute of the gradingScheme? -->
							<gradingScheme xml:lang="no"/>
<!-- 2012-12-04 resultDistribution not in the original example, imagined here -->
<!-- 2012-12-04 here we have added a locref attribute to category -->
							<resultDistribution>
								<category locref="http://www.uio.no/locrefs/NO30/A" label="A" count="10"/>
								<category locref="http://www.uio.no/locrefs/NO30/B" label="B" count="30"/>
								<category locref="http://www.uio.no/locrefs/NO30/C" label="C" count="60"/>
								<category locref="http://www.uio.no/locrefs/NO30/D" label="D" count="30"/>
								<category locref="http://www.uio.no/locrefs/NO30/E" label="E" count="10"/>
							</resultDistribution>
						</learningOpportunityInstance>
					</specifies>
				</learningOpportunitySpecification>
			</hasPart>
		<learningOpportunitySpecification>
	</report>
</elmo>

Annexes

Some usefull links: