Learning Platforms Technical Specifications (Version 1)

Learning platform technical specifications

Learning platform technical specifications Version 1

15 June 2006 http://www.becta.org.uk/industry Page 1 of 21 © Becta 2006 Learning platform technical specifications Version 1 Becta | Learning platform technical specifications

Contents

Contents...... 2

1 Introduction...... 3

2 Requirements and specifications...... 3 2.1 Content management...... 4 2.2 Curriculum mapping and planning...... 7 2.3 Learner engagement and administration...... 9 2.4 Tools and services...... 12

3 Summary...... 14

Appendix 1 SCORM...... 15 A.1.1 Content packaging...... 15 A.1.2 Run-time interactions...... 15 A.1.3 Sequencing and navigation...... 17

Appendix 2 Location of specifications...... 18

15 June 2006 http://www.becta.org.uk/industry page 2 of 21 © Becta 2006 Learning platform technical specifications Version 1 Becta | Learning platform technical specifications

1 Introduction

This document is part of the British Educational Communications and Technology Agency (Becta) learning platform framework project. It presents a set of technical specifications for learning platform software and systems to be used in schools in England.

It covers parts of the learning services and data services components of Becta’s national digital infrastructure. Beyond the scope of this document are requirements and specifications for connectivity and institutional infrastructure.

A learning platform is not expected to be a single product but rather a collection of interoperable systems or modules. Each may perform discrete functions, but collectively they should deliver the requirements described below.

It is expected that platforms will meet the requirements and the specifications in a variety of ways.

This document is the learning platform technical specifications, the partner document to the learning platform functional requirements.

2 Requirements and specifications

The following are guidelines for specifications that should be supported in order to deliver the requirements.

Each requirement is indicated as mandatory or recommended. Specifications are indicated as mandatory, recommended or for consideration. The use of the word 'shall' indicates mandatory and 'should' indicates recommended but optional. 'Could' is used to provide illustrative examples of how requirements might be met rather than to indicate mandatory or recommended requirements.

Platforms may deliver a functional requirement in their own way, in addition to any mandatory or recommended specifications.

Requirements may have notes that describe how they shall be met. Some have specifications that shall or should be supported.

If a requirement is mandatory and a specification is mandatory, a platform shall provide the functionality described and meet all the specifications.

If a requirement is mandatory and a specification is recommended, a platform shall provide the functionality described but may choose specifications that are appropriate.

If a requirement is recommended but a specification is indicated as 'mandatory (conditional)' then a platform that claims to meet the requirement must support the technical specifications described.

Some specifications are indicated as being for future consideration.

Some requirements do not have any mandatory or recommended specifications associated with them.

It is recognised that specifications will advance and, as a consequence, there will be a process of review and updating to the learning platform technical specifications. Some changes and developments are already anticipated and suppliers should be aware of them. These include the following factors:

 The next version of the Curriculum Online metadata schema will be released later this year.

 The Government is working on coherent solutions for unique identification of learners.  Becta is working on specifications in the data services strand (information management/MIS)  The BBC Jam materials will be available to all suppliers on the framework to deliver through solutions they provide.

Additional advice will be provided on how any updates impact on the implementation of the learning platform technical specifications. It is expected that solution providers under the scheme shall meet appropriate specifications as soon as possible.

2.1 Content management

O = obligation M = mandatory R = optional but recommended

Requirement name O Description Specifications and notes R1: Assessment M Assessment items Mandatory: IMS QTI 1.2 and v2.0. items shall be loaded and Further guidance is expected to be provided. used. For consideration: IMS QTI Version 2.1.

Assessment items that are present on the system shall be capable of being displayed to users. Display means that either the assessment item itself or a link to it can be seen by the user. A user shall be able to launch an assessment item that is displayed. (Subsequent interactions are covered by R14.) R2: Launch M The user shall be Mandatory: the mandatory (Adopted) e- resources able to launch digital Government Interoperability Framework 6.1 content via a web requirements for the public sector shall be met. browser or other (See Technical Standards Catalogue Version application. 6.2.)

It is necessary for platforms to be able to launch resources that are in common formats using common protocols such as those that meet W3C specifications (http, html and so forth).

‘Other application’ means software that forms part of the overall platform (for example a dedicated content client). If there is no dedicated content client, then digital content must be able to be launched in an installed web browser. If remote content exists outside the platform, but is listed by the platform, then it should also be capable of being launched.

Requirement name O Description Specifications and notes R3: Load content M It shall be possible to Mandatory: several specifications defined by objects load, store and make SCORM shall be supported. sharable content objects available to Recommended: other SCORM specifications users. Run-time should be supported. interactions with content objects (See Appendix 1 SCORM for details.) should be supported. This includes being Content objects could be imported as part of a able to load bundled package rather as individual files. resources (content packages) and unpack them. R4: Load resources M It shall be possible to There are no specifications recommended for load digital content how resources should be stored, but it is into a storage area recommended that their location can be that can be specified using a URL, and that this is presented to learners persistent. and accessed via the platform interface. The platform shall make 'browse and search' functionality available to learners, so that loaded resources can be accessed by learners. The names of loaded resource files should be displayed. R5: Metadata M Users shall be able Mandatory: Curriculum Online version 1.1 creation to classify and tag Metadata Schema shall be used for tagging resources. resources.

Recommended: for sharing with other systems a subset of Curriculum Online 1.1 elements should be used if all the mandatory elements are not required.

The method of tagging and how much this is automated can be varied, possibly using the Becta Tagging Tool. There are no mandatory metadata specifications for how local information is to be recorded and used, though it is recommended that any schemas that are used should be made openly available and be profiles of common open specifications.

Users shall be able to add, edit and remove metadata associated with resources.

Requirement name O Description Specifications and notes R6: Metadata M It shall be possible to Mandatory: Curriculum Online version 1.1 import and display load and store Metadata Schema and eGMS version 3.0. metadata records and display Recommended: Dublin Core, IEEE LOM information derived 1484.12.1. from them to the user. The platform shall be able to: 1. load metadata records that are provided by a supplier 2. store permanently metadata records that are provided by a supplier 3. display metadata records to users.

It is recognised that there may be policies that place limits on which metadata can be shown to the user. Users must be able to see that a metadata record exists for a given resource and must be able to view the record subject to these policies. It is recognised that metadata records may be imported as part of a package rather as individual files or may be accessed via a web service. R7: Resource M Users shall be able There are no recommended specifications – creation to create new though resources that are only created in resources, integrate proprietary formats should be avoided. them with the platform and export The platform shall: them. 1. include an authoring tool that enables users to create and save new content 2. be able to run (see other requirements) any content that has been created using the authoring tool. R8: Coursework R Schools should be There are no recommended specifications. A able to submit pupils’ specification could be created in future. coursework (formally agreed and accredited units of study) to examination bodies in an agreed format. R9: Cross device R Resources should be There are no recommended specifications. made available to a range of devices. There is increasing use of a range of devices to support learning. These could include mobile devices such as PDAs and cell phones. R10: Identifiers R Globally unique Mandatory (conditional): identification 1. Unique Pupil Number coding scheme namespaces should 2. URI – being able to recognise and parse a be interpreted and URI conforming to the IETF Generic Syntax for managed. URIs (RFC 3986). R11: Resource lists R Lists of resources For consideration: IMS Resource List should be made Interoperability v1. available in a shareable format.

Requirement name O Description Specifications and notes R12: Syndicate R Users should be able Mandatory (conditional): IETF Atom content to combine data- Syndication Format (RFC 4287). streams and selectively share them with others.

2.2 Curriculum mapping and planning

Requirement name O Description Specifications and notes R13: Accessibility M The platform Mandatory: W3C Web Accessibility Initiative interface shall be v2.0 guidelines level A and eGIF 6.1 Technical accessible to users. Standards Catalogue Version 6.2 (see Table 20).

Recommended: W3C Web Accessibility Initiative v2.0 guidelines level AA.

It is the responsibility of a platform provider to ensure appropriate accessibility guidelines are followed and that legislation such as the Disability Discrimination Act is adhered to.

It is the platform, rather than the resources provided, that should meet any requirements or tests. R14: Assessment for M The platform shall Recommended: BS 7988:2002 Code of learning enable learners to be Practice for the use of information technology provided with (IT) in the delivery of assessments assessments and diagnostics to See R1 for specifications and delivery of support learning assessments. plans. The platform shall be able to: 1. deliver assessments to users 2. display which content a user has run. 3. report results for each content that a learner has run, including the following information: date of run, marks awarded, output from user, and comments from other users.

Types of assessment should include multiple- choice, essay, single-word answer. R15: Customisable M The user interface There are no recommended specifications. interface shall be capable of being customised to All user interfaces within the platform shall adapt to the learner’s allow the user to change the screen colours, preferences. font and font size. R16: Lesson planning M It shall be possible Recommended: IMS Learning Design v1.0 for teachers to can be used for lesson plans. produce and manage lesson plans.

Requirement name O Description Specifications and notes R17: Navigation and M Curriculum Mandatory: the published English National search information shall be Curriculum structures provided by Becta: used to search for Programmes of Study and Schemes of Work. and to navigate to These will be published via Becta Vocabulary resources within the Bank. platform. Recommended: further curriculum structures are likely to be made available. The Zthes XML format should be supported for import of these structures.

For consideration: eXchanging Course-Related Information (XCRI). XCRI is a technical specification for curriculum structures being developed in the UK community with input from UCAS and others.

Users shall be able to browse resource collections. Such collections and resources shall be represented by an assigned name or link. Collections shall be presented to users for browsing according to required curriculum structures. R18: Personalisation M Users should be able There are no recommended specifications, to personalise their although specifications in other requirements learning experience. may be used to support personalisation.

There are many ways in which platforms may support personalisation. These are not defined here.

Allocation of resources to users shall be enabled at the individual, as well as group or public, level. R19: Sequence M Users shall be able Recommended: resources or to create structured 1. IMS Learning Design v1.0 activities units and sequence 2. IMS Simple Sequencing v1.0. learning resources or activities. (Some aspects of sequencing and navigation are mandatory as part of managing content objects see R3 and Appendix 1 SCORM )

The platform shall be able to sequence discrete resources based on a system of rules. The platform shall be able to demonstrate that different resources are presented to users given different values or rules. ‘Presented’ means that the content is run automatically or is displayed to the user as the next piece of content.

Requirement name O Description Specifications and notes R20: Metadata R The platform should Mandatory (conditional): Open Archives harvesting be able to retrieve Initiative – Protocol for Metadata Harvesting metadata instances v2.0 (OAI-PMH) is the recognised specification from distributed for metadata harvesting. repositories. 1. The platform shall be able to retrieve metadata from remote repositories. 2. The platform shall be able to retrieve metadata from web services. 3. Metadata so received shall be displayed to users.

2.3 Learner engagement and administration

Requirement name O Description Specifications and notes R21: Access off site M Users shall be able Mandatory: the learning platform shall be to access the accessible using open web protocols (see learning platform eGIF 6.1 Technical Standards Catalogue away from the Version 6.2). organisation. The platform shall be accessible outside of normal school times. R22: Authentication M Users shall be Recommended: Shibboleth. and authorisation uniquely identified and verified. Shibboleth is a system to allow organisations to exchange information about users in a secure and privacy-preserving manner.

The platform shall associate an identifier with a user. Each identifier must be associated uniquely with a single user. The platform shall be able to verify a presented identifier. The platform should integrate into an existing authentication system. R23: Consistent M Learner information For consideration: a hub integration model, for learner information shall be consistent example based on parts of the Schools throughout the Interoperability Framework, allows data to be platform. shared and managed across several systems. Alternatively, learner information may be accessed through a single shared web service.

Where a platform is distributed, the platform shall: 1. accept the same unique identifier and verification information for a user at all of the distributed access points 2. ensure that learner information is accessible to users at all of the distributed access points 3. ensure that duplicated information is consistent across the platform.

Distributed refers to systems where there are multiple servers.

Requirement name O Description Specifications and notes R24: Data protection M All stored data shall There are no recommended specifications. be secure. As a minimum, this will require conformance with current legislation. This is considered as a more of a management and policy issue than a predominantly software specification requirement. R25: Groups and M It shall be possible There are no recommended specifications. roles for users be allocated to one or The platform shall allow different groups to be more groups and set up to which users can be assigned. assigned roles. Each user shall be assigned to at least one group. A user can be assigned to more than one group. Each group shall contain authorisation permissions. Platform functionality shall be linked to the group authorisation model. Each user in a group shall be able to execute all of the system functionality that is available to the group. R26: Information M Users with privileges Recommended: OASIS XACML for access access shall be able to control policy. access appropriate information. The platform shall support an authorisation permissions model. Information stored on the platform shall be assigned authorisation permission. The platform shall present users with data that matches their level of authorisation. R27: Learner M It shall be possible Recommended: information export for learner 1. IMS Enterprise Services information to be 2. Common Basic Data Set exported from the 3. Common Transfer File v4. platform. For future consideration: IMS ePortfolio, IMS LIP and UK Leap, SIF.

The platform shall allow a copy of a learner record to be exported as a file. R28: Learner M It shall be possible Recommended: information Import for learner 1. IMS Enterprise Services information to be 2. Common Basic Data Set imported to the 3. Common Transfer File v4. platform. For future consideration: IMS ePortfolio, IMS LIP and UK Leap, SIF.

The platform shall store a copy of the learner information received from an external system. R29: Portfolios M Users shall be able There are no recommended specifications. to create and maintain portfolios The platform shall be able to permanently store for sharing content a user’s portfolio. This could be via an external and to support hosting service. personal development. The platform shall be able to provide access to a user’s portfolio.

Requirement name O Description Specifications and notes R30: Scheduling M Access to resources There are no recommended specifications. shall be controllable. For consideration: IMS Enterprise Services + iCalendar (RFC2445) extensions.

Platforms shall allow rules to be assigned to the access of resources. Rules shall allow resources to be available for set times only. Rules should allow resources to be made available only if other content objects have been completed. R31: Tracking M Facilities shall be There are no recommended specifications. provided to track learners’ support The platform shall provide reports. needs and The platform shall be able to print copies of performance. reports. The platform shall be able to store copies of reports. The report shall contain the following information: date, learner's name list of content objects used by the learner. NB Reports may be provided on screen, not necessarily printed. R32: Usage data M Information about There are no recommended specifications. individual and group usage of the The platform shall be able to produce the resources shall be reports detailed below. available. The platform shall be able to print a copy of the reports. The platform shall be able to store a copy of the reports.

A report shall contain the following information: date, total number of objects, time spent on all objects by all learners and number of learners.

A report shall contain the following information: date, name of learning object, number of times learning object has been used between input dates, total amount of time spent on learning object between input dates and total number of users that have used the learning object between input dates. R33: Attendance R Support should be There are no recommended specifications. provided for the measurement and reporting of attendance. R34: Self- R Users should be able There are no recommended specifications. organisation to organise and annotate resources. R35: Timetabling R A timetable, or an Recommended: IETF iCalendar. interface to one, should be supported.

2.4 Tools and services

Requirement name O Description Specifications and notes R36: Discussion M Users shall be able to take part Recommended: forums in discussion forums by IETF Atom Syndication Format posting and reading (RFC 4287) – for syndication messages. IETF Atom Publishing Protocol for submission.

The platform shall offer discussion forums. The platform shall post a message from an authorised and authenticated user to the appropriate forum. The platform shall permit other authorised and authenticated users to read the messages posted in the forum. The platform shall permit the message author to edit messages so posted. The platform shall permit the message author to delete messages so posted. The platform shall permit administrators to edit any messages posted. The platform shall permit administrators to delete any messages posted. R37: Rights M Functionality shall be provided Recommended: Creative management that supports and recognises Commons. licensing conditions. The platform should enable users to associate created resources with Creative Commons rights information.

The platform shall enable the association of rights information with resources that are created using the platform authoring tool. The platform shall display, or enable links to, licences, rights and other copyright information to users of content that contains such rights statements. R38: Web services M The platform shall be capable Mandatory: Web Services of transparently interacting Protocols (SOAP, WSDL, UDDI). with web services using standard protocols. Note: Curriculum Online web services will be accessible using either SRW (SOAP) and SRU (REST). Platforms shall support one of these. R39: Audio-visual R Audio- and video-conferencing Mandatory (conditional): eGIF 6.1 conferencing should be supported. Technical Standards Catalogue Version 6.2 – (see Table 9 and Table 10).

Requirement name O Description Specifications and notes R40: Blog R Users should be able to create There are no recommended web logs. specifications.

Blog content should be shared using IETF Atom Syndication Format (RFC 4287), IETF Atom Publishing Protocol (see R45). R41: Email R One-one and one-many Mandatory (conditional): eGIF 6.1 messaging should be Technical Standards Catalogue facilitated. Version 6.2 (see Table 1). R42: Knowledge R Knowledge construction tools There are no recommended construction should be available. specifications. R43: Messaging R Individuals and groups of Mandatory (conditional): SMS, users should be able to send MMS (see eGIF 6.1 Technical messages to each other. Standards Catalogue Version 6.2 Table 8).

For Consideration: IETF SIP. R44: Other activities R Support for non-teaching There are no recommended activities should be provided. specifications. R45: Resource R Syndicated content, such as Recommended: syndication newsfeeds, should be IETF Atom Syndication Format supported. (RFC 4287).

For consideration: RSS various versions. Note: ownership is disputed; RSS 1.0, RSS 3.0, RSS 0.93 have different IPR.

3 Summary

The following are the mandatory requirements that have mandatory specifications.

R1: Assessment items IMS QTI 1.2 and v2.0

R2: Launch resources Adopted formats in e-GIF 6.1 requirements (Technical Standards Catalogue Version 6.2).

R3: Load content objects Several specifications shall be supported. (see Appendix 1 SCORM).

R5: Metadata creation Curriculum Online version 1.1. for uploading into the Curriculum Online Portal.

R6: Metadata import and display Curriculum Online version 1.1.

e-GIF 6.1 requirements (Technical Standards Catalogue Version 6.2).

R17: Navigation and search The published English National Curriculum structures: Programmes of Study and Schemes of Work.

R21: Access off site Adopted protocols in e-GIF 6.1 (Technical Standards Catalogue Version 6.2).

Some specifications include other specifications or are defined though more than one document. See Appendix 2 for location of referenced documents.

Appendix 1 SCORM

Shareable Content Object Reference Model (SCORM) is a model that contains a collection of profiles of several standards and specifications, plus some additional data models and recommendations. The SCORM 2004 books provide very useful information and explanations of some of the key concepts and definitions.

Providers should refer to the SCORM 2004 version 3 (v1.3.2) to provide background to a framework for delivering and managing learning content. Providers should also note that version 3 is a public draft and is likely to replace version 2 following a period of public comment which ended on 1 May 2006.

Not all of the specifications that are described in SCORM are adopted as mandatory requirements for learning platforms. The following describes the obligations for various parts of SCORM 2004. The SCORM specifications not mentioned are to be considered as recommended but not mandatory.

A.1.1 Content packaging

Content aggregation is the assembling of assets and learning objects into a particular structure with metadata so that it can be unpackaged and delivered to the user by a learning platform. Publishers may wish to place restrictions on the level of disaggregation permitted and platform providers should attempt to respect such preferences.

Content can be provided in various forms. Some are assets (the SCORM term is Sharable Content Asset SCA) that are simply initiated by the platform without any further communication, while others are learning objects that provide the platform with information that can support tracking and feedback (the SCORM term is Sharable Content Object SCO).

A learning platform:

 shall be able to accept and unpack content packages that are conformant with the IMS Content Packaging data model and binding specifications for versions 1.1.3, 1.1.4 and 1.2  shall have support for ZIP (DEFLATE version 1.3 RFC1951)  should support the ADL SCORM 2004 Content Packaging Extensions XML XSD Version 1.1 (Draft).

A.1.2 Run-time interactions

Some learning resources can provide information to a learning platform. This includes simple start and stop signals and more complex information about a learner’s performance.

A learning platform:

 shall conform to the IEEE ECMAScript API for Content to Runtime Services Communication (1484.11.2-2003), and in particular be interoperable with the SCORM 2004 Run-Time Environment API calls as follows: o Initialize o Terminate o GetValue o SetValue o Commit o GetLastError o GetErrorString o GetDiagnostic.

 shall conform to the IEEE Data Model for Content to Learning Management System Communication (IEEE 1484.11.1-2004) and support the following elements:

Data Model Element Description

comments from contains text from the learner learner

comments from LMS contains comments and annotations intended to be made available to the learner

completion status indicates whether the learner has completed the SCO

completion threshold a value against which the measure of the progress the learner has made toward completing the SCO can be compared to determine whether the SCO should be considered completed

credit indicates whether the learner will be credited for performance in this SCO

entry contains information that asserts whether the learner has previously accessed the SCO

exit indicates how or why the learner left the SCO

interactions defines information pertaining to an interaction for the purpose of measurement or assessment

launch data provides data specific to a SCO that the SCO can use for initialisation

learner ID identifies the learner on behalf of whom the SCO instance was launched

learner name represents the name of the learner

learner preference specifies learner preferences associated with the learner’s use of the SCO

location represents a location in the SCO

maximum time the amount of accumulated time the learner is allowed to use a SCO in the allowed learner attempt

mode identifies the modes in which the SCO may be presented to the learner

objectives specifies learning or performance objectives associated with a SCO

progress measure a measure of the progress the learner has made toward completing the SCO

scaled passing score the scaled passing score for a SCO

score the learner’s score for the SCO

session time the amount of time that the learner has spent in the current learner session for the SCO

success status indicates whether the learner has mastered the SCO

Data Model Element Description

suspend data provides information that may be created by a SCO as a result of a learner accessing or interacting with the SCO

time limit action indicates what the SCO should do when the maximum time allowed is exceeded

total time the sum of all of the learner’s learner session times accumulated in the current learner attempt prior to the current learner session.

SCORM run-time environment data model elements summary (source: Advanced Distributed Learning (ADL), Sharable Content Object Reference Model (SCORM®) Run-Time Environment Version 1.3.1, 2004)

Providers should be able to provide details of how they meet appropriate SCORM self-certification tests. Find additional informative guidance in the document SCORM Run-Time Environment Version 1.3.1.

A.1.3 Sequencing and navigation

The following are given as draft in SCORM 2004, but there is expected to be a large number of learning resources that may require include sequencing and navigation. Therefore support for the SCORM 2004 sequencing and navigation is mandatory. Further clarification is expected as content requirements change.

A learning platform shall support:

 SCORM 2004 Sequencing Extensions XML XSD Version 1.0 Draft [http://www.adlnet.gov/downloads/263.cfm]  SCORM 2004 Navigation Extensions XML XSD Version 1.1 Draft [http://www.adlnet.gov/downloads/264.cfm].

Appendix 2 Location of specifications

M = mandatory MR = a mandatory specification for a recommended requirement R = recommended C = for consideration X = referenced specifications

Specification Location Status ADL SCORM 2004 v2 http://www.adlnet.gov/downloads/70.cfm M parts

ADL SCORM 2004 Navigation http://www.adlnet.gov/downloads/264.cfm M Extensions v1.1

ADL SCORM 2004 Sequencing http://www.adlnet.gov/downloads/263.cfm M Extensions v1.0

Curriculum Online v1.1 Metadata http://www.curriculumonline.gov.uk/SupplierCentr M Scheme e/Metadataguides.htm

eGovernment Interoperability http://www.govtalk.gov.uk/schemasstandards/egif M Framework v6.1 .asp parts

IEEE ECMAScript API for Content to http://standards.ieee.org/catalog/olis/learning.htm M Runtime Services Communication l (1484.11.2-2003)

IMS Content Packaging v1.1.3 http://www.imsglobal.org/content/packaging/index M .html

IMS Content Packaging v1.1.4 http://www.imsglobal.org/content/packaging/index M .html

IMS Content Packaging v1.2 http://www.imsglobal.org/content/packaging/index M .html

IMS Question & Test Interoperability http://www.imsglobal.org/question M v1.2.1

IMS Question & Test Interoperability http://www.imsglobal.org/question M v2.0

National Curriculum Programmes of http://www.becta.org.uk/vocab/ M Study

National Curriculum Schemes of http://www.becta.org.uk/vocab/ M Work

Search/Retrieval via URL v1.1 http://www.loc.gov/standards/sru/ M

Search/Retrieve WebService http://www.loc.gov/standards/sru/srw/ M

Web Services Protocols (SOAP, http://roadmap.cbdiforum.com/reports/protocols/i M WSDL, UDDI) ndex.php

ZIP (DEFLATE v1.3) http://www.ietf.org/rfc/rfc1951.txt M

ATOM Syndication Format http://www.ietf.org/rfc/rfc4287.txt MR

IETF Generic Syntax for Uniform http://www.ietf.org/rfc/rfc3986.txt MR Resource Identifiers

Open Archives Initiative - Protocol for http://www.openarchives.org/OAI/openarchivespr MR Metadata Harvesting v2.0 otocol.html

ADL SCORM 2004 Content http://www.adlnet.gov/downloads/262.cfm R Packaging Extensions v1.1

BS 7988:2002 Code of practice for http://www.bsi- R the use of information technology (IT) global.com/ICT/Elearning/bs7988.xalter in the delivery of assessments

Common Basic Data Set http://www.teachernet.gov.uk/management/ims/d R atamanagement/cbds/

Common Transfer File v4 http://www.teachernet.gov.uk/management/ims/d R atatransfers/CTF/

Common Transfer File v5 http://www.teachernet.gov.uk/management/ims/d R atatransfers/CTF/

Creative Commons http://www.creativecommons.org.uk/ R

Dublin Core Metadata Element Set http://dublincore.org/documents/dces/ R v1.1

eGovernment Metadata Standard http://www.govtalk.gov.uk/schemasstandards/met R v3.0 adata_document.asp?docnum=872

Extensible Access Control Markup http://www.oasis- R Language open.org/committees/tc_home.php? wg_abbrev=xacml#XACML20

IEEE LOM http://ieeeltsc.org/wg12LOM/ R

IMS Learning Design v1.0 http://imsglobal.org/learningdesign R

IMS Meta-Data v1.2.1 http://www.imsglobal.org/metadata/index.html R

IMS Simple Sequencing v1.0 http://www.imsglobal.org/simplesequencing R

Learning Activity Management http://www.lamsfoundation.org/CD/index.html R System

Open Digital Rights Language v1.1 http://odrl.net/ R

Shibboleth v1.3 http://shibboleth.internet2.edu/ R

Web Accessibility Initiative http://www.w3.org/WAI/Resources/Overview R

Web Accessibility Initiative 2.0 http://www.w3.org/WAI/intro/wcag20 R

ZThes XML Format http://zthes.z3950.org/xml/index.html R

ADL SCORM 2004 v3 http://www.adlnet.gov/scorm/index.cfm C

Common Transfer File v6 http://www.teachernet.gov.uk/management/ims/d C atatransfers/CTF/

eXchanging Course-Related http://www.elframework.org/projects/xcri C Information

IETF iCalendar http://www.ietf.org/rfc/rfc2445.txt C

IETF Session Initiation Protocol http://www.ietf.org/rfc/rfc3261.txt C

IMS Accessibility Guidelines v1.0 http://www.imsglobal.org/accessibility/index.html C

IMS Accessibility LIPv1.0 http://www.imsglobal.org/accessibility/index.html C

IMS Accessibility MDv1.0 http://www.imsglobal.org/accessibility/index.html C

IMS Competency Definitions v1.0 http://www.imsglobal.org/competencies/index.htm C l

IMS Digital Repositories v1.0 http://www.imsglobal.org/digitalrepositories/index. C html

IMS Enterprise Services v1 http://www.imsglobal.org/es/ C

IMS Enterprise v1.1 http://www.imsglobal.org/enterprise C

IMS ePortfolio v1.0 http://www.imsglobal.org/ep/index.html C

IMS Learner Information Package http://www.imsglobal.org/profiles/index.html C v1.01

IMS Question & Test Interoperability http://www.imsglobal.org/question C v2.1

IMS Resource List Interoperability v1 http://www.imsglobal.org/rli/ C

IMS Shareable State Persistence v1.0 http://www.imsglobal.org/ssp/index.html C

IMS Vocabularies Definition http://www.imsglobal.org/vdex/index.html C Exchange v1.0

Really Simple Syndication 2.0.1 http://blogs.law.harvard.edu/tech/rss C

Schools Interoperability Framework http://www.sifinfo.org/sif-specification.asp C

UK LEAP http://www.bsi- C global.com/ICT/Elearning/standards.xalter

SCORM 1.2 http://www.adlnet.gov/downloads/120.cfm X

Topic Maps (XTM) http://www.topicmaps.org/xtm/index.html X

NB The persistence of these links cannot be guaranteed.

15 June 2006 http://www.becta.org.uk/industry page 21 of 21 © Becta 2006 Learning platform technical specifications Version 1