1、 IEEE Std 1484.13.5-2013 IEEE Recommended Practice for Learning Technology IETF RFC 4287Atom Syndication FormatMapping to the Conceptual Model for Resource Aggregation Sponsor Learning Technology Standards Committee of the IEEE Computer Society Approved 31 October 2013 IEEE-SA Standards Board Copyri
2、ght permissions: The scope notes in Clause 7 and the definitions of the atom-prefixed data types in Clause 9 are reprinted with permission from the IETF Trust, IETF RFC 4287The Atom Syndication Format, 2005. Dublin Coreis a registered trademark of the Dublin Core Metadata Initiative Limited (USPTO 2
3、519654). Knoodlis a registered trademark of Revelytix, Inc. 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. XMLExtensible Markup Language; Language by W3Cclaimed as a
4、trademark or generic term by MIT, ERCIM, and/or Keio on behalf of the W3C. Abstract: This recommended practice specifies how the elements and attributes defined in the Atom Syndication Format (Atom) relate to the components of the conceptual model for resource aggregation defined in IEEE Std 1484.13
5、.1-2012. Keywords: aggregation format, Atom Syndication Format, conceptual model, content aggregation, digital aggregation, digital resource, IEEE 1484.13.5, RAMLET, resource aggregation, resource aggregation format The Institute of Electrical and Electronics Engineers, Inc. 3 Park Avenue, New York,
6、 NY 10016-5997, USA Copyright 2013 by The Institute of Electrical and Electronics Engineers, Inc. All rights reserved. Published 16 December 2013. Printed in the United States of America. IEEE is a registered trademark in the U.S. Patent fitness for a particular purpose; non-infringement; and qualit
7、y, 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 IE
8、EE 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 th
9、rough 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 owe
10、d 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 appropri
11、ateness 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 A
12、ND 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.
13、 Translations The IEEE consensus development process involves the review of documents in English only. In the event that an IEEE standard is translated, only the English version published by IEEE should be considered the approved IEEE standard. Official statements A statement, written or oral, that
14、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 e
15、ducational 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
16、 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 suppo
17、rting 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
18、 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
19、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 pr
20、ovisions 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 th
21、at 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
22、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 wa
23、ive 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 f
24、or 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
25、. 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
26、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
27、 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
28、 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 IEEEs standards development process, visit the IEEE-SA Website
29、 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
30、 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
31、 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
32、 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 f
33、or 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 licensi
34、ng 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 Ass
35、ociation. Copyright 2013 IEEE. All rights reserved. vi 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 Willem Kraan, Principal Investi
36、gator Scott Lewis, Technical Editor Nancy Hoebelheinrich 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 Keith Chow Geoffrey Darnton David Fusc
37、hi Randall Groves Nancy Hoebelheinrich Werner Hoelzl Noriyuki Ikeuchi Mark Jaeger Willem Kraan Susan Land David Massart Charles Ngethe Daniel Rehak Thomas Starai Katrien Verbert John Vergis Oren Yuen Janusz Zalewski Daidi Zhong When the IEEE-SA Standards Board approved this recommended practice on 3
38、1 October 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 Hof
39、fman 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 DeBlasi
40、o, 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 rights reserved. viiIntroduction This introduction is not part of IEEE St
41、d 1484.13.5-2013, IEEE Recommended Practice for Learning TechnologyIETF RFC 4287Atom Syndication FormatMapping to the Conceptual Model for Resource Aggregation. This Recommended Practice specifies how the elements and attributes defined in Atom Syndication Format (Atom) relate to the components of t
42、he conceptual model for resource aggregation defined in IEEE Std 1484.13.12012. The Resource Aggregation Models for Learning, Education, and Training (RAMLET) Working Group would like to thank Revelytix, Inc., for making available the Knoodlontology tools that were used to aid in the development and
43、 maintenance of the ontology files.aaKnoodl 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 l
44、ead to the same results. Copyright 2013 IEEE. All rights reserved. viii Contents 1. Overview 1 1.1 Scope . 1 1.2 Purpose 1 2. Normative references 2 3. Definitions, acronyms, and abbreviations 2 3.1 Definitions . 2 3.2 Acronyms and abbreviations . 5 4. Special terms 6 5. Class and property prefix de
45、finitions 6 6. Conformance 6 6.1 Conforming aggregation instances 7 6.2 Conforming bindings . 7 6.3 Conforming extensions of the Atom mapping ontology 7 6.4 Conforming transforming implementations . 7 7. Atom mapping ontologyclasses 7 7.1 atom:author 8 7.2 atom:category 9 7.3 atom:content 9 7.4 atom
46、:content.type .10 7.5 atom:contributor .10 7.6 atom:email 11 7.7 atom:entry .11 7.8 atom:feed 13 7.9 atom:generator 14 7.10 atom:href .14 7.11 atom:hrefLang 15 7.12 atom:icon 15 7.13 atom:ID .15 7.14 atom:label .16 7.15 atom:length .16 7.16 atom:link .16 7.17 atom:link.title 17 7.18 atom:link.type .
47、17 7.19 atom:logo 18 7.20 atom:name 18 7.21 atom:published18 7.22 atom:rel .19 7.23 atom:rights 19 7.24 atom:scheme .20 7.25 atom:source .20 7.26 atom:src 21 7.27 atom:subtitle .21 7.28 atom:summary 22 7.29 atom:term 22 7.30 atom:text.type .22 Copyright 2013 IEEE. All rights reserved. ix 7.31 atom:t
48、itle .23 7.32 atom:updated 23 7.33 atom:URI 24 7.34 atom:version .24 8. Atom mapping ontologyobject properties .24 8.1 ramlet:includes24 8.2 ramlet:isIncludedBy 25 9. Atom mapping ontologydata types 25 9.1 atom:atomEmailAddress.25 9.2 atom:atomLanguageTag .25 9.3 atom:atomTextConstruct 26 9.4 atom:I
49、RI 26 9.5 atom:textValues 26 9.6 atom:typeValues .27 9.7 xsd:anyURI .28 9.8 xsd:dateTime 28 9.9 xsd:integer 28 9.10 xsd:string 28 9.11 xsd:token .29 Annex A (informative) Bibliography 30 Annex B (informative) Conceptual overview 31 Annex C (informative) The binding of the core and Atom mapping ontologies .32 Annex D (normative) Internet availability and use of the Turtle representation of the conceptual model and Atom mapping .33 Annex E (informative) Internet availability and use of the RDF/XML representations of the conceptual model and Atom mapping
