Norwegian Z39.50 Interest Group
http://www.norzig.no/ 
 

NorZIG Z39.50 Profile Version 2.

Relation to other profiles

Document revision: 2002-03-03: Peliminary draft (OH)
Document revision: 2002-03-07: 1st draft (OH)
Document revision: 2002-05-02: 2nd draft (OH)

This document describes the NorZIG Z39.50 Profile Version 2 [1], compared to related Z39.50 profiles.

Introduction
Relations to the Norwegian Z39.50 profile Version 1.0
Relations to the ONE-2 Profile v3 r2
Relations to the The Bath profile version 1.1
References

Introduction

The intended audience of this document are implementors of Z39.50 services in Norway and their partners and system suppliers.

Further information about the NorZIG activities is available from the official NorZIG Web-site: http://www.norzig.no/

Relations to the Norwegian Z39.50 profile Version 1.0

This previous version of the Norwegian Z39.50 profile [2] was published by NorZIG in 1999, and has been adopted in most Norwegian Z39.50 implementations.

Version 2 includes requirements that were not present in version 1.0: holdings search and retrieval, explain lite, and cross domain search and retrieval.

The two versions are quite differently organized, and a detailed comparison is nontrivial.

Main relationship

The NorZIG profile Version 2 (NorZIG v2) extends (is a superset of) version 1 (v1) with one major exception:

NorZIG v2 does not require Origin support for any attribute combinations.

Details

The following table lists all the minor exceptions and all the extensions.

Functional Area Exceptions Extensions
A: Common Requirements    
Protocol Version   NorZIG v2 requires Z39.50 Version 3.
Initialisation Facility   NorZIG v2 requires UserID and Password as ID/Authentication parameters.
NorZIG v2 specifies requirements for IP authentication.
Termination Facility   This facility is not required in v1
ExplainLite Facility   This facility is not required in v1
Character set   NorZIG v2 includes character set requirements.
B: Bibliographic Search and Retrieval    
Search Service NorZIG v2 does not describe the use of semantic qualifiers.
NorZIG v2 does not require support for Truncation attribute = "Process # in search term".
NorZIG v2 does not require Origin support for any attribute combinations.
NorZIG v2 does not allow year to be used as secondary search term only. 		NorZIG v2 requires default DB names.
NorZIG v2 adds more detailed requirements for Target support of the different attribute types.
NorZIG v2 adds a considerable number of required attribute combinations at the Target.
Present Service NorZIG v2 has no Origin requirements. NorZIG v2 requires target support for certain ESNs.
NorZIG v2 requires holdings for ESN = F.
NorZIG requires NORMARC support.
NorZIG v2 includes character set requirements.
NorZIG requires support for the NorZIG Holdings profile Version 2.
Scan Service   NorZIG requires support for default dbnames.
NorZIG v2 includes table of required attribute combinations.
NorZIG v2 requires scan response to include number of entries.
C: Holdings Information Search and Retrieval   Not included in v1
E: Cross-domain Search and Retrieval   Not included in v1

Relations to the ONE-2 Profile v3 r2

The ONE-2 Profile v3 r2 [3] is the final version from the ONE-2 project, and has served as the main basis for the NorZIG Z39.50 Profile Version 2.

Main relationship

The NorZIG profile Version 2 (NorZIG v2) extends (is a superset of) the ONE-2 profile (ONE-2) with two major exceptions:

ONE-2 includes requirements for the Functional Areas which are missing in NorZIG v2:

Details

The following table lists all the minor exceptions and all the extensions.

Functional Area Exceptions Extensions
A: Common Requirements    
Initialisation Facility   NorZIG v2 requires ID/Authentication
NorZIG v2 describes IP-based authentication.
ExplainLite Facility NorZIG v2 has this as a "should" requirement.  
Character set ONE-2 requires character set negotiations NorZIG v2 includes character set requirements.
B: Bibliographic Search and Retrieval    
Search Service NorZIG v2 does not require level-1 segmentation (1).
NorZIG v2 does not require unconditional support of the Bib-1 attribute combinations (2). 		NorZIG v2 explicitly defines default values for missing atrribute types.
NorZIG v2 requires support for dbname "default".
NorZIG v2 extends table of required attribute combinations, and specifies all 6 attribute types..
Present Service NorZIG v2 does not require UNIMARC support (3) NorZIG v2 requires holdings for ESN = F.
NorZIG v2 requires NORMARC support.
NorZIG v2requires support for the NorZIG Holdings profile Version 2.
Scan Service NorZIG v2 does not require unconditional support of the Bib-1 attribute combinations (2). NorZIG v2 requires support for dbname "default".
NorZIG v2 extends table of required attribute combinations.
C: Holdings Information Search and Retrieval    
Level-1 Holdings   NorZIG v2 requires support for the NorZIG Holdings profile Version 2.
NorZIG v2 requires NORMARC support.
Level-2 Holdings    
E: Cross-domain Search and Retrieval    
Search Service   NorZIG v2 explicitly includes the same general requirements as in Functional Area B.
NorZIG v2 explicitly lists required attribute combinations based on the Dublin Core set.
Present Service    

Comments

(1) The requirement for segmentation support in ONE-2 is probably an error.

(2) The conditional requirement in NorZIG probably coincides with the "intention" in ONE-2.

(3) UNIMARC support is in ONE-2 stated as a "strong recommendation".

Relations to the Bath Profile version 1.1

The Bath Profile [4] is the result of an international effort. The National Library of Canada is the maintenance agency for the Bath Profile.

The Bath profile is organized into three functional areas:

A. Basic Bibliographic Search and Retrieval
B. Bibliographic Holdings Search and Retrieval
C. Cross-Domain Search and Retrieval

Within each area there are two or more conformance levels defined.

The two profiles are quite differently organized, and a detailed comparison is nontrivial.

Main relationship

The NorZIG Profile Version 2 is designed to include the requirements of the current version of the Bath Profile as far as possible. One main difference is, that the NorZIG Profile is primarily specified in terms of Target requirements, while the Bath Profile is defined in terms of both Target- and Origin requirements. There are further significant differences concerning the support of predefined combinations og attribute types.

As a general statement, one could claim that the NorZIG profile Version 2 (NorZIG v2) extends (is a superset of) the Bath profile with some exceptions. The details are given below.

Details

The following table lists all the minor exceptions and all the extensions.

 
Functional Area Exceptions Extensions
A: Common Requirements  
Protocol version   Bath allows version 2 in some areas, but requires version 3 in others.
Initialisation Facility   NorZIG v2 requires UserID and Password as ID/Authentication parameters.
NorZIG v2 specifies requirements for IP authentication.
ExplainLite Facility This facility is not required by Bath
Termination Facility   This facility is not required by Bath
Character set Bath has a rather complex set of requirements for the use of  character sets.
Bath requires character set negotiation and language negotiation in some areas.		  
B: Bibliographic Search and Retrieval    
Search Service Bath requires origin to supply all 6 attribute types.
Bath level 1 requires several attribute combinations that are not required by NorZIG v2.
(All level 0 requirements are included in NorZIG v2).		 NorZIG v2 requires default DB names.
NorZIG v2 explicitly defines default values for missing atrribute types.
NorZIG v2 explicitly requires inverted syntax for personal names when structure attribute = 101.
NorZIG v2 requires some attribute combinations that are not part of Bath level 1.

 
Present Service NorZIG v2 has no Origin requirements. NorZIG v2 requires target support for certain ESNs.
NorZIG v2 requires holdings for ESN = F.
NorZIG requires NORMARC support.
NorZIG requires support for the NorZIG Holdings profile Version 2.
Scan Service Bath level 1 requires support for Position-in-response = 0

Bath level 1 requires several attribute combinations that are not required by NorZIG v2. (All level 0 requirements are included in NorZIG v2).

 Bath level 0 does not require SCAN

NorZIG v2 requires some attribute combinations that are not part of Bath level 1.
C: Holdings Information Search and Retrieval    
Level-1 Holdings Bath level-1 is quite vaguely described. (It is in fact the only level).

Bath requires support for GRS-1

Bath requires support for the holdings attribute set.

 NorZIG v2 requires support for the NorZIG Holdings profile Version 2.

NorZIG v2 requires support for Bib-1 USE attribute = 1044 (Posessing-Institution).
NorZIG v2 requires NORMARC support.

Level-2 Holdings Bath has no level-2
E: Cross-domain Search and Retrieval    
Search Service Bath lists required attribute combinations based on the non-Dublin-Core part of Bib-1. NorZIG explicitly includes the same general requirements as in Functional Area B.
NorZIG lists required attribute combinations based on the Dublin Core set.
Present Service NorZIG v2 has no Origin requirements.

Bath requires SUTRS

 NorZIG v2 eplicitly requires ESN = F.

References

[1] Norwegian Z39.50 Profile Version 2.
http://www.norzig.no/profiles/profile2.html

[2] Norwegian Z39.50 profile Version 1.0.
http://www.norzig.no/profiles/norprof.html

[3] ONE-2 Profile v3 r2.
http://www.portia.dk/pubs/one2/Profiles/ProfileV3R2/ONE-2ProfileV3R2.pdf

[4] The Bath Profile: An International Z39.50 Specification for Library Applications and Resource Discovery. Release 1.1
http://www.nlc-bnc.ca/bath/bp-current.htm