Content packaging
Concetti principali
Descrizione del package
bookshelf SCORM
SCORM
BOOK 1:
The SCORM
Overview
BOOK 2: The SCORM
Content Aggregation Model
BOOK 3: The
SCORM Run Time
Environment
Meta-data Dictionary (from IEEE)
Content Packaging (from IMS)
Content Structure (derived from AICC)
(Meta-data XML Binding and Best Practice (from IMS)
Data Model (from AICC)
Launch, Communication API (from AICC)
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 opzionale Organization 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).
Content packaging
Aggregation
Content aggregation
Content structure
Learning resource
Aggregation
Learning resource
Learning resource
asset
asset
asset
asset
SCO
SCO
SCO
asset
asset
asset
asset
SCO
asset
SCO
asset
asset
SCO
asset
asset
Learning resource
Learning resource
asset
asset
Aggregation
Learning resource
asset
asset
Learning resource
Learning resource
SCO
SCO
Learning resource
Aggregation
asset
SCO
SCO
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)
Aggregation
Learning resource
Aggregation
Learning resource
Learning resource
Learning resource
Aggregation
Learning resource
Learning resource
Aggregation
Learning resource
Learning resource
Learning resource
Descrizione del package
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
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
Package Interchange File
Manifest File
Meta-data sono descrittori
della risorsa nella sua
interezza, possono anche
descrivere (al loro livello)
organizations e resources
metadata
organizations
organizations serve a
strutturare il contenuto,
generalmente come
tassonomia gerarchica di
apprendimento
resources
(sub)Manifest(s)
Fi.dwg Pino.doc a.html
…
…
…
…
…
…
Resources può descrivere risorse
esterne o gli stessi files della
sezione ‘physical files’
Physical files
x.htm
Pip.gif Res.doc
…
…
…
Package
Files
…
…Interchange
…
è 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>
3.1 Default
3.2.1 identifier
3.2.2 Structure
3.2.3 title
Manifest map
3.2.4.1 identifier
3.2.4.2.identifier ref
3.2.4.3 is visible
3.2.4.4 parameters
3.2.4.5 title
3.2.4.6 item
3.2.4.7.1 Schema
3. Organizations
3.2.4 item
3.2.4.7 metadata
3.2 Organization
3.2.4.7.2 Schema version
3.2.4.7.3 Adlcp:location
3.2.4.7.4 {metadata}
3.2.4.8 Prerequisites
3.2.4.8.1 type
3.2.4.9 Max time allowed
2.1 Schema
2.2 Schema version
2.3 Adlcp:location
3.2.4.10 Time Limit Action
3.2.4.11 Data from LMS
2 Metadata
3.2.4.12 Mastery Score
2.4 {metadata}
3.2.5.1 Schema
Imsmanifest
3.2.5 metadata
29/05/2003 - v9
3.2.5.2 Schema version
3.2.5.3 Adlcp:location
3.2.5.4 {metadata}
1.1 Identifier
1.2 version
1 Manifest
4.1.1 identifier
4.1.2 type
4.1.3 href
4.1.4 SCORM type
4.1.5.1 Schema
4.1.5 metadata
4.1.5.2 Schema version
4.1.5.3 Adlcp:location
4.1.5.4 {metadata}
4. Resources
4.1 Resource
4.1.6.1 Href
4.1.6.2.1 Schema
4.1.6 file
4.1.6.2 Metadata
4.1.6.2.2 Schema version
4.1.6.2.3 Adlcp:location
4.1.6.2.4 {metadata}
Enter Sub-topic
4.1.7 dependency
4.1.7.1 Identifier ref
Note sugli schemi
L’elemento ha uno o più figli
L’elemento contiene dati.
Il testo riquadrato denota l’XML Schema Definition (XSD) assegnato
(no symbol)
Quando non c’è alcun simbolo di molteplicità, l’elemento è presente una e una sola
volta.
+
L’elemento appare una o più volte .
?
L’elemento appare zero o più volte.
Manifest: general rules
Data model
Nr
Name
Explanation
Multiplicity
Data Type
1
Manifest
The first, outermost <manifest> element in the
Manifest encloses all the reference data.
Subsequent occurrences of the <manifest>
elements inside the outermost <manifest> are
used to compartmentalize files, meta-data, and
organization structure for aggregation,
disaggregation, and reuse. All namespace
declarations should be declared inside the
<manifest> element.
1 and only 1
Container
1.1
Identifier
An identifier, provided by an author or
authoring tool, that is unique within the
Manifest.
1 and only 1
ID
1.2
Version
Identifies the version of the Manifest.
1 and only 1
String (smallest
permitted
maximum: 20
characters)
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>
-<manifest identifier="lesson/361" version="1.0"
<organizations>
xmlns="http://www.imsproject.org/xsd/imscp_rootv1p1p2"
<resources>
xmlns:imsmd="http://www.imsproject.org/xsd/ims_md_rootv1p1">
<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
<manifest identifier="SingleExternalSCOManifest" version="1.1“
adl_cp_rootv1p1.xsd">
xmlns=http://www.imsproject.org/xsd/imscp_rootv1p1p2
<!-- imsmanifest contents -->
xmlns:adlcp="http://www.adlnet.org/xsd/adlcp_rootv1p2"
</manifest>
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
2
Metadata
This element contains context specific meta-data that is used to describe the content of the overall package
(Package level meta-data). If meta-data is provided, the meta-data must be valid IMS Learning Resource
Meta-data.
0 or 1
Container
2.1
Schema
Describes the schema that defines the meta-data. This element is optional, however if present it must
contain the value of “ADL SCORM”.
0 or 1
String (smallest
permitted
maximum: 100
characters)
2.2
Schema
Version
Describes the version of the schema that defines the meta-data. This element is optional, however if
present it must contain the value of “1.2”.
0 or 1
String (smallest
permitted
maximum: 20
characters)
2.3
Location
This element describes the location where the meta-data describing the package may be found. This may
be a Universal Resource Indicator (URI).
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model.
This element can be used to reference a file that contains the meta-data. Either the meta-data is included inline within the <metadata> element, or this element is used to provide the file location.
ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the content package
developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension mechanism.
0 or 1
String (smallest
permitted
maximum: 2000
characters)
2.4
{Metadata}
This is where meta-data is placed.
ADL Note: ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the
content package developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the manifest using the appropriate XML extension mechanism.
0 or 1
Inline Meta-data
Record
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
3
Organizations
Describes one or more structures or organizations for this package.
When defining a SCORM Resource Package, this element is required to
be empty. When defining a SCORM Content Aggregation Package, this
element is required to contain at least one organization sub-element.
1 and only
1
Container
3.1
Default
Identifies to the system the default organization to use. The value for
this field should be an ID Reference to an ID of an Organization. If the
Organizations element contains more than one Organization element
and the Default element is not provided, the first Organization element
encountered is assumed to be the default.
0 or 1
IDRef
Organizations: data model
3.2
Organization
This element describes a particular organization. Different views
or organizational paths through the content can be described
using multiple instances of the Organization element.
ADL Note: This element replaces the outermost <block>
element defined in the SCORM Version 1.1 CSF. At least one
organization element is required for a SCORM Content
Aggregation Package. The organization element is not permitted
to be present for a SCORM Resource Package.
0 or more
Container
3.21
Identifier
An identifier, provided by an author or authoring tool, that is
unique within the Manifest.
1 and only
1
ID
3.22
Structure
Has a default value of “hierarchical” for describing the shape of
an organization.
0 or 1
String
(smallest
permitted
maximum:
200)
3.23
Title
Title of the organization.
ADL Note: This element replaces the <title> sub-element of the
outermost <block> element within the SCORM Version 1.1 CSF.
1 and only
1
String
(smallest
permitted
maximum:
200)
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>
16 <item identifier="ITEM5" identifierref="RESOURCE5" isvisible="false">
17 ....
40 </organization>
41 </organizations
Organization ->item: data model
3.2.4
Item
This element describes a node within the organization structure.
ADL Note: This element is used to represent <block> and <sco> elements that are defined in the
SCORM Version 1.1 CSF. The identifierref attribute is required to be empty (“”) for items that
represent <block> elements. A <block> element is just a container for other <block> elements and
<sco> elements and does not contain actual content and therefore does not need to reference a
resource. The identifierref attribute for items that represent <sco> elements is required to reference
a resource that defines a SCO.
The parameters attribute of this element replaces the <parameterString> SCORM Version 1.1 CSF
element.
0 or More
Container
3.2.4.1
Identifier
An identifier, provided by an author or authoring tool, that is unique within the Manifest.
1 and only 1
ID
3.2.4.2
Identifier
Ref
A reference to a <resource> identifier (within the same package or a submanifest) that is
0 or 1
String (smallest
permitted
maximum: 2000
characters)
3.2.4.3
Is Visible
Indicates whether or not the title of the item is displayed by the LMS navigation mechanism. If not
present, value is assumed to be “true”.
0 or 1
Boolean
3.2.4.4
Parameters
Static parameters to be passed to the content file at launch time. The parameters attribute of this
element replaces the <parameterString> SCORM Version 1.1 CSF element.
0 or 1
String (smallest
permitted
maximum: 1000
characters)
3.2.4.5
Title
Title of the item.
1 and only 1
String (smallest
permitted
maximum: 200
characters)
3.2.4.6
Item
A sub-node within this item. This is a sub-item and repeats all the parts of 3.2.4 Item.
0 or More
Container
used to resolve the ultimate location of the file. If no identifierref is supplied, it is assumed that
there is no content associated with this entry in the organization.
3.2.4.7
Metadata
This element contains context specific meta-data that is used to describe the item. If meta-data is provided, the
meta-data must be valid SCORM Content Aggregation Meta-data.
0 or 1
Container
3.2.4.7.1
Schema
Describes the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of “ADL SCORM”.
0 or 1
String (smallest
permitted
maximum: 100
characters)
3.2.4.7.2
Schema
Version
Describes the version of the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of “1.2”.
0 or 1
String (smallest
permitted
maximum: 20
characters)
3.2.4.7.3
Location
This element describes the location where the meta-data describing the organization may be found. This may be
a URI.
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model. If meta-data is
provided, the meta-data must be valid SCORM Content Aggregation Meta-data.
This element can be used to reference a file that contains the meta-data. Either the meta-data is included in-line
within the <metadata> element, or this element is used to provide the file location.
ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the content package
developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension mechanism.
0 or 1
String (smallest
permitted
maximum: 2000
characters)
3.2.4.7.4
{Metadata}
This is where meta-data is placed. If meta-data is provided, the meta-data must be valid SCORM Content
Aggregation Meta-data.
ADL Note: ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the content
package developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension mechanism.
3.2.4.8
Prerequi
sites
This element defines what other parts of the learning content must have been completed before
starting the Block/SCO. This allows an LMS to compute multiple paths through the learning content.
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model.
0 or
1
String (smallest permitted
maximum: 200)
3.2.4.8.1
Type
Defines the scripting language used to represent the prerequisites.
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model.
Vocabulary List:
aicc_script
0 or
1
Vocabulary (Restricted)
3.2.4.9
Max
Time
Allowe
d
This element defines the amount of time a student is allowed to have in the current attempt of the
SCO represented by the item.
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model.
This element is only allowed to exist if the parent item element is representing a SCO and not a Block.
This element was a sub-element of the <timeLimit> element defined within the SCORM Version 1.1
CSF. The <timeLimit> container element was removed.
0 or
1
Timespan
3.2.4.10
Time
Limit
Action
This element defines the action that should be taken when the max time allowed in the current
attempt of the SCO represented by the <item> is exceeded.
Vocabulary List:
exit,message
exit,no message
continue,message
continue,no message
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model.
This element is only allowed to exist if the parent item element is representing a SCO and not a Block.
This element was a sub-element of the <timeLimit> element defined within the SCORM Version 1.1
CSF. The <timeLimit> container element was removed.
0 or
1
Vocabulary (Restricted)
3.2.4.11
Data
From
LMS
This element provides a place for initialization data expected
by the SCO represented by the item after launch. This data is
unconstrained and undefined. Usage of this element is not yet
well defined and should be used with caution.
ADL Note: This is an ADL extension to the IMS Content
Packaging Information Model.
This element is only allowed to exist if the parent item element
is representing a SCO and not a Block. This element was a
sub-element of the <launch> element defined within the
SCORM Version 1.1 CSF. The <launch> container element
was removed.
0 or 1
String
(smallest
permitted
maximum:
255
characters)
3.2.4.12
Mastery
Score
This element establishes the passing score for this SCO
represented by the <item>. Note that what is considered a
passing score often depends on the context of a SCO within
the learning content. Some learning content may set the
mastery score for a SCO higher than in others.
The mastery score should be a normalized value between 0
and 100.
ADL Note: This is an ADL extension to the IMS Content
Packaging Information Model.
This element assumes that the SCO has some content that will
report score (such as a test) via the SCORM Run-Time
Environment API and data model defined in the SCORM.
This element is only allowed to exist if the parent item element
is representing a SCO and not a Block.
0 or 1
String
(smallest
permitted
maximum:
200)
3.2.5
Metadata
This element contains context specific meta-data that is used to describe the
organization. If meta-data is provided, the meta-data must be valid SCORM Content
Aggregation Meta-data.
0 or
1
Container
3.2.5.1
Schema
Describes the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of
“ADL SCORM”.
0 or
1
String
(smallest
permitted
maximum:
100
characters)
3.2.5.2
Schema
Version
Describes the version of the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of
“1.2”.
0 or
1
String
(smallest
permitted
maximum: 20
characters)
3.2.5.3
Location
This element describes the location where the meta-data describing the organization
may be found. This may be a URI.
0 or
1
String
(smallest
permitted
maximum:
2000
characters)
0 or
1
Inline Metadata Record
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model. If meta-data is
provided, the meta-data must be valid SCORM Content Aggregation Meta-data.
This element can be used to reference a file that contains the meta-data. Either the meta-data is
included in-line within the <metadata> element, or this element is used to provide the file location.
ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the content
package developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension mechanism.
3.2.5.4
{Metadata}
This is where meta-data is placed. If meta-data is provided, the meta-data must be
valid SCORM Content Aggregation Meta-data.
ADL Note: ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the
content package developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension mechanism.
resources
4.1
Resource
A reference to a resource.
0 or More
Container
4.1.1
Identifier
An identifier, provided by an author or authoring tool, that is unique within
the Manifest.
1 and only 1
ID
4.1.2
Type
A string that identifies the type of resource.
The only current type is “webcontent”, defined as content that can be
hosted in or launched by an Internet Browser. This includes:
HTML-based content
Content that requires plug-ins (e.g. Flash, Real Media)
Executables that are launched by a browser
1 and only 1
String
(smallest
permitted
maximum:
1000
characters)
4.1.3
Href
A reference to the “entry point” of this resource.
ADL Note: This value will be used as the launch location when Resources
are launched.
1 and only 1
String
(smallest
permitted
maximum:
2000
characters)
4.1.4
SCORM Type
Defines the type of the resource.
ADL Note: This is an ADL extension to the IMS Content Packaging
Information Model.
Vocabulary List:
sco
asset
1 and only 1
Vocabulary
(Restricted)
4.1.5
Metadata
This element contains context independent meta-data that is used to describe the resource. If
the Resource is a SCO, then the meta-data must be valid SCO Meta-data. If the Resource is
an Asset, then the meta-data must be valid Asset Meta-data. If the Resource is anything other
than a SCO or an Asset, then the meta-data must be valid IMS Learning Resource Meta-data.
0 or 1
Container
4.1.5.1
Schema
Describes the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of “ADL
SCORM”.
0 or 1
String (smallest
permitted
maximum: 100
characters)
4.1.5.2
Schema
Version
Describes the version of the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of “1.2”.
0 or 1
String (smallest
permitted
maximum: 20
characters)
4.1.5.3
Location
This element describes the location where the meta-data describing the organization may be
found. This may be a URI.
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model. If
the Resource is a SCO, then the meta-data must be valid SCO Meta-data. If the Resource is
an Asset, then the meta-data must be valid Asset Meta-data. If the Resource is anything other
than a SCO or an Asset, then the meta-data must be valid IMS Learning Resource Meta-data.
This element can be used to reference a file that contains the meta-data. Either the meta-data
is included in-line within the <metadata> element, or this element is used to provide the file
location.
0 or 1
String (smallest
permitted
maximum: 2000
characters)
4.1.5.4
{Meta-data}
This is where meta-data is placed. If the Resource is a SCO, then the meta-data must be valid
SCO Meta-data. If the Resource is an Asset, then the meta-data must be valid Asset Metadata. If the Resource is anything other than a SCO or an Asset, then the meta-data must be
valid IMS Learning Resource Meta-data.
ADL Note: ADL allows two mechanisms for placing meta-data in a manifest. The choice is
up to the content package developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension
mechanism.
4.1.6
File
Identifies one or more local files that this resource is dependent on.
ADL Note: This element can only be present if the parent resource element is describing a locally
referenced SCO or Asset. In the case of the file representing a SCO, the href value must refer to the launch
location of a SCO, and this value will be used to run the SCORM Run-Time Environment test.
0 or More
Container
4.1.6.1
Href
A reference to the location of this file.
0 or 1
String
(smallest
permitted
maximum:
2000
characters)
4.1.6.2
Metadat
a
This element contains context independent meta-data that is used to describe the file (Asset). If meta-data is
provided, the meta-data must be valid SCORM Asset Meta-data.
0 or 1
Container
4.1.6.2.1
Schema
Describes the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of “ADL SCORM”.
0 or 1
String
(smallest
permitted
maximum:
100
characters)
4.1.6.2.2
Schema
Version
Describes the version of the schema that defines the meta-data.
ADL Note: This element is optional, however if present it must contain the value of “1.2”.
0 or 1
String
(smallest
permitted
maximum:
20
characters)
4.1.6.2.3
Locatio
n
This element describes the location where the meta-data describing the file (Asset) may be found. This may
be a URI.
ADL Note: This is an ADL extension to the IMS Content Packaging Information Model. If meta-data is
provided, the meta-data must be valid SCORM Asset Meta-data.
This element can be used to reference a file that contains the meta-data. Either the meta-data is included inline within the <metadata> element, or this element is used to provide the file location.
ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the content package
developer.
Use the Location element to reference the location (internal or external to the package) or;
Place the meta-data directly into the imsmanifest using the appropriate XML extension mechanism.
0 or 1
String
(smallest
permitted
maximum:
2000
characters)
4.1.6.2.4
{Metadata}
This is where meta-data is placed. If meta-data is provided, the meta-data must be valid SCORM Asset
Meta-data.
ADL Note: ADL allows two mechanisms for placing meta-data in a manifest. The choice is up to the
content package developer.
0 or 1
Inline Metadata Record.
4.1.7.
Dependency
This element contains a
reference to a single
resource that can act as a
container for multiple
files that resources may
be dependent on.
0 or More
Empty
Element
4.1.7.1
Identifier Ref
A reference to the
resource.
1 and only
1
IDRef
Manifest….

Riferimento a sub-manifest