uk centre content specifications content packaging content launch content runtime api question and...
TRANSCRIPT
UK
Centre
Content Specifications
• Content Packaging
• Content Launch
• Content Runtime API
• Question and Test
UK
Centre
Content Packaging
• Aim: to transport Content between Systems
• Content can be compound and structured
• A Package carries its own metadata
• Structural and metadata info in special file
• Content files are ‘flat’ within the package
• Compressed zip/JAR format
UK
Centre
Content PackagingThe Manifest
• Every IMS Package has a Manifest• Must be called: META-INF/MANIFEST.IMS
• This is a nested tree structure of sub-Packs– Allows multiple files to be aggregated
• The root Pack is called the Manifest
UK
Centre
Content PackagingPACKS Contain:
• one METAD element (holds metadata)
• one CORG element (Content Organisation)
and
• Either: one DATA element (a Content file)
• Or: one or more (sub) PACK elements
UK
Centre
Content PackagingA Simple PACK
PACK
METAD
CORG
DATA (Note: each data element is wrapped in a Pack)
UK
Centre
Content PackagingA Compound PACK
PACK
METAD
CORG
PACK (Note: Packs can be wrapped in a Pack)
UK
Centre
Content PackagingThe METAD Element
• Contains one or more META elements
• a META element contains– a TYPE– a NAME (of the metadata file)
• The IMS type element holds IMS meta-data
• Other types may be included:– install– launch
UK
Centre
Content Packaging The METAD Element
METAD
Meta-data (“ims”)
Meta-data (“install”)
Meta-data (“launch”)
UK
Centre
Content PackagingThe CORG Element
• Can contain multiple TOCs
• a TOC can be more than a Table of Contents
• Can be an index, suggested paths, etc
• Extending to also hold active sequencers
• CORG elements cannot reference upwards
• a CORG is optional but recommended
UK
Centre
Content Packaging The CORG Element
CORG
Table of Contents 1: Historical Sequence
Table of Contents 2: By Geographic Distribution
Table of Contents 3: Animated Diagrams
UK
Centre
Content PackagingThe DATA Element
• These are references to zipped files
• They are the ‘payload’ of the Package
• The Payload files can be:– web pages, programs, any type of data file, etc.
• Data Elements may also reference URLs to external files
UK
Centre
Content Launch
• How do Content & LMS talk together?
• V0.5 used CORBA, RMI and DCOM
• An IMS system would have to support ALL
• Vendor Wars!
• Also large and relatively complex to– Implement– Install– Operate
UK
Centre
Content Launch Solution
• LMS initializes Content with a Proxy
• Proxy has an IMS defined API
• Content knows how to talk to Proxy
• Proxy knows how to talk to LMS
• Hides the underlying comms infrastructure
• IMS rises above Vendor wars
UK
Centre
Content LaunchA Binding Problem
• Content implemented in various languages– HTML, JavaScript, Java, ActiveX, etc
• Therefore need a ‘binding’ for each type– LMS needs to provide a proxy in each language– the right ‘binding’ must be given to the Content
• Java could be a universal binder/adapter,but Vendor wars break out again.
UK
Centre
Content Runtime API
• Once communication established, need:• An agreed way to communicate• Proposed:• A virtual tree hierarchy data schema• A simple set of messages
– getValue, setValue in the ‘Data Tree’– Move virtual location in data tree.
UK
Centre
Content Runtime API
• XML used for interchange format
• LMS translates internal data structures
into XML format specified by IMS
• Info about learner and profile
• Info about content and metadata
• Info about state of LMS
• Also need info about learning group
UK
Centre
Learner Profile - PAPI
• Personal and Private Information - PAPI
• Also being submitted to IEEE LTSC 1484
• More than record of achievement
• Seeking to support Intelligent Tutoring
• Preferences likely to become complex
• Work with live Content and Sequencers
UK
Centre
Learner Profile - PAPI
• Personal (Private - name, address, email, etc)
• Preferences (Public - accessability, learning style…)
• Performance (Machine - performance & assessment)
• Portfolio (Human - work produced by the learner)
Security is an important part of the PAPI spec
UK
Centre
Learner Profile - PAPICodings, API & Protocols
PAPI codings. A PAPI record may be coded in a PAPI coding. The data interchange is facilitated among data exchange participants by an agreed coding specification.
PAPI Application Programming Interfaces (APIs). The API is a control transfer mechanism (control is transferred from caller to callee) that affects data interchange.
PAPI protocols. The protocols are both control transfer and data transfer mechanisms.
“A conforming implementation shall include one or more bindings to codings, APIs, and/or protocols.”
UK
Centre
Learner Profile - PAPI
Delivery Evaluation
SystemCoach
KnowledgeLibrary
Content Index(metadata)
Query Index
LearningContent
Performance (new)
Multimedia Behavior
LearningPrefs
RecordsDatabase
Learning Content
Performance(current)Performance
(history)
A s s e s s m e n tL o c a t o r I n d e x
LearnerEntity
The IEEE 1484.1 Learning Technology System Architecture (LTSA) specification
PAPI applies to both Individual and Groups of Learners
UK
Centre
Learner Profile - PAPI Special account taken of:
• Nomadic and Sporadic users
• Distributed Systems
• Lifelong Learning = distributed over time
• Synchronise Local & Remote Profile Servers
UK
Centre
Learner Profile - PAPISecurity
• Features specified in the context of threats
• Based on:
– ANSI IISP security model
– the work of ISO/IEC JTC1 SC27
UK
Centre
Learner Profile - PAPISecurity
Considers:
• Perimeter integrity
• Inbound threats (entering, changing data)
• Outbound threats (taking data)
• Security strength
UK
Centre
Learner Profile - PAPISecurity
Personal, Preference, Performance & Portfolio security considered under scenarios, e.g.
• Naming of views• Who has access• Unauthorized reads• Unauthorized write• Transfer to/from back office
Discussion is ‘informative’ - no solutions yet!
UK
Centre
Groups
• Set out in original IMS Requirements
• Part of original 0.5 spec, but dropped in 0.6
• Needed for Classes and group learning
• Group Scope accepted at last Tech Board
UK
Centre
Groupsthe need
• Course Preparation and Admin Systems(Prospectus publishing and Enrolment Systems)
• Enrolment Systems and LMS• Between Learning Management Systems• Server-based and personal/portable LMS• Runtime Services and multi-user Content• Extend single user content to provide group
access• LMS and analysis systems (e.g. evaluation)• enable association between person/s & content
UK
Centre
GroupsSupport two functional areas
• Bulk data exchange format between Systems
• Run-time access to Group data by Content
UK
Centre
Groupsthe basic scheme
Group
• optionally contains Members
• optionally contains Resources
• optionally contains SubGroups
UK
Centre
GroupsElaborating the scheme
Group
ContentIMS Package
IMS Package
IMS Metadata Item URL
Members
IMS Profile E-Mail
Sub-Groups
Sub-Group 1 Sub-Group 2
UK
Centre
GroupsSketch of schema
<Group><Members>
<Teachers>…
</Teachers><Learners>
…</ Learners >
</Members>
<Resources>…
</Resources>
<SubGroups>…
</SubGroups></Group>
UK
Centre
Admin & Support Systems(Enterprise Systems)
• Main objective: integrate Admin & LMSan essential prerequisite
• Define a set of Messages (Transactions)
• Define a supporting Protocol
UK
Centre
Admin & Support SystemsRequirements
• Neutral wrt Data & Function distribution
• Conform to IMS Data architecture & protocols
• Support Publish/Subscribe & Query/Response
• Core Messages with Minimal Required Data
• Extensible
• Support Critical ‘Enterprise’ Systems:Human Resources, Student Admin, eMail, Security, Directory Services
UK
Centre
Admin & Support SystemsRequirements
• Define Messages for Basic Data & Processes
• Compatible with other IMS Specifications
• Incorporate other Standards Initiatives– SPEEDE/Express– PESC (Post Secondary Education Standards)– SIF (MS K-12 Schools Interoperability Framework)
UK
Centre
eCommerce
• Initially: Brad Cox’s SuperDistribution– Supported Component approach– Aggregation / Disaggregation– Pay per use to top level vendor– Payments flow down the chain– Flexible payment policies
• But– needs a security chip built into every machine!
UK
Centre
eCommerce
• Large vendors didn’t like it
• Superdistribution seen as ‘in the future’
• New group studying existing options
• No reports produced yet
UK
Centre
Taking IMS Further
IMS Specs due Summer or Autumn ‘99Still in formation period
Trial and Implementation sequence:
• Test draft specs by implementing in Systems
• With tools, can develop IMS compliant Content
• When got systems and content, can implement Live Systems with users
UK
Centre
Taking IMS Further
UK IMS Centre is setting up 4 Groups:
• Metadata
• Content
• Learning Management Systems
• Administrative Systems and Student Profile
UK
Centre
Taking IMS Further
Aims:
• Create a group of interoperable systems
• Test Specs by implementing
• Check if any UK Requirements not met
• Make input into Spec development
Contact:[email protected]
UK
Centre
Taking IMS Further
• IMS Web site: http://www.imsproject.org
• Gaining full access to restricted areas, email: