Content packaging

Content packaging Concetti principali Descrizione del package

bookshelf SCORM

Scopo cel content packaging • Fornire un modello standardizzato per scambiare risorse didattiche digitali tra differenti sistemi o strumenti. • Content Packaging definisce anche • La struttura (o organization) • il comportamento previsto di un insieme di risorse.

nel content packaging vengono definiti: • Un Manifest file che descrive il package e che contiene • Meta-data relativi al package ; • Una sezione opzionaleOrganization che definisce la struttura del contenuto ; • Un elenco di riferimenti (link) alle risorse utilizzate • Il binding di questi dati in un file xml • Indicazioni su come aggregare il file manifest e le altre risorse in un unico file zip o su CD-ROM, etc.

Relazioni con IMS • SCORM Content Packaging is a set of specific use examples, or application profiles, of the IMS Content Packaging Specification. SCORM packaging adheres strictly to the IMS Content Packaging Specification but provides additional explicit implementation guidance for packaging digital learning resources (Assets, Sharable Content Objects and Content Aggregations).

Aggregation asset asset SCO Learning resource asset SCO asset asset Aggregation asset asset SCO asset Learning resource SCO asset Learning resource SCO Learning resource SCO asset asset Aggregation asset asset Learning resource asset SCO SCO Learning resource asset Aggregation asset SCO asset Learning resource asset Learning resource SCO Learning resource Content packaging Content aggregation Content structure

Aggregation Learning resource Aggregation Learning resource Learning resource Learning resource Aggregation Learning resource Learning resource Aggregation Learning resource Learning resource Learning resource Content structure • E’ una ‘mappa’ del materiale • Consente la navigazione • Definisce il comportamento • Derivato da AICC Definisce: • Gerarchia dei contenuti • Metadata specifici del contesto • Sequencing & navigation • Regole per presentare all’utente le risorse • Prerequisite=f(cmi.core.lesson_status) • Passed • Completed • Browsed • Failed • Not attempted • Incomplete • AICC script operators (AND, OR, etc) • Si demanda a scorm 1.3 (simple sequencing)

Physical files Fi.dwg Pino.doc a.html … … … … … … x.htm Pip.gif Res.doc … … … … … … Package Unità usabile e riutilizzabile, erogabile in modo autonomo, parte di corso o corso intero. Giunto su un LMS, deve essere permessa l’aggregazione e disaggregazione Descrizione del package Manifest descrizione in XML delle risorse e del modo di usarle. Il top level manifest decrive l’intero pacchetto, i sottostanti descivono la loro parte Meta-data sono descrittori della risorsa nella sua interezza, possono anche descrivere (al loro livello) organizations e resources Package Interchange File Manifest File metadata organizations organizations serve a strutturare il contenuto, generalmente come tassonomia gerarchica di apprendimento resources (sub)Manifest(s) Resources può descrivere risorse esterne o gli stessi files della sezione ‘physical files’ Package Interchange Files è l’insieme dei files compressi (zip, arj, etc) con estensione .PIF, sistema standard di scambio materiali tra piattaforme Physical Files files indicati dalla sezione resources, interni o esterni (URL)

Manifest file Come si presenta il file Imsmanifest.xml Il Packaging dei corsi SCORM è descritto da un file speciale chiamato "imsmanifest.xml." Deve essere al top-level dell’insieme dei files e deve contenere quattro distinte sezioni; queste iniziano con un tag univoco e sono in questo ordine: - PREAMBLE <manifest identifier = "MANIFEST" .... > - META-DATA <metadata> ... course meta-data (title, keywords, etc.) </metadata> - ORGANIZATION <organizations default = "Linear"> ... a description of the course sequencing </organizations> - RESOURCES <resources> ... a names, resource meta-data and location of the files used in the course </resources>

Manifest map

Note sugli schemi

Manifest: general rules

Data model

Binding: esempi Data Type: This element is a container element and only contains other elements. Multiplicity: The manifest element is the top-level element for content package. Attributes: identifier (required) – An identifier, provided by an author or authoring tool, that is unique within the Manifest. version (optional) – Identifies the version of the Manifest. It is used to distinguish between manifests with the same identifier. xml:base (optional).This provides a relative path offset for the files contained in the manifest. The usage of this element is defined in the XML Base Working Draft from the W3C. Data type = String. Elements: <metadata> <organizations> <resources> <manifest> Example: <manifest identifier=”Manifest" version="1.1" xmlns="http://www.imsproject.org/xsd/imscp_rootv1p1p2" xmlns:adlcp="http://www.adlnet.org/xsd/adl_cp_rootv1p1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.imsproject.org/xsd/imscp_rootv1p1p2 imscp_rootv1p1p2.xsd http://www.imsproject.org/xsd/imsmd_rootv1p2 ims_md_rootv1p1.xsd http://www.adlnet.org/xsd/adl_cp_rootv1p1 adl_cp_rootv1p1.xsd">  </manifest> • <manifest identifier="lesson/361" version="1.0" • xmlns="http://www.imsproject.org/xsd/imscp_rootv1p1p2" xmlns:imsmd="http://www.imsproject.org/xsd/ims_md_rootv1p1"> <manifest identifier="SingleExternalSCOManifest" version="1.1“ xmlns=http://www.imsproject.org/xsd/imscp_rootv1p1p2 xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_rootv1p2" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance“ xsi:schemaLocation="http://www.imsproject.org/xsd/imscp_rootv1p1p2 imscp_rootv1p1p2.xsd http://www.adlnet.org/xsd/adlcp_rootv1p2 adlcp_rootv1p2.xsd">

metadata Si riferisce ai metadata di contesto, ovvero relativi al corso intero; non è obbligatorio

Metadata: data model

Metadata: binding • Data Type: This element is a container element and only contains other elements. • Multiplicity: The <metadata> element may occur 0 or 1 time within the <manifest> element. • Attributes: • None • Elements: • <schema> • <schemaversion> • <adlcp:location> • IMS Meta-data • Example: • 1 <metadata> • 2 <schema>ADL SCORM</schema> • 3 <schemaversion>1.2</schemaversion> • 4 <imsmd:lom> • 5 <imsmd:general> • 6 <imsmd:title> • 7 <imsmd:langstring xml:lang="en-US">Simple Manifest</imsmd:langstring> • 8 </imsmd:title> • 9 </imsmd:general> • 10 </imsmd:lom> • 11 </metadata>

organizations • Serve per descrivere la struttura del corso ; quando viene descritto un asset o uno SCO, organization deve essere vuoto; quando si descrive un content aggregation, deve esistere almeno un organization

Organizations: data model

Organizations: binding • Multiplicity: The organizations element may occur 0 or 1 time within a <manifest> element. • Attributes: • default (required). Identifies the default organization to use. Data type = IDRef. • Elements: • <organization> • Example: • 1 <organizations default="TOC1"> • 2 <organization identifier="TOC1" structure="hierarchical"> • 3 <title>default</title> • 4 <item identifier="ITEM1" identifierref="RESOURCE1" isvisible="true"> • 5 <title>Lesson 1</title> • 6 <item identifier="ITEM2" identifierref="RESOURCE2" isvisible="true"> • 7 <title>Introduction 1</title> • 8 </item> • 9 <item identifier="ITEM3" identifierref="RESOURCE3" isvisible="true"> • 10 <title>Content 1</title> • 11 </item> • 12 <item identifier="ITEM4" identifierref="RESOURCE4" isvisible="true"> • 13 <title>Summary 1</title> • 14 </item> • 15 </item> • <item identifier="ITEM5" identifierref="RESOURCE5" isvisible="false"> • .... • 40 </organization> • 41 </organizations

Organization ->item: data model

resources

Manifest…. • Riferimento a sub-manifest

Content packaging