GB/T 36347-2018Information technology - Learning, education and training - Common cartridge for learning resources (English PDF)

3.1 Universal packaging

A learning resource content packaging standard that provides a uniform format for tagging, packaging, distributing, and accessing learning resources.

3.2 Universal package

A content package made and packaged in a universal package.

3.3 Dependent element

An element that marks a particular type of resource and some relationship between resource types.

3.4 Directory

The physical folder of the document in the content pack.

3.5 Exchange package

A collection of components exchanged between systems.

Note: When this standard uses "exchange package", it always includes a list of contents and can include content files and control files. All the texts contained in the exchange package The pieces are described in the content list. For a logical package, when all the components in the logical package are local to the exchange, the exchange is equivalent to the Logical package.

3.6 Runnable URI

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

Note: The URI that can be run cannot be parsed by the package reader. After processing the contents of the exchange package, the URI cannot be stored for other software components (for example, Web browser) use.

3.7 Learning module

A collection of learning content and/or application functions used to represent a learning activity or part of a learning activity.

3.8 Learning resource

Any entity that is digital or non-digital for learning, education, or training.

3.9 Local component

Any component of the logical package contained in the exchange package.

3.10 Material

All static text, images, or media objects that are provided to the user rather than being processed by the system.

3.11 Namespace

A set of names, each of which is unique and has a semantic value that is different from other names in the same group.

3.12 Package

A logical directory that contains a content list file with a specific name and the actual resource file referenced in the content manifest file.

3.13 Package exchange file

A file that can be exchanged by a package is a convenient form of structured information transmitted over a network.

3.14 Package reader

A software component that reads a list of content and verifies the contents of the exchange package.

Note: Package readers can handle logical packages (eg, retrieve and store information referenced by content lists, unpack local files from package exchange files, retrieve or log in The location of the remote file, etc.) or perform tasks on behalf of another software component.

3.15 Package writer

A software component that creates or modifies exchange package instances, assembly content files, and other files declared locally to the exchange package and Write the bound target exchange package or perform such tasks on behalf of other software components.

3.16 Item

A single question in a set of questions is the smallest exchangeable subject.

3.17 Question and test interoperability

A data exchange format for characterizing problems and test data and their corresponding results reports.

3.18 Relative reference

A URL that references a resource by describing an extension to the reference context.

Note: The extension and context combination constitute the target URI.

3.19 Remote component

Any component of a logical package that is outside the exchange package.

3.20 Target system

Import a learning package system or similar system for a generic package.

5.1 General Packaging Concept Diagram

Some of the features of a generic package are similar to the "packages" in existing commercial solutions. Conceptually, a universal package is available.

A package and its metadata that are integrated into the LMS learning environment. At the higher level, it can directly relate to the concept of "course" in LMS. correspond.

The conceptual model of the universal package is shown in Figure 1.

In the conceptual model diagram shown in Figure 1, a logical package is the representation of one or more available (or reusable) content units, including a list of content descriptions.

All components described, including local and external components incorporated by reference.

The logical package contains two parts. the exchange package and the external content.

---Exchange package. The main body of the learning content package specified in this standard is the exchange package, and the provider provides appropriate groups for various groups of people through exchange packages.

The learning content, the user exchanges relevant information through the exchange package. An exchange package is a collection of components exchanged between systems, including Content lists, learning application objects, package-level web content, and specific computer files. Its instance is a package exchange file, a package exchange file Is a compressed file, its implementation can be used, for example, zip, rar and jar and other common file compression formats, this standard does not stipulate What compression format is used by the body;

---External content. Several external components are defined in the conceptual model, indicating that the conceptual model defined in this standard will support the definition of new The vocabulary and structure of the extension mechanism.

5.2 Conceptual Model Description

5.2.1 Exchange package structure

The structure of the exchange package of the general package is shown in Figure 2.

The package exchange file consists of a large list of content such as a list of content, n learning application objects, and package-level web content.

a) Content list. manifest is a content list file. For manifest.*, if implemented in XML, then Manifest.xml. According to this standard, all content is defined in the content list file under the root directory, and no sub-content clearing is used.

A single, sub-content list refers to another complete list that is subordinate to the list.

b) Learning application objects. is any type of resource that requires additional information before being imported into the target system and further characterized Rational and explanation. Physically, a learning application object consists of a directory and subdirectories that are specific to the object in the content package. each The learning application object folder includes learning application object resources (presented in a descriptor file) and optional associated content.

1) Descriptor file. A file as an entry point for accessing information about a learning application object so that the learning application pair Like importing into the target system. The descriptor file is usually an XML file that conforms to the learning application based pair.

A specific file specification like the type. But in some cases, the file can also be a zip file or other structure.

Formatted documents. The descriptor file is not to be rendered in the target system, but to be imported when the generic package is imported. Standard system processing;

2) Associated content. is a resource type that contains a collection of files for a particular learning application object. Each quoted text The piece should exist in the directory containing the descriptor file of the learning application object associated with it, or any of its subfolders Under contents. Related content types include. folders, web content resources, web link resources, discussion topics Resources, assessment resources, associated content resources, in-package references, generic package-level metadata, question bank resources, and extensions Source, etc.

c) Package-level web content. A package-level web content folder can be included in a generic package. If the package level web content If the folder exists, it should be located in the root directory of the package. This standard does not define the name of the folder. Package-level web content The web content in the folder can be referenced by any of the learning application objects in the package. Allow this folder and its subfolders The file is referenced by a relative path, but the files in the folder are not allowed to reference a learning application object folder or its The files in the linked content folder.

5.2.2 Content Type

5.2.2.1 Folder

A folder is a simple collection of content items and subfolders in a specific order; the subfolders are nested folders, that is, Other folders. A content-based folder represents a way of presenting content that can be used to define how content is organized and presented to the school. Learner.

5.2.2.2 Resources/Web Content

Is a resource type. Web content can be all files that can be spread on the web, including HTML files, images, audio, and video.

Frequency and so on. HTML files can contain links to other web content files, either inside or outside the package.

5.2.2.3 Resources/Web Links

Is a resource type. The web link expresses the learning application object in the form of a standard HTTP link, which is expanded by adding a title.

The standard HTTP link. It also contains some properties that describe which window the resource is open in, as well as the other windows that are open. Sign, such as window size.

5.2.2.4 Resources/Discussion Topics

Is a resource type that is used to initiate a learning application object for a discussion activity. It represents a placeholder for discussion topics, for storage Generate initial information about the topic of the discussion, but not a link to an existing discussion topic on the external system. After importing LMS, I hope to use only Internal tools to generate a new discussion topic. Its properties include title, description, attachments, and more.

5.2.2.5 Resources/Assessment

Is a resource type. The evaluation class resource is an instance of the QTI evaluation and can include any type of problem supported by the generic package. Evaluation includes Attributes include, such as the number of attempts, time limits, and whether to allow extensions to be submitted.

5.2.2.6 Resources/Associated Content

The resource/associated content is an associated content resource of a specific learning application object under the "associated content" in the learning application object folder.

It is also a resource type that is a collection of files that are specific to a single learning application object.

The associated content resource contains the set of files used by a particular learning application object. Each file referenced exists in the contains associated with it The directory where the descriptor file of the application object is located or its subdirectory. In addition, each associated content resource is associated with one and only one specific Learn application object associations.

5.2.2.7 References in the package

In-package referencing is a way to implement associations, allowing learning application objects or package files to reference other files within this package.

5.2.2.8 Package Level Metadata

It is the metadata at the general package level, including the authorization, interface, description and other elements. Listed in the manifest.* file.

5.2.2.9 Resources/Question Bank

Is a resource type, its representation is the QTI object library instance. A maximum of one question bank is included in each general package. Can pack Includes all QTI questions supported by universal packaging. The item in the question bank is not available for any evaluation reference in the general package. Universal packaging supports at least the following questions.

---Multiple choice questions (single choice);

---Multiple choice questions (multiple choice);

--- Yes or no question;

--- Fill in the blank question (the answer box has only one correct answer);

--- Matching question (provides a single answer box, but also supports matching of "container" class components and regular expressions in the generic wrapper);

---Essay questions.

The item can be included only in a generic package or as part of an assessment resource or question bank resource. Usually, an item contains the following.

---The label/title of the item;

--- The text of the item (may include HTML, in-package references, URLs, styles, etc.);

---Answer options (may include HTML, in-package references, URLs, styles, images, video and audio, etc.);

---Item answer score;

---Feedback (may include HTML, in-package references, URLs, styles, images, video and audio, etc.);

--- Answer display settings;

--- Answer hints (may include HTML, in-package references, multiple URLs, styles, images, video and audio, etc.);

--- Item setting parameters (such as time, etc.);

--- Item metadata.

5.2.2.10 Resources/Extensions

Extended class resources are resources that provide complementary functionality and are not covered by this general package but are registered with CELTS.

5.2.3 Supported Resource Types

The resource types supported by the generic package are shown in Table 1.

6.1 General Packaging Information Model Structure

The structure of the general packaging information model is shown in Figure 3.

Note: Model components are represented by boxes in the diagram, and the relationships between components are represented by lines with arrows (solid diamonds indicate the starting point and dashed lines indicate possible extension relationships).

The starting point and ending point of the arrow and the connection point of the box are for the entire large frame. The English words in double angle brackets (< < >> in the figure indicate the component type, component The text below the type is an instance that is categorized into this class component.

The components of the generic packaging information model are divided into four types. container, value, unspecified, and characteristic.

a) Container. A container class component may contain one or more other container class components or other major classes of information models. s component. For example, the information carried in the instance component of the content list supports components in other types of containers, and also supports the large A component in a class. In the related description, this supported and supported relationship is called a parent and a child.

b) value. The component of this large class has no child components, ie it should not be a group in a large class such as container, value, unspecified or property.

Piece synthesis. A value class component is a child of a container class component, and its semantic value is within the semantic value of its parent class component.

c) unspecified. A component that is not currently accurate (alternate class) or a component that is considered unimportant. Class component not specified Can be a parent. Unspecified classes act as extension points for the information model.

d) Characteristic. The property class and its component instances are not explicitly shown in the figure. Feature class components are distributed across containers in. The information for such a component is the decorated class information for the container class component, which has no subordinate components. Feature class component is used to declare the content The quality or value of a class component is part of the intrinsic feature of the container class component or the container class building feature. Feature class components and The container class components that it modifies or actually describes are tightly coupled.

6.2 Information Model Components

6.2.1 Component Description Format

The components of the general category information such as containers, values, unspecified, and attribute classes in the general package information model are described in Table 2, that is, The definitions or descriptions of several descriptors at the beginning of the component's name and corresponding descriptors are described.

6.2.2 Information Model Component Description

6.2.2.1 Information Model Component Name and Type