1484 13 1 2012 ieee standard for learning technology conceptual model for resource aggregation for l by Jinghua

IEEE Standard for Learning Technology— Conceptual Model for Resource Aggregation for Learning, Education, and Training

IEEE Computer Society

Sponsored by the Learning Technology Standards Committee

IEEE 3 Park Avenue New York, NY 10016-5997 USA

IEEE Std 1484.13.1™-2012

29 June 2012

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1â&#x201E;˘-2012

IEEE Standard for Learning Technologyâ&#x20AC;&#x201D; Conceptual Model for Resource Aggregation for Learning, Education, and Training Sponsor

Learning Technology Standards Committee of the

IEEE Computer Society Approved 29 March 2012

IEEE-SA Standards Board

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Permissions Scope notes for the object properties dcterms:hasPart and dcterms:isPartOf in 8.2 and 8.6, respectively, are reprinted with permission from Dublin Core™ Metadata Initiative Recommendation (10 November 2010), DCMI Metadata Terms, http://dublincore.org/ documents/ 2010/10/11/dcmi-terms/. Copyright © 2010. Dublin Core Metadata Initiative http://www.dublincore.org/about/copyright/. Licensed under http://creativecommons.org/ licenses/ by/3.0/. The graphics legends shown in Figure F.1 and Figure G.1 in Annex F and Annex G, respectively, are reprinted with permission from Revelytix, Inc. © 2006–2012.

Abstract: A conceptual model for interpreting externalized representations of digital aggregations of resources for learning, education, and training is defined. The conceptual model is defined as an ontology. Internal compositions and uses of digital resources are not specified nor are processing methods for resource aggregations. Keywords: aggregation format, conceptual model, content aggregation, digital aggregation, digital resource, IEEE 1484.13.1, resource aggregation, resource aggregation format

•

The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright © 2012 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 29 June 2012. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent & Trademark Office, owned by The Institute of Electrical and Electronics Engineers, Incorporated. Dublin Core is a trademark of the Dublin Core Metadata Initiative Limited (USPTO 2519654). Knoodl is a registered trademark of Revelytix, Inc. W3C is a registered trademark of the World Wide Web Consortium (registered in numerous countries). Marks of W3C are registered and held by its host institutions: Massachusetts Institute of Technology (MIT), European Research Consortium for Information and Mathematics (ERCIM), and Keio University, Japan. PDF: Print:

ISBN 978-0-7381-7243-9 ISBN 978-0-7381-7244-6

STD97230 STDPD97230

IEEE prohibits discrimination, harassment, and bullying. For more information, visit http://www.ieee.org/web/aboutus/whatis/policies/p9-26.html. No part of this publication may be reproduced in any form, in an electronic retrieval system or otherwise, without the prior written permission of the publisher.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Notice and Disclaimer of Liability Concerning the Use of IEEE Documents: IEEE Standards documents are developed within the IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (IEEE-SA) Standards Board. IEEE develops its standards through a consensus development process, approved by the American National Standards Institute, which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and serve without compensation. While IEEE administers the process and establishes rules to promote fairness in the consensus development process, IEEE does not independently evaluate, test, or verify the accuracy of any of the information or the soundness of any judgments contained in its standards. Use of an IEEE Standard is wholly voluntary. IEEE disclaims liability for any personal injury, property or other damage, of any nature whatsoever, whether special, indirect, consequential, or compensatory, directly or indirectly resulting from the publication, use of, or reliance upon any IEEE Standard document. IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and expressly disclaims any express or implied warranty, including any implied warranty of merchantability or fitness for a specific purpose, or that the use of the material contained in its standards is free from patent infringement. IEEE Standards documents are supplied "AS IS." The existence of an IEEE Standard does not imply that there are no other ways to produce, test, measure, purchase, market, or provide other goods and services related to the scope of the IEEE standard. Furthermore, the viewpoint expressed at the time a standard is approved and issued is subject to change brought about through developments in the state of the art and comments received from users of the standard. Every IEEE standard is subjected to review at least every ten years. When a document is more than ten years old and has not undergone a revision process, it is reasonable to conclude that its contents, although still of some value, do not wholly reflect the present state of the art. Users are cautioned to check to determine that they have the latest edition of any IEEE standard. In publishing and making its standards available, IEEE is not suggesting or rendering professional or other services for, or on behalf of, any person or entity. Nor is IEEE undertaking to perform any duty owed by any other person or entity to another. Any person utilizing any IEEE Standards document, should rely upon his or her own independent judgment in the exercise of reasonable care in any given circumstances or, as appropriate, seek the advice of a competent professional in determining the appropriateness of a given IEEE standard. Translations: The IEEE consensus development process involves the review of documents in English only. In the event that an IEEE standard is translated, only the English version published by IEEE should be considered the approved IEEE standard. Official Statements: A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered the official position of IEEE or any of its committees and shall not be considered to be, nor be relied upon as, a formal position of IEEE. At lectures, symposia, seminars, or educational courses, an individual presenting information on IEEE standards shall make it clear that his or her views should be considered the personal views of that individual rather than the formal position of IEEE. Comments on Standards: Comments for revision of IEEE Standards documents are welcome from any interested party, regardless of membership affiliation with IEEE. However, IEEE does not provide consulting information or advice pertaining to IEEE Standards documents. Suggestions for changes in documents should be in the form of a proposed change of text, together with appropriate supporting comments. Since IEEE standards represent a consensus of concerned interests, it is important to ensure that any responses to comments and questions also receive the concurrence of a balance of interests. For this reason, IEEE and the members of its societies and Standards Coordinating Committees are not able to provide an instant response to comments or questions except in those cases where the matter has previously been addressed. Any person who would like to participate in evaluating comments or revisions to an IEEE standard is welcome to join the relevant IEEE working group at http://standards.ieee.org/develop/wg/. Comments on standards should be submitted to the following address: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA Photocopies: Authorization to photocopy portions of any individual standard for internal or personal use is granted by The Institute of Electrical and Electronics Engineers, Inc., provided that the appropriate fee is paid to Copyright Clearance Center. To arrange for payment of licensing fee, please contact Copyright Clearance Center, Customer Service, 222 Rosewood Drive, Danvers, MA 01923 USA; +1 978 750 8400. Permission to photocopy portions of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Notice to users Laws and regulations Users of IEEE Standards documents should consult all applicable laws and regulations. Compliance with the provisions of any IEEE Standards document does not imply compliance to any applicable regulatory requirements. Implementers of the standard are responsible for observing or referring to the applicable regulatory requirements. IEEE does not, by the publication of its standards, intend to urge action that is not in compliance with applicable laws, and these documents may not be construed as doing so.

Copyrights This document is copyrighted by the IEEE. It is made available for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private selfregulation, standardization, and the promotion of engineering practices and methods. By making this document available for use and adoption by public authorities and private users, the IEEE does not waive any rights in copyright to this document.

Updating of IEEE documents Users of IEEE Standards documents should be aware that these documents may be superseded at any time by the issuance of new editions or may be amended from time to time through the issuance of amendments, corrigenda, or errata. An official IEEE document at any point in time consists of the current edition of the document together with any amendments, corrigenda, or errata then in effect. In order to determine whether a given document is the current edition and whether it has been amended through the issuance of amendments, corrigenda, or errata, visit the IEEE-SA Website at http://standards.ieee.org/index.html or contact the IEEE at the address listed previously. For more information about the IEEE Standards Association or the IEEE standards development process, visit IEEE-SA Website at http://standards.ieee.org/index.html.

Errata Errata, if any, for this and all other standards can be accessed at the following URL: http://standards.ieee.org/findstds/errata/index.html. Users are encouraged to check this URL for errata periodically.

Patents Attention is called to the possibility that implementation of this standard may require use of subject matter covered by patent rights. By publication of this standard, no position is taken by the IEEE with respect to the existence or validity of any patent rights in connection therewith. If a patent holder or patent applicant has filed a statement of assurance via an Accepted Letter of Assurance, then the statement is listed on the IEEE-SA Website at http://standards.ieee.org/about/sasb/patcom/patents.html. Letters of Assurance may indicate whether the Submitter is willing or unwilling to grant licenses under patent rights without compensation or under reasonable rates, with reasonable terms and conditions that are demonstrably free of any unfair discrimination to applicants desiring to obtain such licenses.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Essential Patent Claims may exist for which a Letter of Assurance has not been received. The IEEE is not responsible for identifying Essential Patent Claims for which a license may be required, for conducting inquiries into the legal validity or scope of Patents Claims, or determining whether any licensing terms or conditions provided in connection with submission of a Letter of Assurance, if any, or in any licensing agreements are reasonable or non-discriminatory. Users of this standard are expressly advised that determination of the validity of any patent rights, and the risk of infringement of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Participants At the time this IEEE standard was completed, the Resource Aggregation Models for Learning, Education, and Training (RAMLET) Working Group had the following membership: Kerry Blinco, Chair Scott Lewis, Technical Editor Nancy Hoebelheinrich

Willem Kraan

Katrien Verbert

The following members of the individual balloting committee voted on this standard. Balloters may have voted for approval, disapproval, or abstention. Charles Barest Kerry Blinco Mitchell Bonnett Keith Chow Geoffrey Darnton Ryan Dellolio David Fuschi Randall Groves Rutger A. Heunks Nancy Hoebelheinrich

Werner Hoelzl Don Holmes Noriyuki Ikeuchi Mark Jaeger Piotr Karocki Fanny Klett Willem Kraan Susan Land Greg Luri David Massart Michael S. Newman

Daniel Rehak Tyde Richards Bartien Sayogo Gil Shultz Steven Smith Thomas Starai Gerald Stueve Marcy Stutzman Katrien Verbert John Vergis

When the IEEE-SA Standards Board approved this standard on 29 March 2012, it had the following membership: Richard H. Hulett, Chair John Kulick, Vice Chair Robert M. Grow, Past Chair Satish Aggarwal Masayuki Ariyoshi Peter Balma William Bartley Ted Burse Clint Chaplin Wael Diab Jean-Philippe Faure

Alexander Gelman Paul HouzĂŠ Jim Hughes Young Kyun Kim Joseph L. Koepfinger* David J. Law Thomas Lee Hung Ling

Oleg Logvinov Ted Olsen Gary Robinson Jon Walter Rosdahl Mike Seavey Yatin Trivedi Phil Winston Yu Yuan

*Member Emeritus

Also included are the following nonvoting IEEE-SA Standards Board liaisons: Richard DeBlasio, DOE Representative Michael Janezic, NIST Representative Julie Alessi IEEE Standards Program Manager, Document Development Michael D. Kipness IEEE Standards Program Manager, Technical Program Development

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Introduction This introduction is not part of IEEE Std 1484.13.1-2012, IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training.

This standard defines a conceptual model for interpreting externalized representations of digital aggregations of resources for learning, education, and training. The conceptual model is defined as an ontology. Internal compositions and uses of digital resources are not specified nor are processing methods for resource aggregations.

Acknowledgments The Resource Aggregation Models for Learning, Education, and Training (RAMLET) Working Group would like to thank the following people for their contributions and comments during the formative stages of this standard: Andy Heath, Rolf Lindner, Claude Ostyn, Daniel Rehak, Tyde Richards, Robby Robson, Christian Stracke, and Rob Wolfe. The Working Group would also like to thank Revelytix, Inc., for making available the Knoodl® ontology tools that were used to aid in the development and maintenance of the ontology files and to create the graphical representations in Annex G and Annex H. a

Knoodl is a registered trademark of Revelytix, Inc. This information is given for the convenience of users of this standard and does not constitute an endorsement by the IEEE of these products. Equivalent products may be used if they can be shown to lead to the same results.

vii

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Contents 1. Overview .................................................................................................................................................... 1 1.1 Scope ................................................................................................................................................... 1 1.2 Purpose ................................................................................................................................................ 1 2. Normative references.................................................................................................................................. 2 3. Definitions, acronyms, and abbreviations .................................................................................................. 2 3.1 Definitions ........................................................................................................................................... 2 3.2 Acronyms and abbreviations ............................................................................................................... 5 4. Special terms .............................................................................................................................................. 7 5. Class and property prefix definitions.......................................................................................................... 7 6. Conformance .............................................................................................................................................. 7 6.1 Conforming aggregation instances ...................................................................................................... 8 6.2 Conforming bindings ........................................................................................................................... 8 6.3 Conforming mappings ......................................................................................................................... 8 6.4 Conforming extensions of the core ontology....................................................................................... 8 6.5 Conforming transforming implementations......................................................................................... 8 7. Conceptual modelâ&#x20AC;&#x201D;classes........................................................................................................................ 9 7.1 ramlet:administrativeDescriptorObject................................................................................................ 9 7.2 ramlet:admRef ..................................................................................................................................... 9 7.3 ramlet:aggregationID......................................................................................................................... 10 7.4 ramlet:aggregationSchema ................................................................................................................ 10 7.5 ramlet:aggregationSchemaVersion.................................................................................................... 11 7.6 ramlet:aggregationType..................................................................................................................... 11 7.7 ramlet:alternateID.............................................................................................................................. 11 7.8 ramlet:altResourceRef ....................................................................................................................... 12 7.9 ramlet:anchor ..................................................................................................................................... 12 7.10 ramlet:anchorType........................................................................................................................... 13 7.11 ramlet:assertion................................................................................................................................ 13 7.12 ramlet:beginPoint............................................................................................................................. 14 7.13 ramlet:cardinalityLabel.................................................................................................................... 14 7.14 ramlet:checksum.............................................................................................................................. 14 7.15 ramlet:checksumType...................................................................................................................... 15 7.16 ramlet:choice ................................................................................................................................... 15 7.17 ramlet:componentTarget.................................................................................................................. 16 7.18 ramlet:condition............................................................................................................................... 16 7.19 ramlet:coordinates ........................................................................................................................... 16 7.20 ramlet:creationDate ......................................................................................................................... 17 7.21 ramlet:defaultSelection .................................................................................................................... 17 7.22 ramlet:descriptiveDescriptorObject ................................................................................................. 18 7.23 ramlet:descriptiveRef....................................................................................................................... 18 7.24 ramlet:descriptorObject ................................................................................................................... 18 7.25 ramlet:descriptorTypeIndicator ....................................................................................................... 20 7.26 ramlet:digitalResource..................................................................................................................... 20 7.27 ramlet:digitalResourceFragment...................................................................................................... 20 7.28 ramlet:dynamicStructure.................................................................................................................. 21 7.29 ramlet:dynamicStructureID ............................................................................................................. 21

viii

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

7.30 ramlet:dynamicStructureType ......................................................................................................... 22 7.31 ramlet:elementID ............................................................................................................................. 22 7.32 ramlet:encodingType ....................................................................................................................... 23 7.33 ramlet:endPoint................................................................................................................................ 23 7.34 ramlet:except ................................................................................................................................... 24 7.35 ramlet:extent .................................................................................................................................... 24 7.36 ramlet:false ...................................................................................................................................... 24 7.37 ramlet:fileDescriptor........................................................................................................................ 25 7.38 ramlet:fileSize.................................................................................................................................. 25 7.39 ramlet:functionalResourceGroup..................................................................................................... 26 7.40 ramlet:generatingTool...................................................................................................................... 26 7.41 ramlet:generatingToolVersion ......................................................................................................... 26 7.42 ramlet:groupingID ........................................................................................................................... 27 7.43 ramlet:hasOrder ............................................................................................................................... 27 7.44 ramlet:hasRank ................................................................................................................................ 28 7.45 ramlet:humanLanguage ................................................................................................................... 28 7.46 ramlet:icon ....................................................................................................................................... 29 7.47 ramlet:identifierType ....................................................................................................................... 29 7.48 ramlet:intendedUse .......................................................................................................................... 29 7.49 ramlet:interfaceDefLink .................................................................................................................. 30 7.50 ramlet:intraAggregationLink ........................................................................................................... 30 7.51 ramlet:inventory............................................................................................................................... 31 7.52 ramlet:localRef ................................................................................................................................ 31 7.53 ramlet:locator................................................................................................................................... 32 7.54 ramlet:locatorDescriptor .................................................................................................................. 32 7.55 ramlet:maxSelections....................................................................................................................... 33 7.56 ramlet:mimeType............................................................................................................................. 33 7.57 ramlet:minSelections ....................................................................................................................... 34 7.58 ramlet:modificationDate .................................................................................................................. 34 7.59 ramlet:nodeID.................................................................................................................................. 34 7.60 ramlet:nodeVisibility ....................................................................................................................... 35 7.61 ramlet:note ....................................................................................................................................... 35 7.62 ramlet:parallel.................................................................................................................................. 36 7.63 ramlet:party...................................................................................................................................... 36 7.64 ramlet:partyEmail ............................................................................................................................ 37 7.65 ramlet:partyName ............................................................................................................................ 37 7.66 ramlet:partyRole .............................................................................................................................. 37 7.67 ramlet:partyType ............................................................................................................................. 38 7.68 ramlet:partyURI............................................................................................................................... 38 7.69 ramlet:provenance ........................................................................................................................... 39 7.70 ramlet:remoteDescriptorObject ....................................................................................................... 39 7.71 ramlet:remoteNode .......................................................................................................................... 39 7.72 ramlet:remoteResource .................................................................................................................... 40 7.73 ramlet:remoteTopNode.................................................................................................................... 40 7.74 ramlet:require................................................................................................................................... 41 7.75 ramlet:resourceAggregation ............................................................................................................ 41 7.76 ramlet:resourceGroup ...................................................................................................................... 41 7.77 ramlet:resourceIntraAggregationLink ............................................................................................. 42 7.78 ramlet:resourceProcessing ............................................................................................................... 42 7.79 ramlet:resourceProcessingAlgorithm............................................................................................... 43 7.80 ramlet:resourceProcessingBehavior................................................................................................. 43 7.81 ramlet:resourceProcessingKey......................................................................................................... 44 7.82 ramlet:resourceProcessingSet .......................................................................................................... 44 7.83 ramlet:resourceProcessingType ....................................................................................................... 45 7.84 ramlet:resourceType ........................................................................................................................ 45 7.85 ramlet:resourceWrapper .................................................................................................................. 45 ix

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

7.86 ramlet:resourceWrapperSet ............................................................................................................. 46 7.87 ramlet:rights..................................................................................................................................... 46 7.88 ramlet:selection................................................................................................................................ 47 7.89 ramlet:shapeIndicator ...................................................................................................................... 47 7.90 ramlet:source ................................................................................................................................... 47 7.91 ramlet:staticStructure....................................................................................................................... 48 7.92 ramlet:staticStructureSet.................................................................................................................. 48 7.93 ramlet:staticStructureType............................................................................................................... 49 7.94 ramlet:status..................................................................................................................................... 49 7.95 ramlet:stream ................................................................................................................................... 50 7.96 ramlet:streamType ........................................................................................................................... 50 7.97 ramlet:structRef ............................................................................................................................... 50 7.98 ramlet:structureNode ....................................................................................................................... 51 7.99 ramlet:structureNodeType ............................................................................................................... 51 7.100 ramlet:technicalDescriptorObject .................................................................................................. 52 7.101 ramlet:textType.............................................................................................................................. 52 7.102 ramlet:title...................................................................................................................................... 53 7.103 ramlet:topNode .............................................................................................................................. 53 7.104 ramlet:transformOrdering .............................................................................................................. 55 7.105 ramlet:true...................................................................................................................................... 55 7.106 ramlet:virtualResourceGroup......................................................................................................... 56 7.107 ramlet:wholeAggregationDescriptorObject................................................................................... 56 8. Conceptual model—object properties ...................................................................................................... 57 8.1 ramlet:describes ................................................................................................................................. 57 8.2 dcterms:hasPart.................................................................................................................................. 57 8.3 ramlet:includes................................................................................................................................... 58 8.4 ramlet:isDescribedBy ........................................................................................................................ 58 8.5 ramlet:isIncludedBy........................................................................................................................... 58 8.6 dcterms:isPartOf ................................................................................................................................ 58 8.7 ramlet:isReferencedBy ...................................................................................................................... 59 8.8 ramlet:references ............................................................................................................................... 59 9. Conceptual model—data types................................................................................................................. 59 9.1 xsd:anyURI........................................................................................................................................ 60 9.2 xsd:base64Binary............................................................................................................................... 60 9.3 xsd:positiveInteger............................................................................................................................. 60 9.4 xsd:string ........................................................................................................................................... 60 9.5 xsd:token............................................................................................................................................ 60 Annex A (informative) Bibliography ........................................................................................................... 61 Annex B (informative) Conceptual overview............................................................................................... 64 Annex C (informative) Ontologies—a brief primer ..................................................................................... 69 Annex D (informative) Use cases................................................................................................................. 71 Annex E (informative) Mapping of the XML Linking Language mapping ontology to the conceptual model for resource aggregation ............................................................................................. 82 Annex F (informative) Graphical representations of RAMLET classes....................................................... 88

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

Annex G (informative) Graphical representations of RAMLET properties ............................................... 130 Annex H (normative) Internet availability and use of the Turtle representations of the conceptual model and XLink mapping.................................................................................................. 133 Annex I (informative) Internet availability and use of the RDF/XML representations of the conceptual model and XLink mapping........................................................................................ 134

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Standard for Learning Technology— Conceptual Model for Resource Aggregation for Learning, Education, and Training IMPORTANT NOTICE: IEEE Standards documents are not intended to ensure safety, health, or environmental protection, or ensure against interference with or from other devices or networks. Implementers of IEEE Standards documents are responsible for determining and complying with all appropriate safety, security, environmental, health, and interference protection practices and all applicable laws and regulations. This IEEE document is made available for use subject to important notices and legal disclaimers. These notices and disclaimers appear in all publications containing this document and may be found under the heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Documents.” They can also be obtained on request from IEEE or viewed at http://standards.ieee.org/IPR/disclaimers.html.

1. Overview

1.1 Scope This standard defines a conceptual model for interpreting externalized representations of digital aggregations of resources for learning, education, and training. The conceptual model defines a set of concepts and the relationships among them and is expressed as a formal ontology. Internal compositions and uses of digital resources are not specified nor are processing methods for resource aggregations.

1.2 Purpose Currently, resource aggregations used in learning, education, and training are defined in a variety of standards and specifications. The conceptual model defined in this standard facilitates interoperability by providing an ontology that can be used to represent a variety of aggregation formats. Interoperability may be achieved by the creation of crosswalks among the various aggregation standards and specifications. In addition, this standard may serve as a common reference for the development and evolution of standards and specifications for resource aggregations and may assist the development of profiles that maximize interoperability between the various aggregation formats.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

2. Normative references The following referenced documents are indispensable for the application of this document (i.e., they must be understood and used, so each referenced document is cited in text and its relationship to this document is explained). For dated references, only the edition cited applies. For undated references, the latest edition of the referenced document (including any amendments or corrigenda) applies. W3C® Recommendation (28 October 2004), XML Schema Part 2: Datatypes, Second Edition. 1,

3. Definitions, acronyms, and abbreviations

3.1 Definitions For the purposes of this document, the following terms and definitions apply. The IEEE Standards Dictionary Online should be consulted for terms not defined in this clause. 3 aggregation definition document: A document that lists and structures the digital resources of an aggregation. See also: digital resource; resource aggregation. NOTE—Examples: the manifest document in IMS Content Packaging (IMS CP) (IMS Specification [B9]); the mets documents in the Metadata Encoding and Transmission Standard (METS) ([B19], [B20]); the Digital Item Declaration Language (DIDL) document in MPEG-21 Digital Item Declaration (DID) (ISO/IEC 21000-2:2005 [B15]). 4, 5

aggregation format: A documented method of aggregating digital resources into a complex object that can be exchanged among systems. An aggregation format may be defined by a formal specification or standard, but may also be informal. The defining characteristic is that an aggregation format specifies how to combine digital resources into a structured whole, without prescribing the kinds of digital resources, their internal structures, or their intended uses. See also: digital resource. aggregation instance: An instantiation of an aggregation definition document that includes all data necessary to construct a complex object including any references to external data. Multiple aggregation instances, each of which conforms to a different aggregation format, may exist for the same complex object. See also: aggregation definition document; aggregation format. binding: The process that binds a model to a data structure. For example, it can refer to the binding of a conceptual model to the Web Ontology Language (OWL) ontology language. NOTE—See W3C Recommendation [B29].

W3C publications are available from the World Wide Web Consortium, 32 Vassar Street, Room 32-G515, Cambridge, MA 02139, USA (http://www.w3.org/). 2 W3C is a registered trademark of the World Wide Web Consortium (registered in numerous countries). Marks of W3C are registered and held by its host institutions: Massachusetts Institute of Technology (MIT), European Research Consortium for Information and Mathematics (ERCIM), and Keio University, Japan. 3 IEEE Standards Dictionary Online subscription is available at http://www.ieee.org/portal/innovate/products/standard/ standards_dictionary.html. 4 The numbers in brackets correspond to those of the bibliography in Annex A. 5 Notes in text, tables, and figures of a standard are given for information only and do not contain requirements needed to implement this standard.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

class: A category of items that share one or more common characteristics. Characteristics can be described informally in a scope note or formally as properties explicitly formulated in logical terms. A class cannot be defined by enumerating its instances because it is generally impossible to know all instances of a class in the world, and the future can bring new instances into being at any time. See also: class instance; open world; scope note. class extension: The set of all real-life instances belonging to a class that fulfill the criteria of the class’s intention. An extension is an open set in the sense that it is generally impossible to know all instances of a class. In an open world, new instances of a class may be created at any time. See also: class; intention; instance; open world. class instance: An instantiation of a class. A class instance has properties that meet the criteria of the intention of the class. The number of instances of a given class declared in an information system is usually less than the total number of instances in the real world. For example, although an individual is an instance of “person,” the individual may not be mentioned in all information systems describing “persons.” See also: class; intention; property. component: Any data attribute or data element as described by the data model of an aggregation format. See also: aggregation format; data attribute; data element.. data attribute: A characteristic of a unit of data, often expressed in Extensible Markup Language (XML). data element: A uniquely named and defined component of the data model of an aggregation format into which data items (actual values) can be placed. See also: aggregation format; component. digital resource: Any resource that can be expressed in an electronic format, such as binary formats, Extensible Markup Language (XML), plain text, various encodings (e.g., base64), media-specific formats, and compressed archives (e.g., zip files). NOTE—Media-specific formats include Joint Photographic Experts Group [JPEG] (ISO/IEC 10918-1) [B13]) and MPEG–1 Audio Layer 3 [MP3] (ISO/IEC 13818-3 [B14]).

domain: A constraint on a property that limits the class instances to which the property can be applied. Instances of a property are applicable to instances of its domain. For example, if property A has only the classes X and Y as a domain, then only instances of classes X and Y can have property A. See also: class; class instance; property; property instance; range. identifier: Associates a name with a thing. Context defines how the name is interpreted. Within a given context, a name is unique. inheritance: The ability of classes to derive characteristics from other classes and properties to derive characteristics from other properties. If characteristics are removed from a class or property, they are also removed from its subclasses or subproperties. See also: class; multiple inheritance; property; subclass; subproperty. intention: The intended meaning of a class or property. The intention consists of the common characteristics shared by all instances of the class or property. The intention need not be explicitly formulated as properties in the case of a class or as the domain and range in the case of a property. Instead, the intention can be described in a scope note that refers to a conceptualization shared by domain experts. See also: class; class instance; domain; property; property instance; range; scope note. locator: An identifier that can be used to retrieve a digital resource or component. The digital resource or component may be either internal or external to the aggregation definition document. See also: aggregation definition document; component; digital resource; identifier.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

mapping: An ontology of an aggregation format that relates the aggregation format’s classes and properties to the classes and properties of another ontology. See also: aggregation format. multiple inheritance: The inheritance of characteristics by a class from more than one immediate superclass or by a property from more than one immediate superproperty. If multiple inheritance is used, the resulting class or property hierarchy is a directed graph, not a tree structure. If multiple inheritance in a class or property hierarchy is represented as an indented list, then some classes or properties will inevitably be repeated at different positions in the indented list. For example, “person” could be a member of both the classes “critic” and “author,” and, therefore, would be repeated at different positions in the indented list. This feature distinguishes an ontology from a simple tree structure. See also: class; inheritance; property; superclass; superproperty. open world: An assumption that an ontology and its instances are incomplete with regard to the world they attempt to describe. As a consequence, the open-world assumption states that everything that is not known is undefined. In contrast, a closed-world assumption implies that everything that is not known is false. property: A characteristic that defines a relationship of a specific kind between two classes or sets of classes. A property has exactly one domain and one range. Which classes are selected as the domain and which as the range is arbitrary. In other words, a property can be interpreted in both directions with two distinct but related interpretations. Property names are designed to be semantically meaningful and grammatically correct when read from domain to range. Inverse property names are designed to be semantically meaningful and grammatically correct when read from range to domain. Properties can also be specialized in the same manner as classes, resulting in parent/child relationships between superproperties and their subproperties. Like a class, a property is characterized by an intention, which is conveyed by a scope note. See also: class; domain; intention; range; scope note; subproperty; superproperty. property instance: An instantiation of a property that defines the domain and range of a relationship between two classes or sets of classes. For example, class X may be “containedBy” another class Y. In this example, “containedBy” is the instantiation of property. The inverse property in this example would be “contains,” i.e., class Y “contains” class X. See also: class; domain; property; range. range: The set of instances of a given class to which a property can be applied. For example, the range of property A might consist of those instances of class X and class Y that exhibit property A. A property can link only to instances of the classes that serve as its range. See also: class; class instance; domain; property. representation: A method or syntax for serializing data. For example, it can refer to the different serializations of a Web Ontology Language (OWL) ontology according to the Terse RDF Triple Language (Turtle) or Resource Description Framework/Extensible Markup Language (RDF/XML) syntaxes. NOTE—For OWL, see W3C Recommendation [B29]; for Turtle, see W3C Team Submission [B35].

resource aggregation: (A) Digital resources of diverse types that are gathered together to form a new complex object. Information is contained in the resource aggregation for purposes of specifying the categories of and the relationships among the aggregated resources. A resource aggregation may be contained in an exchange file or not, and may be self-contained or reference resources held in other locations. A resource aggregation may be disaggregated into its component digital resources. Resource aggregations are stored and processed using system formats (internal representations) and are usually transmitted between systems using aggregation formats. See also: aggregation format; digital resource. (B) The process of aggregating digital resources so that the result can be used in one or more applications, such as transmission, storage, and delivery to users. See also: digital resource. scope note: A textual description of the intention of a class or property. Scope notes are not formal constructs but are provided to help explain the intended meaning and application of classes and properties. See also: class; intention; property.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

strict inheritance: The inheritance of characteristics by classes or properties that allows no exceptions. See also: class; inheritance; property. subclass: A specialization of a class by inheritance from one or more superclasses. A subclass inherits all the properties of its superclasses (i.e., strict inheritance) in addition to having zero or more additional properties of its own. If a subclass inherits properties from more than one superclass, it is said to have multiple inheritance. See also: class; inheritance; multiple inheritance; property; subclass; superclass. subproperty: A specialization of a property by inheritance from one or more superproperties. All instances of a subproperty are also instances of its immediate superproperty. The intention of a subproperty extends the intention of its immediate superproperty, i.e., its characteristics are more restrictive than that of its superproperty. See also: inheritance; intention; property instance; superproperty. superclass: A generalization of one or more other classes, i.e., the subclasses. A superclass subsumes all instances of its subclasses and may have additional instances that do not belong to any of its subclasses. The intention of the superclass is less restrictive than the intentions of any of its subclasses. A superclass/subclass relationship may also be referred to as a parent/child relationship. See also: class; class instance; intention; subclass. superproperty: A generalization of one or more other properties, i.e., the subproperties. A superproperty subsumes all instances of its subproperties and may have additional instances that do not belong to any of its subproperties. A superproperty/subproperty relationship may also be referred to as a parent/child relationship. The intention of the superproperty is less restrictive than the intentions of any of its subproperties. See also: intention; property; subproperty.

3.2 Acronyms and abbreviations ALOCOM

Abstract Learning Object Content Model

Atom

Atom Syndication Format

CAD

computer-aided design

CODEC

compressor-decompressor

Dublin Core™ 6

DID

Digital Item Declaration

DIDL

Digital Item Declaration Language

DOI

Digital Object Identifier

EAD

Encoded Archival Description

HTML

Hypertext Markup Language

IMS CP

IMS Content Packaging

ISBN

International Standard Book Number

JPEG

Joint Photographic Experts Group

LMS

learning management system

Dublin Core is a trademark of the Dublin Core Metadata Initiative Limited (USPTO 2519654).

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

LOM

Learning Object Metadata

MARC

Machine-Readable Cataloging

MD5

Message-Digest algorithm 5

METS

Metadata Encoding and Transmission Standard

MIME

Multipurpose Internet Mail Extension

MP3

MPEG-1 Audio Layer 3

MPEG

Moving Pictures Experts Group

OAI-ORE

Open Archives Initiative Object Reuse and Exchange

OASIS

Organization for the Advancement of Structured Information Standards

ODRL

Open Digital Rights Language

OWL

Web Ontology Language

PDA

personal digital assistant

RAMLET

Resource Aggregation Models for Learning, Education, and Training

RDF

Resource Description Framework

RDFS

RDF Schema

RSS

Really Simple Syndication

RTS

run-time system

SCO

Shareable Content Object

SKOS

Simple Knowledge Organization System

SPARQL

SPARQL Protocol and RDF Query Language

Turtle

Terse RDF Triple Language

URI

Uniform Resource Identifier

URL

Uniform Resource Locator

URN

Uniform Resource Name

W3C

World Wide Web Consortium

WAVE

Waveform Audio File Format

XLink

XML Linking Language

XML

Extensible Markup Language

XPath

XML Path Language

XSLT

Extensible Stylesheet Language Transformations

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

4. Special terms In this standard, the following special term and definition applies. core ontology: A shorthand way of referencing the conceptual model described in this standard. The core ontology does not include any recommended practice mappings.

5. Class and property prefix definitions The class and property names in this standard included prefixes that reference the documents in which the classes and properties are fully described. The prefixes used and the documents they reference are as follows: ⎯

atom: IEEE P1484.13.5™, Draft Recommended Practice for Learning Technology—IETF RFC 4287—Atom Syndication Format—Mapping to the Conceptual Model for Resource Aggregation. 7

⎯

cp: IEEE P1484.13.4™, Draft Recommended Practice for Learning Technology—IMS Content Packaging Information Model (CP) Version 1.2—Mapping to the Conceptual Model for Resource Aggregation.

⎯

dcterms: Dublin Core Metadata Initiative Recommendation [B3] (10 November 2010), DCMI Metadata Terms, http://www.dublincore.org/documents/2010/10/11/dcmi-terms/.

⎯

mets: IEEE P1484.13.2™, Draft Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation.

⎯

mpeg: IEEE P1484.13.3™, Draft Recommended Practice for Learning Technology—ISO 21000– 2:2005 Information Technology—Multimedia Framework (MPEG-21)—Part 2: Digital Item Declaration Mapping to the Conceptual Model for Resource Aggregation.

⎯

oai-ore: IEEE P1484.13.6™, Draft Recommended Practice for Learning Technology—Open Archives Initiative Object Reuse and Exchange Abstract Model (OAI-ORE)—Mapping to the Conceptual Model for Resource Aggregation.

⎯

owl: W3C OWL 2 Namespace Document, http://www.w3.org/2002/07/owl#.

⎯

ramlet: This standard.

⎯

xlink: This standard (see Annex E).

⎯

xmln: W3C Recommendation, Namespaces in XML http://www.w3.org/TR/2009/REC-xml-names-20091208.

⎯

xsd: W3C Recommendation, XML Schema Part 2: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028. 8

1.0

(Third

Datatypes,

Edition) Second

[B28], Edition,

6. Conformance Conformance to this standard is discussed in 6.1 through 6.5. In this standard, “shall” is to be interpreted as a requirement; “shall not” is to be interpreted as a prohibition. 7

IEEE P1484.13.2, IEEE P1484.13.3, IEEE P1484.13.4, IEEE P1484.13.5, and IEEE P1484.13.6 are in development. For more information, contact the IEEE. 8 Information on references can be found in Clause 2.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

6.1 Conforming aggregation instances A conforming aggregation instance shall be an instance of an aggregation format that has been modeled or described in terms of the core ontology (via a mapping or otherwise) following the intentions of the core ontology as expressed in Clause 7, Clause 8, and Clause 9 of this standard.

6.2 Conforming bindings Conforming bindings of the core ontology: ⎯

Shall conform to the requirements of Clause 7, Clause 8, and Clause 9 of this standard.

⎯

If the binding technology language supports Uniform Resource Identifiers (URIs), then it shall use the same URIs as those in the Terse RDF Triple Language (Turtle) representation referenced in Annex H of this standard.

⎯

If the binding technology language supports URIs and the binding contains extensions to the core ontology (see 6.4), then identifiers for the extensions shall be defined in another namespace.

6.3 Conforming mappings Conforming mappings for new aggregation formats may be defined. A conforming mapping shall be an ontology of an aggregation format expressed in terms of the core ontology defined in Clause 7, Clause 8, and Clause 9 of this standard. Conformance requirements for mappings include the following: ⎯

When a concept is already expressed as a class or property in the core ontology, the mapping shall use the identifiers for that class or property as defined in the core ontology.

⎯

When a concept is not already expressed as a class or property in the core ontology, the mapping may extend the core ontology by adding a new class or property and by defining a new identifier. The new identifier shall not be used to identify a concept that already exists in the core ontology.

6.4 Conforming extensions of the core ontology When a concept relating to interpreting externalized representations of digital aggregations is not already expressed as a class or property in the core ontology, a mapping may extend the core ontology. The core ontology may be extended by adding a new class or property and by defining a new identifier in a new ontology. The new identifier shall not be used to identify a concept that already exists in the core ontology. Bindings for conforming extensions shall conform to the requirements in 6.2. NOTE—Concepts relating to interpreting externalized representations of digital aggregations should be defined as conforming extensions to the core ontology. Other concepts may be represented by other vocabularies or ontologies and combined with the core ontology using standard Semantic Web practices.

6.5 Conforming transforming implementations A conforming transforming implementation shall implement a transformation from an aggregation format to the core ontology and its identifiers or from the core ontology and its identifiers to an aggregation format by using a model following the intention of the core ontology as defined in classes in Clause 7, Clause 8, and Clause 9 of this standard.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

NOTE—In an implementation that transforms between two aggregation formats, the core ontology need not be physically instantiated for the implementation to conform.

7. Conceptual model—classes This clause provides declarations of all the classes in the core ontology. The declarations use the following format: ⎯

Class name: The name of the class.

⎯

Subclass of: The parent of the class. The class may inherit properties from its parent.

⎯

Superclass of: The children of the class that are also in the core ontology.

⎯

Scope note: A textual description of the class.

⎯

Data type: The data type of the class as defined in Clause 9.

⎯

Properties: The properties of the class as described in Clause 8. Inherited properties are not included in the entry.

⎯

Asserted conditions: Any conditions that are asserted for the class as a result of restrictions on its properties.

⎯

Examples: Examples of subclasses from aggregation formats that map to the class.

7.1 ramlet:administrativeDescriptorObject Class name:

ramlet:administrativeDescriptorObject

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Contains information about the management of digital resources in an aggregation instance.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:version mets:amdSec

7.2 ramlet:admRef Class name:

ramlet:admRef

Subclass of:

ramlet:locator

Superclass of:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

A locator (see 7.53) that associates administrative metadata with a digital resource or groups of digital resources that share the administrative metadata.

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

mets:admID

7.3 ramlet:aggregationID Class name:

ramlet:aggregationID

Subclass of:

owl:class

Superclass of:

None

Scope note:

An identifier for an aggregation instance ramlet:aggregationID is used by external systems.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual is a member of owl:class.

whole.

Generally,

Being a member of this class implies that an individual has some value of the property dcterms:isPartOf that is a member of ramlet:topNode. Examples:

atom:ID mets:objID mpeg:didlDocumentID

7.4 ramlet:aggregationSchema Class name:

ramlet:aggregationSchema

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

An identifying string for a formal schema binding of an aggregation format.

Properties:

None

Data type:

None

Asserted conditions:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Examples:

cp:schema mets:profile mpeg:schema

7.5 ramlet:aggregationSchemaVersion Class name:

ramlet:aggregationSchemaVersion

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

An identifier for a formal schema binding of an aggregation format.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:schemaVersion

7.6 ramlet:aggregationType Class name:

ramlet:aggregationType

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The category of an aggregation instance, e.g., IMS Content Packaging (IMS CP) (IMS Specification [B9]) or Metadata Encoding and Transmission Standard (METS) ([B19], [B20]).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:metsType

7.7 ramlet:alternateID Class name:

ramlet:alternateID

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

An identifying string by which an associated component is known in another system.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:altRecordID mets:ownerID

7.8 ramlet:altResourceRef Class name:

ramlet:altResourceRef

Subclass of:

ramlet:descriptiveRef

Superclass of:

None

Scope note:

Locates a ramlet:resourceGroup that has different media accessibility properties from the ramlet:resourceGroup (see 7.76) that includes the ramlet:altResourceRef.

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

cp:variant

7.9 ramlet:anchor Class name:

ramlet:anchor

Subclass of:

owl:class

Superclass of:

ramlet:anchorType ramlet:beginPoint ramlet:componentTarget ramlet:coordinates ramlet:endpoint ramlet:extent ramlet:shapeIndicator ramlet:stream ramlet:streamType

Scope note:

Contains components that identify and describe a portion of or location within a digital resource, e.g., a specific point in time in an audio file or a shape within a larger image.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual is a member of owl:class. Being a member of this class implies that an individual has some value of the property dcterms:isPartOf that is a member of ramlet:topNode.

Examples:

mets:area mpeg:anchor mpeg:fragment

7.10 ramlet:anchorType Class name:

ramlet:anchorType

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

The unit of measurement used by an anchor (see 7.9), e.g., time or byte.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:beType mets:extType

7.11 ramlet:assertion Class name:

ramlet:assertion

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

Defines a full or partially configured state of a choice (see 7.16) by asserting true (see 7.105) or false (see 7.36) values for some number of predicate tests associated with the selections for that choice. If no assertion is made, the choice is undecided. For example, an assertion could be used to “save” a configuration within an aggregation definition document. The assertion would target the format choice and might assert true for the predicate test of the MPEG–1 Audio Layer 3 (MP3) (ISO/IEC 13818-3 [B14]) selection so that the MP3 component is selected by default.

Properties:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Data type:

None

Asserted conditions:

None

Examples:

mpeg:assertion

7.12 ramlet:beginPoint Class name:

ramlet:beginPoint

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

Indicates at what point within a digital resource an anchor (see 7.9) starts.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:begin

7.13 ramlet:cardinalityLabel Class name:

ramlet:cardinalityLabel

Subclass of:

ramlet:title

Superclass of:

None

Scope note:

Elements that define a label for an order sequence, e.g., “I”, “a)” or “1.”

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

Examples:

mets:orderLabel

7.14 ramlet:checksum Class name:

ramlet:checksum

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

A value used to ensure the integrity of a digital resource after the resource has been stored or transmitted.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:checksum

7.15 ramlet:checksumType Class name:

ramlet:checksumType

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The algorithm used to calculate the checksum of a digital resource, e.g., CRC–32– IEEE–802.3 (Koopman [B16]) or Message-Digest algorithm 5 (MD5) IETF RFC 1321 [B6]).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:checksumType

7.16 ramlet:choice Class name:

ramlet:choice

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

Contains components of a ramlet:dynamicStructure (see 7.28) that identify members of a set of selection(s) (see 7.88) that enable a processing application to choose among options for processing a digital resource.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:choice

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.17 ramlet:componentTarget Class name:

ramlet:componentTarget

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

An anchor (see 7.9) that identifies or describes a portion of a digital resource dynamically at runtime, e.g., via an XML Path Language (XPath) (W3C [B37]) expression that is encapsulated in a Uniform Resource Locator (URL).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:xPointer mets:xptr

7.18 ramlet:condition Class name:

ramlet:condition

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

A logical condition. In a particular aggregation instance, a condition denotes that its parent component is conditional on a set of predicate tests [see the example of choice (7.16)]. The require component (see 7.74) lists the set of predicate tests that must become true and the ramlet:except component (see 7.34) lists the set of predicate tests that must become false in order for the condition to be satisfied. Each predicate test is identified by the value of the ramlet:dynamicStructureID (see 7.29) included in a selection (see 7.88).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:condition

7.19 ramlet:coordinates Class name:

ramlet:coordinates

Subclass of:

ramlet:anchor

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Superclass of:

None

Scope note:

The boundaries of the shape of an anchor (see 7.9). Typically, this class is used with ramlet:shapeIndicator (see 7.89), e.g., to define a region within an image.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:coords

7.20 ramlet:creationDate Class name:

ramlet:creationDate

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

A recognized creation date related to a digital resource or an aggregation instance, e.g., the date a digital resource was made available in a system or when an aggregation instance was created.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:published mets:created mets:createDate mets:versDate

7.21 ramlet:defaultSelection Class name:

ramlet:defaultSelection

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

The ramlet:dynamicStructureID(s) (see 7.29) associated with a selection that should be chosen by a processing application automatically in the absence of any actively chosen ramlet:selection(s) (see 7.88).

Properties:

None

Data type:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Asserted conditions:

None

Examples:

cp:default mpeg:default

7.22 ramlet:descriptiveDescriptorObject Class name:

ramlet:descriptiveDescriptorObject

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Information to support finding, identifying, selecting, and obtaining a digital resource.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:subtitle atom:summary mets:dmdSec

7.23 ramlet:descriptiveRef Class name:

ramlet:descriptiveRef

Subclass of:

ramlet:locator

Superclass of:

ramlet:altResourceRef

Scope note:

A ramlet:locator (see 7.53) that associates descriptive metadata with digital resources or resource groupings.

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

mets:dmdID mpeg:target

7.24 ramlet:descriptorObject Class name:

ramlet:descriptorObject

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Subclass of:

owl:class

Superclass of:

ramlet:administrativeDescriptorObject ramlet:aggregationSchema ramlet:aggregationType ramlet:alternateID ramlet:checksum ramlet:checksumType ramlet:creationDate ramlet:descriptiveDescriptorObject ramlet:descriptorType ramlet:descriptorTypeIndicator ramlet:encodingType ramlet:fileSize ramlet:generatingTool ramlet:humanLanguage ramlet:identifierType ramlet:intendedUse ramlet:modificationDate ramlet:nodeVisibility ramlet:note ramlet:party ramlet:provenance ramlet:resourceProcessing ramlet:resourceType ramlet:rights ramlet:source ramlet:status ramlet:structureNodeType ramlet:technicalDescriptorObject ramlet:textType ramlet:wholeAggregationDescriptorObject

Scope note:

Information that describes a digital resource for purposes of discovery and identification by a human reader.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

atom:category atom:term cp:metadata mets:mdWrap mpeg:annotation mpeg:descriptor mpeg:statement

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.25 ramlet:descriptorTypeIndicator Class name:

ramlet:descriptorTypeIndicator

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The category for the type of metadata contained in a component, e.g., MachineReadable Cataloging (MARC) (MARC 21 [B18]), Learning Object Metadata (LOM) (IEEE Std 1484.12.1™-2002 [B5]), or Dublin Core Metadata Initiative [B3].

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:scheme mets:mdType mets:otherMdType

7.26 ramlet:digitalResource Class name:

ramlet:digitalResource

Subclass of:

owl:class

Superclass of:

ramlet:digitalResourceFragment

Scope note:

Refers to a digital resource contained in an aggregation instance.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

oai-ore:aggregatedResource

7.27 ramlet:digitalResourceFragment Class name:

ramlet:digitalResourceFragment

Subclass of:

ramlet:digitalResource

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Superclass of:

None

Scope note:

A part of a digital resource described within an aggregation instance.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

None

7.28 ramlet:dynamicStructure Class name:

ramlet:dynamicStructure

Subclass of:

owl:class

Superclass of:

ramlet:assertion ramlet:choice ramlet:condition ramlet:defaultSelection ramlet:dynamicStructureID ramlet:dynamicStructureType ramlet:except ramlet:false ramlet:maxSelections ramlet:minSelections ramlet:require ramlet:selection ramlet:true

Scope note:

Contains the relationships among ramlet:structureNode(s) (see 7.98) in an aggregation instance that depend on factors true for only one state. The state of the relationships depends upon the processing at run time, e.g., the state may change after user interactions.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mpeg:container

7.29 ramlet:dynamicStructureID Class name:

ramlet:dynamicStructureID

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

Identifies components eligible to be included in a ramlet:dynamicStructure (see 7.28).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:choiceID mpeg:selectID

7.30 ramlet:dynamicStructureType Class name:

ramlet:dynamicStructureType

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

The category of a ramlet:dynamicStructure (see 7.28) within an aggregation instance, e.g., display behavior or authentication approval.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:bType

7.31 ramlet:elementID Class name:

ramlet:elementID

Subclass of:

owl:class

Superclass of:

ramlet:nodeID

Scope note:

A local identifier for a data element in an aggregation instance.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Asserted conditions:

Examples:

atom:ID cp:identifier mets:ID mpeg:ID mpeg:identifier mpeg:target

7.32 ramlet:encodingType Class name:

ramlet:encodingType

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The encoding method for a digital resource, e.g., an audio track encoded as base64.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:contentEncoding mpeg:encoding

7.33 ramlet:endPoint Class name:

ramlet:endPoint

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

Indicates at what point within a digital resource a ramlet:anchor (see 7.9) ends.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:end

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.34 ramlet:except Class name:

ramlet:except

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

The set of predicate tests that are required to become false in order to satisfy a ramlet:condition (see 7.18).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:except

7.35 ramlet:extent Class name:

ramlet:extent

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

Measures the sequential or contiguous portion of a digital resource defined by a ramlet:anchor (see 7.9), e.g., the duration of an audio clip or the coordinates of an area within an image.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:length mets:extent

7.36 ramlet:false Class name:

ramlet:false

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

Asserts an associated ramlet:condition (see 7.18) to be false.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:false

7.37 ramlet:fileDescriptor Class name:

ramlet:fileDescriptor

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains file descriptors relating to a single digital resource, e.g., locators, file size.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

atom:entry atom:link cp:file mets:file mpeg:resource

7.38 ramlet:fileSize Class name:

ramlet:fileSize

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The size of a file or bitstream referenced in an aggregation instance. The expression of the unit of measurement is specified by the mapping.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:size

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.39 ramlet:functionalResourceGroup Class name:

ramlet:functionalResourceGroup

Subclass of:

ramlet:resourceGroup

Superclass of:

None

Scope note:

Contains a collection of ramlet:fileDescriptor(s) (see 7.37) for a set of functionally related digital resources.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:resource mets:fileGrp mpeg:component

7.40 ramlet:generatingTool Class name:

ramlet:generatingTool

Subclass of:

ramlet:descriptorObject

Superclass of:

ramlet:generatingToolVersion

Scope note:

The tool used to create an aggregation instance.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:generator

7.41 ramlet:generatingToolVersion Class name:

ramlet:generatingToolVersion

Subclass of:

ramlet:generatingTool

Superclass of:

None

Scope note:

The version of the tool used to create an aggregation instance.

Properties:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Data type:

None

Asserted conditions:

None

Examples:

atom:version

7.42 ramlet:groupingID Class name:

ramlet:groupingID

Subclass of:

owl:class

Superclass of:

None

Scope note:

Associates multiple digital resources into a group by means of a single group identifier.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mets:groupID

7.43 ramlet:hasOrder Class name:

ramlet:hasOrder

Subclass of:

owl:class

Superclass of:

ramlet:transformOrdering

Scope note:

A preferred order by sequence for digital resources and/or portions of digital resources within an aggregation instance, e.g., for rendering pages in a book in a preferred sequence.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mets:order mets:seq

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.44 ramlet:hasRank Class name:

ramlet:hasRank

Subclass of:

owl:class

Superclass of:

None

Scope note:

A preference by rank for digital resources and/or portions of a digital resource within an aggregation instance. A digital resource or portion thereof may have no rank, the same rank, or a different rank from another. For example, the beginning of an audio clip may be denoted as the starting point for a whole session. A second point placed at 17 minutes 30 seconds past the beginning of the audio clip begins a drum solo section within the audio file that is described separately but still included within the aggregation instance. By assigning a high ramlet:hasRank value to the beginning point of the audio clip and either a lower or no ramlet:hasRank value to the drum solo, a user interface would display the beginning of the session first when displaying the list of byte streams within the file and make the beginning of the session the default display.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mpeg:precedence

7.45 ramlet:humanLanguage Class name:

ramlet:humanLanguage

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The category for the human language in which a digital resource is rendered, e.g., en-GB or fr-CA.

Properties:

None

Data type:

xsd:token

Asserted conditions:

None

Examples:

atom:hrefLang cp:language

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.46 ramlet:icon Class name:

ramlet:icon

Subclass of:

owl:class

Superclass of:

None

Scope note:

An image that visually identifies an aggregation instance or a digital resource to a user via an appropriate tool, e.g., a logo.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

atom:icon atom:logo

7.47 ramlet:identifierType Class name:

ramlet:identifierType

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The category for an identifier used within an aggregation instance, e.g., International Standard Book Number (ISBN) (ISO 2108 [B10]) or Digital Object Identifier (DOI) (ISO 26324 [B12]).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:altRecordIDType

7.48 ramlet:intendedUse Class name:

ramlet:intendedUse

Subclass of:

ramlet:descriptorObject

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Superclass of:

None

Scope note:

How a digital resource is expected to be used, e.g., as an archival-quality image, thumbnail, or audio sample.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:use

7.49 ramlet:interfaceDefLink Class name:

ramlet:interfaceDefLink

Subclass of:

ramlet:locator

Superclass of:

None

Scope note:

Contains components that point to a definition of a single behavior or a set of behaviors associated with a digital resource. The definition may be either human or machine readable. Alternatively, ramlet:interfaceDefLink can point directly to the single behavior or set of behaviors, e.g., a piece of executable code. ramlet:interfaceDefLink may be embedded within a resourceProcessingSet (see 7.82).

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

mets:interfaceDef mets:mechanism

7.50 ramlet:intraAggregationLink Class name:

ramlet:intraAggregationLink

Subclass of:

ramlet:locator

Superclass of:

ramlet:resourceIntraAggregationLink

Scope note:

Contains ramlet:resourceIntraAggregationLink(s) (see 7.77).

Properties:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

mets:structLink

7.51 ramlet:inventory Class name:

ramlet:inventory

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains the list of all digital resources included in an aggregation instance.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

cp:resources mets:fileSec

7.52 ramlet:localRef Class name:

ramlet:localRef

Subclass of:

ramlet:locator

Superclass of:

None

Scope note:

A ramlet:locator (see 7.53) for a component within an aggregation definition document.

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

cp:identifierRef mets:fileID

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.53 ramlet:locator Class name:

ramlet:locator

Subclass of:

owl:class

Superclass of:

ramlet:admRef ramlet:descriptiveRef ramlet:interfaceDefLink ramlet:intraAggregationLink ramlet:localRef ramlet:structRef

Scope note:

Identifies a network location of a component or a digital resource and may be used to obtain it.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

xsd:anyURI

Asserted conditions:

Examples:

atom:href atom:src cp:href mpeg:fragmentID mpeg:ref xlink:href

7.54 ramlet:locatorDescriptor Class name:

ramlet:locatorDescriptor

Subclass of:

owl:class

Superclass of:

None

Scope note:

Descriptive information about ramlet:locator(s) (see 7.53).

Properties:

None

Data type:

None

Asserted conditions:

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Examples:

atom:rel mets:locType mets:otherLocType xlink:actuate xlink:arcRole xlink:from xlink:label xlink:role xlink:show xlink:title xlink:to xlink:type

7.55 ramlet:maxSelections Class name:

ramlet:maxSelections

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

The maximum number of ramlet:selection(s) (see 7.88) that are required to be made for a ramlet:choice (see 7.16) to be resolved by a processing application.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:maxSelections

7.56 ramlet:mimeType Class name:

ramlet:mimeType

Subclass of:

ramlet:resourceType

Superclass of:

None

Scope note:

The Multipurpose Internet Mail Extension (MIME) (IETF RFC 2046 [B7]) type of a digital resource referenced in an aggregation instance, e.g., text/html.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Examples:

atom:link.type mpeg:mimeType mets:mimeType

7.57 ramlet:minSelections Class name:

ramlet:minSelections

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

The minimum number of selection(s) (see 7.88) that are required to be made for a ramlet:choice (see 7.16) to be resolved by a processing application.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:minSelections

7.58 ramlet:modificationDate Class name:

ramlet:modificationDate

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The last date of modification of one or more associated components.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:updated mets:lastModDate

7.59 ramlet:nodeID Class name:

ramlet:nodeID

Subclass of:

ramlet:elementID

Superclass of:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

An identifier for a ramlet:structureNode (see 7.98) in an external aggregation instance that describes a digital resource. The external aggregation instance that contains the ramlet:structureNode may use a different aggregation format. For example, ramlet:nodeID (see 7.59) might identify a structureNode denoting an article of a journal that is fully described within an aggregation instance of the journal, but is also included by means of the ramlet:nodeID as a ramlet:structureNode within an aggregation instance for a course bibliography.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:contentIDs

7.60 ramlet:nodeVisibility Class name:

ramlet:nodeVisibility

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Specifies whether a ramlet:structureNode (see 7.98) in an aggregation instance should be rendered to the user.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:isVisible

7.61 ramlet:note Class name:

ramlet:note

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Any additional information not described elsewhere.

Properties:

None

Data type:

None

Asserted conditions:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Examples:

mets:note

7.62 ramlet:parallel Class name:

ramlet:parallel

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains components that indicate parallel relationships between digital resources within an aggregation instance, e.g., two pages in a bilingual text containing the same content, or a topographical map and a road map of the same area.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mets:par

7.63 ramlet:party Class name:

ramlet:party

Subclass of:

ramlet:descriptorObject

Superclass of:

ramlet:partyEmail ramlet:partyName ramlet:partyRole ramlet:partyType ramlet:partyURI

Scope note:

Contains information about a person or group performing a role in relationship to a specific community. (After ISO 2146 [B11].)

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:agent

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.64 ramlet:partyEmail Class name:

ramlet:partyEmail

Subclass of:

ramlet:party

Superclass of:

None

Scope note:

An e-mail address where the ramlet:party (see 7.63) can be contacted.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:email

7.65 ramlet:partyName Class name:

ramlet:partyName

Subclass of:

ramlet:party

Superclass of:

None

Scope note:

The name of the ramlet:party (see 7.63).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:name mets:name

7.66 ramlet:partyRole Class name:

ramlet:partyRole

Subclass of:

ramlet:party

Superclass of:

None

Scope note:

The relationship the ramlet:party (see 7.63) has to an aggregation instance or its component.

Properties:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Data type:

None

Asserted conditions:

None

Examples:

atom:author atom:contributor mets:otherRole mets:role

7.67 ramlet:partyType Class name:

ramlet:partyType

Subclass of:

ramlet:party

Superclass of:

None

Scope note:

The category for the ramlet:party (see 7.63) that describes its nature, e.g., person or organization.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:agentType mets:otherType

7.68 ramlet:partyURI Class name:

ramlet:partyURI

Subclass of:

ramlet:party

Superclass of:

None

Scope note:

A URI that may be de-referenced to find more information about the ramlet:party (see 7.63).

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

atom:URI

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.69 ramlet:provenance Class name:

ramlet:provenance

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Information describing the circumstances related to the creation and custody over time of a digital resource.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:source mets:digiProvMd

7.70 ramlet:remoteDescriptorObject Class name:

ramlet:remoteDescriptorObject

Subclass of:

ramlet:remoteNode

Superclass of:

None

Scope note:

Contains components that locate an instance of a remote ramlet:descriptorObject (see 7.24).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:mdRef

7.71 ramlet:remoteNode Class name:

ramlet:remoteNode

Subclass of:

owl:class

Superclass of:

ramlet:remoteDescriptorObject ramlet:remoteResource ramlet:remoteTopNode

Scope note:

Contains a ramlet:locator (see 7.53) for a part of an aggregation definition

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

document located outside of an aggregation instance. Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

cp:iPointer

7.72 ramlet:remoteResource Class name:

ramlet:remoteResource

Subclass of:

ramlet:remoteNode

Superclass of:

None

Scope note:

Contains components that locate (see 7.53) a remote digital resource.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:fLocat

7.73 ramlet:remoteTopNode Class name:

ramlet:remoteTopNode

Subclass of:

ramlet:remoteNode

Superclass of:

None

Scope note:

Contains components that locate (see 7.53) an instance of a remote ramlet:topNode (see 7.103).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:mPtr

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.74 ramlet:require Class name:

ramlet:require

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

The set of predicate tests that are required to become true in order to satisfy a ramlet:condition (see 7.18).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:require

7.75 ramlet:resourceAggregation Class name:

ramlet:resourceAggregation

Subclass of:

owl:class

Superclass of:

None

Scope note:

Digital resources of diverse types that are gathered together to form a new complex object. Information is contained in the resource aggregation for purposes of specifying the categories of and the relationships among the aggregated resources. A resource aggregation may be contained in an exchange file or not, and may be self-contained or reference resources held in other locations. A resource aggregation may be disaggregated into its component digital resources. Resource aggregations are stored and processed using system formats (internal representations) and are usually transmitted between systems using aggregation formats.

Properties:

None

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual is a member of owl:class.

Examples:

oai-ore:aggregation

7.76 ramlet:resourceGroup Class name:

ramlet:resourceGroup

Subclass of:

owl:class

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Superclass of:

ramlet:functionalResourceGroup ramlet:virtualResourceGroup

Scope note:

Contains a collection of fileDescriptor(s) (see 7.37) for digital resources. For example, a resourceGroup might comprise the digital resources associated with a Web page.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mpeg:declarations

7.77 ramlet:resourceIntraAggregationLink Class name:

ramlet:resourceIntraAggregationLink

Subclass of:

ramlet:intraAggregationLink

Superclass of:

None

Scope note:

Specifies links between two ramlet:structureNode(s) (see 7.98) within an aggregation instance structure to declare an association between them, e.g., two embedded hyperlinks within one or more Web page structures. (See also: dynamicStructure [7.28], staticStructure [7.91].)

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

mets:smLink

7.78 ramlet:resourceProcessing Class name:

ramlet:resourceProcessing

Subclass of:

ramlet:descriptorObject

Superclass of:

ramlet:resourceProcessingAlgorithm ramlet:resourceProcessingBehavior ramlet:resourceProcessingKey ramlet:resourceProcessingType

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

Contains machine- or human-readable statements and instructions required to process a digital resource, e.g., how to uncompress and render a compressed digital resource. NOTE—Making a digital resource renderable may require multiple processes. For example, a digital resource may have to be both decrypted and uncompressed.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:behavior mets:transformFile

7.79 ramlet:resourceProcessingAlgorithm Class name:

ramlet:resourceProcessingAlgorithm

Subclass of:

ramlet:resourceProcessing

Superclass of:

None

Scope note:

A processing algorithm used to make a digital resource renderable. [See also: ramlet:resourceProcessing (7.78).]

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:transformAlgorithm

7.80 ramlet:resourceProcessingBehavior Class name:

ramlet:resourceProcessingBehavior

Subclass of:

ramlet:resourceProcessing

Superclass of:

None

Scope note:

Locates a component within an aggregation instance that describes the behavior of a process in a technology specific way, e.g., a Perl script (Perl 5 [B24]) or an Extensible Stylesheet Language Transformation (XSLT) (W3C [B38]). [See also: ramlet:resourceProcessing (7.78).]

Properties:

None

Data type:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Asserted conditions:

None

Examples:

mets:transformBehavior

7.81 ramlet:resourceProcessingKey Class name:

ramlet:resourceProcessingKey

Subclass of:

ramlet:resourceProcessing

Superclass of:

None

Scope note:

Describes a required parameter for a processing algorithm for a digital resource, e.g., a string that tells the processing agent which output format is required. [See also: resourceProcessing (7.78).]

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:transformKey

7.82 ramlet:resourceProcessingSet Class name:

ramlet:resourceProcessingSet

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains collections of ramlet:dynamicStructure(s) (see 7.28) for an aggregation instance and the relationships among them, e.g., the relationship between computer programming code that is used to render a digital resource and that digital resource. [See also: ramlet:resourceProcessing (7.78).]

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mets:behaviorSec

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.83 ramlet:resourceProcessingType Class name:

ramlet:resourceProcessingType

Subclass of:

ramlet:resourceProcessing

Superclass of:

None

Scope note:

The category for a process required to make a digital resource renderable, e.g., decompression. [See also: ramlet:resourceProcessing (7.78).]

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:transformType

7.84 ramlet:resourceType Class name:

ramlet:resourceType

Subclass of:

ramlet:descriptorObject

Superclass of:

ramlet:mimeType

Scope note:

Provides a broad categorization of the media type of the associated digital resource, e.g., “web content” or “software application.”

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:type

7.85 ramlet:resourceWrapper Class name:

ramlet:resourceWrapper

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains an inline encoding of a digital resource that is represented within the aggregation definition document that describes an aggregation instance, e.g., a base64 encoding.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

atom:content mets:binData mets:xmlData

7.86 ramlet:resourceWrapperSet Class name:

ramlet:resourceWrapperSet

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains ramlet:resourceWrapper (see 7.85) instances.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

mets:fContent

7.87 ramlet:rights Class name:

ramlet:rights

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Contains information about the rights, obligations, and restrictions governing the use of an aggregation instance or a digital resource, e.g., Creative Commons Attribution-ShareAlike [B1] or an Open Digital Rights Language (ODRL) instance [B23].

Properties:

None

Data type:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Asserted conditions:

None

Examples:

atom:rights mets:rightsMd

7.88 ramlet:selection Class name:

ramlet:selection

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

Identifies one of a set of options within a ramlet:dynamicStructure (see 7.28) that can be chosen by a processing application to process the ramlet:dynamicStructure depending upon parameters such as user interaction. The members of the set, i.e., the ramlet:selection(s), represent the possible decisions of a particular choice (see 7.16).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:selection

7.89 ramlet:shapeIndicator Class name:

ramlet:shapeIndicator

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

The category for the shape of a ramlet:anchor (see 7.9), e.g., polygon or circle. Typically, this class is used with still-image or video-frame digital resources.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:shape

7.90 ramlet:source Class name:

ramlet:source

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Contains information about the original source of a digital resource, e.g., the technical characteristics of the audio tape from which an audio file has been digitized.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:sourceMd

7.91 ramlet:staticStructure Class name:

ramlet:staticStructure

Subclass of:

owl:class

Superclass of:

ramlet:staticStructureType

Scope note:

Contains the relationships among ramlet:structureNode(s) (see 7.98) within an aggregation instance. These relationships hold true regardless of the processing state of an aggregation instance.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

cp:organization mets:structMap mpeg:container

7.92 ramlet:staticStructureSet Class name:

ramlet:staticStructureSet

Subclass of:

owl:class

Superclass of:

None

Scope note:

Contains collections of staticStructure(s) (see 7.91).

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

cp:organizations

7.93 ramlet:staticStructureType Class name:

ramlet:staticStructureType

Subclass of:

ramlet:staticStructure

Superclass of:

None

Scope note:

The category for the ramlet:staticStructure (see 7.91) of an aggregation instance, e.g., tree or graph.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:structure mets:structMapType

7.94 ramlet:status Class name:

ramlet:status

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The status of the associated component, e.g., whether it is current or superseded information.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:recordStatus mets:status

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.95 ramlet:stream Class name:

ramlet:stream

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

Contains ramlet:locator(s) (see 7.53) to ramlet:descriptorObject(s) (see 7.24) for a byte stream within a digital resource, e.g., an audio stream within an MPEG–4 video file.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:stream

7.96 ramlet:streamType Class name:

ramlet:streamType

Subclass of:

ramlet:anchor

Superclass of:

None

Scope note:

The category for the stream identified within a digital resource, e.g., a Waveform Audio File Format (WAVE) (Multiple Channel Audio Data and WAVE Files [B21]) ramlet:stream (see 7.95) within a video resource.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:streamType

7.97 ramlet:structRef Class name:

ramlet:structRef

Subclass of:

ramlet:locator

Superclass of:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

A ramlet:locator (see 7.53) from ramlet:resourceProcessing (see 7.78) to a ramlet:structureNode (see 7.98), e.g., from a piece of executable code designed to display an Encoded Archival Description (EAD) [B4] finding aid to the finding aid text, or from a computer-aided design (CAD) rendering program to the CAD files.

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

Examples:

mets:structID

7.98 ramlet:structureNode Class name:

ramlet:structureNode

Subclass of:

owl:class

Superclass of:

None

Scope note:

A node in a structure that organizes digital resources in an aggregation instance. For example, a node may be a chapter within a book. [See also: ramlet:dynamicStructure (7.28), ramlet:staticStructure (7.91).]

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

None

Asserted conditions:

Examples:

cp:item mets:div mets:fptr mpeg:item oai-ore:proxy

7.99 ramlet:structureNodeType Class name:

ramlet:structureNodeType

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The category for a ramlet:structureNode (see 7.98), e.g., page or Shareable Content Object (SCO) (SCORM 2004 [B26]).

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:divType

7.100 ramlet:technicalDescriptorObject Class name:

ramlet:technicalDescriptorObject

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Contains information about technical aspects of a digital resource, e.g., a file’s format characteristics, such as the color profile and compressor-decompressor (CODEC) used to create a JPEG image (ISO 10918-1 [B13]).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:techMd

7.101 ramlet:textType Class name:

ramlet:textType

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

The format for text used in an associated container node, e.g., plain text or Hypertext Markup Language (HTML) (W3C [B27]).

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

atom:content.type atom:text.type

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

7.102 ramlet:title Class name:

ramlet:title

Subclass of:

owl:class

Superclass of:

ramlet:cardinalityLabel

Scope note:

A human-readable descriptor for a component in an aggregation instance.

Properties:

dcterms:isPartOf someValueFrom ramlet:topNode

Data type:

xsd:string

Asserted conditions:

Examples:

atom:label atom:link.title atom:title cp:lingualTitle cp:title mets:label

7.103 ramlet:topNode Class name:

ramlet:topNode

Subclass of:

owl:class

Superclass of:

None

Scope note:

The highest class level of an aggregation defined by an aggregation format.

Properties:

dcterms:hasPart someValueFrom one or more of ⎯

ramlet:aggregationID

⎯

ramlet:anchor

⎯

ramlet:descriptorObject

⎯

ramlet:digitalResource

⎯

ramlet:dynamicStructure

⎯

ramlet:elementID

⎯

ramlet:fileDescriptor

⎯

ramlet:groupingID

⎯

ramlet:hasOrder

⎯

ramlet:hasRank 53

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

⎯

ramlet:icon

⎯

ramlet:inventory

⎯

ramlet:locator

⎯

ramlet:locatorDescriptor

⎯

ramlet:parallel

⎯

ramlet:remoteNode

⎯

ramlet:resourceGroup

⎯

ramlet:resourceProcessingSet

⎯

ramlet:resourceWrapper

⎯

resourceWrapperSet

⎯

ramlet:staticStructure

⎯

ramlet:staticStructureSet

⎯

ramlet:structureNode

⎯

ramlet:title

Data type:

⎯ None

Asserted conditions:

Being a member of this class implies that an individual is a member of owl:class.

ramlet:topNode

Being a member of this class implies that an individual has some value of the property dcterms:hasPart that either ⎯

is a member of ramlet:aggregationID

⎯

or is a member of ramlet:anchor

⎯

or is a member of ramlet:descriptorObject

⎯

or is a member of ramlet:digitalResource

⎯

or is a member of ramlet:dynamicStructure

⎯

or is a member of ramlet:elementID

⎯

or is a member of ramlet:fileDescriptor

⎯

or is a member of ramlet:groupingID

⎯

or is a member of ramlet:hasOrder

⎯

or is a member of ramlet:hasRank

⎯

or is a member of ramlet:icon

⎯

or is a member of ramlet:inventory

⎯

or is a member of ramlet:locator

⎯

or is a member of ramlet:locatorDescriptor

⎯

or is a member of ramlet:parallel

⎯

or is a member of ramlet:remoteNode 54

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Examples:

⎯

or is a member of ramlet:resourceGroup

⎯

or is a member of ramlet:resourceProcessingSet

⎯

or is a member of ramlet:resourceWrapper

⎯

or is a member of resourceWrapperSet

⎯

or is a member of ramlet:staticStructure

⎯

or is a member of ramlet:staticStructureSet

⎯

or is a member of ramlet:structureNode

⎯

or is a member of ramlet:title

⎯ or is a member of ramlet:topNode atom:feed cp:manifest mets:mets mpeg:didl oai-ore:resourceMap

NOTE—Because ramlet:topNode is the highest class level defined by an aggregation format, it has all other classes as its potential constituent parts.

7.104 ramlet:transformOrdering Class name:

ramlet:transformOrdering

Subclass of:

ramlet:hasOrder

Superclass of:

None

Scope note:

A preferred order among instructions for processing a digital resource or portion thereof. [See also: ramlet:resourceProcessing (7.78).]

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mets:transformOrder

7.105 ramlet:true Class name:

ramlet:true

Subclass of:

ramlet:dynamicStructure

Superclass of:

None

Scope note:

Asserts an associated ramlet:condition (see 7.18) to be true.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

mpeg:true

7.106 ramlet:virtualResourceGroup Class name:

ramlet:virtualResourceGroup

Subclass of:

ramlet:virtualResource

Superclass of:

None

Scope note:

A reference to a ramlet:resourceGroup (see 7.76) to avoid repeated direct inclusion of its ramlet:fileDescriptor(s) (see 7.37). For example, each unique digital resource in a Web page could be listed in an aggregation instance as ramlet:resourceGroup A. A set of similar Web pages could have many files, such as scripting language scripts or style sheets, in common. Rather than list the common files with every resource group in an aggregation instance, they could be declared once as ramlet:resourceGroup B. A ramlet:virtualResourceGroup indicates that ramlet:resourceGroup A depends on another ramlet:resourceGroup B.

Properties:

None

Data type:

None

Asserted conditions:

None

Examples:

cp:dependency

7.107 ramlet:wholeAggregationDescriptorObject Class name:

ramlet:wholeAggregationDescriptorObject

Subclass of:

ramlet:descriptorObject

Superclass of:

None

Scope note:

Contains information about an aggregation instance itself, rather than the digital resources it aggregates, e.g., date of creation or life-cycle status.

Properties:

None

Data type:

None

Asserted conditions:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Examples:

cp:manifest.metadata mets:metsHdr mpeg:didlInfo

8. Conceptual model—object properties This clause provides declarations of all the object properties in the core ontology. The declarations use the following format: ⎯

Property name: The name of the property.

⎯

Subproperty of: The parent of the property. The property may inherit from its parent.

⎯

Superproperty of: The children of the property.

⎯

Scope note: A textual description of the property.

⎯

Has inverse: The inverse property of the property.

8.1 ramlet:describes Property name:

ramlet:describes

Subproperty of:

None

Superproperty of:

None

Scope note:

Expresses the fact that the associated component describes another component.

Has inverse:

ramlet:isDescribedBy

8.2 dcterms:hasPart Property name:

dcterms:hasPart

Subproperty of:

None

Superproperty of:

ramlet:includes ramlet:references

Scope note:

A related resource that is included either physically or logically in the described resource.

Has inverse:

dcterms:isPartOf

NOTE—As defined by the Dublin Core Metadata Initiative [B3]. The definition can be accessed at the following URI: http://www.dublincore.org/documents/2010/10/11/dcmi-terms/#terms-hasPart.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

8.3 ramlet:includes Property name:

ramlet:includes

Subproperty of:

dcterms:hasPart

Superproperty of:

None

Scope note:

A hierarchical relationship between two components. The component with the ramlet:includes property is the parent of the other component, known as the child. This property describes a purely syntactic relationship between components; it does not imply a refinement relationship.

Has inverse:

ramlet:isIncludedBy

NOTE—Semantically, this property is a refinement of the Dublin Core Metadata Initiative [B3] relation metadata term. The relation metadata element defined by IEEE Std 1484.12.1™–2002 [B5] is semantically equivalent to Dublin Core’s relation metadata term.

8.4 ramlet:isDescribedBy Property name:

ramlet:isDescribedBy

Subproperty of:

None

Superproperty of:

None

Scope note:

Expresses the fact that the associated component is described by another component.

Has inverse:

ramlet:describes

8.5 ramlet:isIncludedBy Property name:

ramlet:isIncludedBy

Subproperty of:

dcterms:isPartOf

Superproperty of:

None

Scope note:

A hierarchical relationship between two components. The component with the ramlet:isIncludedBy property is the child of the other component, known as the parent. This property describes a purely syntactic relationship between components; it does not imply a refinement relationship.

Has inverse:

ramlet:includes

8.6 dcterms:isPartOf Property name:

dcterms:isPartOf

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Subproperty of:

None

Superproperty of:

ramlet:isIncludedBy ramlet:isReferencedBy

Scope note:

A related resource in which the described resource is physically or logically included.

Has inverse:

dcterms:hasPart

NOTE—As defined by the Dublin Core Metadata Initiative [B3]. The definition can be accessed at the following URI: http://www.dublincore.org/documents/2010/10/11/dcmi-terms/#terms-isPartOf.

8.7 ramlet:isReferencedBy Property name:

ramlet:isReferencedBy

Subproperty of:

dcterms:isPartOf

Superproperty of:

None

Scope note:

The inverse of the ramlet:references property (see 8.8).

Has inverse:

ramlet:references

8.8 ramlet:references Property name:

ramlet:references

Subproperty of:

dcterms:hasPart

Superproperty of:

None

Scope note:

An arbitrary association between components signaled by an identifier reference to an identifier elsewhere. The component with the references property carries the reference to an identifier or identifiers of one or more other components.

Has inverse:

ramlet:isReferencedBy

NOTE—Semantically, this property is a refinement of the Dublin Core (DC) relation metadata term (Dublin Core Metadata Initiative [B3]). The relation metadata element defined by IEEE Std 1484.12.1–2002 [B5] is semantically equivalent to DC’s relation metadata term.

9. Conceptual model—data types This clause provides declarations of all the data types in the core ontology. The declarations use the following format: ⎯

Name: The name of the data type.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

⎯

Definition: The URI for the W3C definition of the data type. The definitions are from W3C Recommendation, XML Schema Part 2: Datatypes.

9.1 xsd:anyURI Name:

xsd:anyURI

Definition:

See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI

9.2 xsd:base64Binary Name:

xsd:base64Binary

Definition:

See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#base64binary

9.3 xsd:positiveInteger Name:

xsd:positiveInteger

Definition:

See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#positiveinteger

9.4 xsd:string Name:

xsd:string

Definition:

See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#string

9.5 xsd:token Name:

xsd:token

Definition:

See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#token

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex A (informative) Bibliography Bibliographical references are resources that provide additional or helpful material but do not need to be understood or used to implement this standard. Reference to these resources is made for informational use only. [B1] Attribution-ShareAlike 3.0, Creative Commons. 9 [B2] Costello, R. L., and D. B. Jacobs, OWL Web Ontology Language. The Mitre Corporation, 2008, sponsored by the Defense Advanced Research Projects Agency (DARPA). 10 [B3] Dublin Core Metadata Initiative Recommendation (10 November 2010), DCMI Metadata Terms. 11 [B4] Encoded Archival Description, Version 2002, Library of Congress and Society of American Archivists. 12 [B5] IEEE Std 1484.12.1™-2002, IEEE Standard for Learning Object Metadata. 13 [B6] IETF RFC 1321, The MDF Message–Digest Algorithm. 14 [B7] IETF RFC 2046, Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. 15 [B8] IETF RFC 4287, The Atom Syndication Format. 16 [B9] IMS Specification, IMS Content Packaging Specification Information Model, Version 1.2, Public Draft 2. 17 [B10] ISO 2108, Information and documentation—International standard book number (ISBN). 18 [B11] ISO 2146, Information and documentation—Registry services for libraries and related organizations. [B12] ISO 26324, Information and documentation—Digital Object Identifier System. [B13] ISO/IEC 10918-1, Information Technology—Digital compression and coding of continuous-tone still images: Requirements and guidelines. [B14] ISO/IEC 13818-3, Information technology—Generic coding of moving pictures and associated audio information—Part 3: Audio.

Creative Commons licensing documents are available at http://creativecommons.org/. See: https://mentor.ieee.org/ramlet/dcn/10/ramlet-10-0002-00-Docs-owl-web-ontology-language.ppt. 11 DCMI Metadata Terms is available at http://www.dublincore.org/documents/2010/10/11/dcmi-terms/. 12 Encoded Archival Description, Version 2002, is available at http://www.loc.gov/ead/. 13 IEEE publications are available from the Institute of Electrical and Electronics Engineers, Inc., 445 Hoes Lane, Piscataway, NJ 08854, USA (http://standards.ieee.org/). 14 IETF RFC 1321 is available at http://datatracker.ietf.org/doc/ rfc1321/. 15 IETF RFC 2046 is available at http://datatracker.ietf.org/doc/rfc2046/. 16 IETF RFC 4287 is available at http://tools.ietf.org/html/ rfc4287. 17 IMS publications are available from the IMS Global Learning Consortium at http://www.imsglobal.org/specifications.html. 18 ISO/IEC publications are available from the ISO Central Secretariat (http://www.iso.org/). ISO publications are also available in the United States from the American National Standards Institute (http://www.ansi.org/). 10

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

[B15] ISO/IEC 21000-2:2005, Information technology—Multimedia framework (MPEG-21), Part 2: Digital Item Declaration, Second edition. 19 [B16] Koopman, P., 32–bit cyclic redundancy codes for Internet applications, The International Conference on Dependable Systems and Networks: 459, June 2002. [B17] Kraan, W., RAMLET implementation study report, JISC–CETIS, August 2008. 20 [B18] MARC 21, Specifications for Record Structure, Character Sets, and Exchange Media, January 2000. 21 [B19] METS, Metadata Encoding and Transmission Standard: Primer and Reference Manual, Version 1.6, Revised, 2010. 22 [B20] METS, METS Schema Documentation, Version 1.7. 23 [B21] Multiple Channel Audio Data and WAVE Files, Microsoft Corporation, March 2007. 24 [B22] Open Archives Initiative, Object Reuse and Exchange, ORE Specification—Abstract Data Model, Version 1.0, October 2008. 25 [B23] Open Digital Rights Initiative, ODRL Version 2.0 Draft. 26 [B24] Perl 5 version 12.2 documentation. 27 [B25] RSS Specification, RSS Advisory Board. 28 [B26] SCORM 2004 4th Edition, Advanced Distributed Learning Initiative, August 2009. 29 [B27] W3C Recommendation, HTML 4.01 Specification. 30 [B28] W3C Recommendation, Namespaces in XML 1.0 (Third Edition). 31 [B29] W3C Recommendation, OWL 2 Ontology Language Document Overview. 32 [B30] W3C Recommendation, RDF Primer. 33 [B31] W3C Recommendation, RDF Vocabulary Description Language 1.0: RDF Schema. 34 [B32] W3C Recommendation, RDF/XML Syntax Specification. 35 [B33] W3C Working Group Note, SKOS Simple Knowledge Organization System Primer. 36

ISO/IEC 21000–2:2005 (MPEG–21, Part 2) is available for download at http://standards.iso.org/ittf/PubliclyAvailableStandards/ c041112_ISO_IEC_21000-2_2005(E).zip. 20 RAMLET implementation study report is available at http://digitalcommons.bolton.ac.uk/iec_reports/28/. 21 MARC 21 is available at http://www.loc.gov/marc/specifications/spechome.html. 22 Metadata Encoding and Transmission Standard: Primer and Reference Manual, Version 1.6, Revised, 2010, is available at http://www.loc.gov/standards/mets/METSPrimerRevised.pdf. 23 METS Schema Documentation, Version 1.7, is available at http://www.loc.gov/standards/mets/docs/mets.v1-7.html. 24 Multiple Channel Audio Data and WAVE Files is available at http://www.microsoft.com/whdc/device/audio/multichaud.mspx. 25 ORE Specification—Abstract Data Model is available at http://www.openarchives.org/ore/1.0/datamodel. 26 ODRL Version 2.0 Draft is available at http://www.w3.org/community/odrl/two/. 27 Perl 5 version 12.2 is available at http://www.perl.org/. 28 RSS Specification is available at http://www.rssboard.org/rss-specification. 29 SCORM 2004 4th Edition is available at http://www.adlnet.gov/. 30 HTML 4.01 Specification is available at http://www.w3.org/TR/REC-html40/. 31 Namespaces in XML is available at http://www.w3.org/TR/ REC-xml-names/. 32 OWL 2 Ontology Language Document Overview is available at http://www.w3.org/ TR/owl2-overview/. 33 RDF Primer is available at http://www.w3.org/TR/rdf-primer/. 34 RDF Vocabulary Description Language 1.0: RDF Schema is available at http://www.w3.org/TR/rdf-schema/. 35 RDF/XML Syntax Specification is available at http://www.w3.org/TR/REC-rdf-syntax/. 36 SKOS Simple Knowledge Organization System Primer is available at http://www.w3.org/TR/skos-primer/.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

[B34] W3C Recommendation, SPARQL Query Language for RDF. 37 [B35] W3C Team Submission, Turtle—Terse RDF Triple Language. 38 [B36] W3C Recommendation, XML Linking Language (XLink) Version 1.0. 39 [B37] W3C Recommendation, XML Path Language (XPath) 2.0. 40 [B38] W3C Recommendation, XSL Transformations (XSLT) Version 2.0. 41

SPARQL Query Language for RDF is available at http://www.w3.org/TR/rdf-sparql-query/. Turtle—Terse RDF Triple Language is available at http://www.w3.org/ TeamSubmission/turtle/. 39 XML Linking Language (XLink) Version 1.0 is available at http://www.w3.org/TR/2001/REC-xlink-20010627/. 40 XML Path Language (XPath) 2.0 is available at http://www.w3.org/TR/xpath20/. 41 XSL Transformations (XSLT) Version 2.0 is available at http://www.w3.org/ TR/xslt20/. 38

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex B (informative) Conceptual overview

B.1 Resource aggregations Resource aggregation is the process of gathering digital resources and describing their structures so that the resulting resource aggregation can be used for transmission, storage, and delivery to users. The creators of digital materials for learning, education, and training usually draw together more than one digital resource to create a group of related resources. Creators may apply a structure to this group of digital resources and associate it with descriptions of the educational and technical attributes of the group as a whole and of each individual resource. Information intended to aid in the management over time of the group of digital resources may also be created. Many people have realized the benefits of sharing these materials between communities. To make the materials useful when shared, the accompanying information needs to be persistently associated with the group of digital resources so that the resources and the accompanying information become a single, identifiable, resource aggregation. To facilitate the exchange and interoperability of resource aggregations, communities of practice have created agreements known as aggregation formats that document the methods of aggregating digital resources into objects that can be exchanged among systems. An aggregation format may be defined by a formal specification or standard, but may also be informal. The defining characteristic is that an aggregation format specifies how to combine digital resources into a structured whole without prescribing the kinds of digital resources, their internal structures, or their intended uses. A resource aggregation is instantiated using an aggregation definition document, a document that lists and structures the digital resources of an aggregation. Examples include the manifest document defined by IMS Content Packaging (IMS CP) (IMS Specification [B9]), the mets documents of Metadata Encoding and Transmission Standard (METS) ([B19], [B20]), and the Digital Item Declaration Language (DIDL) document of MPEG-21 Digital Item Declaration (DID) (ISO/IEC 21000-2:2005 [B15]).

B.2 Why and how the conceptual model and mapping recommended practices were developed Individual communities have developed different aggregation formats, each focusing on that communityâ&#x20AC;&#x2122;s special needs and requirements. There is a need to exchange resource aggregations between communities that may be using different aggregation formats. In these cases, it is necessary to map between aggregation formats. Several use cases (see Annex D) were used by the Resource Aggregation Models for Learning, Education, and Training (RAMLET) Working Group to inform the approach used to develop the RAMLET conceptual model described in this standard. Different methods, such as Extensible Stylesheet Language Transformations (XSLT) (W3C [B38]) and Perl scripts (Perl [B24]) have been used to undertake mappings between aggregation formats with varying degrees of information loss. This standard uses a Semantic Web technology approach in the form of a conceptual model to map between aggregation formats. The conceptual model describes the functional similarities of and the relationships among the components of the data models of various aggregation formats. It focuses on the structures of aggregation formats by analyzing and describing the functional characteristics of common structural elements, then abstracting and expressing them in ontological form as

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

a core ontology. Figure B.1 shows the relationship between the extent of the conceptual model and aggregation formats.

Resource Aggregation Format 1

Resource Aggregation Format 3

Resource Aggregation Format 2

RAMLET Conceptual Model

Figure B.1—Extent of the conceptual model and aggregation formats Significant concepts within the conceptual model map to significant concepts of different aggregation formats, thus identifying the overlaps and differences among them. Not all concepts within the conceptual model may be present in any particular aggregation format. However, for those aggregation formats that have been authoritatively mapped to the conceptual model in the course of its development, all structural details of the aggregation formats are represented in the model. The conceptual model does not address generic content models, such as that described in the Abstract Learning Object Content Model (ALOCOM), or informational properties of the content of resource aggregations. 42 For example, the conceptual model is not concerned with the semantic relationship between sections and chapters of a book or with the interactive properties of different media types. Because overlaps exist between the structural descriptions provided by the conceptual model and generic content models, software developers, content managers, and other information specialists will need to consider how these different informational aspects relate to their specific circumstances. A clear set of principles was used in the development of the conceptual model, as follows:

⎯

Describe only the semantics of the functionality of each component as described in the data models of the aggregation formats.

⎯

Do not describe the epistemological status or pedagogical import of a component.

⎯

The upper and lower boundaries of the model are, respectively, ramlet:resourceAggregation and ramlet:digitalResource and its children. Although two of the boundary classes have real-world examples, it is not a requirement that boundary classes have examples.

More information on the ALOCOM project is available at http://www.cs.kuleuven.be/groups/hmdb/alocom/index.php.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

⎯

Between the boundary classes of the conceptual model, include only classes that have real-world examples.

⎯

Do not describe the internal structures of the digital resources that are aggregated. Digital resources are treated as black boxes.

⎯

Do not describe the epistemological, instructional, or educational purposes of the digital resources that are aggregated.

⎯

Do not specify processing methods for resource aggregations.

⎯

Do not describe the internal structures of descriptive metadata schemas.

NOTE 1—The ramlet:resourceAggregation (see 7.75) and ramlet:digitalResource (see 7.26) classes in the conceptual model are exceptions to the requirement that real-world examples exist. These classes function as facades for the upper and lower boundaries of the model, respectively. NOTE 2—The description of the epistemological, instructional, or educational purposes of the digital resources could be the role of another standardization activity, based on the previously mentioned work of the ALOCOM project and the Organization for the Advancement of Structured Information Standards (OASIS) Darwin Information Typing Architecture (DITA) Learning and Training Content Specialization Subcommittee. 43

B.3 Why use an ontological approach and OWL? The conceptual model has been developed using an ontological approach and the set of principles described in B.2. Five aggregation formats, IMS CP, METS, MPEG-21 DID, Atom Syndication Format (Atom) (IETF RFC 4287 [B8]), and Open Archives Initiative Object Reuse and Exchange (OAI-ORE) (Open Archives Initiative [B22]), were analyzed, and a core ontology was constructed that represents an abstract generalization of the aggregation formats. For example, the ramlet:topNode class (see 7.103) represents the root data element of a resource aggregation and corresponds to the IMS CP manifest, Atom feed, METS mets, OAI-ORE resourceMap, and MPEG-21 DID DIDL data elements. By mapping each component of multiple aggregation formats to the core ontology described in this standard, mappings can then be generated between aggregation formats. To develop the conceptual model, each of the five aggregation formats were analyzed and applied to the developing ontology. The ontology was refined to avoid inconsistencies until the conceptual model was expressed as a core ontology. Mappings were then defined between the conceptual model and the aggregation formats and expressed as ontologies. These mappings will be published as IEEE recommended practices. The conceptual model was first implemented in the World Wide Web Consortium (W3C) Web Ontology Language (OWL) [B29] and then expressed in human-readable tables in this standard. OWL was selected for use as a formalism for expressing the structural concepts of the conceptual model and their interrelationships for the following reasons: ⎯

OWL is an open standard.

⎯

OWL allows expression of the relationships between components explicitly.

⎯

OWL allows a well-understood method of specialization.

⎯

OWL is part of a Semantic Web technology stack that was designed to deal with heterogenous data.

⎯

OWL is supported by readily available and well-developed tools, including open source tools that were available to the RAMLET Working Group.

More information on the DITA Learning and Training Content Specialization Subcommittee is available at http://wiki.oasisopen.org/dita/LearningSubcommittee.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

The OWL expression of the conceptual model was developed first because the explicit semantics require the model to be described rigorously, and this formalism can be enforced with OWL development tools. Ontology mappings defined by RAMLET are bidirectional, that is, an IMS CP resource aggregation can be expressed using RAMLET terms and vice versa. To map resource aggregation instances from one aggregation format, such as IMS CP, to another, such as METS, two steps are required. First, a mapping is made from the IMS CP instance to the core ontology and then from the core ontology to the METS instance. This approach can scale as the number of aggregation formats increases. To include a new aggregation format, such as Really Simple Syndication (RSS) (RSS Specification [B25]), only a bidirectional mapping between the core ontology and the new aggregation format would need to be expressed. Without the RAMLET conceptual model, instead of a single mapping from RSS to the core ontology, individual mappings from RSS to all other aggregation formats of interest would need to be developed (e.g., RSS to Atom, RSS to METS, RSS to MPEG-21 DID). RAMLET provides an integrative conceptual model that covers IMS CP, MPEG-21 DID, METS, Atom and OAI-ORE. Coverage of these aggregation formats implies that all data elements of these formats are represented in the conceptual model, which enables lossless transformation from the aggregation formats to the conceptual model. However, a potential loss of information exists when translating from an aggregation instance in one format to the core ontology and then to an aggregation instance in another format (e.g., METS to RAMLET to IMS CP), depending on the semantic overlap between the source and target aggregation formats. Although the transformation between resource aggregations is not always lossless, important structural relationships should be preserved, thus achieving a maximal preservation of meaning.

B.4 Extension and use of the core ontology In addition to a maximal preservation of meaning, the RAMLET approach has the advantage of scalability as the number of aggregation formats increases. Adding an aggregation format requires only one additional mapping ontology to establish formal relationships between the new format and all existing mapped formats. While the addition of a new format would leave the mapping from the core ontology to the existing mappings unchanged, the maximal preservation of meaning from the additional mapping to the core would probably require an extension to the core. Such an extension would capture those components of the new aggregation format that are unique to that format. The core ontology can also be used to develop new aggregation formats, both because it records many of the components that have already been used in content aggregation, and—via the mappings—because it indicates how widely those components are used in existing formats. In addition, generalizations about how the various components relate to each other are captured by the core and mapping ontologies. Consequently, it is easier for communities to follow good practice and design new formats that stay within the bounds of the semantics of existing formats as much as possible, adding new functionality only where absolutely necessary. Because the RAMLET core and mapping ontologies have been formulated using standard Semantic Web technology, extensions to the ontologies can be easily accommodated by defining equivalence, refinement, inclusion, or any other relationship between the extensions and the existing ontology using OWL and other Resource Description Framework (RDF) (W3C [B30]) vocabularies, such as RDF Schema (RDFS) (W3C [B31]) and Simple Knowledge Organization System (SKOS) (W3C [B33]). Likewise, the ontologies can be combined with existing vocabularies or ontologies that are designed to describe aspects of a resource aggregation other than interpreting externalized representations of digital aggregations. One such combination that is immediately obvious is the augmentation of the RAMLET conceptual model with descriptive metadata schemes. Many resource aggregations contain descriptive metadata of some kind that would be well worth preserving in a RAMLET-enabled environment. Another

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

case would be the combination of the RAMLET conceptual model with generic content models such as ALOCOM or DITA.

B.5 The binding of the core ontology An OWL ontology can be represented or bound in several different ways so that it can be used by different implementation systems. A Resource Description Framework/Extensible Markup Language (RDF/XML) (W3C [B32]) representation is provided as downloadable files (see Annex I). The advantage of RDF/XML is that it is among the more widely implemented RDF binding formats and can easily be translated into other binding formats using a variety of tools. A Terse RDF Triple Language (Turtle) (W3C [B35]) representation is provided as a downloadable file because it is one of the more human readable RDF bindings (see Annex H). In terms of which RDF statements get expressed where, it is possible to express both the core ontology and all the mapping ontologies in a single document. For some implementations, that may well be the most expedient way of making use of this standard. For the standard itself, however, the core ontology and each of the mappings have their own namespaces and are represented in their own files, mainly to aid maintainability. A change to one ontology can leave the other ontologies unaffected. In order to express how the mapping ontologies relate to the core ontology, the file set for the standard and associated recommended practices has been structured so that the core ontology file imports the other files. By extension, it is advisable to explore the mapping ontologies through the core ontology in this manner, because it will place the mapping-to-core relationships in their complete context. Looking at the mappings in isolation of the core ontology means that similarities with other formats will be missed as will crucial information about the structure of the relevant core ontology classes and properties. The core ontology, as distributed, will import the latest version of each mapping ontology. Persistent identifiers are allocated to each version of the mapping ontologies, and the core ontology can be edited to import specific versions of the mapping ontologies, if required, by using the relevant persistent identifiers. In this standard, class and property names are represented in camel case for human readability and in lowercase in the binding files for processability. The underlying reason is that, though aggregation formats may prescribe case, actual aggregation definition documents are rather variable in practice. Tools also vary in their case sensitivity. Therefore, in order to aid transformation and querying, it is easiest to reduce all incoming data to lowercase, and the ontology binding files reflect this. Finally, although the cardinalities for data types are included in the downloadable files for the core ontology (see Annex I), they are not included in the class tables in this standard (see Clause 7) because the cardinality requirements for the core ontology are minimally restrictive. The cardinality requirements for the aggregation formats that are mapped to the core ontology in the mapping recommended practices vary and are more restrictive. Therefore, cardinality requirements for each aggregation format will be found in the mapping recommended practices.

B.6 Implementation experiences Various options and architectures for the implementation of a RAMLET-based infrastructure have been proposed in a RAMLET implementation study report (Kraan [B17]). It concluded that, although a centralized repository using RAMLET-structured RDF was one way of providing transformations from one aggregation format to another, a more distributed architecture was likely to be more resilient and easier to implement. In such a distributed architecture, existing repositories of content aggregations could implement an agent or SPARQL Protocol and RDF Query Language (SPARQL) (W3C [B34]) endpoint to expose their contents, which could then be queried in RAMLET terms and the return transformed into the desired aggregation definition document. Work on the required XSLTs and SPARQL queries continues.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex C (informative) Ontologiesâ&#x20AC;&#x201D;a brief primer As discussed in Annex B, the core ontology defines a conceptual model for interpreting externalized representations of resource aggregations by describing the functional semantics of the components of existing aggregation formats. That is, it describes what the components of the various formats are designed to do in the aggregation definition documents that practitioners are generally used to seeing. The externalized representations of the core ontology look much like such aggregation definition documents and necessarily use familiar terms and concepts. Like those definition documents, the core ontology also has classes with parents and children, but the parent/child relationship means something quite different. In the core ontology, a child represents a specialization of its parent. An IMS Content Packaging (IMS CP) manifest (IMS Specification [B9]), for example, is a more narrowly defined ramlet:topNode (see 7.103) because it only applies to IMS CP. Likewise, ramlet:identifierType (see 7.47) is narrower than its ramlet:descriptorObject (see 7.24) parent, because it only describes identifiers. In contrast, a parent/child relationship in a definition document only indicates a place to put information and need not make any statement about the nature of the information. The core ontology comprises a set of classes. A class is a category of items that share one or more common characteristics. Characteristics can be described informally in a scope note or formally as properties explicitly formulated in logical terms. A class cannot be defined by enumerating its instances because it is generally impossible to know all existing instances of a class in the world and the future can bring new instances into being at any time. This standard is based on the concept of an open world, which assumes that an ontology and its instances are incomplete with regard to the world they attempt to describe. As a consequence, the open-world assumption states that everything that is not known is undefined. (In contrast, a closed-world assumption implies that everything that is not known is false.) Therefore, this standard provides examples of class instances based on the recommended-practice mappings of aggregation formats, but we would expect that additional examples will be found in other aggregation formats as they are mapped. A class may have subclasses, superclasses, or both. A subclass is a specialization of one or more superclasses. A subclass inherits all the properties of its superclasses (i.e., strict inheritance) in addition to having zero or more additional properties of its own. If a subclass inherits properties from more than one superclass, it is said to have multiple inheritance. A superclass is a generalization of one or more other classes, which are its subclasses. A superclass subsumes all instances of its subclasses and may have additional instances that do not belong to any of its subclasses. (A superclass/subclass relationship may also be referred to as a parent/child relationship.) The intention, or intended meaning, of a superclass is less restrictive than the intentions of any of its subclasses. The intention consists of the common characteristics shared by all instances of a class or property. The intention need not be explicitly formulated as properties in the case of a class or as the domain and range in the case of a property. Instead, the intention can be described in a scope note that refers to a conceptualization shared by domain experts. A property is a characteristic that defines a relationship of a specific kind between two sets of classes. A property has exactly one domain and one range. The domain is a constraint on a property that limits the instances of the classes to which the property can be applied. Instances of a property are applicable to instances of its domain. For example, if property A has only the classes X and Y as a domain, then only instances of classes X and classes Y can have property A. The range is the set of instances of a given class

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

to which a property can be applied, i.e., the range of property A consists of those instances of class X and class Y that exhibit property A. A property can link only to instances of the classes that serve as its range. Which classes are selected as the domain and which as the range of a property is arbitrary. In other words, a property can be understood in both directions with two distinct but related interpretations. Property names are designed to be semantically meaningful and grammatically correct when read from domain to range. Inverse property names are designed to be semantically meaningful and grammatically correct when read from range to domain. For example, the property ramlet:includes (see 8.3) has an inverse property of ramlet:isIncludedBy (see 8.5). Properties can be specialized in the same manner as classes, resulting in parent/child relationships between superproperties and their subproperties. Like a class, a property is characterized by an intention, which is conveyed by a scope note. Inheritance is the ability of classes to derive characteristics from other classes and properties to derive characteristics from other properties. If characteristics are removed from a class or property, they are also removed from its subclasses or subproperties. Multiple inheritance is the inheritance of characteristics by a class from more than one immediate superclass or by a property from more than one immediate superproperty. If multiple inheritance is used, the resulting class or property hierarchy is a directed graph, not a tree structure. If multiple inheritance in a class or property hierarchy is represented as an indented list, then some classes or properties will inevitably be repeated at different positions in the indented list. For example, “person” could be a member of both the classes “critic” and “author,” and, therefore, would be repeated at different positions in the indented list. This feature distinguishes an ontology from a simple tree structure. An instance of a class has properties that meet the criteria of the intention of the class. The number of instances of a class declared in an information system is usually less than the total number of instances in the real world. For example, although an individual is an instance of the class “person,” the individual may not be mentioned in all information systems describing “persons.” A useful tutorial on the Web Ontology Language (OWL) (Costello and Jacobs [B2]) is available online at the following URI: https://mentor.ieee.org/ramlet/dcn/10/ramlet-10-0002-00-Docs-owl-web-ontology-language.ppt The starting point for W3C information on vocabularies and pointers to working groups, specifications, and information on books and papers collected by W3C members resides in the ontologies section of the W3C Web site. 44

The ontologies section of the W3C Web site is available at http://www.w3.org/standards/semanticweb/ontology.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex D (informative) Use cases This annex describes several use cases that were used to inform the approach to the development of the conceptual model described in this standard. Support for a given use case assumes that mappings of the associated aggregation formats to the conceptual model are available. Recommended practices planned for the IEEE 1484.13™ series are IMS Content Packaging (IMS CP) (IMS Specification [B9]), MPEG-21 Digital Item Declaration (DID) (ISO/IEC 21000-2:2005 [B15]), Metadata Encoding and Transmission Standard (METS) ([B19], [B20]), Atom Syndication Format (Atom) (IETF RFC 4287 [B8]), and Open Archives Initiative Object Reuse and Exchange (OAI-ORE) (Open Archives Initiative [B22]). The use cases are not exhaustive. The conceptual model could be applied to additional contexts in learning, education, and training assuming appropriate mappings for additional aggregation formats are developed. NOTE 1—Use case support may be limited by the extent that equivalent capabilities exist in different resource aggregation specifications. As a result, mappings between aggregation formats may not be lossless. NOTE 2—Support for use cases is limited to interpretation of the aggregation formats using the conceptual model. Direct conversions between different aggregation formats are not supported. NOTE 3—The figures in this annex are intended to be high-level illustrations of data flows and are not intended to illustrate transactional procedures. NOTE 4—Digital resources, including other resource aggregations, may be imported into a resource aggregation either by inclusion or reference. A resource aggregation may contain only descriptions of digital resources and locators for resources and may not actually contain any resources.

D.1 Use case 1 Exchange and reuse of resource aggregations among systems using different specifications. For example, a system using METS might import resource aggregations that use IMS CP, MPEG-21 DID, and Atom and create a new resource aggregation. D.1.1 Usage scenario A content author in a university is developing a new resource aggregation and wishes to include digital resources from different sources, including learning resources, reference materials, and research data. The author searches for appropriate materials and retrieves each digital resource to an authoring system. The resources are exported from their repositories in aggregation formats specific to their respective repositories. The authoring system interprets the incoming aggregation formats and converts them to its native format. The author then creates the new resource aggregation, including the imported digital resources, and makes the new resource aggregation available to the local learning management system (LMS) or run-time system (RTS). The new resource aggregation is in the resource format used by the authoring system. Figure D.1 illustrates this scenario.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

IMS CP Resource Aggregation METS Resource Aggregation MPEG–21 DID Resource Aggregation ATOM Resource Aggregation

R A M L E T

Authoring System Aggregation Process

Resource Aggregation in Authoring System Aggregation Format

T R A N S F O R M

LMS/ RTS

Figure D.1—Use case 1 usage scenario example D.1.2 Use case summary: retrieve–interpret–aggregate–deploy This use case addresses retrieving resource aggregations from diverse digital resource repositories that provide resource aggregations in different aggregation formats. The aggregation formats of the retrieved resource aggregations are interpreted and transformed into a single aggregation format that can be used by an authoring system, and then aggregated into a new resource aggregation. The new resource aggregation can be deployed by an LMS/RTS that is limited to a single aggregation format.

D.2 Use case 2 Exchange and reuse of individual digital resources of resource aggregations among systems using different aggregation formats. For example, a system using METS might import resource aggregations that use IMS CP, OAI-ORE, MPEG-21 DID, and Atom and create new aggregations from the digital resources from one or more of these resource aggregations. D.2.1 Usage scenario A content author in a university is developing a new resource aggregation and wishes to include digital resources from different sources, including learning resources, reference materials, and research data. The content author searches for appropriate materials. Some of these digital resources are parts of resource aggregations, but the author wishes to use the appropriate parts only and not the whole resource aggregation. The author retrieves each digital resource in its resource aggregation to an authoring system. The resources are exported from their repositories in aggregation formats specific to their respective repositories. The authoring system interprets the incoming aggregation formats and converts them to its native format. The content author then creates the new resource aggregation, including complete imported resource aggregations and individual digital resources disaggregated from their parent resource aggregations. The

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

author makes the new resource aggregation available to the local LMS. The new resource aggregation is in the aggregation format used by the authoring system. Figure D.2 illustrates this scenario.

IMS CP Resource Aggregation OAI–ORE Resource Aggregation MPEG–21 DID Resource Aggregation ATOM Resource Aggregation

R A M L E T T R A N S F O R M

Authoring System Aggregation Process

METS Resource Aggregation

LMS/ RTS

Figure D.2—Use case 2 usage scenario example D.2.2 Use case summary: retrieve–interpret–disaggregate–aggregate–deploy This use case addresses retrieving resource aggregations from diverse resource repositories that provide resource aggregations in different aggregation formats. The retrieved resource aggregations are interpreted and converted into a single format that can be used by an authoring system. Some of the resource aggregations are disaggregated so that individual digital resources may be used. Resource aggregations and individual digital resources are then aggregated into a new resource aggregation. The new resource aggregation can be deployed by an LMS/RTS that is limited to a single aggregation format.

D.3 Use case 3 Import, store, and make available resource aggregations from systems using different specifications. For example, a system using METS might import resource aggregations that use IMS CP, OAI-ORE, Atom, and MPEG-21 DID and store them in a single aggregation format. D.3.1 Usage scenario A librarian is helping a teacher collect digital resources that are relevant to the unit he or she is teaching and wishes to store the digital resources in a local repository for student access. They discover relevant digital resources in several different repositories and retrieve each digital resource. The digital resources are exported from their repositories in aggregation formats specific to their respective repositories. The local repository stores resource aggregations in a single aggregation format. Upon import to the local repository, the incoming aggregation formats are interpreted and the resource aggregations are stored in the aggregation format supported by the local repository.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Students are directed to the digital resources in the local repository by the teacher, and the access system is able to display the material using the aggregation format supported by the local repository. Figure D.3 illustrates this scenario.

R A M L E T

IMS CP Store

OAI–ORE Store

T R A N S F O R M

MPEG–21 DID Store

ATOM Store

Accessible Local Repository METS Store

Figure D.3—Use case 3 usage scenario example D.3.2 Use case summary: retrieve–interpret–store–provide This use case addresses retrieving resource aggregations from diverse digital resource repositories that use different aggregation formats, interpreting the different formats, storing the resource aggregations in a single format, and providing the digital resource aggregations in a single format.

D.4 Use case 4 Import, store, and exchange resource aggregations from systems using different specifications. For example, a system using METS might import and export resource aggregations that use IMS CP, OAIORE, and MPEG-21 DID in addition to METS. D.4.1 Usage scenario Resource suppliers provide digital resources to a resource exchange in the aggregation formats that are exported by their respective resource repositories, which may include different formats. Upon import to the resource exchange, the incoming aggregation formats are interpreted and converted to the specific aggregation format supported by the resource exchange. Resource consumers search the resource exchange and download digital resources to their local systems. Upon download, a consumer can specify the aggregation format preferred by the consumer’s local 74

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

repository. Upon export, the resource repository converts its aggregation format to the format supported by the consumer’s repository. Figure D.4 illustrates this scenario.

IMS CP Store

METS Store

MPEG–21 DID Store

OAI–ORE Store

R A M L E T T R A N S F O R M

R A M L E T Accessible Local Repository METs Store

T R A N S F O R M

IMS CP Store

METS Store

MPEG–21 DID Store

OAI–ORE Store

Figure D.4—Use case 4 usage scenario example D.4.2 Use case summary: retrieve–interpret–store–interpret–provide This use case addresses retrieving resource aggregations from diverse resource repositories that use different aggregation formats, interpreting the different formats, storing the resource aggregations in a single format, and providing the resource aggregations in multiple formats. When a resource aggregation is provided it will either be provided in the repository-specific format or interpreted and provided in the user’s preferred aggregation format.

D.5 Use case 5 A repository stores resources in diverse aggregation formats but supports a delivery system that can render only one such format. For example, a repository might store resource aggregations that use IMS CP, MPEG-21 DID, OAI-ORE, and the format used by a student-information store, and support a delivery system that uses IMS CP only. D.5.1 Usage scenario A content author is developing a new resource aggregation in an authoring system for an equipment manufacturer. The new resource aggregation will include several resources from different sources, including simulations, multimedia materials, and existing general learning resources (e.g., a digital resource describing an electrical safety procedure). The author searches for appropriate materials and retrieves each digital resource or resource aggregation, or a locator [e.g., a Uniform Resource Identifier (URI)], Uniform Resource Name (URN), Uniform Resource Locator (URL), or other resolvable identifier] for the digital resource or resource aggregation into the authoring system. A digital resource or resource aggregation is either exported from its repository in the aggregation format used by that repository or is referenced and remains in the original repository in the original format. Imported resource aggregations retain their original aggregation formats. 75

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

The author creates the new resource aggregation, which includes the imported and referenced resource aggregations, and makes it available to the local LMS. When a student accesses the new resource aggregation in the LMS and uses one of its individual resource aggregations, the LMS interprets the individual aggregation format. The individual resource aggregation retains its format from the originating repository. Figure D.5 illustrates this scenario.

IMS CP Store

MPEG–21 DID Store

OAI–ORE Store

Student information System

Locator (eg URI, URN, URL)

Authoring System Aggregation Process

Authoring System Created R esource Aggregation

IMS CP Interactive Simulation Resource Aggregation

MPEG–21 Resource Aggregation

OAI–ORE Resource Aggregation

Student Learning Context

R A M L E T T R A N S F O R M

LMS/ RTS

Student Learning Context

Figure D.5—Use case 5 usage scenario example D.5.2 Use case summary: retrieve–aggregation–interpret–deploy This use case addresses retrieving digital resources and resource aggregations, either directly or by reference, from diverse resource repositories that use different aggregation formats. These resource aggregations are aggregated into a new resource aggregation. They retain their original aggregation formats as parts of a larger resource aggregation. The individual resource aggregations are interpreted when they are deployed by an LMS/RTS that understands the repository’s format and the formats used by the individual resource aggregations. This use case is similar to use case 1 (see D.1), but the conversion takes place at run time. The original data is not altered. NOTE—The amount of loss among the mappings may change over time as various resource aggregation specifications evolve. One advantage of run-time interpretation may be that a mapping done at a future time may be able to take advantage of improved mapping features.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

D.6 Use case 6 An LMS creates a resource aggregation at run time, and will import, store, and make available to end users resource aggregations from systems using different specifications. For example, a system using its own internal format might import resource aggregations that use IMS CP, MPEG-21 DID, OAIORE, and METS at the time they are required in the learning path. D.6.1 Usage scenario An LMS supports a learner by using and providing learning resources that are appropriate in the respective context of the learning situation and the individual requirements of the learner at a particular time. Such requirements may include accessibility preferences or needs in order to access the material. The LMS retrieves, provides, and aggregates required resources just in time and makes use of different sources that provide digital resources in different aggregation formats. Figure D.6 illustrates this scenario.

IMS CP Store

R A M L E T

MPEG–21 DID Store

OAI–ORE Store

Student Information System

Locator (eg URI, URN, URL)

T R A N S F O R M

Locator (eg URI, URN, URL)

Internalization Process of LMS/ RTS

LMS/RTS

Figure D.6—Use case 6 usage scenario example D.6.2 Use case summary: retrieve–interpret–internalize–deploy This use case avoids building a complete resource aggregation prior to deployment. The conceptual model supports the transformation and interpretation of retrieved resource aggregations in diverse aggregation formats into a single format. The delivery system is able to produce an internal representation of the resource aggregation and render the resources. 77

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

D.7 Use case 7 Use of the conceptual model by system designers to inform an implementation of their internal aggregation formats. Resource aggregations would then be more easily convertible into other aggregation formats. D.7.1 Usage scenario A resource repository system designer is creating an internal aggregation format for a resource publisher. The publisher’s customers have repositories that use different, repository-specific formats. The publisher’s repository will provide a single resource aggregation in different formats depending on the customers’ needs. Digital resources will be included in the resource aggregation by reference only. Some resources will be held in the publisher’s resource repository while others will be held and made accessible elsewhere on the Internet. By providing a resource aggregation that references resources, the publisher can ensure that the most current versions of the resources managed by the publisher are made available to the customer, include resources managed by third parties in the resource aggregation, and include open-access resources in the resource aggregation. The designer uses the conceptual model to inform the design of the internal storage format to facilitate the conversion of resource aggregations from the publisher’s internal format to other aggregation formats at the time of provision to the customer. Figure D.7 illustrates this scenario.

R A M L E T Publisher's Store Resource Aggregation Model based on RAMLET

T R A N S F O R M

IMS CP Resource Aggregation

Locators (e.g., URIs, URLs, URNs)

MPEG–21 DID Resource Aggregation

METS Resource Aggregation

ATOM Feed

Figure D.7—Use case 7 usage scenario example

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

D.7.2 Use case summary: produce–store–provide–retrieve This use case addresses the design of systems producing resource aggregations that will be provided to diverse repositories each of which may be limited to an aggregation format differing from the providing repository. Resource aggregations are produced and stored in a repository-specific format, but provided in the aggregation formats required by different consumers. Resources are retrieved from their home repository as required.

D.8 Use case 8 Extension of the useful scope of a resource aggregation by providing alternatives that adapt to different contexts, such as accessibility requirements or the limitations of individual delivery systems. NOTE 1—In all cases, some means of identifying and selecting the most appropriate alternative resource must be provided. This is beyond the scope of this standard. NOTE 2—Although the following usage scenario focuses on the provision of alternative resources to support the disabled, the ability to provide alternatives to a particular resource has wide application, including the provision of the following: ⎯

Digital resources in a form suitable to a particular delivery device [e.g., an alternative version suitable for a mobile user accessing resources using a personal digital assistant (PDA)];

⎯

Digital resources in a form suitable to a particular environment, such as an audio equivalent for visual information that can be listened to while driving;

⎯

Digital resources that are “badged” appropriately for users’ contexts (e.g., resources with Army or Navy badges);

⎯

Digital resources that match the access requirements of people with specific limitations or disabilities (e.g., alternative resources for the elderly); and

⎯

The same digital resource in multiple languages.

D.8.1 Usage scenario A specialized support teacher for the disabled in a university is working to support specific learners and tutors by improving the accessibility of resources originally created by tutors without specialized accessibility knowledge. The teacher is using a combination of software tools that report on accessibility properties of resources. The teacher then uses human judgment to supply equivalent alternatives for those resources whose access properties have not been described in the resource aggregations. The alternatives are being provided for the dual purposes of making the resources accessible to learners in the local context in which they will be used and of making the resources more generally accessible to meet as wide a variety of contexts as possible. The resulting outputs can contain multiple alternatives for some resource parts, each suiting different contexts, for example, to suit blind users and dyslexic users. The teacher creates some alternatives and also searches for and gathers available alternatives from repositories on the Internet. He or she then creates a new resource aggregation that contains the original resources authored by the tutors, the alternatives the teacher has authored, and the alternatives obtained from repositories. The teacher is careful to use the mechanisms the output aggregation format supports to record information that will enable the alternatives he or she has authored to be reused in other organizations and contexts and to preserve that same information for the resources the teacher has imported. Figure D.8 illustrates this scenario.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

IMS CP Resource Aggregation

MPEG–21 DID Resource Aggregation

METS Resource Aggregation

R A M L E T T R A N S F O R M

Manual Accessibility Authoring Process * Dissaggregate * Evaluate and Author * Reaggregate

R A M L E T T R A N S F O R M

IMS CP Resource Aggregation

MPEG–21 DID Resource Aggregation

METS Resource Aggregation

OAI–ORE Resource Aggregation

Figure D.8—Use case 8 usage scenario example D.8.2 Use case summary: retrieve–interpret–disaggregate–evaluate–author–aggregate This use case addresses retrieving resource aggregations from diverse resource repositories that provide resource aggregations in different aggregation formats. The retrieved resource aggregations are interpreted and converted into a single format that can be used by an authoring system. Some of the digital resources are disaggregated. After evaluation of the original resources, other digital resources are authored. Resource aggregations and individual digital resources are then aggregated into a new resource aggregation. NOTE—The use of a separate accessibility conceptual model is required to record the judgment of support teachers about the accessibility properties of the resources. The use of such an accessibility conceptual model in resource aggregations could partially or even fully automate the described use case.

D.9 Use case 9 Widgets in a mash-up personal-learning environment that use different specifications create, import, exchange, and make available to end users resource aggregations at run time. For example, a widget using its own internal format might import resource aggregations that use IMS CP and METS and transfer the imported resource aggregations to an MPEG-21–based rendering widget. D.9.1 Usage scenario John is working in the sales department of a company. He is preparing for a meeting with an important customer. During preparation, he realizes that he needs information about different products in which the customer might be interested. To close this knowledge gap, he logs into his personalized learning environment. His start page consists of a combination of several widgets, services, and portlets. These are, for example, widgets that include 80

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

functions, such as content search, content rendering, content recommendation, calendar, and chat. John can select, add, and arrange widgets that support his personal learning needs. One of the widgets on his personal start page gives John access to a course that is stored in the IMS-based company LMS. He also finds a widget that includes additional information related to the topic of the course from different resources. This information is being collected automatically from open content repositories, external wikis, and blogs. Using a learning-path widget, he can view all relevant resources in an integrated learning experience. The learning process is supported by multiple tools, such as specialized content players, course management tools, and alerting services. Resources can be viewed from different angles by separate but cooperating tools. Figure D.9 illustrates this scenario. Further Education LMS * Courses * IMS CP Resources * Forum

MPEG–21 DID Open Content Repository * Content resources * Podcast channels * ...

Wiki, blog system * Feed/alerts * Content * Forum

C w our i d se ge ts

Content widgets

s/ ed s Fe lert a

R A M L E T T R A N S F O R M

Wrapping and mediation

Personalized learning tools Mashup services

Lightweight federation

Wrapping and mediation

Figure D.9—Use case 9 usage scenario example D.9.1.1 Use case summary: retrieve–interpret–aggregate–convert–deploy This use case addresses retrieving resource aggregations and information from diverse sources that use different formats. The retrieved resource aggregations are interpreted and aggregated so that they can be deployed by a mash-up personalized learning environment. Some of the widgets of the environment convert resource aggregations into their underlying formats. At any point, resource aggregations can be transferred between widgets. The individual resource aggregations are converted when they are deployed by the target widget.

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex E (informative) Mapping of the XML Linking Language mapping ontology to the conceptual model for resource aggregation The W3C XML Linking Language (XLink) specification (W3C [B36]) is used by several resource aggregation formats to add hyperlink features to resource aggregations. Because XLink is already a shared vocabulary, there is no need to map it to a new, shared representation in the RAMLET conceptual model. However, at the time of this writing, there appeared to be no expression of the XLink data model in the Web Ontology Language (OWL) (W3C [B29]), which would limit the implementability of the conceptual model. Therefore, a mapping of XLink to the RAMLET conceptual model is provided in this annex.

E.1 XLink mapping ontology—classes This subclause provides declarations of all the classes in the in the XLink mapping ontology. The declarations use the following format: ⎯

Class name: The name of the class in the XLink mapping ontology.

⎯

Mapped from: A RAMLET-allocated identifier representing the name (including capitalization) of the component in the XLink aggregation format. This identifier is expressed as a URI, which may not resolve at the fragment level.

⎯

Mapped to: The core ontology class to which the XLink mapping ontology class maps.

⎯

Scope note: The URI for the W3C textual description of the class. The descriptions are from W3C Recommendation, XML Linking Language (XLink) [B36].

⎯

Data type: The data type of the XLink mapping ontology class as defined in Clause E.2.

⎯

Properties: The properties of the XLink mapping ontology class. Inherited properties are not included in the entry.

⎯

Asserted conditions: Any conditions that are asserted for the XLink mapping ontology class as a result of its properties.

E.1.1 xlink:actuate Class name:

xlink:actuate

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#actuate

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-behaviors

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Properties:

Data type: Asserted conditions:

xsd:token someValueFrom oneOf ⎯

none

⎯

onLoad

⎯

onRequest

⎯ other xsd:token Being a member of this class implies that an individual has some value of the property xsd:token that belongs to the enumerated data range ⎯

none

⎯

onLoad

⎯

onRequest

⎯

other

E.1.2 xlink:arcole Class name:

xlink:arcole

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#actuate

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-semantics

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

E.1.3 xlink:from Class name:

xlink:from

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#from

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#traversal-atts

Properties:

None

Data type:

xmln:NT-NCName

Asserted conditions:

None

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

E.1.4 xlink:href Class name:

xlink:href

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#href

Mapped to:

ramlet:locator

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-locators

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

E.1.5 xlink:label Class name:

xlink:label

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#label

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#traversal-atts

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

E.1.6 xlink:role Class name:

xlink:role

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#role

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-semantics

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

E.1.7 xlink:show Class name:

xlink:show

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#show

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-behaviors

Properties:

xsd:token someValueFrom oneOf

Data type: Asserted conditions:

⎯

embed

⎯

new

⎯

none

⎯

other

⎯ replace xsd:token Being a member of this class implies that an individual has some value of the property xsd:token that belongs to the enumerated data range ⎯

embed

⎯

new

⎯

none

⎯

other

⎯

replace

E.1.8 xlink:title Class name:

xlink:title

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#title

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-semantics

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

E.1.9 xlink:to Class name:

xlink:to

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#to

Mapped to:

ramlet:locatorDescriptor

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#traversal-atts

Properties:

None

Data type:

xmln:NT-NCNName

Asserted conditions:

None

E.1.10 xlink:type Class name:

xlink:type

Mapped from:

http://www.w3.org/TR/2001/REC-xlink-20010627/#type

Mapped to:

ramlet:locatorDescriptor

Scope note:

See: http://www.w3.org/TR/2001/REC-xlink-20010627/#link-types

Properties:

xsd:token someValueFrom oneOf

Data type: Asserted conditions:

⎯

arc

⎯

extended

⎯

locator

⎯

none

⎯

resource

⎯

simple

⎯ title xsd:token Being a member of this class implies that an individual has some value of the property xsd:token that belongs to the enumerated data range ⎯

arc

⎯

extended

⎯

locator

⎯

none

⎯

resource

⎯

simple

⎯

title

E.2 XLink mapping ontology—data types This clause provides declarations of all the data types in the XLink mapping. The declarations use the following format:

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

⎯

Name: The name of the data type.

⎯

Definition: The reference and URI for the W3C definition of the data type.

E.2.1 xsd:anyURI Name:

xsd:anyURI

Definition:

As defined by W3C Recommendation, XML Schema Part 2: Datatypes. See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#anyURI

E.2.2 xmln:NT–NCName Name:

xmln:NT-NCName

Definition:

As defined by W3C Recommendation, Namespaces in XML http://www.w3.org/TR/2009/REC-xml-names-20091208/#NT-NCName

[B28].

See:

E.2.3 xsd:string Name:

xsd:string

Definition:

As defined by W3C Recommendation, XML Schema Part 2: Datatypes. See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#string

E.2.4 xsd:token Name:

xsd:token

Definition:

As defined by W3C Recommendation, XML Schema Part 2: Datatypes. See: http://www.w3.org/TR/2004/REC-xmlschema-2-20041028/#token

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex F (informative) Graphical representations of RAMLET classes This annex provides graphical representations of the classes in the core ontology as defined in Clause 7 to aid in understanding the ontology. The graphical representations are sorted alphabetically by class name and appear in the same order as the descriptions in Clause 7. Figure F.1 provides a legend for interpreting the graphical representations. The graphical representations are shown in Figure F.2 through Figure F.108.

Figure F.1—Graphics legend

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.2—ramlet:administrativeDescriptorObject

Figure F.3—ramlet:admRef

Figure F.4—ramlet:aggregationID 89

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.5—ramlet:aggregationSchema

Figure F.6—ramlet:aggregationSchemaVersion

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.7—ramlet:aggregationType

Figure F.8—ramlet:alternateID

Figure F.9—ramlet:altResourceRef

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.10—ramlet:anchor

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.11—ramlet:anchorType

Figure F.12—ramlet:assertion

Figure F.13—ramlet:beginPoint

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.14—ramlet:cardinalityLabel

Figure F.15—ramlet:checksum

Figure F.16—ramlet:checksumType

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.17—ramlet:choice

Figure F.18—ramlet:componentTarget

Figure F.19—ramlet:condition

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.20—ramlet:coordinates

Figure F.21—ramlet:creationDate

Figure F.22—ramlet:defaultSelection

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.23—ramlet:descriptiveDescriptorObject

Figure F.24—ramlet:descriptiveRef

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.25—ramlet:descriptorObject 98

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.26—ramlet:descriptorTypeIndicator

Figure F.27—ramlet:digitalResource

Figure F.28—ramlet:digitalResourceFragment

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.29—ramlet:dynamicStructure

Figure F.30—ramlet:dynamicStructureID 100

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.31—ramlet:dynamicStructureType

Figure F.32—ramlet:elementID

Figure F.33—ramlet:encodingType

101

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.34—ramlet:endpoint

Figure F.35—ramlet:except

Figure F.36—ramlet:extent

102

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.37—ramlet:false

Figure F.38—ramlet:fileDescriptor

Figure F.39—ramlet:fileSize

103

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.40—ramlet:functionalResourceGroup

Figure F.41—ramlet:generatingTool

Figure F.42—ramlet:generatingToolVersion 104

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.43—ramlet:groupingID

Figure F.44—ramlet:hasOrder

Figure F.45—ramlet:hasRank

105

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.46—ramlet:humanLanguage

Figure F.47—ramlet:icon

Figure F.48—ramlet:identifierType

106

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.49—ramlet:intendedUse

Figure F.50—ramlet:interfaceDefLink

Figure F.51—ramlet:intraAggregationLink

107

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.52—ramlet:inventory

Figure F.53—ramlet:localRef

108

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.54—ramlet:locator

109

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.55—ramlet:locatorDescriptor

Figure F.56—ramlet:maxSelections

110

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.57—ramlet:mimeType

Figure F.58—ramlet:minSelections

Figure F.59—ramlet:modificationDate 111

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.60—ramlet:nodeID

Figure F.61—ramlet:nodeVisibility

Figure F.62—ramlet:note

112

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.63—ramlet:parallel

Figure F.64—ramlet:party

Figure F.65—ramlet:partyEmail

113

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.66—ramlet:partyName

Figure F.67—ramlet:partyRole

Figure F.68—ramlet:partyType

114

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.69—ramlet:partyURI

Figure F.70—ramlet:provenance

Figure F.71—ramlet:remoteDescriptorObject

115

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.72—ramlet:remoteNode

Figure F.73—ramlet:remoteResource

Figure F.74—ramlet:remoteTopNode

116

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.75—ramlet:require

Figure F.76—ramlet:resourceAggregation

Figure F.77—ramlet:resourceGroup

117

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.78—ramlet:resourceIntraAggregationLink

Figure F.79—ramlet:resourceProcessing

118

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.80—ramlet:resourceProcessingAlgorithm

Figure F.81—ramlet:resourceProcessingBehavior

Figure F.82—ramlet:resourceProcessingKey

119

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.83—ramlet:resourceProcessingSet

Figure F.84—ramlet:resourceProcessingType

Figure F.85—ramlet:resourceType

120

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.86—ramlet:resourceWrapper

Figure F.87—ramlet:resourceWrapperSet

Figure F.88—ramlet:rights

121

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.89—ramlet:selection

Figure F.90—ramlet:shapeIndicator

Figure F.91—ramlet:source 122

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.92—ramlet:staticStructure

Figure F.93—ramlet:staticStructureSet

Figure F.94—ramlet:staticStructureType 123

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.95—ramlet:status

Figure F.96—ramlet:stream

Figure F.97—ramlet:streamType

124

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.98—ramlet:structureNode

Figure F.99—ramlet:structureNodeType

Figure F.100—ramlet:structRef

125

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.101—ramlet:technicalDescriptorObject

Figure F.102—ramlet:textType

126

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.103—ramlet:title

Figure F.104—ramlet:topNode 127

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.105—ramlet:transformOrdering

Figure F.106—ramlet:true

Figure F.107—ramlet:virtualResourceGroup

128

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure F.108—ramlet:wholeAggregationDescriptorObject

129

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex G (informative) Graphical representations of RAMLET properties This annex provides graphical representations of the properties in the core ontology defined in Clause 8 to aid in understanding the ontology. Figure G.1 provides a legend for interpreting the graphical representation. The graphical representations are shown in Figure G.2, Figure G.3, and Figure G.4.

Figure G.1—Graphics legend

130

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure G.2—ramlet:describes and ramlet:isDescribedBy

Figure G.3—dcterms:isPartOf, ramlet:isIncludedBy, ramlet:includes, and dcterms:hasPart

131

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training

Figure G.4—dcterms:isPartOf, ramlet:isReferencedBy, ramlet:references, and dcterms:hasPart

132

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex H (normative) Internet availability and use of the Turtle representations of the conceptual model and XLink mapping Terse RDF Triple Language (Turtle) representations of the conceptual model and the XML Linking Language (XLink) mapping (Turtle ontology files) are available on the Web. The Uniform Resource Identifiers (URIs) that identify classes and properties in these representations are normative. The latest version of the Turtle ontology file of the conceptual model is available at the following URI: http://standards.ieee.org/downloads/1484/1484.13.1/ramletCoreTurtle The latest version of the Turtle ontology file of the XLink mapping is available at the following URI: http://standards.ieee.org/downloads/1484/1484.13.1/ramletXlinkMappingTurtle The Turtle representation of the conceptual model also contains URIs that resolve to the latest versions of the ontology files for this standard and each of the mapping recommended practices. If a specific version of a particular ontology file is required, the Turtle ontology file of the conceptual model should be associated with the URI of that specific version. A registry of ontology file versions and URIs is available at the following URI: https://mentor.ieee.org/ramlet/bp/RAMLET_URI_Registry The Turtle files are available for downloading and for direct inclusion in applications. These files reflect the content of this standard at the time of approval. These and other files the Turtle files reference may reflect approved or draft editions or be subject to amendment. As such, these files are subject to change. USE AT YOUR OWN RISK!

133

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.1-2012 IEEE Standard for Learning Technologyâ&#x20AC;&#x201D;Conceptual Model for Resource Aggregation for Learning, Education, and Training

Annex I (informative) Internet availability and use of the RDF/XML representations of the conceptual model and XLink mapping W3C RDF/XML representations of the OWL bindings of the conceptual model and the XLink mapping are available on the Web. These representations are informative. The latest version of the RAMLET conceptual model RDF/XML representation of the OWL binding (RAMLET core ontology file) is available at the following URI: http://standards.ieee.org/downloads/1484/1484.13.1/ramletCore The latest version of the XLink mapping ontology RDF/XML representation of the OWL binding (Xlink mapping ontology file) is available at the following URI: http://standards.ieee.org/downloads/1484/1484.13.1/ramletXlinkMapping The RAMLET core ontology file that accompanies this standard contains URIs that resolve to the latest versions of the ontology files for this standard and each of the mapping recommended practices. If a specific version of a particular ontology file is required, the RAMLET core ontology file should be associated with the URI of that specific version. A registry of ontology file versions and URIs is available at the following URI: https://mentor.ieee.org/ramlet/bp/RAMLET_URI_Registry The RDF/XML (OWL) files are available for downloading and for direct inclusion in applications. The core ontology file and XLink mapping ontology file reflect the content of this standard at the time of approval. These and other ontology files they reference may reflect approved or draft editions or be subject to amendment. As such, these ontology files are subject to change. USE AT YOUR OWN RISK!

134

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:35 UTC from IEEE Xplore. Restrictions apply.