idnits 2.17.1 draft-ietf-uri-url-irp-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 173 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 18 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** There are 10 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 111 has weird spacing: '...alue of small...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' Summary: 12 errors (**), 0 flaws (~~), 3 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 IETF URI Working Group R. Denenberg 2 Internet-Draft J. Kunze 3 draft-ietf-uri-url-irp-00.txt B. McLean 4 22 November 1994 Editors 5 Expires in six months 7 Uniform Resource Locators for Z39.50 9 1. Status of this Document 11 This document is an Internet-Draft. Internet-Drafts are working documents 12 of the Internet Engineering Task Force (IETF), its Areas, and its Working 13 Groups. Note that other groups may also distribute working documents as 14 Internet-Drafts. 16 Internet-Drafts are working documents valid for a maximum of six months. 17 Internet-Drafts may be updated, replaced, or obsoleted by other documents 18 at any time. It is not appropriate to use Internet-Drafts as reference 19 material or to cite them other than as a ``working draft' or ``work in 20 progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 24 Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or 25 munnari.oz.au. 27 Distribution of this document is unlimited. Please send comments to 28 jak@violet.berkeley.edu, or to the discussion lists uri@bunyip.com and 29 z3950iw@nervm.nerdc.ufl.edu. 31 2. Introduction 33 Z39.50 is an information retrieval protocol that does not fit neatly into 34 a retrieval model designed primarily around the stateless fetch of data. 35 Instead, it models a general user inquery as a session-oriented, multi- 36 step task, any step of which may be suspended temporarily while the 37 server requests additional parameters from the client before continuing. 38 Some, none, or all of these client/server interactions may require 39 participation of the client user, depending only on the client software 40 (the protocol itself make no such requirements). 42 On the other hand, retrieval of "well-known" data may be performed in 43 a single step, that is, with a degenerate Z39.50 session consisting of 44 exactly one protocol search request and response. Besides the basic 45 search sub-service, there are several ancillary sub-services (e.g., Scan, 46 Result Set Delete). Among the functions covered by combinations of the 47 sub-services, two core functions emerge as appropriately handled by two 48 separate URL schemes: the Session URL and the Retrieval URL. 50 Using two schemes instead of one makes a critical distinction between 51 a Z39.50 Session URL, which opens a client session -- leaving the user 52 to close it -- and a Z39.50 Retrieval URL, which opens and closes a client 53 session, then displays any retrieved results. Making this distinction at 54 the scheme level allows the user interface to reflect it on to the user, 55 but without actually requiring the user display formatter to parse 56 otherwise opaque parts of the URL (consistent with current practice). 58 3. The Z39.50 Session URL 60 The Z39.50 Session and Retrieval URLs follow the Common Internet Scheme 61 Syntax as defined in RFC ???, "Uniform Resource Locators (URL)" [1]. 62 The specific syntax for the Session URL is: 64 z39.50s://host[:port] 65 [/database[+database...] 66 [?docid 67 [&esn=elementset] 68 [&rs=recordsyntax[+recordsyntax...]]]] 70 This may be informally described as providing the mechanism to switch 71 the user of the browser to a window in which a Z39.50 client is running. 73 - Host is required. 74 - Port is optional, and defaults to 210. 75 - All other parameters are optional, however, if docid is present, 76 then database must be present. 77 - The Z39.50 client will start a session to the specified host/port 78 (alternatively, it need not explicitly start a session, but may 79 instead utilize an already open session to the same host/port). 80 - If docid is included, the client will perform the specified search 81 (in the same manner as for the retrieval URL, specified below). 82 - If docid is not included, and other parameters (besides host/port) 83 are specified, the client may use those parameters as "hints". 84 Various clients may choose to treat them as requirements, or as 85 preferences, or ignore them. 86 - In any case (whether a search is performed or not), the client will 87 leave the Z39.50 session open for the user, to do retrievals, new 88 searches, etc. This is the main distinction from the z39.50r URL. 90 4. The Z39.50 Retrieval URL 92 The specific syntax for the Retrieval URL is: 94 z39.50r://host[:port] 95 [/database[+database...] 96 [?docid 97 [&esn=elementset] 98 [&rs=recordsyntax[+recordsyntax...]]]] 100 The model is designed for minimal interaction by the user with the Z39.50 101 session to be used as a transparent transfer mechanism if possible. The 102 result of processing this URL should be a Result Set, which the client is 103 responsible for returning to the user's browser in an appropriate form 104 (e.g., HTML). 106 - Host, database, and docid are required. 107 - The docid is server-defined and otherwise opaque. 108 - Port is optional, and defaults to 210. 109 - If element set name (esn) is not specified, it is client's choice. 110 If esn is specified, it should be used within the Search request for 111 the value of small- and/or medium- set-element-set-names. These 112 terms and their use are defined within the Z39.50 Standard [2]. 113 - If record syntax (rs) is not specified, it is client's choice. 114 If one or more record syntaxes are specified, the client should 115 select one (preferably the first in the list that it supports) and 116 use it within the Search request as the value of PreferredRecordSyntax. 117 - The docid is placed into a type-1 query, as the single term, in 118 the general format (tag 45), using the Bib-1 attribute set, with 119 a Use attribute value of docid, and a structure attribute of URX. 120 The docid string is completely opaque to the client. 122 Future extensions to these URLs will be of the form of [&keyword=value]. 124 5. Acknowledgements 126 The Z39.50 Implementors Group contributed the substance of this document. 128 6. References 130 [1] Berners-Lee, T., Masinter, L., McCahill, M. (editors), "Uniform 131 Resource Locators (URL)", soon to be RFC ???, October 1994. 132 ftp://ds.internic.net/internet-drafts/draft-ietf-uri-url-09.txt 134 [2] ANSI/NISO Z39.50-1992, "ANSI Z39.50: Information Retrieval Service 135 and Protocol", Version 2, 1992, 136 ftp://ftp.cni.org/pub/NISO/docs/Z39.50-1992/www/Z39.50.toc.html 137 (also available in hard copy from Omnicom Information Service, 138 115 Park St., SE, Vienna, VA 22180). 140 7. Editors' Addresses 142 Ray Denenberg 143 Library of Congress 144 Collections Services 145 Network Development/MSO 146 Washington DC 20540 147 ray@rden.loc.gov 148 Voice: (202) 707-5795 149 Fax: (202) 707-0115 151 John A. Kunze 152 Information Systems and Technology 153 University of California at Berkeley 154 293 Evans Hall 155 Berkeley, CA 94720 156 jak@violet.berkeley.edu 157 Voice: (510) 642-1530 158 Fax: (510) 643-5385 160 Bradley McLean 161 Gaylord Information Systems 162 7272 Morgan Rd. 163 Liverpool, NY 13088 164 brad@bradpc.gaylord.com 165 Voice: (315) 457-5070 166 Fax: (800) 272-3412