ANSI NISO Z39.88-2004 The OpenURL Framework for Context-Sensitive Services《上下文有关服务的开放的URL框架》.pdf

《ANSI NISO Z39.88-2004 The OpenURL Framework for Context-Sensitive Services《上下文有关服务的开放的URL框架》.pdf》由会员分享，可在线阅读，更多相关《ANSI NISO Z39.88-2004 The OpenURL Framework for Context-Sensitive Services《上下文有关服务的开放的URL框架》.pdf（120页珍藏版）》请在麦多课文档分享上搜索。

1、 ANSI/NISO Z39.88-2004 ISSN: 1041-5653 The OpenURL Framework for Context-Sensitive Services Abstract: The OpenURL Framework Standard defines an architecture for creating OpenURL Framework Applications. An OpenURL Framework Application is a networked service environment, in which packages of informat

2、ion are transported over a network. These packages have a description of a referenced resource at their core, and they are transported with the intent of obtaining context-sensitive services pertaining to the referenced resource. To enable the recipients of these packages to deliver such context-sen

3、sitive services, each package describes the referenced resource itself, the network context in which the resource is referenced, and the context in which the service request takes place. This Standard specifies how to construct these packages as Representations of abstract information constructs cal

4、led ContextObjects. To this end, the OpenURL Framework Standard defines the following core components: Character Encoding, Serialization, Constraint Language, ContextObject Format, Metadata Format, and Namespace. In addition, this Standard defines Transport, a core component that enables communities

5、 to specify how to transport ContextObject Representations. Finally, this Standard specifies how a community can deploy a new OpenURL Framework Application by defining a new Community Profile, the last core component. This Standard defines the OpenURL Framework Registry and the rules that govern the

6、 usage of this Registry. The OpenURL Framework Registry contains all instances of all core components created by communities that have deployed OpenURL Framework Applications. This Standard defines and registers the initial content of the OpenURL Framework Registry, thereby deploying two distinct Op

7、enURL Framework Applications. An American National Standard Developed by the National Information Standards Organization Approved: April 15, 2005 by the American National Standards Institute Published by the National Information Standards Organization NISO Press, Bethesda, Maryland, U.S.A. ANSI/NISO

8、 Z39.88-2004 NISO 2005 About NISO Standards NISO Standards are developed by the Standards Committees of the National Information Standards Organization. The development process is a strenuous one that includes a rigorous peer review of proposed standards open to each NISO Voting Member and any other

9、 interested party. Final approval of the standard involves verification by the American National Standards Institute that its requirements for due process, consensus, and other approval criteria have been met by NISO. Once verified and approved, NISO Standards also become American National Standards

10、. This standard may be revised or withdrawn at any time. For current information on the status of this standard contact the NISO office or visit the NISO website at: http:/www.niso.org Published by NISO Press 4733 Bethesda Avenue, Suite 300 Bethesda, MD 20814 www.niso.org Copyright 2005 by the Natio

11、nal Information Standards Organization All rights reserved under International and Pan-American Copyright Conventions. For noncommercial purposes only, this publication may be reproduced or transmitted in any form or by any means without prior permission in writing from the publisher, provided it is

12、 reproduced accurately, the source of the material is identified, and the NISO copyright status is acknowledged. All inquires regarding translations into other languages or commercial reproduction or distribution should be addressed to: NISO Press, 4733 Bethesda Avenue, Suite 300, Bethesda, MD 20814

13、. Printed in the United States of America ISSN: 1041-5653 National Information Standards series ISBN-10: 1-880124-61-0 ISBN-13: 978-1-880124-61-1 Library of Congress Cataloging-in-Publication Data National Information Standards Organization (U.S.) The OpenURL Framework for context-sensitive services

14、 : an American national standard / developed by the National Information Standards Organization ; approved April 13, 2005 by the American National Standards Institute. p. cm. (National information standards series) “ANSI/NISO Z39.88-2004.“ Includes bibliographical references. ISBN-13: 978-1-880124-6

15、1-1 ISBN 10: 1-880124-61-0 1. Web servicesStandards. 2. Uniform Resource Identifiers. I. American National Standards Institute. II. Title. III. Series TK5105.88813.N38 2006 006.76dc22 2006044980 ANSI/NISO Z39.88-2004 2005 NISO i Contents Foreword v 1 Purpose and Scope 1 2 Referenced Standards. 2 3 N

16、otational Conventions. 4 4 Definitions. 5 Part 1: ContextObjects and Transports 9 5 ContextObject, Entity, and Descriptor. 11 5.1 ContextObject and Entity 11 5.2 Descriptor 12 5.2.1 Identifier12 5.2.2 By-Value Metadata. 13 5.2.3 By-Reference Metadata 13 5.2.4 Private Data 13 5.3 Constraints 14 6 Reg

17、istry. 15 6.1 Registry Entries. 15 6.2 Registry Identifiers 17 6.3 Using the Registry. 17 7 Formats . 18 7.1 Serializations Registry 19 7.2 Constraint Languages Registry. 20 7.3 Constraint Definitions 20 8 Representing ContextObjects 21 8.1 Character Encodings Registry 21 8.2 ContextObject Formats R

18、egistry. 22 9 Representing Entities 24 9.1 Namespaces Registry. 24 9.2 Metadata Formats Registry. 25 10 Transporting ContextObject Representations: Transports Registry. 27 11 Defining Applications: Community Profiles Registry 28 Part 2: The KEV ContextObject Format 31 12 The KEV ContextObject Format

19、 . 33 12.1 The KEV Serialization.33 12.2 The Z39.88-2004 Matrix Constraint Language. 34 12.3 Constraint Definitions in the KEV ContextObject Format . 35 12.3.1 Z39.88-2004 Matrix Constraint Definition for the KEV ContextObject Format. 35 12.3.2 Z39.88-2004 Matrix Constraint Definitions for KEV Metad

20、ata Formats . 36 ANSI/NISO Z39.88-2004 ii 2005 NISO 13 KEV ContextObject Representations .37 13.1 Cardinality Constraints on the KEV ContextObject Format.38 13.2 Keys in the KEV ContextObject Format 38 13.2.1 Keys for Entity Descriptors39 13.2.2 Keys for By-Value Metadata Descriptors.40 13.2.3 Keys

21、for By-Reference Metadata Descriptors 40 13.2.4 Keys for Administrative Data.40 13.3 Character Encoding in the KEV ContextObject Format 40 13.4 URL-Encoding in the KEV ContextObject Format.41 14 Entity Descriptors in the KEV ContextObject Format.41 14.1 Identifier Descriptors41 14.2 By-Value and By-

22、Reference Metadata Descriptors 42 14.2.1 Rules Guiding By-Value and By-Reference Metadata Descriptors 42 14.2.2 By-Value Metadata Descriptors 43 14.2.3 By-Reference Metadata Descriptors.43 14.3 Private Data Descriptors44 14.4 Example of a KEV ContextObject Representation45 15 KEV-Based Community Pro

23、files .46 Part 3: The XML ContextObject Format 47 16 The XML ContextObject Format49 16.1 The XML Serialization .49 16.2 XML Schema as a Constraint Language.49 16.3 Constraint Definitions in the XML ContextObject Format49 16.3.1 XML Schema Constraint Definition for the XML ContextObject Format.50 16.

24、3.2 XML Schema Constraint Definitions for XML Metadata Formats .54 17 XML ContextObject Representations .62 17.1 Cardinality Constraints on the XML ContextObject Format 63 17.2 Entity and Descriptor Elements in the XML ContextObject Format 64 17.3 Administrative Elements and Attributes in the XML Co

25、ntextObject Format66 17.4 Character Encoding in the XML ContextObject Format66 18 Entity Descriptors in the XML ContextObject Format 66 18.1 Identifier Descriptors67 18.2 By-Value and By-Reference Metadata Descriptors 67 18.2.1 Rules Guiding By-Value and By-Reference Metadata Descriptors 67 18.2.2 B

26、y-Value Metadata Descriptors 68 18.2.3 By-Reference Metadata Descriptors.69 18.3 Private Data Descriptors69 18.4 Example of an XML ContextObject Representation70 19 XML-Based Community Profiles.71 Part 4: OpenURL Transports 73 20 By-Reference OpenURL Transports.75 20.1 OpenURL Keys in By-Reference O

27、penURL Transports .75 20.2 By-Reference OpenURL Transports using HTTP(S) GET76 20.3 By-Reference OpenURL Transports using HTTP(S) POST .77 ANSI/NISO Z39.88-2004 2005 NISO iii 21 By-Value OpenURL Transports 77 21.1 OpenURL Keys in By-Value OpenURL Transports 78 21.2 By-Value OpenURL Transports using

28、HTTP(S) GET. 79 21.3 By-Value OpenURL Transports using HTTP(S) POST 80 22 Inline OpenURL Transports 81 22.1 OpenURL Keys in Inline OpenURL Transports 82 22.2 Inline OpenURL Transports using HTTP(S) GET. 83 22.3 Inline OpenURL Transports using HTTP(S) POST 84 Appendix A Responsibilities of the Mainte

29、nance Agency for the OpenURL Framework Standard (informative) 87 Appendix B Specification of the Z39.88-2004 Matrix Constraint Language (normative) 89 B.1 The Z39.88-2004 Matrix Constraint Language. 89 B.2 Constraint Definitions in the KEV ContextObject Format . 90 Appendix C The Level 1 San Antonio

30、 Community Profile (informative) 95 C.1 History. 95 C.2 Maintenance of SAP1 . 95 C.3 Introduction to SAP1 . 95 C.4 Purpose and Scope 96 C.5 Registry Entries in SAP1. 97 Appendix D The Level 2 San Antonio Community Profile (informative) 99 D.1 History. 99 D.2 Maintenance of SAP2 . 99 D.3 Introduction

31、 to SAP2 . 99 D.4 Purpose and Scope 99 D.5 Registry Entries in SAP2. 101 Appendix E Implementation Guidelines for the OpenURL Transports (informative) 103 E.1 Length of HTTP(S) GET URIs 103 E.2 URL-Encoding and URL-Decoding. 103 E.3 Parsing of HTTP(S) Query Strings . 103 Figures Figure 1: Core Compo

32、nents of the OpenURL Framework.16 Tables Table 1: Fundamental ContextObject Constraints .14 Table 2: Core Components and their Registry Identifiers 17 Table 3: Registry Identifiers for Serializations19 Table 4: Registry Identifiers for Constraint Languages 20 Table 5: Registry Identifiers for Charac

33、ter Encodings22 Table 6: Registry Identifiers for ContextObject Formats 23 Table 7: Registry Identifiers for Namespaces 25 Table 8: Registry Identifiers for Registered Metadata Formats26 Table 9: Registry Identifiers for Transports 27 Table 10: Registry Identifiers for Community Profiles 29 Table 11

34、: SAP1 Community Profile, Excerpt30 ANSI/NISO Z39.88-2004 iv 2005 NISO Table 12: Structure of the Z39.88-2004 Matrix 34 Table 13: Z39.88-2004 Matrix Constraint Definition of KEV ContextObject Format, Excerpt . 36 Table 14: Z39.88-2004 Matrix Constraint Definition of KEV Metadata Format for “book”, E

35、xcerpt. 37 Table 15: KEV ContextObject Format Cardinality Constraints . 38 Table 16: KEV ContextObject Format Keys for Entity Descriptors. 39 Table 17: KEV ContextObject Format Administration Key Prefix and Suffixes 40 Table 18: XML Schema Constraint Definition of XML ContextObject Format. 50 Table

36、19: XML Schema Constraint Definition of XML Metadata Format for “journal” . 55 Table 20: XML ContextObject Format Cardinality Constraints. 64 Table 21: XML ContextObject Format Entities and Descriptors . 65 Table 22: XML ContextObject Format Administrative Information . 66 Table 23: Structure of the

37、 Z39.88-2004 Matrix 89 Table 24: XHTML Template for Z39.88-2004 Matrix . 91 Table 25: Use of ContextObject Entities in the Scholarly-Information Community 96 Table 26: SAP1 Registered Elements . 97 Table 27: Use of ContextObject Entities in the Scholarly-Information Community 100 Table 28: SAP2 Regi

38、stered Elements . 101 Examples Example 1: Examples of Entities . 12 Example 2: Identifiers for a Referent, Requester, and Resolver . 12 Example 3: By-Value Metadata for a Referent 13 Example 4: By-Reference Metadata for a Requester 13 Example 5: Private Data for a Referent . 14 Example 6: A Registry

39、 Entry 16 Example 7: Identification of a Character Encoding 22 Example 8: Identification of a ContextObject Format 24 Example 9: Identification of Entities using Identifiers from Namespaces 25 Example 10: Identification of Unregistered Metadata Formats 27 Example 11: KEV ContextObject Representation

40、 . 38 Example 12: Identifier Descriptors in a KEV ContextObject Representation 41 Example 13: By-Value Metadata Descriptor in a KEV ContextObject Representation . 43 Example 14: By-Reference Metadata Descriptor as a Property List . 43 Example 15: Private Data Descriptor in a KEV ContextObject Repres

41、entation 44 Example 16: KEV ContextObject Representation . 45 Example 17: XML ContextObject Representation . 63 Example 18: Identifier Descriptors in an XML ContextObject Representation 67 Example 19: Referent with a By-Value Metadata Descriptor. 68 Example 20: Requester with a By-Reference Metadata

42、 Descriptor 69 Example 21: ReferringEntity with a Private Data Descriptor . 69 Example 22: XML ContextObject Representation . 70 Example 23: By-Reference OpenURL Transport using HTTP GET 76 Example 24: By-Reference OpenURL Transport using HTTP POST . 77 Example 25: By-Value OpenURL Transport using H

43、TTP GET . 79 Example 26: By-Value OpenURL Transport using HTTP POST. 80 Example 27: Inline OpenURL Transport using HTTP GET . 83 Example 28: An HTML Form (POST Method) to generate an Inline OpenURL Transport . 85 Example 29: Inline OpenURL Transport using HTTP POST. 85 ANSI/NISO Z39.88-2004 2005 NIS

44、O v Foreword (This foreword is not part of The OpenURL Framework for Context Sensitive Services, ANSI/NISO Z39.88-2004. It is included for information only.) History As the World Wide Web began its explosive growth in the early 1990s, the scholarly-information community made available digital schola

45、rly materials, consisting of metadata and full-text content. As this body of materials grew, it became increasingly difficult to provide adequate links between related information assets, distributed across many collections and controlled by different custodians. By 1999, the scholarly-information c

46、ommunity had embarked on several linking efforts, surveyed in Van de Sompel and Hochstenbach R1. In 1999, NISO started a series of invitational workshops to explore issues in the area of reference linking. Representatives from the library, publishing, and information services communities identified

47、the appropriate-copy problem as a major issue, because its solution was expected to solve other link-resolution problems. The appropriate-copy problem arises when multiple copies of a resource exist, and each copy is governed by a different access policy. A specific user should be directed to a copy

48、 of the resource that is governed by an access policy compatible with that users access privileges. None of the proposed linking architectures could accomplish this. A series of collaborations by Herbert Van de Sompel (Ghent University, Los Alamos National Laboratory, and Cornell University), Patric

49、k Hochstenbach (Ghent University), and Oren Beit-Arie (Ex Libris) culminated in the solution of the appropriate-copy problem. Their solution also addressed related issues in the delivery of context-sensitive services for the web-based scholarly information environment. This collaboration resulted in: Development of the SFX linking server and the OpenURL architecture R1 R2 R3. Publication of the OpenURL 0.1 specification that defines an HTTP GET syntax for transporting metadata and identifiers from an information service to a linking