ISO/IEC 12785-2:2011 情報技術—学習、教育、およびトレーニング—コンテンツパッケージング—パート2：XMLバインディング | ページ 2

3.1

binding

XML data binding

means of representing the information in an XML document

Note 1 to entry: See XML data binding of Wikipedia: http://en.wikipedia.org/wiki/XML_data_bindingxlink:type="simple" (retrieved November 18, 2009).

3.2

control file

single computer file that governs the binding of the Content Packaging Information Model 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.

3.3

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: logical package can contain one or more units of content.

3.4

logical package

representation of one or more units of usable (and reusable) 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.

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

3.5

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

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

3.8

organization

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

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

3.9

package

unit of usable (and reusable) content

Note 1 to entry: This can be part of a learning course that has instructional relevance outside of a 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.

3.10

resource

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

schema

XML Schema

description of a class of XML documents, expressed in terms of constraints on the structure and content of those documents

Note 1 to entry: For more information see http://www.w3c.org/XML/Schema.

Note 2 to entry: XML Schema in Content Packaging follows W3C recommendation XML Schema.

Note 3 to entry: The definition refers to the concept of a schema in an XML context, as well as a specific language for creating such schemas: the W3C XML Schema. The"IMS Content Packaging XML XSD" is an application of the W3C XML Schema language.

3.12

unit of content

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

3.13

XML validation

process whereby documents written in XML (eXtensible Markup Language) are verified against the defined structure

Note 1 to entry: Strict validation in XML means that it must follow the rules dictated by an XML schema.