Z39.50 International Standard Maintenance Agency - Library of Congress, Network Development and MARC Standards Office

Z39.50 Text
Part 12

Appendices 1 (OID):Object Identifiers,
and 2 (CTX): Application Contexts

[Table of Contents | Previous Section | Next Section]

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 ::=

{ iso (1) member-body (2) US (840) ANSI-standard-Z39.50 (10003)}

Z39-50-context OBJECT IDENTIFIER ::= {Z39-50 1} -- See Appendix 2, CTX.
Z39-50-APDU OBJECT IDENTIFIER ::= {Z39-50 2} -- See Appendix 1,  OID.3.1.
Z39-50-attributeSet OBJECT IDENTIFIER ::= {Z39-50 3} -- See Appendix 3,  ATR.
Z39-50-diagnostic OBJECT IDENTIFIER ::= {Z39-50 4} -- See Appendix 4,  ERR.
Z39-50-recordSyntax OBJECT IDENTIFIER ::= {Z39-50 5} -- See Appendix 5,  REC.
Z39-50-transferSyntax OBJECT IDENTIFIER ::= {Z39-50 6} -- See note below.
Z39-50-resourceReport OBJECT IDENTIFIER ::= {Z39-50 7} -- See Appendix 6,  RSC.
Z39-50-accessControl OBJECT IDENTIFIER ::= {Z39-50 8} -- See Appendix 7,  ACC.
Z39-50-extendedService OBJECT IDENTIFIER ::= {Z39-50 9} -- See Appendix 8,  EXT.
Z39-50-userInfoFormat OBJECT IDENTIFIER ::= {Z39-50 10} -- See Appendix 9,  USR.
Z39-50-elementSpec OBJECT IDENTIFIER ::= {Z39-50 11} -- See Appendix 10, ESP.
Z39-50-variantSet OBJECT IDENTIFIER ::= {Z39-50 12} -- See Appendix 11, VAR.
Z39-50-schema OBJECT IDENTIFIER ::= {Z39-50 13} -- See Appendix 12, TAG.
Z39-50-tagSet OBJECT IDENTIFIER ::= {Z39-50 14} -- See Appendix 12, TAG.

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):

  1. the association control service element (ACSE, ISO 8650), and
  2. 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).


[Table of Contents | Previous Section | Next Section]