ISO/IEC 12785-1:2009 情報技術—学習、教育、およびトレーニング—コンテンツパッケージング—パート1：情報モデル | ページ 6

3.1

child manifest

complete, subordinate manifest contained in parent manifest

Note 1 to entry: A manifest can contain one or more child manifests.

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.

Note 4 to entry: A child manifest can be local or remote.

cf. interchange package, local, logical package, manifest, remote

3.2

content file

computer file(s) that embodies the LET content described by the manifest

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

Note 2 to entry: Content will often contain more than one content file. For example, web content is often instantiated by HTML, JPEG, and CSS files. Content files can be local or remote.

cf. local, logical package, remote

3.3

content organization

organization

logical relationships, such as a hierarchical tree, among units of LET content

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

Note 2 to entry: An organization is bound to files through the relationship among item components and their referenced resource components of a manifest.

Note 3 to entry: The rules governing the structuring and ordering of a hierarchical tree need to be specified.

cf. resource

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.

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

cf. logical package, package interchange file

3.6

launchable URI

representation of a Universal Resource Locator (URL) that may be included in a resource description and that is used to locate and access the content described by the resource

Note 1 to entry: The launchable Uniform Resource Identifier (URI) is not meant to be resolved by a package reader.

cf. interchange package, package reader

3.7

LET content

content

logical unit to represent usable (and reusable) information contained in or related to learning, education, and training (LET) data in a formalized manner suitable for interpretation by human means

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 LET content.

cf. logical package

3.8

local

contained within the interchange package

cf. logical package, interchange package

3.9

logical package

representation of one or more units of usable (and reusable) LET content

Note 1 to entry: A logical package encompasses the full set of components described by the manifest and its child manifests, including the local components and the remote components included by reference.

cf. child manifest, local, manifest, remote

3.10

manifest

description of a complete instance of a logical package

Note 1 to entry: A manifest describes resources in the logical package, their organization and the locations of the associated content and control files.

Note 2 to entry: A manifest can contain references to components that are local or remote.

cf. local, logical package, remote

3.11

manifest document

manifest with contents that are structured according to various binding technologies

3.12

metadata

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

Note 1 to entry: Metadata can be assigned to any of the core structures 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.

cf. local, logical package, remote

3.13

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

3.14

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.

cf. interchange package, logical package

3.15

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 can be instantiated in a format other than a package interchange file (PIF).

Note 2 to entry: Usually the representation (binding) is expressed in XML.

cf. interchange package

3.16

package reader

software that reads a manifest and verifies the contents of an interchange package

Note 1 to entry: A package reader can also process a logical package (retrieve and store information referenced by the manifest, unpack local files from a PIF, retrieve or log addresses of remote files, etc.) or delegate that task to another software typed process.

cf. interchange package, logical package

3.17

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

cf. interchange package

3.18

referenced manifest

manifest or a component of a manifest that is referenced from within another manifest

Note 1 to entry: A manifest can reference an organization in another manifest.

Note 2 to entry: The manifest containing the component being referenced is called a referenced-manifest.

Note 3 to entry: A manifest can contain references to components that are local or remote.

cf. local, remote

3.19

relative reference

expression of a URI reference relative to the namespace of another hierarchical URI

Note 1 to entry: See IETF RFC 3986 (2005).

Note 2 to entry: The extension and the context are combined to create a target URI.

3.20

remote

located outside the interchange package

cf. interchange package, logical package

3.21

resource

description of a collection of content files used by the logical package

Note 1 to entry: The description can include metadata about the collection of LET content and resource files, a description of each of the files, and information about variant forms of the collection of files.

cf. logical package

Note 2 to entry: A resource is often used to describe a unit of LET content. When this is the case, the resource can contain a launchable URI for the LET content.

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

cf. launchable URI, local, remote

3.22

stand-alone resource

resource that allows a manifest to declare a relationship to another manifest in such a way that the related manifests are processed as separate but related data sets

Note 1 to entry: The related manifests can be contained within a single content package or accessible as an external URI addressable resource.

Note 2 to entry: Each manifest represents a stand-alone learning resource which can be aggregated with other learning resources to create arbitrarily rich learning experiences.

3.23

uniform resource identifier

URI

compact sequence of characters that identifies an abstract or physical resource

Note 1 to entry: See IETF RFC 3986 (2005).

3.24

uniform resource locator

URL

subset of URIs that provide a means of locating a resource by describing its primary access mechanism

Note 1 to entry: See (IETF RFC 3986 (2005).

3.25

variant

container for referencing and describing somewhat different LET content

Note 1 to entry: A particular resource can have variants of different formats and for different purposes.

Note 2 to entry: The listing of variants within a resource identifies alternative collections of files for the resource.

Note 3 to entry: Metadata is used to describe the intended uses of the original resource and the intended uses of the variants.

cf. metadata, resource