1484 13 2 2013 ieee recommended practice for learning technology metadata encoding and transmission by Jinghua

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

IEEE Std 1484.13.2â&#x201E;˘-2013

IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation Sponsor

Learning Technology Standards Committee of the

IEEE Computer Society Approved 11 December 2013

IEEE-SA Standards Board

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

Copyright permissions: Definitions in scope notes are either reproduced directly from or adapted from the descriptions of the components in Metadata Encoding and Transmission Standard: Primer and Reference Manual, Revised © 2010 and METS Schema 1.7 Documentation reprinted with permission from the Digital Library Federation, Council on Library and Information Resources. Knoodl® is a registered trademark of Revelytix, Inc. This information is given for the convenience of users of this recommended practice 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. W3C® is a trademark (registered in numerous countries) of the World Wide Web Consortium; marks of W3C are registered and held by its host institutions MIT, ERCIM, Keio, and Beihang. XML®—Extensible Markup Language; Language by W3C—claimed as a trademark or generic term by MIT, ERCIM, and/or Keio on behalf of the W3C. Acknowledgments: The Resource Aggregation Models for Learning, Education, and Training (RAMLET) Working Group would like to thank the METS Editorial Board for its cooperation and support. 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. Abstract: This recommended practice specifies how the elements and attributes defined in the Metadata Encoding and Transmission Standard (METS) relate to the components of the conceptual model for resource aggregation defined in IEEE Std 1484.13.1™-2012. Keywords: aggregation format, conceptual model, content aggregation, digital aggregation, digital resource, IEEE 1484.13.2™, Metadata Encoding and Transmission Standard, RAMLET, resource aggregation, resource aggregation format

•

The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York, NY 10016-5997, USA Copyright © 2013 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 30 December 2013. 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. PDF: Print:

ISBN 978-0-7381-8848-5 ISBN 978-0-7381-8849-2

STD98494 STDPD98494

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:57 UTC from IEEE Xplore. Restrictions apply.

Important Notices and Disclaimers Concerning IEEE Standards Documents IEEE documents are made available for use subject to important notices and legal disclaimers. These notices and disclaimers, or a reference to this page, appear in all standards and may be found under the heading “Important Notice” or “Important Notices and Disclaimers Concerning IEEE Standards Documents.”

Notice and Disclaimer of Liability Concerning the Use of IEEE Standards Documents IEEE Standards documents (standards, recommended practices, and guides), both full-use and trial-use, are developed within IEEE Societies and the Standards Coordinating Committees of the IEEE Standards Association (“IEEE-SA”) Standards Board. IEEE (“the Institute”) develops its standards through a consensus development process, approved by the American National Standards Institute (“ANSI”), which brings together volunteers representing varied viewpoints and interests to achieve the final product. Volunteers are not necessarily members of the Institute and participate without compensation from IEEE. 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. IEEE does not warrant or represent the accuracy or content of the material contained in its standards, and expressly disclaims all warranties (express, implied and statutory) not included in this or any other document relating to the standard, including, but not limited to, the warranties of: merchantability; fitness for a particular purpose; non-infringement; and quality, accuracy, effectiveness, currency, or completeness of material. In addition, IEEE disclaims any and all conditions relating to: results; and workmanlike effort. IEEE standards documents are supplied “AS IS” and “WITH ALL FAULTS.” Use of an IEEE standard is wholly voluntary. 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. 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. IN NO EVENT SHALL IEEE BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO: PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE PUBLICATION, USE OF, OR RELIANCE UPON ANY STANDARD, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE AND REGARDLESS OF WHETHER SUCH DAMAGE WAS FORESEEABLE.

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.

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

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 or inferred to be the official position of IEEE or any of its committees and shall not be considered to be, or 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 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. For the same reason, IEEE does not respond to interpretation requests. Any person who would like to participate in revisions to an IEEE standard is welcome to join the relevant IEEE working group. Comments on standards should be submitted to the following address: Secretary, IEEE-SA Standards Board 445 Hoes Lane Piscataway, NJ 08854 USA

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 IEEE draft and approved standards are copyrighted by IEEE under U.S. and international copyright laws. They are made available by IEEE and are adopted for a wide variety of both public and private uses. These include both use, by reference, in laws and regulations, and use in private self-regulation, standardization, and the promotion of engineering practices and methods. By making these documents available for use and adoption by public authorities and private users, IEEE does not waive any rights in copyright to the documents.

Photocopies Subject to payment of the appropriate fee, IEEE will grant users a limited, non-exclusive license to photocopy portions of any individual standard for company or organizational internal use or individual, non-commercial use only. To arrange for payment of licensing fees, 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:57 UTC from IEEE Xplore. Restrictions apply.

Updating of IEEE Standards 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. 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 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://ieeexplore.ieee.org/xpl/standards.jsp or contact IEEE at the address listed previously. For more information about the IEEE SA or IEEEâ&#x20AC;&#x2122;s standards development process, visit the IEEE-SA Website at http://standards.ieee.org.

Errata Errata, if any, for all IEEE standards can be accessed on the IEEE-SA Website 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. 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:57 UTC from IEEE Xplore. Restrictions apply.

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

Katrien Verbert

The following members of the individual balloting committee voted on this recommended practice. Balloters may have voted for approval, disapproval, or abstention. Kerry Blinco Juan Carreon Geoffrey Darnton David Fuschi Randall Groves Nancy Hoebelheinrich

Werner Hoelzl Noriyuki Ikeuchi Mark Jaeger Willem Kraan David Massart

Daniel Rehak Steven Smith Thomas Starai Gerald Stueve Marcy Stutzman Daidi Zhong

When the IEEE-SA Standards Board approved this recommended practice on 11 December 2013, it had the following membership: John Kulick, Chair David J. Law, Vice Chair Richard H. Hulett, Past Chair Konstantinos Karachalios, Secretary Masayuki Ariyoshi Peter Balma Farooq Bari Ted Burse Wael William Diab Stephen Dukes Jean-Philippe Faure Alexander Gelman

Mark Halpin Gary Hoffman Paul HouzĂŠ Jim Hughes Michael Janezic Joseph L. Koepfinger* Oleg Logvinov

Ron Petersen Gary Robinson Jon Walter Rosdahl Adrian Stephens Peter Sutherland 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 Don Messina IEEE Standards Program Manager, Document Development Michael 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:57 UTC from IEEE Xplore. Restrictions apply.

Introduction This introduction is not part of IEEE Std 1484.13.2-2013, IEEE Recommended Practice for Learning Technology— Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation.

This recommended practice specifies how the elements and attributes defined in the Metadata Encoding and Transmission Standard (METS) relate to the components of the conceptual model for resource aggregation defined in IEEE Std 1484.13.1™–2012.

vii

Authorized licensed use limited to: Khwaja Fareed University of Eng & IT. Downloaded on July 09,2020 at 07:05:57 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 Definitions ................................................................................................................................................. 2 3.1 Acronyms and abbreviations ............................................................................................................... 4 4. Special terms .............................................................................................................................................. 5 5. Class and property prefix definitions .......................................................................................................... 5 6. Conformance .............................................................................................................................................. 5 6.1 Conforming aggregation instances ...................................................................................................... 6 6.2 Conforming bindings ........................................................................................................................... 6 6.3 Conforming extensions of the METS mapping ontology .................................................................... 6 6.4 Conforming transforming implementations ......................................................................................... 6 7. METS mapping ontologyâ&#x20AC;&#x201D;classes ............................................................................................................ 7 7.1 mets:admID ......................................................................................................................................... 7 7.2 mets:agent ............................................................................................................................................ 8 7.3 mets:agentType .................................................................................................................................... 8 7.4 mets:altRecordID ................................................................................................................................. 9 7.5 mets:altRecordIDType ......................................................................................................................... 9 7.6 mets:amdSec ........................................................................................................................................ 9 7.7 mets:area .............................................................................................................................................10 7.8 mets:begin...........................................................................................................................................11 7.9 mets:behavior......................................................................................................................................11 7.10 mets:behaviorSec ..............................................................................................................................12 7.11 mets:beType......................................................................................................................................13 7.12 mets:binData .....................................................................................................................................14 7.13 mets:bType .......................................................................................................................................14 7.14 mets:checksum..................................................................................................................................15 7.15 mets:checksumType .........................................................................................................................15 7.16 mets:contentIDs ................................................................................................................................16 7.17 mets:coords .......................................................................................................................................16 7.18 mets:created ......................................................................................................................................16 7.19 mets:createDate ................................................................................................................................17 7.20 mets:digiProvMd ..............................................................................................................................17 7.21 mets:dmdID ......................................................................................................................................18 7.22 mets:dmdSec .....................................................................................................................................18 7.23 mets:div ............................................................................................................................................19 7.24 mets:divType ....................................................................................................................................20 7.25 mets:end ............................................................................................................................................20 7.26 mets:extent ........................................................................................................................................20 7.27 mets:extType ....................................................................................................................................21 7.28 mets:fContent....................................................................................................................................21 7.29 mets:file ............................................................................................................................................22 7.30 mets:fileGrp ......................................................................................................................................23 viii

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

7.31 mets:fileID ........................................................................................................................................24 7.32 mets:fileSec ......................................................................................................................................24 7.33 mets:file_seq .....................................................................................................................................24 7.34 mets:fLocat .......................................................................................................................................25 7.35 mets:fPtr ...........................................................................................................................................25 7.36 mets:groupID ....................................................................................................................................26 7.37 mets:ID .............................................................................................................................................26 7.38 mets:interfaceDef..............................................................................................................................27 7.39 mets:label ..........................................................................................................................................28 7.40 mets:lastModDate .............................................................................................................................28 7.41 mets:locType ....................................................................................................................................28 7.42 mets:mdRef.......................................................................................................................................29 7.43 mets:mdType ....................................................................................................................................30 7.44 mets:mdWrap....................................................................................................................................31 7.45 mets:mechanism ...............................................................................................................................32 7.46 mets:mets ..........................................................................................................................................33 7.47 mets:metsHdr ....................................................................................................................................33 7.48 mets:metsType ..................................................................................................................................34 7.49 mets:mimeType ................................................................................................................................34 7.50 mets:mPtr ..........................................................................................................................................35 7.51 mets:name .........................................................................................................................................36 7.52 mets:note...........................................................................................................................................36 7.53 mets:objID ........................................................................................................................................36 7.54 mets:order .........................................................................................................................................37 7.55 mets:orderLabel ................................................................................................................................37 7.56 mets:otherLocType ...........................................................................................................................37 7.57 mets:otherMdType............................................................................................................................38 7.58 mets:otherRole ..................................................................................................................................38 7.59 mets:otherType .................................................................................................................................38 7.60 mets:ownerID ...................................................................................................................................39 7.61 mets:par ............................................................................................................................................39 7.62 mets:profile .......................................................................................................................................40 7.63 mets:recordStatus..............................................................................................................................40 7.64 mets:rightsMd ...................................................................................................................................40 7.65 mets:role ...........................................................................................................................................41 7.66 mets:seq ............................................................................................................................................42 7.67 mets:shape ........................................................................................................................................42 7.68 mets:size ...........................................................................................................................................43 7.69 mets:smLink .....................................................................................................................................43 7.70 mets:sourceMd..................................................................................................................................44 7.71 mets:status ........................................................................................................................................45 7.72 mets:stream .......................................................................................................................................45 7.73 mets:streamType ...............................................................................................................................45 7.74 mets:structID ....................................................................................................................................46 7.75 mets:structLink .................................................................................................................................46 7.76 mets:structMap .................................................................................................................................47 7.77 mets:structMapType .........................................................................................................................47 7.78 mets:techMd .....................................................................................................................................48 7.79 mets:transformAlgorithm .................................................................................................................48 7.80 mets:transformBehavior ...................................................................................................................49 7.81 mets:transformFile ............................................................................................................................49 7.82 mets:transformKey ...........................................................................................................................50 7.83 mets:transformOrder .........................................................................................................................50 7.84 mets:transformType ..........................................................................................................................51 7.85 mets:use ............................................................................................................................................51 7.86 mets:versDate ...................................................................................................................................51 ix

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

7.87 mets:xmlData ....................................................................................................................................52 7.88 mets:xptr ...........................................................................................................................................52 8. METS mapping ontology—object properties ............................................................................................52 8.1 ramlet:includes....................................................................................................................................53 8.2 ramlet:references ................................................................................................................................53 8.3 xlink:actuate........................................................................................................................................53 8.4 xlink:arcRole ......................................................................................................................................53 8.5 xlink:from ...........................................................................................................................................53 8.6 xlink:href ............................................................................................................................................53 8.7 xlink:show ..........................................................................................................................................54 8.8 xlink:title.............................................................................................................................................54 8.9 xlink:to ................................................................................................................................................54 8.10 xlink:type ..........................................................................................................................................54 9. METS mapping ontology—data types ......................................................................................................54 9.1 xsd:anyURI .........................................................................................................................................55 9.2 xsd:base64Binary................................................................................................................................55 9.3 xsd:dateTime ......................................................................................................................................55 9.4 xsd:ID .................................................................................................................................................55 9.5 xsd:idRef.............................................................................................................................................55 9.6 xsd:idRefs ...........................................................................................................................................55 9.7 xsd:integer ..........................................................................................................................................55 9.8 xsd:long ..............................................................................................................................................56 9.9 xsd:positiveInteger..............................................................................................................................56 9.10 xsd:string ..........................................................................................................................................56 9.11 xsd:token...........................................................................................................................................56 Annex A (informative) Bibliography ............................................................................................................57 Annex B (informative) Conceptual overview................................................................................................58 Annex C (informative) The binding of the core and METS mapping ontologies .........................................59 Annex D (normative) Internet availability and use of the Turtle representation of the conceptual model and METS mapping .............................................................................................................................................60 Annex E (informative) Internet availability and use of the RDF/XML representations of the conceptual model and METS mapping ............................................................................................................................61

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

IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation IMPORTANT NOTICE: IEEE Standards documents are not intended to ensure safety, security, 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 Recommended Practice specifies how the elements and attributes defined in the Metadata Encoding and Transmission Standard (METS) relate to the components of the conceptual model for resource aggregation defined in IEEE Std 1484.13.1™–2012. 1

1.2 Purpose The mapping specified in this recommended practice may be used with the mappings of other resource aggregation formats to achieve interoperability among the formats via the conceptual model defined in IEEE 1484.13.1–2012.

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

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. Digital Library Federation, Metadata Encoding and Transmission Standard: Primer and Reference Manual, Version 1.6, Revised, 2010. 2 Digital Library Federation, METS Schema 1.7 Documentation. 3 IEEE Std 1484.13.1™-2012, Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training. 4 W3C Recommendation (28 October 2004), XML Schema Part 2: Datatypes, Second Edition. 5 W3C Recommendation, XML Linking Language (XLink) Version 1.0. 6 W3C Team Submission (28 March 2011), Turtle—Terse RDF Triple Language. 7

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. 8 Most definitions are taken from IEEE Std 1484.13.1-2012. aggregation definition document: A document that lists and structures the digital resources of an aggregation. 9 See also: digital resource; resource aggregation. 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. 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. 10

Metadata Encoding and Transmission Standard: Primer and Reference Manual, Revised is available at http://www.loc.gov/standards/mets/METSPrimerRevised.pdf. 3 METS Schema 1.7 Documentation is available at http://www.loc.gov/standards/mets/docs/mets.v1-7.html. 4 IEEE publications are available from The Institute of Electrical and Electronics Engineers (http://standards.ieee.org/). 5 W3C publications are available from the World Wide Web Consortium, 32 Vassar Street, Room 32-G515, Cambridge, MA 02139, USA (http://www.w3.org/). See: http://www.w3.org/TR/xmlschema-2/. 6 See: http://www.w3.org/TR/2001/REC-xlink-20010627/. 7 Turtle—Terse RDF Triple Language is available at http://www.w3.org/TeamSubmission/turtle/. 8 IEEE Standards Dictionary Online subscription is available at: http://www.ieee.org/portal/innovate/products/standard/standards_dictionary.html. 9 Examples include the manifest document in IMS Content Packaging (IMS CP [B3]), the mets documents in the Metadata Encoding and Transmission Standard (METS), the Digital Item Declaration Language (DIDL) document in MPEG-21 Digital Item Declaration (DID) (ISO/IEC 21000-2:2005 [B6]). 10 See Web Ontology Language (OWL) [B7].

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

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; scope note. 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 object: A synonym for digital resource. See: digital resource. 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] 11 and MPEG–1 Audio Layer 3 [MP3]. 12

identifier: Associates a name with a thing. Context defines how the name is interpreted. Within a given context, a name is unique. 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. 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. 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

11 12

See ISO/IEC 10918–1 [B4]. See ISO/IEC 13818–3 [B5].

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

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; 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; property. representation: A method or syntax for serializing data. For example, it can refer to the different serializations of a Web Ontology Language (OWL) 13 ontology according to the Terse RDF Triple Language (Turtle) or Resource Description Framework/Extensible Markup Language (RDF/XML) 14 syntaxes. 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. 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: intention; property instance; superproperty. 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 Atom

Atom Syndication Format

IETF

Internet Engineering Task Force

METS

Metadata Encoding and Transmission Standard

MIME

Multipurpose Internet Mail Extensions

13 14

See OWL 2 Ontology Language Document Overview [B7]. See RDF/XML Syntax Specification [B8].

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

MPEG

Moving Pictures Experts Group

OWL

Web Ontology Language

RAMLET

Resource Aggregation Models for Learning, Education, and Training

RDF

Resource Description Framework

RFC

Request for Comments

Turtle

Terse RDF Triple Language

URI

Uniform Resource Identifier

W3C

World Wide Web Consortium 15

XML

Extensible Markup Language 16

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

5. Class and property prefix definitions The class and property names in this recommended practice included prefixes that reference the documents in which the classes and properties are fully described. The prefixes used and the documents they reference are 

mets: This recommended practice.



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



xlink: IEEE Std 1484.13.1-2012, Standard for Learning Technology—Conceptual Model for Resource Aggregation for Learning, Education, and Training, Annex E. (See W3C Recommendation (27 June 2001), XML Linking Language (XLink) Version 1.0.)



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

Datatypes,

Second

Edition,

6. Conformance Conformance to this recommended practice is discussed in 6.1, 6.2, 6.3, and 6.4.

15 W3C® is a trademark (registered in numerous countries) of the World Wide Web Consortium; marks of W3C are registered and held by its host institutions MIT, ERCIM, Keio, and Beihang. 16 XML®—Extensible Markup Language; Language by W3C—claimed as a trademark or generic term by MIT, ERCIM, and/or Keio on behalf of the W3C.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

In this recommended practice, “shall” is to be interpreted as a requirement; “shall not” is to be interpreted as a prohibition, and “should” as a recommendation.

6.1 Conforming aggregation instances A conforming aggregation instance shall be an instance of an aggregation format that should be modeled or described in terms of the METS mapping ontology, either as a core ontology representation (mapped from a METS instance to a core ontology representation) or as a METS instance (mapped from a core ontology representation to a METS instance) following the intentions of the METS mapping ontology as expressed in Clauses 7, 8, and 9 of this recommended practice.

6.2 Conforming bindings Conforming bindings of the METS mapping ontology 

Should conform to the requirements of Clauses 7, 8, and 9 of this recommended practice.



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 C of this recommended practice.

If the binding technology language supports Uniform Resource Identifiers (URIs) and the binding contains extensions to the METS mapping ontology (see 6.3), then identifiers for the extensions shall be defined in a new namespace.

6.3 Conforming extensions of the METS mapping ontology The METS mapping ontology may be extended for a conformant METS aggregation format extension that relates to interpreting externalized representations of digital aggregations by adding a new class or property and defining a new identifier in a new mapping ontology. The new identifier shall not be used to identify a concept that already exists in the METS mapping 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 METS mapping ontology. Other concepts may be represented by other vocabularies or ontologies and combined with the METS mapping ontology using standard Semantic Web practices.

6.4 Conforming transforming implementations A conforming transforming implementation should implement a transformation from the METS aggregation format to the core ontology and its identifiers, or from the core ontology and its identifiers to the METS aggregation format by following the intention of the METS mapping ontology as defined in classes in Clauses 7, 8, and 9 of this recommended practice.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7. METS mapping ontology—classes This clause provides declarations of all the classes in the METS mapping ontology. The declarations use the following format: 

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



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



Mapped to: The core ontology class to which the METS mapping ontology class maps. (See IEEE Std 1484.13.1-2012.)



Scope note: A textual description of the class. Scope notes are either reproduced directly from or adapted from the descriptions of the METS elements and attributes in Metadata Encoding and Transmission Standard: Primer and Reference Manual, Version 1.6, Revised, 2010 and METS Schema 1.7 Documentation. For additional clarification of any of the terms in the scope notes please consult these documents.



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



Properties: The properties of the METS mapping ontology class as defined in Clause 8. Inherited properties are not included in the entry.



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

NOTE—Where a METS attribute has a different meaning (as described in the scope note) depending on the context provided by the element to which it is attached, a separate ontology class has been described. The notation used in the mapped-from identifier is #element_name@attribute_name.

7.1 mets:admID Class name:

mets:admID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#ADMID

Mapped to:

ramlet:admRef

Scope note:

mets ADMID attribute contains the ID attribute values of the <digiprovMD>, <techMD>, <sourceMD> and/or <rightsMD> elements within the <amdSec> of the METS document that contains administrative metadata pertaining to the current element.

Properties:

None

Data type:

xsd:idRefs

Asserted conditions:

None

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.2 mets:agent Class name:

mets:agent

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#agent

Mapped to:

ramlet:party

Scope note:

Allows for various parties and their roles with respect to the METS document to be recorded.

Properties:

ramlet:includes someValueFrom mets:role ramlet:includes allValuesFrom mets:agentType, mets:ID, mets:name, mets:note, mets:otherRole, mets:otherType, mets:role

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that is a member of mets:role. Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:agentType



or are members of mets:ID



or are members of mets:name



or are members of mets:note



or are members of mets:otherRole



or are members of mets:otherType



or are members of mets:role

7.3 mets:agentType Class name:

mets:agentType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#agent@TYPE

Mapped to:

ramlet:partyType

Scope note:

An optional attribute to specify the nature of the agent acting with respect to the METS object. It can take one of three values: INDIVIDUAL: a single, human agent ORGANIZATION: a collective entity OTHER: some other form of agent (e.g., a software agent).

Properties:

xsd:token someValueFrom oneOf dataRange INDIVIDUAL, ORGANIZATION, OTHER

Data type:

xsd:token

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Asserted conditions:

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: 

INDIVIDUAL



ORGANIZATION



OTHER

7.4 mets:altRecordID Class name:

mets:altRecordID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#altRecordID

Mapped to:

ramlet:alternateID

Scope note:

Allows for documentation of alternative ID values for the METS document in addition to the primary ID stored in the OBJID attribute in the root METS element.

Properties:

ramlet:includes allValuesFrom mets:ID, mets:altRecordIDType

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:ID



or are members of mets:altRecordIDType

7.5 mets:altRecordIDType Class name:

mets:altRecordIDType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#altRecordID@TYPE

Mapped to:

ramlet:identifierType

Scope note:

An optional string describing the type of identifier (e.g., OCLC #, LCCN, etc.).

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.6 mets:amdSec Class name:

mets:amdSec

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#amdSec

Mapped to:

ramlet:administrativeDescriptorObject

Scope note:

This section records all of the administrative metadata for all items in the METS object (including structural map divs, data files, descriptive metadata sections and administrative metadata sections themselves), and is divided into four subsections: techMD (technical metadata), rightsMD (intellectual property rights metadata), sourceMD (analog/digital source metadata), and digiprovMD (digital provenance metadata). Each of these subsections follows the mdSecType model, so that they can either include metadata within the METS hub document (mdWrap) or reference it via an identifier/locator (mdRef). Multiple techMD, rightsMD, sourceMD and digiprovMD elements are allowed so that administrative metadata can be recorded for each separate item within the METS object.

Properties:

ramlet:includes allValuesFrom mets:sourceMd, mets:techMd

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either:

mets:digiProvMd,



are members of mets:digiProvMd



or are members of mets:ID



or are members of mets:rightsMd



or are members of mets:sourceMd



or are members of mets:techMd

mets:ID,

mets:rightsMD,

7.7 mets:area Class name:

mets:area

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#area

Mapped to:

ramlet:anchor

Scope note:

File Area. The area element provides for more sophisticated linking between a div element and content files representing that div, be they text, image, audio, or video files. An area element can link a div to a point within a file, to a one-dimension segment of a file (e.g., text screen, image line, audio/video clip), or a twodimensional section of a file (e.g., subsection of an image, or a subsection of the video display of a video file. See the areaType documentation for more details.

Properties:

ramlet:includes someValueFrom mets:fileID ramlet:includes allValuesFrom mets:admID, mets:begin, mets:beType, mets:contentIDs, mets:coords, mets:end, mets:extent, mets:extType, mets:fileID, mets:ID, mets:shape

Data type:

None

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that is a member of mets:fileID. Being a member of this class implies that an individual has only values of the property ramlet:includes that are members of: 

mets:admID



mets:begin



mets:beType



mets:contentIDs



mets:coords



mets:end



mets:extent



mets:extType



mets:fileID



mets:ID



mets:shape

7.8 mets:begin Class name:

mets:begin

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#BEGIN

Mapped to:

ramlet:beginPoint

Scope note:

An optional string attribute specifying the beginning location for a subpart of the referenced file. Used with the END attribute.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.9 mets:behavior Class name:

mets:behavior

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#behavior

Mapped to:

ramlet:resourceProcessing

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Scope note:

Properties:

A behavior can be used to associate executable behaviors with content in the METS object. A behavior element has an interface definition element that represents an abstract definition of the set of behaviors represented by a particular behavior. A behavior element also has a behavior mechanism that points to a module of executable code that implements and runs the behavior defined abstractly by the interface definition. ramlet:includes someValueFrom mets:ID, someValueFrom mets:structID ramlet:includes allValuesFrom mets:admID, mets:bType, mets:created, mets:groupID, mets:ID, mets:interfaceDef, mets:label, mets:mechanism, mets:structID

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either: 

is a member of mets:ID



or is a member of mets:structID

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:admID



or are members of mets:bType



or are members of mets:created



or are members of mets:groupID



or are members of mets:ID



or are members of mets:interfaceDef



or are members of mets:label



or are members of mets:mechanism



or are members of mets:structID

7.10 mets:behaviorSec Class name:

mets:behaviorSec

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#behaviorSec

Mapped to:

ramlet:resourceProcessingSet

Scope note:

Behavior Section. This section records executable behaviors that are associated with content in the METS object.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Properties:

ramlet:includes allValuesFrom mets:behavior, mets:behaviorSec, mets:created, mets:ID, mets:label

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:behavior



or are members of mets:behaviorSec



or are members of mets:created



or are members of mets:ID



or are members of mets:label

7.11 mets:beType Class name:

mets:beType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#BETYPE

Mapped to:

ramlet:anchorType

Scope note:

Begin/End Type. An optional attribute specifying the syntax used in the values recorded in the BEGIN and END attributes. It must have one of the following values: BYTE: a byte offset IDREF: an XML ID value for an element in the content file SMIL: a SMIL time value MIDI: a MIDI time code SMPTE-25: SMPTE time code for 25 frame/second material SMPTE-24: SMPTE time code for 24 frame/second material SMPTE-DF30: SMPTE time code for 30 frame/second drop frame material SMPTE-NDF30: SMPTE time code for 30 frame/second nondrop frame material SMPTE-DF29.97: SMPTE time code for 29.97 frame/second drop frame material SMPTE-NDF29.97: SMPTE time code for 29.97 frame/second non-drop frame material TIME: a simple time code of the form HH:MM:SS TCF: a Time code Character Format value.

Properties:

xsd:token someValueFrom oneOf dataRange BYTE, IDREF, MIDI, SMIL, SMPTE-24, SMPTE-25, SMPTE-DF29.97, SMPTE-DF30, SMPTE-NDF29.97, SMPTE-NDF30, TCF, TIME

Data type:

xsd:token

Asserted conditions:

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: 

BYTE



IDREF



MIDI



SMIL



SMPTE-24

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



SMPTE-25



SMPTE-DF29.97



SMPTE-DF30



SMPTE-NDF29.97



SMPTE-NDF30



TCF



TIME

7.12 mets:binData Class name:

mets:binData

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#binData

Mapped to:

ramlet:resourceWrapper

Scope note:

A wrapper element to contain Base64 encoded metadata.

Properties:

None

Data type:

xsd:base64Binary

Asserted conditions:

None

7.13 mets:bType Class name:

mets:bType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#BTYPE

Mapped to:

ramlet:dynamicStructureType

Scope note:

Behavior Type. An optional string attribute providing an identifier for a given set of related behaviors.

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.14 mets:checksum Class name:

mets:checksum

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#CHECKSUM

Mapped to:

ramlet:checksum

Scope note:

An optional string attribute providing a checksum value for the included file.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.15 mets:checksumType Class name:

mets:checksumType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#CHECKSUMTYPE

Mapped to:

ramlet:checksumType

Scope note:

An optional attribute specifying the checksum algorithm used to produce the value contained in the CHECKSUM attribute. CHECKSUMTYPE must contain one of the following values: HAVAL MD5 SHA-1 SHA-256 SHA-384 SHA-512 TIGER WHIRLPOOL.

Properties:

xsd:token someValueFrom oneOf dataRange HAVAL, MD5, SHA-1, SHA-256, SHA-384, SHA-512, TIGER, WHIRLPOOL

Data type:

xsd:token

Asserted conditions:

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: 

HAVAL



MD5



SHA-1



SHA-256



SHA-384



SHA-512



TIGER



WHIRLPOOL

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.16 mets:contentIDs Class name:

mets:contentIDs

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#CONTENTIDS

Mapped to:

ramlet:nodeID

Scope note:

Content IDs for this division (equivalent to DIDL DII).

Properties:

None

Data type:

xsd:anyURI

Asserted conditions:

None

7.17 mets:coords Class name:

mets:coords

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#COORDS

Mapped to:

ramlet:coordinates

Scope note:

An optional string attribute listing a set of visual coordinates within an image (still image or video frame). The COORDS attribute should be used as in HTML 4.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.18 mets:created Class name:

mets:created

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#CREATED

Mapped to:

ramlet:creationDate

Scope note:

An optional dateTime providing the date of creation for the associated description or file.

Properties:

None

Data type:

xsd:dateTime

Asserted conditions:

None

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.19 mets:createDate Class name:

mets:createDate

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#CREATEDATE

Mapped to:

ramlet:creationDate

Scope note:

An optional dateTime specifying when the METS document was created.

Properties:

None

Data type:

xsd:dateTime

Asserted conditions:

None

7.20 mets:digiProvMd Class name:

mets:digiProvMd

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#digiprovMD

Mapped to:

ramlet:provenance

Scope note:

Digital Provenance Metadata. The digiprovMD element provides a wrapper around a generic metadata section, which should contain information regarding the ultimate origin of a digital object and the derivation of its current elements. This includes recording master/derivative relationships between various files which currently represent the object, as well recording any transformations or migrations undergone by files composing the digital object subsequent to the initial digitization of an item or, in the case of born digital materials, the files’ creation. In short, digiprovMD should be used to record information to allow both archival/library staff and scholars to understand what modifications have been performed to a digital object during its life cycle in order to judge how those processes might have altered or corrupted the object’s ability to accurately represent the original item.

Properties:

ramlet:includes someValueFrom mets:ID ramlet:includes allValuesFrom mets:admID, mets:created, mets:groupID, mets:ID, mets:mdRef, mets:mdWrap, mets:status

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that is a member of mets:ID. Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:admID



or are members of mets:created

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



or are members of mets:groupID



or are members of mets:ID



or are members of mets:mdRef



or are members of mets:mdWrap



or are members of mets:status

7.21 mets:dmdID Class name:

mets:dmdID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#DMDID

Mapped to:

ramlet:descriptiveRef

Scope note:

An optional attribute providing the XML ID values for the descriptive metadata sections within this METS document applicable to this div.

Properties:

None

Data type:

xsd:idRefs

Asserted conditions:

None

7.22 mets:dmdSec Class name:

mets:dmdSec

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#dmdSec

Mapped to:

ramlet:descriptiveDescriptorObject

Scope note:

Description Metadata Section. This section records all of the descriptive metadata for all items in the METS object (including both structural map divs and descriptive metadata for data files). Metadata can be either included in the METS hub document (mdWrap) or referenced via an identifier/locator (mdRef), a la Warwick Framework. Multiple dmdSec elements are allowed so that descriptive metadata can be recorded for each separate item within the METS object.

Properties:

ramlet:includes someValueFrom mets:ID ramlet:includes allValuesFrom mets:admid, mets:created, mets:groupID, mets:ID, mets:mdRef, mets:mdWrap, mets:status

Data type:

None

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Asserted conditions:

are members of mets:admid



or are members of mets:created



or are members of mets:groupID



or are members of mets:ID



or are members of mets:mdRef



or are members of mets:mdWrap



or are members of mets:status

7.23 mets:div Class name:

mets:div

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#div

Mapped to:

ramlet:structureNode

Scope note:

Division. The METS standard represents a document structurally as a series of nested div elements, that is, as a hierarchy (e.g., a book, which is composed of chapters, which are composed of subchapters, which are composed of text). Every div node in the structural map hierarchy may be connected (via subsidiary mptr or fptr elements) to content files which represent that div’s portion of the whole document.

Properties:

ramlet:includes allValuesFrom mets:admID, mets:contentIDs, mets:div, mets:divType, mets:dmdID, mets:fPtr, mets:ID, mets:label, mets:mPtr, mets:order, mets:orderLabel

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:admID



or are members of mets:contentIDs



or are members of mets:div



or are members of mets:divType



or are members of mets:dmdID



or are members of mets:fPtr



or are members of mets:ID



or are members of mets:label 19

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



or are members of mets:mPtr



or are members of mets:order



or are members of mets:orderLabel

7.24 mets:divType Class name:

mets:divType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#div@TYPE

Mapped to:

ramlet:structureNodeType

Scope note:

An optional string attribute for specifying a type of division (e.g., chapter, article, page, etc.).

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.25 mets:end Class name:

mets:end

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#END

Mapped to:

ramlet:endPoint

Scope note:

An optional string attribute specifying the ending location for a subpart of the referenced file. Used with the BEGIN attribute.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.26 mets:extent Class name:

mets:extent

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#EXTENT

Mapped to:

ramlet:extent

Scope note:

An optional string attribute specifying the duration of the segment pointed to by the area element.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.27 mets:extType Class name:

mets:extType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#EXTTYPE

Mapped to:

ramlet:anchorType

Scope note:

Extent Type. An attribute that specifies the kind of EXTENT values that are being used. For example if BYTE is specified then EXTENT would represent a byte count. If TIME is specified the EXTENT would represent a duration of time. EXTTYPE must be one of the following values: BYTE, SMIL, MIDI, SMPTE-25, SMPTE-24, SMPTE-DF30, SMPTE-NDF30, SMPTE-DF29.97, SMPTENDF29.97, TIME, TCF.

Properties:

xsd:token someValueFrom oneOf dataRange BYTE, MIDI, SMIL, SMPTE-24, SMPTE-25, SMPTE-DF29.97, SMPTE-DF30, SMPTE-NDF29.97, SMPTENDF30, TCF, TIME.

Data type:

xsd:token

Asserted conditions:

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: 

BYTE



MIDI



SMIL



SMPTE-24



SMPTE-25



SMPTE-DF29.97



SMPTE-DF30



SMPTE-NDF29.97



SMPTE-NDF30



TCF



TIME

7.28 mets:fContent Class name:

mets:fContent

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#FContent

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Mapped to:

ramlet:resourceWrapperSet

Scope note:

File Content. The FContent element is used to deliver a content file for a METS document within the METS file itself. The content file must be either Base 64 encoded, and contained within the subsidiary binData wrapper element, or consist of XML information and be contained within the subsidiary xmlData wrapper element.

Properties:

ramlet:includes allValuesFrom mets:binData, mets:ID, mets:use, mets:xmlData

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:binData



or are members of mets:ID



or are members of mets:use



or are members of mets:xmlData

7.29 mets:file Class name:

mets:file

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#file

Mapped to:

ramlet:fileDescriptor

Scope note:

File Element. The file element provides access to content files for a METS object. A file element may contain one or more FLocat elements, which provide pointers to a content file, and/or an FContent element, which wraps an encoded version of the file. Note that ALL FLocat and FContent elements underneath a single file element should identify/contain identical copies of a single file.

Properties:

ramlet:includes someValueFrom mets:ID ramlet:includes allValuesFrom mets:admID, mets:checksum, mets:checksumType, mets:created, mets:dmdID, mets:fContent, mets:file, mets:fLocat, mets:groupID, mets:ID, mets:mimeType, mets:ownerID, mets:seq, mets:size, mets:stream, mets:transformFile, mets:use

Data type:

None

Asserted conditions:

are members of mets:admID



or are members of mets:checksum 22

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



or are members of mets:checksumType



or are members of mets:created



or are members of mets:dmdID



or are members of mets:fContent



or are members of mets:file



or are members of mets:fLocat



or are members of mets:groupID



or are members of mets:ID



or are members of mets:mimeType



or are members of mets:ownerID



or are members of mets:seq



or are members of mets:size



or are members of mets:stream



or are members of mets:transformFile



or are members of mets:use

7.30 mets:fileGrp Class name:

mets:fileGrp

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#fileGrp

Mapped to:

ramlet:functionalResourceGroup

Scope note:

File Group. This element allows for the grouping of content files into sets (all of the master images for a work, all of the images for a particular page, etc.).

Properties:

ramlet:includes allValuesFrom mets:admID, mets:file, mets:fileGrp, mets:ID, mets:use, mets:versDate

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:admID



or are members of mets:file



or are members of mets:fileGrp



or are members of mets:ID



or are members of mets:use



or are members of mets:versDate

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.31 mets:fileID Class name:

mets:fileID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#FILEID

Mapped to:

ramlet:localRef

Scope note:

An IDREF to the file element being pointed to by the div.

Properties:

None

Data type:

xsd:idRef

Asserted conditions:

None

7.32 mets:fileSec Class name:

mets:fileSec

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#fileSec

Mapped to:

ramlet:inventory

Scope note:

Content File Section. The content file section records information regarding all of the data files which comprise the digital library object.

Properties:

ramlet:includes allValuesFrom mets:fileGrp, mets:ID

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:fileGrp



or are members of mets:ID

7.33 mets:file_seq Class name:

mets:file_seq

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#file@SEQ

Mapped to:

ramlet:hasOrder

Scope note:

An optional integer indicating the sequence of a file relative to the others in its file group.

Properties:

None

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Data type:

xsd:integer

Asserted conditions:

None

7.34 mets:fLocat Class name:

mets:fLocat

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#FLocat

Mapped to:

ramlet:remoteResource

Scope note:

File Location. The FLocat element provides a pointer to the location of a content file. It uses the XLink syntax to provide linking information indicating the actual location of the content file, along with a few additional attributes specifying additional linking information. NOTE: FLocat is an empty element. The location of the resource pointed to MUST be stored in the xlink:href element

Properties:

ramlet:includes someValueFrom mets:locType, someValueFrom xlink:href ramlet:includes allValuesFrom mets:use, xlink:href, xlink:type

mets:ID,

mets:locType,

mets:otherLocType,

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either: 

is a member of mets:locType



or is a member of xlink:href

Being a member of this class implies that an individual has only values of the property ramlet:includes that either 

are members of mets:ID



or are members of mets:locType



or are members of mets:otherLocType



or are members of mets:use



or are members of xlink:href



or are members of xlink:type

7.35 mets:fPtr Class name:

mets:fPtr

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#fptr

Mapped to:

ramlet:structureNode

Scope note:

File Pointer. The fptr element associates a div element with content files that represent that div. It can either point to a file directly itself, via the FILEID 25

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

attribute, or it can do more complex links to content via the subsidiary area, par and seq elements. Properties:

ramlet:includes allValuesFrom mets:area, mets:contentIDs, mets:fileID, mets:ID, mets:par, mets:seq

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:area



or are members of mets:contentIDs



or are members of mets:fileID



or are members of mets:ID



or are members of mets:par



or are members of mets:seq

7.36 mets:groupID Class name:

mets:groupID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#GROUPID

Mapped to:

ramlet:groupingID

Scope note:

An optional string attribute providing an identifier that may be used to indicate that different metadata sections may be considered as part of a single group. Two metadata sections with the same GROUPID value are to be considered part of the same group. This facility might be used, for example, to group changed versions of the same metadata if previous versions are maintained in a file for tracking purposes.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.37 mets:ID Class name:

mets:ID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#ID

Mapped to:

ramlet:elementID

Scope note:

A required XML ID value for the element.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Properties:

None

Data type:

xsd:ID

Asserted conditions:

None

7.38 mets:interfaceDef Class name:

mets:interfaceDef

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#interfaceDef

Mapped to:

ramlet:interfaceDefLink

Scope note:

Interface Definition Object. The interface definition element contains a pointer an abstract definition of a set of related behaviors. These abstract behaviors can be associated with the content of a METS object. The interface definition element will be a pointer to another object (an interface definition object). An interface definition object could be another METS object, or some other entity (e.g., a WSDL file). Ideally, an interface definition object should contain metadata that describes a set of behaviors or methods. It may also contain files that describe the intended usage of the behaviors, and possibly files that represent different expressions of the interface definition. The interfaceDef element is optional to allow for cases where an interface definition can be obtained from a behavior mechanism object (see the mechanism element of the behaviorSec.

Properties:

ramlet:includes someValueFrom mets:locType, someValueFrom xlink:href ramlet:includes allValuesFrom mets:ID, mets:otherLocType, xlink:href, xlink:type

mets:label,

mets:locType,

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either: 

is a member of mets:locType



or is a member of xlink:href

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:ID



or are members of mets:label



or are members of mets:locType



or are members of mets:otherLocType



or are members of xlink:href



or are members of xlink:type

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.39 mets:label Class name:

mets:label

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#LABEL

Mapped to:

ramlet:title

Scope note:

An optional string attribute that may be used as a text description or title.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.40 mets:lastModDate Class name:

mets:lastModDate

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#LASTMODDATE

Mapped to:

ramlet:modificationDate

Scope note:

An optional dateTime specifying when the METS document was last modified.

Properties:

None

Data type:

xsd:dateTime

Asserted conditions:

None

7.41 mets:locType Class name:

mets:locType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#LOCTYPE

Mapped to:

ramlet:locatorDescriptor

Scope note:

Location Type. The type of locator used to reference a file. It must have one of the following values: ARK: Archival Resource Key URN: Uniform Resource Name URL: Uniform Resource Locator PURL: Persistent URL HANDLE: a CNRI Handle DOI: A Digital Object Identifier OTHER: a form of locator not specified elsewhere.

Properties:

xsd:token someValueFrom oneOf dataRange ARK, DOI, HANDLE, OTHER, PURL, URL, URN

Data type:

xsd:token

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Asserted conditions:

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: 

ARK



DOI



HANDLE



OTHER



PURL



URL



URN

7.42 mets:mdRef Class name:

mets:mdRef

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#mdRef

Mapped to:

ramlet:remoteDescriptorObject

Scope note:

Metadata Reference. The mdRef element is a generic element used throughout the METS schema to provide a pointer to metadata which resides outside the METS document. NB: mdRef is an empty element. The location of the metadata must be recorded in the xlink:href attribute, supplemented by the XPTR attribute as needed.

Properties:

ramlet:includes someValueFrom mets:locType, mets:mdType, xlink:href ramlet:includes allValuesFrom mets:checksum, mets:checksumType, mets:created, mets:ID, mets:label, mets:locType, mets:mdType, mets:mimeType, mets:otherLocType, mets:otherMdType, mets:size, mets:xptr, xlink:href, xlink:type

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either 

is a member of mets:locType



or is a member of mets:mdType



or is a member of xlink:href

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:checksum



or are members of mets:checksum:type



or are members of mets:created



or are members of mets:ID



or are members of mets:label

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



or are members of mets:locType



or are members of mets:mdType



or are members of mets:mimeType



or are members of mets:otherLocType



or are members of mets:otherMdType



or are members of mets:size



or are members of mets:xptr



or are members of xlink:href



or are members of xlink:type

7.43 mets:mdType Class name:

mets:mdType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#MDTYPE

Mapped to:

ramlet:descriptorTypeIndicator

Scope note:

A required attribute specifying the type of metadata being pointed at (e.g., MARC, EAD, etc.). It must have one of the following values: MARC: any form of MARC record MODS: metadata in the Library of Congress MODS format EAD: Encoded Archival Description finding aid DC: Dublin Core NISOIMG: NISO Technical Metadata for Digital Still Images LC-AV: technical metadata specified in the Library of Congress A/V prototyping project VRA: Visual Resources Association Core TEIHDR: Text Encoding Initiative Header DDI: Data Documentation Initiative FGDC: Federal Geographic Data Committee metadata LOM: Learning Object Model PREMIS: PREservation Metadata: Implementation Strategies PREMIS:OBJECT: PREMIS Object entity PREMIS:AGENT: PREMIS Agent entity PREMIS:RIGHTS: PREMIS Rights entity PREMIS:EVENT: PREMIS Event entity OTHER: metadata in a format not specified above.

Properties:

xsd:token someValueFrom oneOf dataRange DC, DDI, EAD, FGDC, LC-AV, LOM, MARC, MODS, NISOIMG, OTHER, PREMIS, PREMIS:AGENT, PREMIS:EVENT, PREMIS:OBJECT, PREMIS:RIGHTS, TEIHDR, VRA

Data type:

xsd:token

Asserted conditions:

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: 



DDI



EAD



FGDC



LC-AV



LOM

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



MARC



MODS



NISOIMG



OTHER



PREMIS



PREMIS:AGENT



PREMIS:EVENT



PREMIS:OBJECT



PREMIS:RIGHTS



TEIHDR



VRA

7.44 mets:mdWrap Class name:

mets:mdWrap

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#mdWrap

Mapped to:

ramlet:descriptorObject

Scope note:

Metadata Wrapper. A generic element used throughout the METS schema to allow the encoder to place arbitrary metadata conforming to other standards/schema within a METS document. The included metadata can either be encoded in XML, in which case it may be placed directly within the mdWrap element, or it can be Base64 encoded, and placed within a subsidiary binData element.

Properties:

ramlet:includes someValueFrom mets:mdType ramlet:includes allValuesFrom mets:binData, mets:checkSum, mets:checkSumType, mets:created, mets:ID, mets:label, mets:mdType mets:mimeType, mets:otherMdType, mets:size, mets:xmlData

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that is a member of mdType. Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:binData



or are members of mets:checkSum



or are members of mets:checkSumType



or are members of mets:created



or are members of mets:ID



or are members of mets:label 31

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



or are members of mets:mdType



or are members of mets:mimeType



or are members of mets:otherMdType



or are members of mets:size



or are members of mets:xmlData

7.45 mets:mechanism Class name:

mets:mechanism

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#mechanism

Mapped to:

ramlet:interfaceDefLink

Scope note:

Executable Mechanism. A mechanism element contains a pointer to an executable code module that implements a set of behaviors defined by an interface definition. The mechanism element will be a pointer to another object (a mechanism object). A mechanism object could be another METS object, or some other entity (e.g., a WSDL file). A mechanism object should contain executable code, pointers to executable code, or specifications for binding to network services (e.g., web services).

Properties:

ramlet:includes someValueFrom mets:loctype, ramlet:digitalResource, xlink:href ramlet:includes allValuesFrom mets:ID, mets:otherLocType, xlink:href, xlink:type

mets:label,

mets:locType,

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either: 

is a member of mets:locType



or is a member of ramlet:digitalResource



or is a member of xlink:href

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:ID



or are members of mets:label



or are members of mets:locType



or are members of mets:otherLocType



or are members of xlink:href



or are members of xlink:type

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.46 mets:mets Class name:

mets:mets

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#mets

Mapped to:

ramlet:topNode

Scope note:

The root element, mets, establishes the container for the information being stored and/or transmitted by the standard. METS stands for Metadata Encoding and Transmission Standard. METS is intended to provide a standardized XML format for transmission of complex digital library objects between systems. As such, it can be seen as filling a role similar to that defined for the Submission Information Package (SIP), Archival Information Package (AIP) and Dissemination Information Package (DIP) in the Reference Model for an Open Archival Information System.

Properties:

ramlet:includes allValuesFrom mets:amdSec, mets:behaviorSec, mets:dmdSec, mets:fileSec, mets:ID, mets:label, mets:metsHdr, mets:metsType, mets:objID, mets:profile, mets:structLink, mets:structMap

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:amdSec



or are members of mets:behaviorSec



or are members of mets:dmdSec



or are members of mets:fileSec



or are members of mets:ID



or are members of mets:label



or are members of mets:metsHdr



or are members of met:metsType



or are members of mets:objID



or are members of mets:profile



or are members of mets:structLink



or are members of mets:structMap

7.47 mets:metsHdr Class name:

mets:metsHdr

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#metsHdr

Mapped to:

ramlet:wholeAggregationDescriptorObject

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Scope note:

METS Header. Like a TEI Header, the METS Header element records metadata about the METS document itself (not the digital library object that the METS document encodes). It has two possible subsidiary elements, agent (document agent) and altRecordID (alternative Record ID).

Properties:

ramlet:includes allValuesFrom mets:agent, mets:admID, mets:altRecordID, mets:createDate, mets:ID, mets:lastModDate, mets:recordStatus

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:agent



or are members of mets:admID



or are members of mets:altrecordID



or are members of mets:createDate



or are members of mets:ID



or are members of mets:lastModDate



or are members of mets:recordStatus

7.48 mets:metsType Class name:

mets:metsType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#TYPE

Mapped to:

ramlet:aggregationType

Scope note:

An optional string attribute associated with the mets root elements that describes the type of object encoded by the mets document, e.g., book, journal, stereograph, etc.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.49 mets:mimeType Class name:

mets:mimeType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#MIMETYPE

Mapped to:

ramlet:mimeType

Scope note:

An optional string attribute providing the MIME type for the file.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.50 mets:mPtr Class name:

mets:mPtr

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#mptr

Mapped to:

ramlet:remoteTopNode

Scope note:

METS Pointer. The mptr element allows a div to be associated with a separate METS document containing the content corresponding with that div, rather than pointing to an internal file or file group. A typical instance of this would be the case of a METS document for a journal run, with a div element for each individual journal issue. The div elements for the issues might point to separate METS documents for each issue, rather than having files and file groups for every issue encoded in one document. NOTE: mptr is an empty element. The location of the resource pointed to MUST be stored in the xlink:href attribute.

Properties:

ramlet:includes someValueFrom mets:locType, xlink:href ramlet:include allValuesFrom mets:contentIDs, met:otherLocType, xlink:href, xlink:type

mets:ID,

mets:locType,

Data type:

None

Asserted conditions:

Being a member of this class implies that and individual has some value of the property ramlet:includes that either: 

is a member of mets:locType



or is a member of xlink:href

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:contentIDs



or are members of mets:ID



or are members of mets:locType



or are members of mets:otherLocType



or are members of xlink:href



or are members of xlink:type

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.51 mets:name Class name:

mets:name

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#name

Mapped to:

ramlet:partyName

Scope note:

The full name of the METS document agent.

Properties:

ramlet:includes cardinality 1

Data type:

xsd:string

Asserted conditions:

Being a member of this class implies that an individual has exactly one value for the property ramlet:includes.

7.52 mets:note Class name:

mets:note

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#note

Mapped to:

ramlet:note

Scope note:

Any additional information regarding the agent’s activities with respect to the METS document.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.53 mets:objID Class name:

mets:objID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#OBJID

Mapped to:

ramlet:aggregationID

Scope note:

An optional attribute recording a primary identifier assigned to the METS document.

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.54 mets:order Class name:

mets:order

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#ORDER

Mapped to:

ramlet:hasOrder

Scope note:

An optional integer representation of a div’s order among its siblings (e.g., its sequence.

Properties:

None

Data type:

xsd:integer

Asserted conditions:

None

7.55 mets:orderLabel Class name:

mets:orderLabel

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#ORDERLABEL

Mapped to:

ramlet:cardinalityLabel

Scope note:

An optional string representation of a div’s order among its siblings (e.g., “xii”), or a non-integer native numbering system. It is presumed that this value will still be machine-actionable (e.g., supports a page ‘go to’ function), and is not a replacement/substitute for the LABEL attribute.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.56 mets:otherLocType Class name:

mets:otherLocType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#OTHERLOCTYPE

Mapped to:

ramlet:locatorDescriptor

Scope note:

An optional string attribute used to indicate an alternative LOCTYPE if the LOCTYPE attribute itself has a value of “OTHER”.

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.57 mets:otherMdType Class name:

mets:otherMdType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#OTHERMDTYPE

Mapped to:

ramlet:descriptorTypeIndicator

Scope note:

Other Metadata Type. An optional string which may be used to record the particular form of metadata referenced by this element when the MDTYPE attribute has a value of “OTHER”.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.58 mets:otherRole Class name:

mets:otherRole

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#OTHERROLE

Mapped to:

ramlet:partyRole

Scope note:

An optional string attribute to specify the particular role an agent plays with respect to a METS object or its sources; to be used if the ROLE attribute has a value of OTHER.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.59 mets:otherType Class name:

mets:otherType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#OTHERTYPE

Mapped to:

ramlet:partyType

Scope note:

An optional string to indicate the particular type of agent, to be used if a value of OTHER is indicated in the agent’s TYPE attribute.

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.60 mets:ownerID Class name:

mets:ownerID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#OWNERID

Mapped to:

ramlet:alternateID

Scope note:

An optional string attribute which may be used to provide a unique identifier (including a URI) assigned to the file which may differ from the URI used to retrieve the file.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.61 mets:par Class name:

mets:par

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#par

Mapped to:

ramlet:parallel

Scope note:

Parallel Files. The par element should be used to link a div to a set of content files when those files should be played/displayed in unison to deliver the content to the user (e.g., displaying a text transcript simultaneously with playing an audio file). A par element has two possible subsidiary elements, which should be used in different cases. In cases where each bytestream to be played in parallel can fit in a single file, you should use subsidiary <area> elements within the par element to point to those files. However, in some cases, bytestreams which should be played in parallel are too large to fit in a single file (high quality multi-track audio, or video). In those cases, you should use subsidiary <seq> elements, where each <seq> contains the files comprising a particular bytestream in the order they should be played back. So, for example, in the case where you had an audio recording which had to be split into three different, sequential files, and a text transcription of the recording in a single file, you would use a par element containing two seq elements. The first seq element would contain three area elements, one for each audio file; the second seq element would contain a single area element, for the text transcription file.

Properties:

ramlet:includes allValuesFrom mets:area, mets:ID, mets:seq

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:area



or are members of mets:ID



or are members of mets:seq 39

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.62 mets:profile Class name:

mets:profile

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#PROFILE

Mapped to:

ramlet:aggregationSchema

Scope note:

An optional attribute providing a URI or other identifier for a METS profile to which this METS document conforms.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.63 mets:recordStatus Class name:

mets:recordStatus

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#RECORDSTATUS

Mapped to:

ramlet:status

Scope note:

An optional string indicating the status of the METS document, to be used mainly for internal processing purposes.

Properties:

None

Data type:

xsd:String

Asserted conditions:

None

7.64 mets:rightsMd Class name:

mets:rightsMd

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#rightsMD

Mapped to:

ramlet:rights

Scope note:

Intellectual Property Rights Metadata. The rightsMD element provides a wrapper around a generic metadata section, which should contain IP rights metadata.

Properties:

ramlet:includes someValueFrom mets:ID ramlet:includes allValuesFrom mets:admID, mets:created, mets:groupID, mets:ID, mets:mdRef, mets:mdWrap, mets:status

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Data type:

None

Asserted conditions:

are members of mets:admID



or are members of mets:created



or are members of mets:groupID



or are members of mets:ID



or are members of mets:mdRef



or are members of mets:mdWrap



or are members of mets:status

7.65 mets:role Class name:

mets:role

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#ROLE

Mapped to:

ramlet:partyRole

Scope note:

A required attribute specifying the role played by the agent with respect to the METS object. ROLE must have one of the following seven values: CREATOR: an agent responsible for creating the METS document; EDITOR: an agent responsible for editing the METS document; ARCHIVIST: an agent with archival responsibility for the METS document and/or the original sources used to create the METS object; PRESERVATION: an agent responsible for preserving the METS object and/or the original sources used to create the METS object; DISSEMINATOR: an agent responsible for distributing or publishing the METS object; CUSTODIAN: an agent with custodial responsibility for the METS object; IPOWNER: an agent with intellectual property rights in the METS object or some of its components; OTHER: an agent with other rights/responsibilities with respect to the METS object not set forth above.

Properties:

xsd:token someValuefrom oneOf dataRange ARCHIVIST, CREATOR, CUSTODIAN, DISSEMINATOR, EDITOR, IPOWNER, OTHER, PRESERVATION

Data type:

xsd:token

Asserted conditions:

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: 

ARCHIVIST



CREATOR



CUSTODIAN 41

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation



DISSEMINATOR



EDITOR



IPOWNER



OTHER



PRESERVATION

7.66 mets:seq Class name:

mets:seq

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#seq

Mapped to:

ramlet:hasOrder

Scope note:

Sequence of Files. The seq element should be used to link a div to a set of content files when those files should be played/displayed sequentially to deliver content to a user.

Properties:

ramlet:includes allValuesFrom mets:area, mets:ID, mets:par

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:area



or are members of mets:ID



or are members of mets:par

7.67 mets:shape Class name:

mets:shape

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#SHAPE

Mapped to:

ramlet:shapeIndicator

Scope note:

An optional string attribute defining the shape of a two-dimensional area being referenced within a linked content file. It must have one of the following values: RECT: rectangular area CIRCLE: a circular area POLY: an irregular polygon. The SHAPE attribute should be used as in HTML 4.

Properties:

xsd:token SomeValueFrom oneOf dataRange CIRCLE, POLY, RECT

Data type:

xsd:token

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Asserted conditions:

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: 

CIRCLE



POLY



RECT

7.68 mets:size Class name:

mets:size

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#SIZE

Mapped to:

ramlet:fileSize

Scope note:

An optional long integer specifying the size of the file in bytes.

Properties:

None

Data type:

xsd:long

Asserted conditions:

None

7.69 mets:smLink Class name:

mets:smLink

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#smLink

Mapped to:

ramlet:resourceIntraAggregationLink

Scope note:

Structural Map Link. An element linking two elements in the structural map, used to indicate that a hyperlink exists between the two METS components represented by the two structural map nodes. You would use smLink, for example, to record the existence of hypertext links between web pages, if you wish to record those links’ existence inside of METS.

Properties:

ramlet:includes someValueFrom xlink:from, xlink:to ramlet:includes allValuesFrom mets:ID xlink:show, xlink:title, xlink:to

xlink:arcRole xlink:actuate, xlink:from,

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either: 

is a member of xlink:from



or is a member of xlink:to

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:ID



or are members of xlink:arcRole



or are members of xlink:actuate



or are members of xlink:from



or are members of xlink:show



or are members of xlink:title



or are members of xlink:to

7.70 mets:sourceMd Class name:

mets:sourceMd

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#sourceMD

Mapped to:

ramlet:source

Scope note:

Source metadata. The sourceMD element provides a wrapper around a generic metadata section which should contain descriptive or administrative metadata regarding the original source materials used to create the METS object.

Properties:

ramlet:includes someValueFrom mets:ID ramlet:includes allValuesFrom mets:admID, mets:created, mets:groupID, mets:ID, mets:mdRef, mets:mdWrap, mets:status

Data type:

None

Asserted conditions:

are members of mets:admID



or are members of mets:created



or are members of mets:groupID



or are members of mets:ID



or are members of mets:mdRef



or are members of mets:mdWrap



or are members of mets:status

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.71 mets:status Class name:

mets:status

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#STATUS

Mapped to:

ramlet:status

Scope note:

An optional string attribute indicating the status of this metadata (e.g., superceded, current, etc.).

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.72 mets:stream Class name:

mets:stream

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#stream

Mapped to:

ramlet:stream

Scope note:

Component Byte Stream. A file may be composed of one or more subsidiary streams. An MPEG4 file, for example, might contain separate audio and video streams, each of which has its own technical metadata associated with it.

Properties:

ramlet:includes allValueFrom mets:admID, mets:dmdID, mets:ID, mets:ownerID, mets:streamType

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:admID



or are members of mets:dmdID



or are members of mets:ID



or are members of mets:ownerID



or are members of mets:streamType

7.73 mets:streamType Class name:

mets:streamType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#streamType

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Mapped to:

ramlet:streamType

Scope note:

The IANA MIME media type for the bytestream.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.74 mets:structID Class name:

mets:structID

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#STRUCTID

Mapped to:

ramlet:structRef

Scope note:

Structural Map ID. This attribute is an IDREFS to structMap sections or divs within a structMap in the METS document. The content that the STRUCTID attribute points to is considered “input” to the behavior mechanism (executable) defined for the behavior.

Properties:

None

Data type:

xsd:idRefs

Asserted conditions:

None

7.75 mets:structLink Class name:

mets:structLink

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#structLink

Mapped to:

ramlet:intraAggregationLink

Scope note:

Structural Map Linking. The Structural Map Linking section allows for the specification of hyperlinks between different components of a METS structure delineated in a structural map.

Properties:

ramlet:includes allValuesFrom mets:ID, mets:smLink

Data type:

xsd:string

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:ID



or are members of mets:smLink 46

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.76 mets:structMap Class name:

mets:structMap

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#structMap

Mapped to:

ramlet:staticStructure

Scope note:

Structural Map. The structural map is the heart of a METS document, defining the hierarchical arrangement of a primary source document which has been digitized. This hierarchy is encoded as a tree of ‘div’ elements. Any given ‘div’ can point to another METS document via the ‘mptr’ element, or to a single file, to a group of files, or to segments of individual files or groups of files through the ‘fptr’ and subsidiary elements.

Properties:

ramlet:includes allValuesFrom mets:div, mets:ID, mets:label, mets:StructMapType

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:div



or are members of mets:ID



or are members of mets:label



or are members of mets:structMapType

7.77 mets:structMapType Class name:

mets:structMapType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#structmap@TYPE

Mapped to:

ramlet:staticStructureType

Scope note:

An optional string attribute specifying the type of structural map provided. Typical values will be “PHYSICAL” for a map which describes the physical composition of the original work (a series with individual monographs with pages) and “LOGICAL” for one which describes the intellectual structure of the work (a monograph with TOC, forward, chapters, index, etc.).

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.78 mets:techMd Class name:

mets:techMd

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#techMD

Mapped to:

ramlet:technicalDescriptorObject

Scope note:

Technical Metadata. The techMD element provides a wrapper around a generic metadata section, which should contain technical metadata regarding a file or files.

Properties:

ramlet:includes someValueFrom mets:ID ramlet:includes allValuesFrom mets:admID, mets:created, mets:groupID, mets:ID, mets:mdRef, mets:mdWrap, mets:status

Data type:

None

Asserted conditions:

are members of mets:admID



or are members of mets:created



or are members of mets:groupID



or are members of mets:ID



or are members of mets:mdRef



or are members of mets:mdWrap



or are members of mets:status

7.79 mets:transformAlgorithm Class name:

mets:transformAlgorithm

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#TRANSFORMALGORITHM

Mapped to:

ramlet:resourceProcessingAlgorithm

Scope note:

A string describing the specific decompression or decryption routine used to access the contents of this file.

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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.80 mets:transformBehavior Class name:

mets:transformBehavior

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#TRANSFORMBEHAVIOR

Mapped to:

ramlet:resourceProcessingBehavior

Scope note:

An IDREF to a behavior element for this transformation.

Properties:

None

Data type:

xsd:idRef

Asserted conditions:

None

7.81 mets:transformFile Class name:

mets:transformFile

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#transformFile

Mapped to:

ramlet:resourceProcessing

Scope note:

The transform file <transformFile> element provides a means to access any subsidiary files listed below a <file> element by indicating the steps required to “unpack” or transform the subsidiary files. This element is repeatable and might provide a link to a <behavior> in the <behaviorSec> that performs the transformation.

Properties:

ramlet:includes someValueFrom mets:transformAlgorithm, mets:transformOrder, mets:transformType ramlet:includes allValuesFrom mets:ID mets:tranformBehavior, mets:transformKey, mets:transformType

mets:transformAlgorithm, mets:transformOrder,

Data type:

None

Asserted conditions:

Being a member of this class implies that an individual has some value of the property ramlet:includes that either: is a member of mets:transformAlgorithm or is a member of mets:transformOrder or is a member of mets:transformType

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Being a member of this class implies that an individual has only values of the property ramlet:includes that either: 

are members of mets:ID



or are members of mets:transformAlgorithm



or are members of mets:transformBehavior



or are members of mets:transformKey



or are members of mets:transformOrder



or are members of mets:transformType

7.82 mets:transformKey Class name:

mets:transformKey

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#TRANSFORMKEY

Mapped to:

ramlet:resourceProcessingKey

Scope note:

A string attribute representing a key to be used with the transform algorithm for accessing the file’s contents.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.83 mets:transformOrder Class name:

mets:transformOrder

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#TRANSFORMORDER

Mapped to:

ramlet:transformOrdering

Scope note:

The order in which the instructions must be followed in order to unpack or transform the container file.

Properties:

None

Data type:

xsd:positiveInteger

Asserted conditions:

None

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

7.84 mets:transformType Class name:

mets:transformType

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#TRANSFORMTYPE

Mapped to:

ramlet:resourceProcessingType

Scope note:

A type of transformation needed to render content of a file accessible (including unpacking a file into subsidiary files/streams).

Properties:

xsd:token someValueFrom DECRYPTION

Data type:

None

Asserted conditions:

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: 

DECOMPRESSION



DECRYPTION

oneOf

dataRange

DECOMPRESSION,

7.85 mets:use Class name:

mets:use

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#USE

Mapped to:

ramlet:intendedUse

Scope note:

An optional string attribute indicating the intended use of a file (e.g., master, reference, thumbnail for image files).

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

7.86 mets:versDate Class name:

mets:versDate

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#VERSDATE

Mapped to:

ramlet:creationDate

Scope note:

An optional dateTime attribute specifying the date a version/fileGrp of the digital object was created.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Properties:

None

Data type:

xsd:dateTime

Asserted conditions:

None

7.87 mets:xmlData Class name:

mets:xmlData

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#xmlData

Mapped to:

ramlet:resourceWrapper

Scope note:

A wrapper element to contain XML encoded metadata.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None.

7.88 mets:xptr Class name:

mets:xptr

Mapped from:

http://www.loc.gov/standards/mets/version17/mets.xsd#XPTR

Mapped to:

ramlet:componentTarget

Scope note:

An optional string attribute for providing an xptr to a location within the file pointed to by the mdRef element, if applicable.

Properties:

None

Data type:

xsd:string

Asserted conditions:

None

8. METS mapping ontology—object properties This clause provides declarations of all the object properties in the METS mapping ontology. The declarations use the following format: 

Property name: The name of the property.



Definition: The reference to the subclause in IEEE Std 1484.13.1-2012 that defines the property and the URI for the property in the associated OWL file. 52

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

8.1 ramlet:includes Property name:

ramlet:includes

Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#ramlet:includes

subclause

8.3.

See:

subclause

8.8.

See:

subclause

E.1.1.

See:

subclause

E.1.3.

See:

subclause

E.1.3.

See:

subclause

E.1.4.

See:

8.2 ramlet:references Property name:

ramlet:references

Deifinition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#ramlet:references

8.3 xlink:actuate Property name:

xlink:actuate

This Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:actuate

8.4 xlink:arcRole Property name:

xlink:arcRole

This Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:arcrole

8.5 xlink:from Property name:

xlink:from

This Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:from

8.6 xlink:href Property name:

xlink:href

Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:href

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

8.7 xlink:show Property name:

xlink:show

Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:show

subclause

E.1.7.

See:

subclause

E.1.8.

See:

subclause

E.1.9.

See:

E.1.10.

See:

8.8 xlink:title Property name:

xlink:title

Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:title

8.9 xlink:to Property name:

xlink:to

Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:to

8.10 xlink:type Property name:

xlink:type

Definition:

As defined by IEEE Std 1484.13.1-2012 http://standards.ieee.org/downloads/1484/1484.13.12012/ramletXlinkMappingV1.owl#xlink:type

subclause

9. METS mapping ontology—data types This clause provides declarations of all the data types in the METS mapping ontology. The declarations use the following format: 

Data-type name: The name of the data type.



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

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

9.1 xsd:anyURI Data-type name:

xsd:anyURI

Definition:

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

9.2 xsd:base64Binary Data-type name:

xsd:base64Binary

Definition:

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

9.3 xsd:dateTime Data-type name:

xsd:dateTime

Definition:

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

9.4 xsd:ID Data-type name:

xsd:ID

Definition:

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

9.5 xsd:idRef Data-type name:

xsd:idRef

Definition:

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

9.6 xsd:idRefs Data-type name:

xsd:idRefs

Definition:

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

9.7 xsd:integer Data-type name:

xsd:integer

Definition:

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

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

9.8 xsd:long Data-type name:

xsd:long

Definition:

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

9.9 xsd:positiveInteger Data-type name:

xsd:positiveInteger

Definition:

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

9.10 xsd:string Name:

xsd:string

Definition:

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

9.11 xsd:token Data-type 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:57 UTC from IEEE Xplore. Restrictions apply.

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

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] IEEE Std 1484.12.1™–2002, IEEE Standard for Learning Object Metadata. 17 [B2] IETF RFC 4287, The Atom Syndication Format. 18 [B3] IMS Specification, IMS Content Packaging Specification Information Model, Version 1.2, Public Draft 2. 19 [B4] ISO/IEC 10918–1, Information Technology—Digital compression and coding of continuous-tone still images: Requirements and guidelines. 20 [B5] ISO/IEC 13818–3, Information technology—Generic coding of moving pictures and associated audio information—Part 3: Audio. [B6] ISO/IEC 21000–2:2005, Information technology—Multimedia framework (MPEG–21), Part 2: Digital Item Declaration, 2nd ed. 21 [B7] W3C Recommendation (11 December 2012), OWL 2 Ontology Language Document Overview. 22 [B8] W3C Recommendation (10 February 2004), RDF/XML Syntax Specification. 23

17 IEEE publications are available from The Institute of Electrical and Electronics Engineers, Inc., 445 Hoes Lane, Piscataway, NJ 08854, USA (http://standards.ieee.org/). 18 IETF RFC 4287 is available at http://tools.ietf.org/html/ rfc4287. 19 IMS publications are available from the IMS Global Learning Consortium at http://www.imsglobal.org/specifications.html. 20 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/). 21 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. 22 OWL 2 Ontology Language Document Overview is available at http://www.w3.org/TR/owl2-overview/. 23 RDF/XML Syntax Specification is available at http://www.w3.org/TR/REC-rdf-syntax/.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technology—Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Annex B (informative) Conceptual overview The Metadata Encoding and Transmission Standard (METS) is an aggregation format that is primarily designed for the detailed description of digital resources found in various types of digital repositories, especially digital library repositories and archives. METS is typically used to encode descriptive, administrative, and structural metadata for a digital object, and to express the complex links among those forms of metadata. Using METS, it is possible to associate behaviors and services with a digital object. METS is designed to allow the sharing and exchange of digital objects among repositories. Other uses include rendering digital objects for display, navigation among and within digital objects, and digital object management using tools that can read and manipulate the digital resource and its metadata. METS supports the inclusion of resources in an aggregation, as well as referencing them. As a consequence, METS documents (i.e., aggregation definition documents) can aggregate resources either within a METS Extensible Markup Language (XML) document itself or by pointing at those resources wherever they may be located on the Internet as well as in directories adjacent to the aggregation definition document itself. Given the uses and properties of METS, it can be described as an aggregation format for externalized representations of digital aggregations of resources for learning, education, and training, as described in IEEE Std 1484.13.1™-2012. Other examples of this type of format include Atom [B2], IMS Content Packaging [B3], and MPEG–21 Digital Item Declaration (DID) [B6]. This recommended practice describes a canonical mapping from the METS XML elements and attributes to the conceptual model described in IEEE Std 1484.13.1-2012. By following this recommended practice, implementers can be sure that a METS document, expressed in the Resource Aggregation Model for Learning, Education, and Training (RAMLET) (IEEE Std 1484.13.1-2012), can be mapped in a consistent and reliable way to other content aggregation formats that have also been mapped to RAMLET. RAMLET outlines the advantages of using a standard means of mapping between different aggregation formats, which include preserving as much meaning and structure as possible when transforming an aggregation document from one format to another. Other uses include the ability to re-mix aggregation documents regardless of the formats of the source documents, and the construction of repositories and tool chains that are aggregation-format agnostic.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Annex C (informative) The binding of the core and METS mapping ontologies An OWL ontology can be represented or bound in several different ways so that it can be used by different implementation systems. An Resource Description Framework/Extensible Markup Language (RDF/XML) (W3C, RDF/XML Syntax Specification [B8]) representation is provided as downloadable files (Annex E). 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) representation is provided as a downloadable file because it is one of the more human readable RDF bindings (Annex D). 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 recommended practice. For the standard and associated recommended practices themselves, 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 recommended practice, 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.

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Annex D (normative) Internet availability and use of the Turtle representation of the conceptual model and METS mapping Terse RDF Triple Language (Turtle) representations of the conceptual model and the Metadata Encoding and Transmission Standard (METS) 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 METS mapping is available at the following URI: http://standards.ieee.org/downloads/1484/1484.13.2/ramletMETSMappingTurtle The Turtle representation of the conceptual model also contains URIs that resolve to the latest versions of the ontology files for this recommend practice and each of the additional 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 recommended practice 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!

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

IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning Technologyâ&#x20AC;&#x201D;Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation

Annex E (informative) Internet availability and use of the RDF/XML representations of the conceptual model and METS mapping World Wide Web Consortium (W3C) Resource Description Framework/Extensible Markup Language (RDF/XML) representations of the Web Ontology Language (OWL) bindings of the conceptual model and the Metadata Encoding and Transmission Standard (METS) mapping are available on the Web. These representations are informative. The latest version of the RAMLET conceptual model Resource Description Framework/Extensible Markup Language (RDF/XML) representation of the OWL binding (RAMLET core ontology file) is available at the following Uniform Resource Identifier (URI): http://standards.ieee.org/downloads/1484/1484.13.1/ramletCore The latest version of the METS mapping ontology RDF/XML representation of the OWL binding (Atom mapping ontology file) is available at the following URI: http://standards.ieee.org/downloads/1484/1484.13.2/ramletMETSMapping The RAMLET core ontology file that accompanies this recommend practice contains Uniform Resource Identifiers (URIs) that resolve to the latest versions of the ontology files for this recommended practice and each of the additional 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 Atom mapping ontology file reflect the content of this recommended practice 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!

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