ISO/IEC TR 12785-3:2012 情報技術—学習、教育、およびトレーニング—コンテンツパッケージング—パート3：ベストプラクティスと実装ガイド | ページ 6

3.1

child manifest

complete, subordinate manifest contained in or referenced by the parent manifest

Note 1 to entry: According to IMS Content Packaging version 1.2 (and ISO/IEC 12785-1), a manifest can contain more than one child manifest.

Note 2 to entry: A manifest can include a reference to a child manifest that is external to the interchange package.

Note 3 to entry: A child manifest describes a complete logical package that is part of the larger logical package defined by its parent manifest.

3.2

content

individual file or multiple files usable in learning, education and training

Note 1 to entry: A logical unit of usable (and reusable) information can be described by a logical package.

Note 2 to entry: A logical package can contain one or more units of content.

3.3

content file

collection of files, including at least one manifest file, and conforming to the ISO/IEC 12785-1 information model and the ISO/IEC 12785-2 XML binding

Note 1 to entry: Content files can be local or remote.

3.4

control file

single computer file that governs the binding of the Content Packaging Information Model (CPIM) to make it suitable for machine processing

Note 1 to entry: A software component can refer to a control file when assessing the validity of a bound instance of the information model or to guide the creation of a bound instance of the information model. For example, a file containing an XML schema can be used as a control file for an XML binding of a manifest.

[SOURCE: ISO/IEC 12785-1:2009, 3.4]

3.5

interchange package

set of usable (reusable) LET content that is exchanged among computing systems used for information technology for learning, education and training (ITLET) purposes

Note 1 to entry: An interchange package can be instantiated in a single compressed binary file (package interchange file) or as a collection of files on portable media (e.g. CD, DVD, USB memory device).

[SOURCE: ISO/IEC 12785-1:2009, 3.5]

3.6

manifest

description of files and any logical relationships between them, contained or referenced in a content package

3.7

metadata

descriptive information about logical packages, logical organizations, content, and files

Note 1 to entry: Metadata can be assigned to any of the components within the logical package including the manifest.

Note 2 to entry: Any binding of a metadata object is permitted. Each object of metadata can be local or remote.

[SOURCE: ISO/IEC 12785-1:2009, 3.12]

3.8

namespace

XML namespace identified by a URI reference

Note 1 to entry: Namespace in Content Packaging follows W3C recommendation, Namespaces in XML 1.0 (Second Edition).

[SOURCE: ISO/IEC 12785-1:2009, 3.13]

3.9

organization

logical relationships, such as a hierarchical tree, among a unit of content

Note 1 to entry: More than one logical organization can be described in a manifest.

3.10

package

unit of usable (and reusable) LET content

Note 1 to entry: This can be part of a learning course that has instructional relevance outside of a LET content aggregation and can be delivered independently, as an entire learning course or as a collection of learning courses.

Note 2 to entry: A package is able to stand-alone, that is, it contains all the information needed to use the contents for learning, education, and training when it has been unpacked.

[SOURCE: ISO/IEC 12785-1:2009, 3.14]

3.11

package reader

software that processes an interchange package by checking statements in the manifest against corresponding contents and organization

Note 1 to entry: A package reader can process both logical and physical packages.

Note 2 to entry: The term “process” may include the retrieval and storage of information referenced by the manifest, the decompression or unpacking of local files from a PIF, and the retrieval and/or logging of addresses of remote files

3.12

package writer

software that creates or modifies an instance of an interchange package and assembles content file(s) and other files declared local to the interchange package and writes them to the targeted interchange package binding, or delegates those tasks to another software typed process

[SOURCE: ISO/IEC 12785-1:2009, 3.17]

3.13

package interchange file

PIF

instantiation of an interchange package which is physically encapsulated as a compressed binary file conforming to IETF RFC 1951 (1996)

Note 1 to entry: An interchange package may be instantiated in a format other than a package interchange file (PIF).

Note 2 to entry: The representation (binding) is usually expressed in XML.

[SOURCE: ISO/IEC 12785-1:2009, 3.15]

3.14

resource (in content packaging)

one URL entry point and zero or more references to files that are required before the content is launched

Note 1 to entry: The files described by a resource can be local or remote.

3.15

unit of content

either a file or a grouping of files which can be represented within a manifest