[ASCII edition of Z39.50 not guaranteed to be accurate, and guaranteed NOT to be pretty. Z39.50 is provided in alternative forms, any of which would be preferable] Appendix 1 OID: Z39.50 Object Identifiers (Normative) OID.1 Object Identifier Assigned to This Standard ANSI has assigned the following object identifier to this standard, ANSI- standard-Z39.50: {iso (1) member-body (2) US (840) ANSI-standard-Z39.50 (10003)} Note: This OID was originally assigned to Z39.50-1992; it applies also to Z39.50-1995. OID.2 Object Classes Assigned by This Standard This standard assigns the following values for object classes, at the level immediately subordinate to ANSI-standard-Z39.50: 1 = application context definitions 2 = abstract syntax definition for APDUs 3 = attribute set definitions 4 = diagnostic definitions 5 = record syntax definitions 6 = transfer syntax definitions 7 = resource report format definitions 8 = access control format definitions 9 = extended services definitions 10 = user information format definitions 11 = element specification format definitions 12 = variant set definitions 13 = database schema definitions 14 = tag set definitions The following ASN.1 module establishes shorthand notation for the Z39.50 object identifier, and for the object classes. The notation is used in appendices that follow. ANSI-Z39-50-ObjectIdentifier DEFINITIONS ::= BEGIN Z39-50 OBJECT IDENTIFIER ::= { iso (1) member-body (2) US (840) ANSI-standard-Z39.50 (10003)} Z39-50-context OBJECT IDENTIFIER ::= {Z39-50 1} -- See Appendix CTX. Z39-50-APDU OBJECT IDENTIFIER ::= {Z39-50 2} -- See OID.3.1. Z39-50-attributeSet OBJECT IDENTIFIER ::= {Z39-50 3} -- See Appendix ATR. Z39-50-diagnostic OBJECT IDENTIFIER ::= {Z39-50 4} -- See Appendix ERR. Z39-50-recordSyntax OBJECT IDENTIFIER ::= {Z39-50 5} -- See Appendix REC. Z39-50-transferSyntax OBJECT IDENTIFIER ::= {Z39-50 6} -- See note below. Z39-50-resourceReport OBJECT IDENTIFIER ::= {Z39-50 7} -- See Appendix RSC. Z39-50-accessControl OBJECT IDENTIFIER ::= {Z39-50 8} -- See Appendix ACC. Z39-50-extendedService OBJECT IDENTIFIER ::= {Z39-50 9} -- See Appendix EXT. Z39-50-userInfoFormat OBJECT IDENTIFIER ::= {Z39-50 10} -- See Appendix USR. Z39-50-elementSpec OBJECT IDENTIFIER ::= {Z39-50 11} -- See Appendix ESP. Z39-50-variantSet OBJECT IDENTIFIER ::= {Z39-50 12} -- See Appendix VAR. Z39-50-schema OBJECT IDENTIFIER ::= {Z39-50 13} -- See Appendix TAG. Z39-50-tagSet OBJECT IDENTIFIER ::= {Z39-50 14} -- See Appendix TAG. END No object identifier is assigned by this standard for any transfer syntax. For the purpose of presentation context negotiation for an abstract syntax (including the abstract syntax for the APDUs, defined in 4.1), the abstract syntax is paired with a transfer syntax. This pairing is represented by a pair of object identifiers, one for the abstract-syntax (e.g. Z39.50-APDU) and one for the encoding rules. For abstract syntaxes described using ASN.1 (e.g. Z39.50-APDU), a set of basic encoding rules are specified by "ASN.1 Basic Encoding Rules," ISO 8825, identified by the following object identifier: { joint-iso-ccitt asn1 (1) basic-encoding (1) } OID.3 Object Identifiers Assigned by This Standard All object identifiers assigned by this standard (with the exception of the OID for Z39.50 APDUs, assigned in OID.3.1) are explicitly assigned in the appendices that follow. OID.3.1 Object Identifiers for Z39.50 APDUs This standard assigns the following object identifier for the ASN.1 definition of APDUs in 4.1. Z39-50-APDU {Z39-50-APDU 1} Note: the same OID is used for APDUs both for Z39.50-1992 and Z39.50-1995, because of the interworking capability between the two versions. OID.4 Object Identifiers Used by This Standard Z39.50 object identifiers are either public or locally defined. Public Z39.50 object identifiers are officially registered, by this standard or by the Z39.50 maintenance agency (see OID.5). Locally defined Z39.50 object identifiers are registered by a registered Z39.50 implementor (see OID.6 and OID.7). OID.5 Object Identifiers Assigned by the Z39.50 Maintenance Agency Additional object identifiers (official Z39.50 object identifiers not registered by this standard) may be assigned by the Z39.50 Maintenance Agency (see note), of the form: {Z39-50 n m} where {z39-50 n} is an object class defined in OID.2, or is an additional object class defined by the maintenance agency. Note: At the time of approval of this standard, the Z39.50 Maintenance Agency is the Library of Congress. OID.6 Locally Registered Objects Locally registered objects are of the form: {Z39-50 n 1000 p m} where {z39-50 n} is as described in OID.5, and 'p' is the OID index of a registered Z39.50 Implementor (contact the Z39.50 Maintenance Agency for procedures for registration of an implementor). A locally registered object may be published or private. Local, published objects are those whose definitions are coordinated with and published by the Z39.50 Maintenance Agency. Local, private objects are those whose definitions are not published by the Z39.50 Maintenance Agency. OID.7 Experimental Objects Experimental objects are of the form: {Z39-50 n 2000 p m} where {z39-50 n} is as described in OID.5, and 'p' is the OID index of a registered Z39.50 Implementor. Appendix 2: CTX: Application Context basic-Z39.50- ac (Normative) This standard defines and registers the application context basic-Z39.50-ac. The object identifier for application context basic-Z39.50-ac is: { Z39-50-context 1 } Definition of application context basic-Z39.50-ac ANSI-standard-Z39.50 application context basic-Z39.50-ac supports an application-entity that contains only the following two application service elements (ASEs): a) the association control service element (ACSE, ISO 8650), and b) the Z39.50 service element. Z39.50 and ACSE are used according to the procedures in section 4.2.1. The presentation services required are those contained in the presentation kernel functional unit and the session duplex functional unit. All Information Retrieval protocol data units will be mapped onto the P-Data service. In the event of protocol errors, the system detecting the error shall abort the association. Only the origin may invoke the A-RELEASE service (to initiate orderly release of an A-association). Appendix 3 ATR: Attribute Sets (Normative) This standard registers the attribute sets listed below, and assigns the following object identifiers: Bib-1 {Z39-50-attributeSet 1} (See ATR.1) Exp-1 {Z39-50-attributeSet 2} (See ATR.2) Ext-1 {Z39-50-attributeSet 3} (See ATR.3) CCL-1 {Z39-50-attributeSet 4} GILS {Z39-50-attributeSet 5} STAS {Z39-50-attributeSet 6} Each attribute set defines a set of types and for each type a set of values. An attribute list (see AttributeList in the ASN.1 for APDUs, 4.1), constructed from an attribute set definition, is a list of attribute pairs. An attribute pair (AttributeElement in the ASN.1 for APDUs) consists of an attribute type and a value list (attributeValue within AttributeElement), where each value in the list is defined for that type. When version 2 is in force, each value list is a single value and is an integer. When version 3 is in force, attributeValue (within AttributeElement) may select 'complex', allowing the value list to include multiple values (each may be integer or string) and also to specify a 'semanticAction', indicating how the target is to treat the multiple attributes. When an attribute list contains any attribute pair where attributeValue selects 'complex', there must not be any attribute type within the attribute list for which there is more than a single attribute pair. ATR.1 Attribute Set bib-1 This section defines the attribute set bib-1. ATR.1.1 Bib-1 Types and Values This section lists the attribute types and values for attribute-set bib-1 (see Tables A-3-1 through A-3-6). Attribute Attribute Type Value Type Value Use 1 Structure 4 Relation 2 Truncation 5 Position 3 Completeness 6 Table A-3-1: Bib-1 Use Attributes Use Value Personal name 1 Corporate name 2 Conference name 3 Title 4 Title series 5 Title uniform 6 ISBN 7 ISSN 8 LC card number 9 BNB card no. 10 BGF number 11 Local number 12 Dewey classification 13 UDC classification 14 Bliss classification 15 LC call number 16 NLM call number 17 NAL call number 18 MOS call number 19 Local classification 20 Use Value Subject heading 21 Subject Rameau 22 BDI index subject 23 INSPEC subject 24 MESH subject 25 PA subject 26 LC subject heading 27 RVM subject heading 28 Local subject index 29 Date 30 Date of publication 31 Date of acquisition 32 Title key 33 Title collective 34 Title parallel 35 Title cover 36 Title added title page 37 Title caption 38 Title running 39 Title spine 40 Use Value Title other variant 41 Title former 42 Title abbreviated 43 Title expanded 44 Subject precis 45 Subject rswk 46 Subject subdivision 47 No. nat'l biblio. 48 No. legal deposit 49 No. govt pub. 50 No. music publisher 51 Number db 52 Number local call 53 Code--language 54 Code--geographic area 55 Code--institution 56 Name and title 57 Name geographic 58 Place publication 59 CODEN 60 Microform generation 61 Abstract 62 Note 63 Author-title 1000 Record type 1001 Name 1002 Author 1003 Author-name personal 1004 Author-name corporate 1005 Author-name conference 1006 Identifier--standard 1007 Subject--LC children's 1008 Subject name -- personal 1009 Body of text 1010 Date/time added to db 1011 Date/time last modified 1012 Authority/format id 1013 Concept-text 1014 Concept-reference 1015 Any 1016 Server-choice 1017 Publisher 1018 Record-source 1019 Editor 1020 Bib-level 1021 Geographic-class 1022 Use Value Indexed-by 1023 Map-scale 1024 Music-key 1025 Related-periodical 1026 Report-number 1027 Stock-number 1028 Thematic-number 1030 Material-type 1031 Doc-id 1032 Host-item 1033 Content-type 1034 Anywhere 1035 Author-Title-Subject 1036 Table A-3-2: Bib-1 Relation Attributes Relation Value less than 1 less than or equal 2 equal 3 Relation Value greater or equal 4 greater than 5 not equal 6 Relation Value phonetic 100 stem 101 relevance 102 AlwaysMatches 103 Table A-3-3: Bib-1 Position Attributes Position Value first in field 1 Position Value first in subfield 2 Position Value any position in field 3 Table A-3-4: Structure Attribute Structure Value phrase 1 word 2 key 3 year 4 date (normalized) 5 Structure Value word list 6 date (un-normalized) 100 name (normalized) 101 name (un-normalized) 102 structure 103 Structure Value urx 104 free-form-text 105 document-text 106 local number 107 string 108 numeric string 109 Table A-3-5: Bib-1 Truncation Attributes Truncation Value right Truncation 1 left truncation 2 left and right 3 Truncation Value do not truncate 100 process # in search term 101 Truncation Value regExpr-1 102 regExpr-2 103 Table A-3-6: Bib-1 Completeness Attributes Completeness Value incomplete subfield 1 Completeness Value complete subfield 2 Completeness Value complete field 3 ATR.1.2 Bib-1 Attribute Combinations If a target does not support a given attribute list, it should fail the search and supply an appropriate diagnostic. A given attribute type may appear zero times, one time, or more than one time, in an attribute list. - If an attribute type does not occur in an attribute list, then (in the absence of any prior understanding, either outside of the standard or via the Explain facility) the origin should not expect any particular default target behavior. - If an attribute type occurs exactly once in an attribute list, then the attribute value specifies the preferred target behavior with respect to that attribute type. - It is recommended that an attribute type not occur more than once in an attribute list, unless an associated "semantic action" is included (i.e. attributeValue selects 'complex'). When attributeValue selects 'complex', 'semanticAction' may be included. SemanticAction is a sequence of integers; for bib-1, it is either a single integer or a sequence of two integers. For the first integer in the sequence, values are: 1 May not substitute another attribute. If none in the list is supported, fail the search. 2 May substitute another attribute, but only if none in the list is supported. 3 May substitute another attribute at target discretion (even if one or more in the list is supported). The second integer in the sequence is to be supplied if and only if there are multiple attributes in the list. Values are: 1 Select the first supported attribute in the list. 2 Select the best attribute in the list. ATR.2 Attribute Set exp-1 This section defines the attribute-set exp-1, for use with an Explain database. The attribute set exp-1 defines a single attribute type, 'Use'. In addition, this attribute set definition imports non-Use bib-1 attributes, i.e. those of type Relation, Position, Structure, Truncation, and Completeness (see tables A-3-2 through A-3-6). The types and values defined within the bib-1 attribute set for these attributes may be used within the exp-1 attribute set, using the object identifier for this attribute set. It is recommended that a target supporting the Explain facility support the Relation attribute 'equal', Position attribute 'any' position in field', and Structure attribute 'key'. Note: If the target supports searching based on date ranges (e.g. to limit a search to records created before or after a particular date or between two dates), the target should also support one or more of the following relation attributes: 'less than', 'less than or equal', 'greater than', and 'greater or equal'. Table A-3-7: Exp-1 Use Attributes Use Value ExplainCategory 1 HumanStringLanguage 2 DatabaseName 3 TargetName 4 AttributeSetOID 5 RecordSyntaxOID 6 TagSetOID 7 ExtendedServiceOID 8 DateAdded 9 Use Value DateChanged 10 DateExpires 11 ElementSetName 12 ProcessingContext 13 ProcessingName 14 TermListName 15 SchemaOID 16 Producer 17 Supplier 18 Use Value Availability 19 Proprietary 20 UserFee 21 VariantSetOID 22 UnitSystem 23 Keyword 25 ExplainDatabase 26 ProcessingOID 27 Notes: (1) The search terms for Use attribute ExplainCategory are listed in table A-3-8. (2) The search term when the Use attribute is HumanStringLanguage is the three-character language code from ANSI/NISO Z39.53-1994 -- Codes for the Representation of Languages for Information Interchange. (3) The search terms when the Use attribute is ProcessingContext are listed in table A-3-9. (4) Where the search term is an object identifier (where the name of the Use attribute ends with "OID"): for version 2, it is recommended that the term be a character string representing a sequence of integers (each represented by a character string) separated by periods. For version 3, it is recommended that the term be represented as ASN.1 type OBJECT IDENTIFIER. (5) Use attribute Keyword is used when searching for DatabaseInfo records (i.e. in combination with an operand where Use is ExplainCategory and term is DatabaseInfo). Its use is to search in the keyword element, for terms that match one of the query terms. (6) Use attribute ExplainDatabase is used when searching for DatabaseInfo records (i.e. in combination with an operand where Use is ExplainCategory and term is DatabaseInfo). The term should be NULL, for version 3, or otherwise ignored by the target. The Relation attribute either should be omitted or should be AlwaysMatches. Table A-3-8: Search terms associated with use attribute ExplainCategory TargetInfo DatabaseInfo SchemaInfo TagSetInfo RecordSyntaxInfo AttributeSetInfo TermListInfo extendedServicesInfo AttributeDetails TermListDetails ElementSetDetails RetrievalRecordDetails SortDetails Processing CategoryList VariantSetInfo UnitInfo Table A-3-9: Search terms associated with use attribute ProcessingContext Access Search Retrieval RecordPresentation RecordHandling ATR.3 Attribute Set ext-1 This section defines the attribute-set ext-1, for use with an Extended Services database (see Tables A-3-10 and A-3-11). Two types are defined: Attribute Type Value Use 1 Permissions 2 Additional attributes (types and/or values) may be defined within a specific Extended Service definition. The attribute set id to be used to identify those attributes is the ObjectIdentifier that identifies the specific Extended Service. Table A-3-10: Ext-1 Use Attributes Use Value UserId 1 PackageName 2 CreationDatetime 3 Use Value TaskStatus 4 PackageType 5 Use Value RetentionTime 6 TargetReference 7 Table A-3-11: Ext-1 Permission Attributes Permission Value Delete 1 Modify 2 Permission Value ModifyPermissions 3 Present 4 Permission Value Invoke 5 Any 6Note: The Permission attribute is for use only when the value of the Use attribute is UserId, in which case the purpose is to search for task packages for which the specified user has the specified permission. Appendix 4 ERR: Error Diagnostics (Normative) This standard defines and registers the diagnostic set bib-1 and the diagnostic format diag-1. The following object identifiers are assigned: bib-1 {Z39-50-diagnostic 1} (See ERR.1) diag-1 {Z39-50-diagnostic 2} (See ERR.2) When version 2 is in force, a diagnostic record must conform to the following format: DefaultDiagFormat ::= SEQUENCE{ diagnosticSetId OBJECT IDENTIFIER, condition INTEGER, addinfo VisibleString} The diagnostic record includes an integer corresponding to a condition or error, and an (object) identifier of the diagnostic set definition that lists the condition corresponding to that integer. When version 3 is in force, a diagnostic record may assume the form above, or alternatively, may be defined as EXTERNAL, identified by an OBJECT IDENTIFIER (which identifies the diagnostic format, rather than the diagnostic set). Bib-1 is a diagnostic set. It was originally defined and registered in Z39.50-1992. This standard includes an extended definition; the conditions listed below for bib-1 include all those that were listed in the Z39.50-1992 bib-1 definition, as well as several additional diagnostics that have been added. (In particular, several of the conditions described by diag-1 that can be expressed by the above format have been added to bib-1.) Diag-1 is a diagnostic format. It includes several structures for diagnostic information, each tailored to the error information being described. It also includes a single structure through which a diagnostic from a diagnostic set (e.g. bib-1) can be referenced. Diag-1 allows several diagnostic conditions within a single diagnostic record, to describe multiple errors pertaining to the same record or operation. In particular, diagnostics from different diagnostic sets may be included within the same diag-1 diagnostic record. ERR.1 Diagnostic Set Bib-1 Table A-4-1 below is for use when DiagnosticSetId (within DefaultDiagFormat) equals the object identifier for diagnostic set bib-1, in which case, Condition takes values from the "Code" column below. This table may also be used by diagnostic format diag-1 when defaultDiagRec is selected for "diagnostic," and DiagnosticSetId equals the object identifier for this diagnostic set. In that case, the values of "code" and "addinfo" are taken from this table. AddInfo is ASN.1 type VisibleString. However, for several of the diagnostics below, AddInfo is used to express the value of a parameter that has an ASN.1 type other than VisibleString. Where Addinfo is used to express a numeric value, it should be a character string representation of that value. Where Addinfo is used to express an object identifier, it should take the form of a sequence of integers (each represented by a character string) separated by periods. Table A-4-1: Diagnostic Conditions code Meaning Addinfo 1 permanent system error (unspecified) 2 temporary system error (unspecified) 3 unsupported search (unspecified) 4 Terms only exclusion (stop) words (unspecified) 5 Too many argument words (unspecified) 6 Too many boolean operators (unspecified) 7 Too many truncated words (unspecified) 8 Too many incomplete subfields (unspecified) 9 Truncated words too short (unspecified) 10 Invalid format for record number (search term) (unspecified) 11 Too many characters in search statement (unspecified) 12 Too many records retrieved (unspecified) 13 Present request out-of-range (unspecified) 14 System error in presenting records (unspecified) 15 Record not authorized to be sent intersystem (unspecified) 16 Record exceeds Preferred-message-size (unspecified) 17 Record exceeds Exceptional-record-size (unspecified) 18 Result set not supported as a search term (unspecified) 19 Only single result set as search term supported (unspecified) 20 Only ANDing of a single result set as search term (unspecified) 21 Result set exists and replace indicator off (unspecified) 22 Result set naming not supported (unspecified) 23 Specified combination of databases not supported (unspecified) 24 Element set names not supported (unspecified) 25 Specified element set name not valid for specified database (unspecified) 26 Only generic form of element set name supported (unspecified) 27 Result set no longer exists - unilaterally deleted by target (unspecified) 28 Result set is in use (unspecified) 29 One of the specified databases is locked (unspecified) 30 Specified result set does not exist (unspecified) 31 Resources exhausted - no results available (unspecified) 32 Resources exhausted - unpredictable partial results available (unspecified) 33 Resources exhausted - valid subset of results available (unspecified) 100 (unspecified) error (unspecified) 101 Access-control failure (unspecified) 102 Challenge required, could not be issued - operation terminated (unspecified) 103 Challenge required, could not be issued - record not included (unspecified) 104 Challenge failed - record not included (unspecified) 105 Terminated at origin request (unspecified) 106 No abstract syntaxes agreed to for this record (unspecified) 107 Query type not supported (unspecified) 108 Malformed query (unspecified) 109 Database unavailable database name 110 Operator unsupported operator 111 Too many databases specified maximum 112 Too many result sets created maximum 113 Unsupported attribute type type 114 Unsupported Use attribute value 115 Unsupported term value for Use attribute term 116 Use attribute required but not supplied (unspecified) 117 Unsupported Relation attribute value 118 Unsupported Structure attribute value 119 Unsupported Position attribute value 120 Unsupported Truncation attribute value 121 Unsupported Attribute Set oid 122 Unsupported Completeness attribute value 123 Unsupported attribute combination (unspecified) 124 Unsupported coded value for term value 125 Malformed search term (unspecified) 126 Illegal term value for attribute term 127 Unparsable format for un-normalized value value 128 Illegal result set name name 129 Proximity search of sets not supported (unspecified) 130 Illegal result set in proximity search result set name 131 Unsupported proximity relation value 132 Unsupported proximity unit code value 201 Proximity not supported with this attribute combination attribute list 202 Unsupported distance for proximity distance 203 Ordered flag not supported for proximity (unspecified) 205 Only zero step size supported for Scan (unspecified) 206 Specified step size not supported for Scan step size 207 Cannot sort according to sequence sequence 208 No result set name supplied on Sort (unspecified) 209 Generic sort not supported (database-specific sort only supported) (unspecified) 210 Database specific sort not supported (unspecified) 211 Too many sort keys number 212 Duplicate sort keys key 213 Unsupported missing data action value 214 Illegal sort relation relation 215 Illegal case value value 216 Illegal missing data action value 217 Segmentation: Cannot guarantee records will fit in specified segments (unspecified) 218 ES: Package name already in use name 219 ES: no such package, on modify/delete name 220 ES: quota exceeded (unspecified) 221 ES: extended service type not supported type 222 ES: permission denied on ES - id not authorized (unspecified) 223 ES: permission denied on ES - cannot modify or delete (unspecified) 224 ES: immediate execution failed (unspecified) 225 ES: immediate execution not supported for this service (unspecified) 226 ES: immediate execution not supported for these parameters (unspecified) 227 No data available in requested record syntax (unspecified) 228 Scan: malformed scan (unspecified) 229 Term type not supported type 230 Sort: too many input results max 231 Sort: incompatible record formats (unspecified) 232 Scan: term list not supported alternative term list 233 Scan: unsupported value of position-in-response value 234 Too many index terms processed number of terms 235 Database does not exist database name 236 Access to specified database denied database name 237 Sort: illegal sort (unspecified) 238 Record not available in requested syntax alternative suggested syntax(es) 239 Record syntax not supported syntax 240 Scan: Resources exhausted looking for satisfying terms (unspecified) 241 Scan: Beginning or end of term list (unspecified) 242 Segmentation: max-segment-size too small to segment record smallest acceptable size 243 Present: additional-ranges parameter not supported (unspecified) 244 Present: comp-spec parameter not supported (unspecified) 245 Type-1 query: restriction ('resultAttr') operand not supported (unspecified) 246 Type-1 query: 'complex' attributeValue not supported (unspecified) 247 Type-1 query: 'attributeSet' as part of AttributeElement not supported (unspecified) ERR.2 Diagnostic Format Diag-1 This section defines the diagnostic format diag-1. [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.] Appendix 5 REC: Record Syntaxes (Normative) This standard registers the following object identifiers for record syntaxes: Object identifiers assigned for bibliographic syntaxes, not described via ASN.1: Unimarc {Z39-50-recordSyntax 1 } Intermarc {Z39-50-recordSyntax 2 } CCF {Z39-50-recordSyntax 3 } USmarc {Z39-50-recordSyntax 10 } UKmarc {Z39-50-recordSyntax 11 } Normarc {Z39-50-recordSyntax 12 } Librismarc {Z39-50-recordSyntax 13 } Danmarc {Z39-50-recordSyntax 14 } Finmarc {Z39-50-recordSyntax 15 } MAB {Z39-50-recordSyntax 16 } Canmarc {Z39-50-recordSyntax 17 } SBN {Z39-50-recordSyntax 18 } Picamarc {Z39-50-recordSyntax 19 } Ausmarc {Z39-50-recordSyntax 20 } Ibermarc {Z39-50-recordSyntax 21 } Note: The following transfer syntax (see ISO 2709) may be used in conjunction with the above bibliographic definitions: ISO2709 {iso standard 2709 transfer-syntax (1) character-encoding (1)} When presentation context negotiation is used, the above syntaxes may be paired with the transfer syntax identified by the object identifier ISO2709 for the transfer-syntax for bibliographic records defined in ISO 2709. When presentation context negotiation is not used, the above record syntaxes are assumed to be paired with ISO2709. Object identifiers assigned for syntaxes which are described via ASN.1: Explain {Z39-50-recordSyntax 100} (See REC.1) SUTRS {Z39-50-recordSyntax 101} (See REC.2) OPAC {Z39-50-recordSyntax 102} (See REC.3) Summary {Z39-50-recordSyntax 103} (See REC.4) GRS-1 {Z39-50-recordSyntax 105} (See REC.5) Extended {Z39-50-recordSyntax 106} (See REC.6) Services Note: The following transfer syntax (see ISO 8825) may be used in conjunction with these definitions: ISO8825 ::= OBJECT IDENTIFIER {joint-iso-ccitt (2) basic-encoding (1)} When presentation context negotiation is used, these syntaxes may be paired with the transfer syntax identified by the object identifier ISO8825 for the transfer-syntax defined in ISO 8825. When presentation context negotiation is not used, the above record syntaxes are assumed to be paired with ISO8825. REC.1 Explain Record Syntax [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.] REC.2 Simple Unstructured Text Record Syntax The Simple Unstructured Text Record Syntax (SUTRS) is intended to be used as a record syntax in a Search or Present response, to present textual data so that the origin may display them with little or no analysis and manipulation. A SUTRS record is unstructured; the text of a SUTRS record might represent individual elements, but the elements are not explicitly identified by the syntax. The convention prescribed by the SUTRS definition is to use a delimiter within the text to indicate the end of a line of text. The prescribed line terminator is ASCII LF (X'0A'). Thus a SUTRS record consists simply of a string of textual data. This definition recommends that the maximum line length be 72 characters unless an alternative maximum is requested, for example via a variantRequest. This is not an absolute maximum, but it is recommended that targets make a best effort to limit lines to this length. [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.] REC.3 OPAC Record Syntax [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.] REC.4 Summary Record Syntax [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.] REC.5 Generic Record Syntax 1 [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.] REC.6 Record Syntax For Extended Services Task Package [ASN.1 not provided in these txt files. The consolidated ASN.1 is provided in a single file, available vial in wordPerfect, postScript, and ascii: ftp.loc.gov directory pub/z3950 files asn1.wp, asn1.ps and asn1.txt.]