Originator: CIMI

Date: 4/98

Amendment Concerning: Element Specification eSpec-1

Reference in Document: Appendix 10 (ESP)

Reference in Maintenance Agency page: Element Specification eSpec-1

Amendment: In Element Specification eSpec-1, as defined in the Z39.50-1995 standard, the definition of TagPath begins as follows:

     TagPath ::= SEQUENCE OF CHOICE{
        specificTag [1] IMPLICIT SEQUENCE{
                       tagType   [1] IMPLICIT INTEGER OPTIONAL,
                       tagValue  [2] StringOrNumeric,
                       ........

This amendment changes the definition to:

             TagPath ::= SEQUENCE OF CHOICE{
        specificTag [1] IMPLICIT SEQUENCE{
                       schemaId   [0] IMPLICIT OBJECT IDENTIFIER OPTIONAL,
                       tagType    [1] IMPLICIT INTEGER OPTIONAL,
                       tagValue   [2] StringOrNumeric,
                       ........

The schema id may occur only if tagType (within specificTag) is to be interpreted according to some schema other than that which was specified in CompSpec (which is what references eSpec-1). The sole purpose of schemaId is to qualify tagType.

Note: It is presumed that the identified schema definition provides a mapping of numeric tagTypes to Object Identifiers for tagSets. Thus tagType identifies a tagSet, identified by the Object Identifier that tagType maps to, where the mapping is defined by the identified schema.

Status:This was endorsed by the ZIG, October 1998, but will not be progressed further as an amendment. Instead, a new definition and object identifier is assigned. See Element Specification eSpec-2.