ISO IEC TR 12785-3-2012 Information technology - Learning education and training - Content packaging - Part 3 Best practice and implementation guide《信息技术 学习 教育和.pdf

1、 Reference number ISO/IEC TR 12785-3:2012(E) ISO/IEC 2012TECHNICAL REPORT ISO/IEC TR 12785-3 First edition 2012-05-01Information technology Learning, education, and training Content packaging Part 3: Best practice and implementation guide Technologies de linformation Apprentissage, ducation et forma

2、tion Paquetage du contenu Partie 3: Meilleure pratique et guide de mise en application ISO/IEC TR 12785-3:2012(E) COPYRIGHT PROTECTED DOCUMENT ISO/IEC 2012 All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means, electron

3、ic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs member body in the country of the requester. ISO copyright office Case postale 56 CH-1211 Geneva 20 Tel. + 41 22 749 01 11 Fax + 41 22 749 09 47 E-mail copyrightiso.org

4、Web www.iso.org Published in Switzerland ii ISO/IEC 2012 All rights reservedISO/IEC TR 12785-3:2012(E) ISO/IEC 2012 All rights reserved iiiContents Page Foreword iv 0. Introduction . v 1 Scope 1 2 Normative references 1 3 Terms and definitions . 1 4 Abbreviated terms . 4 5 Using content packages Use

5、 cases and practices . 4 5.1 Typical practice . 4 5.2 Keeping control over resources after a package has been published 5 5.3 Aggregate content at an appropriate level of granularity . 6 5.4 Specialized packages with combination of various specifications . 8 5.5 Working with child-manifests and appl

6、ying IMS simple sequencing rules using the new IPointer mechanism 9 5.6 Packaging METS and other complex object encodings 10 5.7 Using alternative organization structures, such as topic maps . 12 5.8 Working with alternative resources . 13 5.9 Avoiding repeated lists of the same assets for different

7、 resources 15 5.10 Working with local and global identifiers . 17 5.11 Support for multiple languages in titles 17 Annex A (informative) Document provenance 19 Annex B (informative) Intellectual property acknowledgements . 20 Bibliography 21 ISO/IEC TR 12785-3:2012(E) iv ISO/IEC 2012 All rights rese

8、rvedForeword ISO (the International Organization for Standardization) and IEC (the International Electrotechnical Commission) form the specialized system for worldwide standardization. National bodies that are members of ISO or IEC participate in the development of International Standards through te

9、chnical committees established by the respective organization to deal with particular fields of technical activity. ISO and IEC technical committees collaborate in fields of mutual interest. Other international organizations, governmental and non-governmental, in liaison with ISO and IEC, also take

10、part in the work. In the field of information technology, ISO and IEC have established a joint technical committee, ISO/IEC JTC 1. International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2. The main task of the joint technical committee is to prepare In

11、ternational Standards. Draft International Standards adopted by the joint technical committee are circulated to national bodies for voting. Publication as an International Standard requires approval by at least 75 % of the national bodies casting a vote. In exceptional circumstances, when the joint

12、technical committee has collected data of a different kind from that which is normally published as an International Standard (“state of the art”, for example), it may decide to publish a Technical Report. A Technical Report is entirely informative in nature and shall be subject to review every five

13、 years in the same manner as an International Standard. Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. ISO shall not be held responsible for identifying any or all such patent rights. ISO/IEC TR 12785-3 was prepared by Joint Tech

14、nical Committee ISO/IEC JTC 1, Information technology, Subcommittee SC 36, Information technology for learning, education and training. ISO/IEC 12785 consists of the following parts, under the general title Information technology Learning, education, and training Content packaging: Part 1: Informati

15、on model Part 2: XML binding Part 3: Best practice and implementation guide Technical Report ISO/IEC TR 12785-3:2012(E) ISO/IEC 2012 All rights reserved v0. Introduction 0.1 Purpose and overview The primary focus of this part of ISO/IEC 12785 is on sharing existing best practice and providing sugges

16、ted practice for implementing the functionality included in this part of ISO/IEC 12785. The ISO/IEC 12785 series has been commonly used in the learning, education, and training (LET) domain and this part of ISO/IEC 12785 is intended to support this use. It focuses on the construction of instances of

17、 manifest documents and the content packages they define. 0.2 Compatibility Given the widespread adoption of IMS Content Packaging and the proliferation of hundreds of thousands of IMS content packages, it is important that existing software components continue to process content packages they were

18、designed to handle, and that new software components conforming to the ISO/IEC 12785 series also process the older IMS content packages as designed. Newer systems will need the ability to process the new extension objects 1 )introduced in the ISO/IEC 12785 series that enable linking and referencing

19、behaviors. The functionality of these new extension objects are described in Clause 5 of this part of ISO/IEC 12785, and normative descriptions are contained in ISO/IEC 12785-1. The new extension objects are defined in a separate namespace that leverages the extension points and semantics of the ISO

20、/IEC 12785 series without affecting the existing IMS Content Packaging namespace. ISO/IEC 12785 also separates the lists of vocabulary terms used by certain objects in the information model (and a dedicated new namespace) from the model itself. These details are contained in the IMS GLC Specificatio

21、n Development Note 11: Vocabulary Definition, Registration, and Maintenance Procedures. By taking this approach, we hope that the best of the past is preserved as it provides a strong foundation for future growth without having to alter the structural integrity of the ISO/IEC 12785-1 information mod

22、el (a detailed, normative description of backwards and forwards compatibility is contained in ISO/IEC 12785-1). 1) The extension refers to those elements that have been newly introduced with IMS Content Packaging version 1.2 which is a source of ISO/IEC 12785. TECHNICAL REPORT ISO/IEC TR 12785-3:201

23、2(E) ISO/IEC 2012 All rights reserved 1Information technology Learning, education, and training Content packaging Part 3: Best practice and implementation guide 1 Scope This part of ISO/IEC 12785 presents use cases and shows how they are satisfied by ISO/IEC 12785-1 which is derived from the IMS Glo

24、bal Learning Consortium (GLC) Content Packaging version 1.2 (v1.2). Though not exhaustive, the range of use cases presented in this part of ISO/IEC 12785 illustrate how the most common issues in the creation, management, and playback of learning material can be addressed by the ISO/IEC 12785 series.

25、 The use cases were contributed by various implementers and users of the IMS Content Packaging and are based on years of practice. 2 Normative references The following referenced documents are indispensable for the application of this document. For dated references, only the edition cited applies. F

26、or undated reference, the latest edition of the referenced document (including any amendments) applies. ISO/IEC 12785-1:2009, Information technology Learning, education, and training Content packaging Part 1: Information model IETF RFC 1951 (1996), DEFLATE Compressed Data Format Specification versio

27、n 1.3 3 Terms and definitions For purposes of this document, the following terms and definitions apply. 3.1 child manifest complete, subordinate manifest contained in or referenced by the parent manifest NOTE 1 According to IMS Content Packaging version 1.2 (and ISO/IEC 12785-1), a manifest can cont

28、ain more than one child manifest. NOTE 2 A manifest can include a reference to a child manifest that is external to the interchange package. NOTE 3 A child manifest describes a complete logical package that is part of the larger logical package defined by its parent manifest. NOTE 4 A child manifest

29、 can be local or remote. Adapted from ISO/IEC 12785-1:2009. ISO/IEC TR 12785-3:2012(E) 2 ISO/IEC 2012 All rights reserved3.2 content individual file or multiple files usable in learning, education and training NOTE 1 A logical unit of usable (and reusable) information can be described by a logical p

30、ackage. NOTE 2 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 Content files can be local or remote. 3.4 control fi

31、le single computer file that governs the binding of the Content Packaging Information Model (CPIM) to make it suitable for machine processing NOTE 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 b

32、ound 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. 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 t

33、echnology for learning, education and training (ITLET) purposes NOTE 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). ISO/IEC 12785-1:2009, 3.5 3.6 manifest descri

34、ption of files and any logical relationships between them, contained or referenced in a content package 3.7 metadata content packaging descriptive information about logical packages, logical organizations, content, and files NOTE 1 Metadata can be assigned to any of the components within the logical

35、 package including the manifest. NOTE 2 Any binding of a metadata object is permitted. Each object of metadata can be local or remote. ISO/IEC 12785-1:2009, 3.12 3.8 namespace XML namespace identified by a URI reference NOTE Namespace in Content Packaging follows W3C recommendation, Namespaces in XM

36、L 1.0 (Second Edition). ISO/IEC 12785-1:2009, 3.13 ISO/IEC TR 12785-3:2012(E) ISO/IEC 2012 All rights reserved 33.9 organization logical relationships, such as a hierarchical tree, among a unit of content NOTE More than one logical organization can be described in a manifest. 3.10 package unit of us

37、able (and reusable) LET content NOTE 1 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 A package is able to stand-alone, that is

38、, it contains all the information needed to use the contents for learning, education, and training when it has been unpacked. 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 organi

39、zation NOTE 1 A package reader can process both logical and physical packages. NOTE 2 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

40、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 pr

41、ocess 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 An interchange package may be instantiated in a format other than a package interchange fi

42、le (PIF). NOTE 2 The representation (binding) is usually expressed in XML. EXAMPLE An interchange package can be instantiated as a collection of files on removable media, e.g. CD, DVD, USB memory device, or compressed using another format such as .zip, .tar, .jar, .cab. ISO/IEC 12785-1:2009, 3.15 3.

43、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 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 mani

44、fest ISO/IEC TR 12785-3:2012(E) 4 ISO/IEC 2012 All rights reserved4 Abbreviated terms CPIM Content Packaging Information Model ITLET Information Technology for Learning, Education and Training LET Learning, Education, and Training LMS Learning Management System LOM Learning Object Metadata METS Meta

45、data Encoding and Transport Schema PIF Package Interchange File SCO Sharable Content Object SCORM Sharable Content Object Reference Model URI Uniform Resource Identifier (IETF RFC 3986) XML Extensible Markup Language (W3C XML) XSD XML Schema Definition 5 Using content packages Use cases and practice

46、s The use cases in this clause illustrate key functionalities of ISO/IEC 12785 by focusing on particular goals that users of the standard may have and then outlining how such goals can be achieved. The section is not exhaustive neither in illustrating all features of the standard nor in outlining al

47、l uses of a specific feature. 5.1 Typical practice Typically, a package contains all its resources in the PIF and uses a ZIP archive for its interchange format. It has only one manifest; no child-manifests are included. All content files are declared in the manifest and are included physically in th

48、e package. When material needs to be presented in more than one language or accessibility modality, two types of organization are contained in the manifest. Content packages that comply with the most popular content-packaging profile, ISO/IEC 29163 SCORM, also typically follow this simple pattern. S

49、imple content packages are likely to be most widely supported in various Learning Management System (LMS), and therefore, are the most robust in interoperability. ISO/IEC TR 12785-3:2012(E) ISO/IEC 2012 All rights reserved 5Table 1 Use case of the classic package Level: Primary use case Actors: Primary: Content authors 2 )Secondary: Content repositories Stakeholders: Content developers Interest: Content-development tool developers Basic flow of events: The content author creates required cont