La presentazione è in caricamento. Aspetta per favore

La presentazione è in caricamento. Aspetta per favore

Content packaging Concetti principali Descrizione del package.

Presentazioni simili


Presentazione sul tema: "Content packaging Concetti principali Descrizione del package."— Transcript della presentazione:

1 Content packaging Concetti principali Descrizione del package

2 bookshelf SCORM

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

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

5 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). 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).

6 SCORM definisce per cp: Content Structure definisce il meccanismo con il quale aggregare risorse in una unità (e.g., course, chapter, module, etc.) ; prende il posto del presedente e deprecato formato CDF (course description format) Content Structure definisce il meccanismo con il quale aggregare risorse in una unità (e.g., course, chapter, module, etc.) ; prende il posto del presedente e deprecato formato CDF (course description format) IMS Package Description descrive la struttura generale del sistema di packaging IMS Package Description descrive la struttura generale del sistema di packaging SCORM Content Packaging Information Model definisce il modello IMS Content Packaging Specification con in aggiunta le specifiche SCORM necessarie (principalmente sezione “organization” ). SCORM Content Packaging Information Model definisce il modello IMS Content Packaging Specification con in aggiunta le specifiche SCORM necessarie (principalmente sezione “organization” ). SCORM Content Package XML Binding “ how to encode the information model into an XML document” SCORM Content Package XML Binding “ how to encode the information model into an XML document” SCORM Content Packaging Application Profiles definisce specificatamente come creare aggregazioni di contenuti SCORM SCORM Content Packaging Application Profiles definisce specificatamente come creare aggregazioni di contenuti SCORM

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

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

9 Descrizione del package Package Interchange File x.htmPip.gifRes.doc… Fi.dwgPino.doca.html… …………… …………… Physical files Manifest File metadata organizations resources (sub)Manifest(s) 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 Meta-data sono descrittori della risorsa nella sua interezza, possono anche descrivere (al loro livello) organizations e resources organizations serve a strutturare il contenuto, generalmente come tassonomia gerarchica di apprendimento Resources può descrivere risorse esterne o gli stessi files della sezione ‘physical files’ Physical Files files indicati dalla sezione resources, interni o esterni (URL) Package Interchange Files è l’insieme dei files compressi (zip, arj, etc) con estensione.PIF, sistema standard di scambio materiali tra piattaforme

10 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 - META-DATA... course meta-data (title, keywords, etc.) - ORGANIZATION... a description of the course sequencing - RESOURCES... a names, resource meta-data and location of the files used in the course

11 Manifest map

12 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.

13 Manifest: general rules

14 Data model NrNameExplanationMultiplicityData Type 1 ManifestThe first, outermost element in the Manifest encloses all the reference data. Subsequent occurrences of the elements inside the outermost are used to compartmentalize files, meta-data, and organization structure for aggregation, disaggregation, and reuse. All namespace declarations should be declared inside the element. 1 and only 1Container 1.1 IdentifierAn identifier, provided by an author or authoring tool, that is unique within the Manifest. 1 and only 1ID 1.2 VersionIdentifies the version of the Manifest.1 and only 1String (smallest permitted maximum: 20 characters)

15 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: Example: - -

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

17 Metadata: data model 2 MetadataThis 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 1Container 2.1 SchemaDescribes the schema that defines the meta-data. This element is optional, however if present it must contain the value of “ADL SCORM”. 0 or 1String (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 1String (smallest permitted maximum: 20 characters) 2.3 LocationThis 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 in- line within the 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 1String (smallest permitted maximum: 2000 characters) 2.4 {Meta- data} 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 1Inline Meta-data Record

18 Metadata: binding Data Type: This element is a container element and only contains other elements. Multiplicity: The element may occur 0 or 1 time within the element. Attributes:  None Elements:   IMS Meta-data Example: 1 2 ADL SCORM Simple Manifest

19 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 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

20 3 OrganizationsDescribes 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 DefaultIdentifies 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 1IDRef

21 Organizations: data model 3.2 OrganizationThis 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 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 moreContainer 3.21 IdentifierAn identifier, provided by an author or authoring tool, that is unique within the Manifest. 1 and only 1 ID 3.22 StructureHas a default value of “hierarchical” for describing the shape of an organization. 0 or 1String (smallest permitted maximum: 200) 3.23 TitleTitle of the organization. ADL Note: This element replaces the sub-element of the outermost element within the SCORM Version 1.1 CSF. 1 and only 1 String (smallest permitted maximum: 200)

22 Organizations: binding Multiplicity: The organizations element may occur 0 or 1 time within a element. Attributes: default (required). Identifies the default organization to use. Data type = IDRef. Elements: Example: default 4 5 Lesson Introduction Content Summary

23 Organization ->item: data model ItemThis element describes a node within the organization structure. ADL Note: This element is used to represent and elements that are defined in the SCORM Version 1.1 CSF. The identifierref attribute is required to be empty (“”) for items that represent elements. A element is just a container for other elements and elements and does not contain actual content and therefore does not need to reference a resource. The identifierref attribute for items that represent elements is required to reference a resource that defines a SCO. The parameters attribute of this element replaces the SCORM Version 1.1 CSF element. 0 or MoreContainer IdentifierAn identifier, provided by an author or authoring tool, that is unique within the Manifest.1 and only 1ID Identifier Ref A reference to a identifier (within the same package or a submanifest) that is 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. 0 or 1String (smallest permitted maximum: 2000 characters) Is VisibleIndicates 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 1Boolean ParametersStatic parameters to be passed to the content file at launch time. The parameters attribute of this element replaces the SCORM Version 1.1 CSF element. 0 or 1String (smallest permitted maximum: 1000 characters) TitleTitle of the item.1 and only 1String (smallest permitted maximum: 200 characters) ItemA sub-node within this item. This is a sub-item and repeats all the parts of Item.0 or MoreContainer

24 MetadataThis 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 1Container SchemaDescribes 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 1String (smallest permitted maximum: 100 characters) 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 1String (smallest permitted maximum: 20 characters) LocationThis 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 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 1String (smallest permitted maximum: 2000 characters) {Meta- data} 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.

25 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) TypeDefines 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) 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 element defined within the SCORM Version 1.1 CSF. The container element was removed. 0 or 1 Timespan 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 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 element defined within the SCORM Version 1.1 CSF. The container element was removed. 0 or 1 Vocabulary (Restricted)

26 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 element defined within the SCORM Version 1.1 CSF. The container element was removed. 0 or 1String (smallest permitted maximum: 255 characters) Mastery Score This element establishes the passing score for this SCO represented by the. 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 1String (smallest permitted maximum: 200)

27 3.2.5 MetadataThis 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 SchemaDescribes 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) 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) LocationThis 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 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) {Meta- data} 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. 0 or 1 Inline Meta- data Record

28 resources

29 4.1 ResourceA reference to a resource.0 or MoreContainer IdentifierAn identifier, provided by an author or authoring tool, that is unique within the Manifest. 1 and only 1ID TypeA 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 1String (smallest permitted maximum: 1000 characters) HrefA 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 1String (smallest permitted maximum: 2000 characters) SCORM TypeDefines 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 1Vocabulary (Restricted)

30

31 4.1.5 MetadataThis 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 1Container SchemaDescribes 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 1String (smallest permitted maximum: 100 characters) 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 1String (smallest permitted maximum: 20 characters) LocationThis 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 element, or this element is used to provide the file location. 0 or 1String (smallest permitted maximum: 2000 characters) {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 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. 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.

32 4.1.6 FileIdentifies 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 MoreContainer HrefA reference to the location of this file.0 or 1String (smallest permitted maximum: 2000 characters) 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 1Container SchemaDescribes 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 1String (smallest permitted maximum: 100 characters) 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 1String (smallest permitted maximum: 20 characters) 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 in- line within the 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 1String (smallest permitted maximum: 2000 characters) {Meta- data} 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.  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 1Inline Meta- data Record.

33 DependencyThis 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 MoreEmpty Element Identifier RefA reference to the resource. 1 and only 1 IDRef

34 Manifest…. Riferimento a sub-manifest Riferimento a sub-manifest


Scaricare ppt "Content packaging Concetti principali Descrizione del package."

Presentazioni simili


Annunci Google