IEEE 1484 13 2-2013 en Recommended Practice for Learning Technology-Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resou.pdf

《IEEE 1484 13 2-2013 en Recommended Practice for Learning Technology-Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resou.pdf》由会员分享，可在线阅读，更多相关《IEEE 1484 13 2-2013 en Recommended Practice for Learning Technology-Metadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resou.pdf（73页珍藏版）》请在麦多课文档分享上搜索。

1、 IEEE Std 1484.13.2-2013 IEEE Recommended Practice for Learning TechnologyMetadata 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 Standar

2、ds Board 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

3、 the Digital Library Federation, Council on Library and Information Resources. Knoodlis 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 produ

4、cts may be used if they can be shown to lead to the same results. W3Cis 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. XMLExtensible Markup Language; Language by W3Cclaimed

5、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 lik

6、e to thank Revelytix, Inc., for making available the Knoodlontology 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) re

7、late 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 aggreg

8、ation, 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 Am

9、erica. IEEE is a registered trademark in the U.S. Patent 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 do

10、cuments 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. F

11、urthermore, 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 pr

12、ofessional 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

13、 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:

14、 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

15、 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 pub

16、lished by IEEE should be considered the approved IEEE standard. Official statements A statement, written or oral, that is not processed in accordance with the IEEE-SA Standards Board Operations Manual shall not be considered or inferred to be the official position of IEEE or any of its committees an

17、d 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 rathe

18、r 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. S

19、uggestions 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 bal

20、ance 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 int

21、erpretation 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 r

22、egulations 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

23、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. a

24、nd 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 meth

25、ods. 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

26、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 portio

27、ns of any individual standard for educational classroom use can also be obtained through the Copyright Clearance Center. 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

28、 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

29、 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

30、 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 list

31、ed previously. For more information about the IEEE SA or IEEEs 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/ind

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

33、he 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. Letter

34、s 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.

35、 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 l

36、icensing 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 infringemen

37、t of such rights, is entirely their own responsibility. Further information may be obtained from the IEEE Standards Association. Copyright 2013 IEEE. All rights reserved. vi Participants At the time this IEEE recommended practice was completed, the Resource Aggregation Models for Learning, Education

38、, 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 ma

39、y 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 Wh

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

41、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 th

42、e 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 Copyright 2013 IEEE. All ri

43、ghts reserved. vii Introduction This introduction is not part of IEEE Std 1484.13.2-2013, IEEE Recommended Practice for Learning TechnologyMetadata Encoding and Transmission Standard (METS) Mapping to the Conceptual Model for Resource Aggregation. This recommended practice specifies how the elements

44、 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.12012. Copyright 2013 IEEE. All rights reserved. viii Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 2. Normativ

45、e 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 mapp

46、ing ontology 6 6.4 Conforming transforming implementations . 6 7. METS mapping ontologyclasses 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:behavior11 7.10 mets:behavio

47、rSec 12 7.11 mets:beType13 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:d

48、ivType 20 7.25 mets:end 20 7.26 mets:extent 20 7.27 mets:extType 21 7.28 mets:fContent21 7.29 mets:file 22 7.30 mets:fileGrp 23 Copyright 2013 IEEE. All rights reserved. ix 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.

49、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:mdWrap31 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:reco