======================================================================== 60 Received: from QUCDN.QueensU.CA by NERVM.NERDC.UFL.EDU (Mailer R2.07) with BSMTP id 9825; Sat, 21 Jul 90 04:40:04 EDT Received: from QUCDN by QUCDN.QueensU.CA (Mailer R2.07+QK) with BSMTP id 8907; Fri, 20 Jul 90 15:26:11 EDT Received: from QueensU.CA by QUCDN.QueensU.CA (Mailer R2.07+QK) with BSMTP id 8906; Fri, 20 Jul 90 15:26:10 EDT Priority: normal P1-Message-Id: **cdn;900720090707 Date: Fri, 20 Jul 90 13:07-0500 X400-Trace: **cdn; arrival Fri, 20 Jul 90 13:07-0500 action Relayed X400-Trace: CA**QueensU.CA; arrival Fri, 20 Jul 90 15:26-0400 action Relayed To: fclmth%nervm.bitnet@qucdn.queensu.CA Subject: Z39.50 - PICS proforma From: Jean-Eudes Beriault Message-Id: <9*beriault@pro.nlc.cdn> Hi Mark At the last Z39.50 Implementors Group meeting in St-Louis, we reviewed the Profile PICS proforma for Z39.50. One of the issue discussed was Section 6.6 - Database Record Syntaxes Supported. The Group agreed that we cannot expect to impose USMARC as the only Database Record Syntax. As an example, another Database Record Syntax which could be used is the Item Identification as defined in the ISI ILL Protocol (ISO 10160 and 10161). The Item Identification includes all the bibliographic information supplied by the requester to describe the required item. It includes one or more of the following components: - item type, whether monograph, or serial or other - held medium type; the format of the item believed to be owned by the responder, i.e. printed, microform, film or videorecording, audiorecording, machine resdable or other - - call number - author - title - sub-title - sponsoring body - place of publication - publisher - series title or number - volume and issue - edition - publication date - publication date of component - author of article - title of article - pagination - national bibliography number - ISBN - ISSN - system number - additional numbers or letters - verification and/or reference source If you have any questions, please let me know. Jean-Eudes Beriault National Library of Canada ======================================================================== 817 Received: from NERVM by NERVM.NERDC.UFL.EDU (Mailer R2.07) with BSMTP id 3832; Fri, 06 Jul 90 16:13:16 EDT Date: Fri, 6 Jul 90 13:11:55 PDT To: "MARK HINNEBUSCH, FCLA" Sender: Distribution List Reply-to: Distribution List From: "Ray Denenberg - LC" To: Z39.50 Implementors Group From: Ray Denenberg Subject: Profile PICS Proforma Version 2 This is the second draft of the Z39.50 Profile PICS Proforma. _______________________________________________________________________ Profile PICS Proforma for Z39.50 Z39.50 Implementors Group June 1990 (SECOND DRAFT) _______________________________________________________________________ CONTENTS 1. Introduction 1.1 Profiles PICS Proformas 1.1.1 OSI Profiles 1.1.2 PICS Proformas 1.2 The Z39.50 Profile PICS Proforma 2. Definitions and Abbreviations 3. References 4. Instructions to Implementors 4.1 Conventions used in the Tables 5. Identification 6. General Features 6.1 Protocol Version 6.2 Query Types 6.3 Attribute Sets 6.4 Abstract Syntaxes Supported 6.4.1 Abstract Syntaxes for APDUs 6.4.2 External Abstract Syntaxes 6.5 Transfer Syntaxes Supported 6.5.1 Transfer Syntaxes for APDUs 6.5.2 External Abstract Syntaxes 6.6 Database Syntaxes Supported 6.7. Origin/Target Capability 7. Origin Implementation 7.1 General 7.1.1 Message Size 7.1.2 Element Set Names 7.2 Supported APDUs 7.3 Supported Parameters 7.3.1 Origin Transmission of Init APDU 7.3.2 Origin Receipt of Init Response APDU 7.3.3 Origin Transmission of Search APDU 7.3.3.1 Result Sets (general) 7.3.3.2 Result Sets in a Query 7.3.4 Origin Receipt of Search Response APDU 7.3.5 Origin Transmission of Present APDU 7.3.6 Origin Receipt of Present Response APDU 7.3.7 Origin Transmission of Delete APDU 7.3.8 Origin Receipt of Delete Response APDU 7.3.9 Origin Receipt of Access-control APDU 7.3.10 Origin Transmission of Access-control-response APDU 7.3.11 Origin Receipt of Resource-control APDU 7.3.12 Origin Transmission of Resource-control-response APDU ______ _________________________________________________________________ 8. Target Implementation 8.1 General 8.1.1 Message Size 8.1.2 Element Set Names 8.2 Supported APDUs 8.3 Supported Parameters 8.3.1 Target Receipt of Init APDU 8.3.2 Target Transmission of Init Response APDU 8.3.3 Target Receipt of Search APDU 8.3.3.1 Maximum Values of Parameters 8.3.3.2 Result Sets (general) 8.3.3.3 Result Sets in a Query 8.3.3.4 Database Names 8.3.4 Target Transmission of Search Response APDU 8.3.4.1 Maximum Values of Parameters 8.3.5 Target Receipt of Present APDU 8.3.6 Target Transmission of Present Response 8.3.7 Target Receipt of Delete APDU 8.3.8 Target Transmission of Delete Response APDU 8.3.9 Target Transmission of Access-control APDU 8.3.10 Target Receipt of Access-control-response APDU 8.3.11 Target Transmission of Resource-control APDU 8.3.12 Target Receipt of Resource-control-response APDU 9. Implementor notes 9.1 Vendor Notes 9.2 Site Specific Information ______________________________ page 1 (top)_ __________________________ 1. Introduction This document contains a Profile PICS Proforma for ANSI Z39.50-1988 [1], hereafter referred to as Z39.50. 1.1 Profiles Proformas 1.1.1 OSI Profiles An OSI application profile designates concrete choices for a specific application environment, where choices are left open in the standards. A profile may also place restrictions on the range of values permitted by the standards. Application Profiles define specifications for OSI layers five through seven, and are developed to increase the probability of interoperability among different implementations (built to the given profile) within a given application environment. Application profiles are developed for specific communities, disciplines, or enterprises. Some examples are manufacturing, office automation, banking, government, and libraries. An application profile for Z39.50 is specified in [2]. 1.1.2 PICS Proformas For many OSI protocol standards (particularly application protocols), a companion standard is developed, called a Protocol Implementation Conformance Statement (PICS) Proforma. A PICS proforma takes the form of a questionnaire to be filled out by suppliers of a product claiming to implement the protocol. The filled-out questionnaire becomes the Protocol Implementation Conformance Statement for the product. The PICS indicates, for example, which capabilities and options have been implemented and what limitations might prevent interworking. It allows a customer of the product to evaluate its conformance to the standard and to determine whether the product meets the customer's requirements. Some protocol standards require that a PICS be provided for a product implementing the protocol, as one of the terms of conformance. A PICS Proforma for Z39.50 is specified in [3]. Some communities annotate the base standard PICS proforma(s) to build one or more components of a profile - the proforma is annotated to indicate what capabilities and options are necessary to conform to the profile. A base proforma which is annotated for a profile is referred to as a "profile PICS proforma". 1.2 The Z39.50 Profile PICS Proforma This document is a Profile PICS Proforma for Z39.50, based on the Z39.50 base PICS proforma. It is intended to provide specification to an implementor who intends to build a product to conform to the Z39.50 application profile. A supplier of such a product should fill out this profile PICS Proforma, which will then become that product's "profile PICS" for the Z39.50 protocol, for the Z39.50 application profile. The profile PICS will then assist a customer of the product to evaluate its conformance to the profile. ______________________________ page 2 (top)____________________ _______ This Z39.50 Profile PICS Proforma was developed by the Z39.50 Implementors Group which at the time of publication of this document was represented by the following organizations. [ list of organizations] 2. Definitions and Abbreviations [to be completed] 3. References [1] ANSI Standard Z39.50-1988. American National Standard for Information Retrieval: Service Definition and Protocol Specification for Library Applications. ISSN: 0276-0762. [2] Application Profile for Z39.50. ZIG 90-1. [3] PICS Proforma for Z39.50. 4. Instructions to Implementors An implementor who wishes to develop a profile PICS for an implementation of Z39.50 should fill out sections 5 and 6, one or both of sections 7 and 8 (see 6.8, "Origin/target Capability"), and optionally, section 9. Sections 7 and 8 pertain to origin and target capabilities respectively. If a product implements both origin and target, then the implementor may choose to represent it as a single product (by providing a single profile PICS) or as two products (by providing separate profile PICS). 4.1 Conventions used in the Tables TABLE HEADINGS "Std" = standard; specifies what is in the Z39.50 standard "Pro" = profile; specifies the requirements of this profile proforma "Impl" = Implementation; to be filled out by the implementor ______________________________ page 3 (top)__________________________ TABLE VALUES Std Column m = mandatory in standard o = optional in standard c = conditional (for example, origin must support receipt of Reference-id if it supports transmission of Reference-id) ns = not specified Pro Column m = mandatory in this profile. Where "m" occurs under "Transmission Supported", transmission of the parameter must be supported. (Note: this does not mean that the parameter must always be transmitted). Where "m" occurs under "Receipt Supported", the parameter must be recognized and processed. mi = (receipt only) mandatory to recognize, but need not be processed, i.e. may be ignored o = optional c = conditional n = (transmission only) not permitted in this profile (applies only to parameters or APDUs which are optional in the standard) na = not applicable to this profile (applies to PDUs not used or parameter within PDUs not used) sp = by special bilateral agreement outside of the standard Impl Column (to be filled in by implementor) y = implemented n = not implemented i = (receipt only) parameter is recognized but not processed (i.e. it is ignored) ______________________________ page 4 (to p)___________________________ 5. Identification Date: __________________ Protocol Implementation Supplier (company, address, etc.): ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ Reference Protocol Identification: ANSI Z39.50-1988 Operating Environment (hardware, oper. system, resource requirements, etc): ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ Implementation Identification: Implementation-id ______________________________________ Implementation-Name ______________________________________ Implementation-Version ______________________________________ ______________________________ page 5 (top)___________________________ 6. General Features 6.1 Protocol Version Std Pro Impl version 1 o o version 2 o m Note: version 2 includes changes to allow interoperation with ISO 10163: Element-set-name in the Search request is replaced by two parameters -- Small-set-element-set-name and Medium-set-element-set-name; the semantics of Medium-set-present-number is changed; the parameter Preferred-record-syntax is included in the Search and Present requests; the abstract syntax description in version 1 is replaced with an ASN.1 description (which includes a description of the diagnostic record and Access Control and Resource Control APDUs); and the default transfer syntax in Appendix A (not part of the standard) of version 1 is not included in version 2. 6.2 Query Types Std Pro Impl Type 0 o sp Type 1 m m Other (please secify) o sp 6.3 Attribute Sets Std Pro Impl bib-1 o m 6.4 Abstract Syntaxes Supported 6.4.1 Abstract Syntax for APDUs Std Pro Impl Z39.50 ASN.1 syntax for APDUs m m 6.4.2 External Abstract Syntaxes Std Pro Impl Z39.50 BibDiagnostic (appendix D) o m (see note) Note: the Z39.50 BiBDiagnostic format is mandatory in this profile PICS proforma. This means that the format must be supported, but not necessarily all of the diagnostic codes listed. List names of external abstract syntaxes supported, for: User-information-field _________________ _________________ _________________ Query (other than type-1) _________________ _________________ _________________ __________________ ____________ page 6 (top)___________________________ 6.5 Transfer Syntaxes Supported 6.5.1 Transfer Syntaxes for APDUs Std Pro Impl Z39.50 ASN.1 BER encoding m m for APDUS Other APDU encodings o n (please specify) 6.5.2 External Transfer Syntaxes Std Pro Impl BER for Z39.50 BibDiagnostic o m List names of external transfer syntaxes supported, for: User-information-field _________________ _________________ _________________ Query (other than type-1) _________________ _________________ _________________ 6.6 Database Record Syntaxes Supported Std Pro Impl USMARC o o Others (please specify) __________________ __________________ __________________ 6.7 Origin/Target Capability Origin capability implemented? (Y/N) _____ (if "Y", fill out section 7) Target capability implemented? (Y/N) _____ (if "Y", fill out section 8) ______________________________ page 7 (top)___________________________ 7. Origin Implementation 7.1 General 7.1.1 Message Size Std Pro Impl Maximum message size supported on ns ns received Search and Present response APDUs Maximum record size supported on ns ns received Search and Present response APDUs Maximum query size transmitted in ns ns Search APDUs 7.1.2 Element Set Names Std Pro Impl Simple form of o o Element-set-names parameters transmitted Complex form transmitted o o Note:In the simple form the parameter consist of a single element set name with no database specified. In the complex form the parameter is a set of one or more pairs of a database name and associated element set name. Element set name values supported: Std Pro Impl full ("F") o o List others: _________________ _________________ _________________ 7.2 Supported APDUs Outgoing APDUs Std Pro Impl Incoming APDUs Std Pro Impl Init m m Init-resp m m Search m m Search-resp m m Present m m Present-resp m m Delete o o Delete-resp o c Access-Cntrl-Resp o c Access-Cntrl o o Rsrc-Cntrl-Resp o c Rsrc-Cntrl o o ______________________________ page 8 (top)___________________________ 7.3 Supported Parameters 7.3.1 Origin Transmission of Init APDU Parameter Std Pro Impl ReferenceId o o ProtVers m m Options m m PrefSize m m MaxSize m m Id/auth o m ImplId o o ImplName o o ImplVers o o UserInfo o o List usage, if any, of ________________________________ User-information-field ________________________________ ________________________________ 7.3.2 Origin Receipt of Init Response APDU Parameter Std Pro Impl ReferenceId c c ProtVers m m Options m m PrefMsgSize m m MaxRecSize m m Result m m ImplId m mi ImplName m mi ImplVers m mi UserInfo m mi List constraints, if any, on ________________________________ User-information-field ________________________________ ________________________________ 7.3.3 Origin Transmission of Search APDU Parameter Std Pro Impl ReferenceId o o SmallUpBnd m m LargeLowBnd m m MedNumber m m ReplaceInd m m ResultSetName m m DatabaseNames m m SmSetElemSetNms o o MedStElemSetNms o o PrefSyntax o o Query m m ______________________________ page 9 (top)_ __________________________ 7.3.3.1 Result Sets (general) Std Pro Impl "default" resultSetName xmitted m m named resultSetName xmitted o o 7.3.3.2 Result Sets in a Query To what extent may result sets be specified as operands in a query; i.e. in place of an attribute-term combination: Std Pro Impl default result set transmitted o m as first operand with operator "AND" (i.e. qualification query) Default result set transmitted o o in a query, other than for Qualification named result sets transmitted o o in a query result sets transmitted as first o o operand in a query may be any operand o o with which operators in general may result sets be used as operands AND o o OR o o AND-NOT o o _______________________ _______ page 10 (top)___________________________ 7.3.4 Origin Receipt of Search Response APDU Parameter Std Pro Impl ReferenceId c c ResultCount m m No.recordsRet m m NextRsltSetPos m m SearchStatus m m ResultSetStat m m PresentStat m m Db/diagRecs m m 7.3.5 Origin Transmission of Present APDU Parameter Std Pro Impl ReferenceId o o ResultSetId m m RsltSetStrtPos m m NumRecsRqstd m m ElemSetNames o o PrefRecSyntax o o 7.3.6 Origin Receipt of Present Response APDU Parameter Std Pro Impl ReferenceId c c NumRecsRetrnd m m NextRsltSetPos m m PresentStatus m m DbDiagRecords m m 7.3.7 Origin Transmission of Delete APDU Parameter Std Pro Impl ReferenceId o o DeleteOperation m m ResultSetId o o ______________________________ page 11 (top)___________________________ 7.3.8 Origin Receipt of Delete Response APDU Parameter Std Pro Impl ReferenceId c c ResultSetId m m DeleteStatus m m NumNotDeleted m m BulkStatuses m m DeleteMsg m m 7.3.9 Origin Receipt of Access-control APDU Parameter Std Pro Impl ReferenceId c c SecurityChlng m m 7.3.10 Origin Transmission of Access-control-response APDU Parameter Std Pro Impl ReferenceId c c SecrtyChlngRsp m m 7.3.11 Origin Receipt of Resource-control APDU Parameter Std Pro Impl ReferenceId c c SuspendedFlag m m ResourceRpt m m PrtlRsltsAvl m m 7.3.12 Origin Transmission of Resource-control-response APDU Parameter Std Pro Impl ReferenceId c c ContinueFlag m m RsltSetWanted c c ______________________________ page 12 (to p)___________________________ 8. Target Implementation 8.1 General 8.1.1 Message Size Std Pro Impl Minimum message size supported on ns ns transmitted Search and Present Response APDUs Minimum record size supported on ns ns transmitted Search and Present Response APDUs Maximum query size supported ns ns in received search APDUs 8.1.2 Element Set Names Std Pro Impl Simple form of ElementSetNames o m parameters supported Complex form supported o o Element set name values supported: Std Pro Impl full ("F") m m List others: ___________________ ___________________ ___________________ 8.2 Supported APDUs Incoming APDUs Std Pro Impl Outgoing APDUs Std Pro Impl Init m m Init-resp m m Search m m Search-resp m m Present m m Present-resp m m Delete o o Delete-resp c c Access-Cntrl-Resp c c Access-Cntrl o o Rsrc-Cntrl-Resp c c Rsrc-Cntrl o o ______________________________ page 13 (top)___________________________ 8.3 Supported Parameters 8.3.1 Target Receipt of Init APDU Parameter Std Pro Impl ReferenceId m m ProtVers m m Options m m PrefSize m m MaxSize m m Id/auth m mi ImplId m mi ImplName m mi ImplVers m mi UserInfo m mi List constraints, if any, on ________________________________ User-information-field ________________________________ ________________________________ 8.3.2 Target Transmission of Init Response APDU Parameter Std Pro Impl ReferenceId m m ProtVers m m Options m m PrefMsgSize m m MaxRecSize m m Result m m ImplId o o ImplName o o ImplVers o o UserInfo o o List usage, if any, of ________________________________ User-information-field ________________________________ ________________________________ 8.3.3 Target Receipt of Search APDU Parameter Std Pro Impl ReferenceId m m SmallUpBnd m m LargeLowBnd m m MedNumber m m ReplaceInd m m ResultSetName m m DatabaseNames m m SmSetElemSetNms m m MedStElemSetNms m mi PrefSyntax m mi Query m m ______________________________ page 14 (top) ___________________________ 8.3.3.1 Maximum values of parameters Std Pro Impl SmallSetUpperBound ns ns LargeSetLowerBound ns ns MediumSetPresentNumber ns ns 8.3.3.2 Result Sets (general) Std Pro Impl "default" resultSetName supprtd m m named resultSetNames supported o o max concurrent result sets ns ns result sets not unilaterally o o deleted 8.3.3.3 Result Sets in a Query To what extent may result sets be specified as operands in a query; i.e. in place of an attribute-term combination: Std Pro Impl default result set supported o m as first operand with operator "AND" (i.e. qualification query) Default result set supported o o in a query, other than for Qualification named result sets supported o o in a query result sets supported as first o o operand in a query may be any operand o o with which operators in general may result sets be used as operands AND o o OR o o AND-NOT o o 8.3.3.4 Database Names Std Pro Impl Maximum number of database at least 1 at least 1 names accepted in parameter DatabaseNames ______________________________ page 15 ( top)___________________________ 8.3.4 Target Transmission of Search Response APDU Parameter Std Pro Impl ReferenceId m m ResultCount m m No.recordsRet m m NextRsltSetPos m m SearchStatus m m ResultSetStatus m m PresentStatus m m Db/diagRecs m m 8.3.4.1 Maximum Values of Parameters Std Pro Impl ResultCount ns ns NumberOfRecordsReturned ns ns 8.3.5 Target Receipt of Present APDU Parameter Std Pro Impl ReferenceId m m ResultSetId m m RsltSetStrtPos. m m NumRecsRqstd m m ElemSetName m m PrefRecSyntax m mi 8.3.6 Target Transmission of Present Response APDU Parameter Std Pro Impl ReferenceId m m NumRecsRetrnd m m NextRsltSetPos m m PresentStatus m m DbDiagRecords m m 8.3.7 Target Receipt of Delete APDU Parameter Std Pro Impl ReferenceId m m DeleteOperation m m ResultSetId m m ______________________________ page 16 (top)___________________________ 8.3.8 Target Transmission of Delete Response APDU Parameter Std Pro Impl ReferenceId m m ResultSetId m m DeleteStatus m m NumNotDeleted o o BulkStatuses o o DeleteMsg o o 8.3.9 Target Transmission of Access-control APDU Parameter Std Pro Impl ReferenceId m m SecurityChlng m m 8.3.10 Target Receipt of Access-control-response APDU Parameter Std Pro Impl ReferenceId m m SecrtyChlngRsp m m 8.3.11 Target Transmission of Resource-control APDU Parameter Std Pro Impl ReferenceId m m SuspendedFlag m m ResourceReport o o PrtlRsltsAvlbl c c 8.3.12 Target Receipt of Resource-control-response APDU Parameter Std Pro Impl ReferenceId m m ContinueFlag m m RsltSetWanted c c ______________________________ page 17 (top)___________________________ 9. Implementor notes 9.1 Vendor Notes _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ 9.2 Site Specific Notes _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________ _________________________________________________________________________