Z39.50 - Factbites

Z39.50 - Factbites
Where results make sense
About us | Why use us? | Reviews | PR | Contact us

Topic: Z39.50

Note: these results are not from the primary (high quality) database.

In the News (Mon 16 Nov 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	Ya-Ym
		The basic level consists of three primary interfaces: ASN, which provides a C representation of the Z39.50/SR protocol packages; ODR, which encodes and decodes the packages according to the BER specification; and COMSTACK, which exchanges the encoded packages with a peer process over a network.
		The YAZ toolkit offers several different levels of access to the Z39.50 and SR protocols.
	stommel.tamu.edu /~baum/linuxlist/linuxlist/node55.html

	Z39.50 Resource Page - National Information Standards Organization (NISO)
		Web to Z39.50 gateway software from the Europgate project.
		50 client from the Center for Networked Information Discovery and Retrieval.
	www.niso.org /z39.50/z3950.html

	Search and Retrieval in The European Library: A New Approach
		SRW was announced as an alternative to Z39.50 under the umbrella of the Z39.50 international Next Generation [ZiNG] Two access mechanisms were proposed: 1) SRW (Search and Retrieve via the Web), based on the use of SOAP
		We anticipate that SRW and SRU will gradually replace Z39.50, and we hope the Z39.50-SRU gateway will stimulate the acceptance SRU/SRW, as it allows existing Z39.50 services to be made available as SRU services without any change.
		By the time the TEL http/URL/XML protocol was specified and implemented, the Z39.50 Implementers Group [Z39.50] had developed a similar concept: Search and Retrieve via the Web (SRW).
	www.dlib.org /dlib/february04/vanveen/02vanveen.html

	P4_cheshire_logs.txt
		============= Transaction # 1 ============================================== Transaction #: 1 Transaction Code: 0 (New Host Selected) Terminal ID: 12781888 Z39.50 Server ID: 0 (Astro/Math/Stat) Session ID: 1 New Z39.50 Server ID: 19 (TREC) Old Z39.50 Server ID: 0 (Astro/Math/Stat) Usr Interface: Prob Time Cmd Sent: Fri Aug 27 12:42:44 1999 Rec.
		============= Transaction # 11 ============================================== Transaction #: 11 Transaction Code: 39 (Full Doc Window --TREC) Terminal ID: 12781888 Z39.50 Server ID: 19 (TREC) Session ID: 1 New Z39.50 Server ID: 0 (Astro/Math/Stat) Old Z39.50 Server ID: 0 (Astro/Math/Stat) Usr Interface: Prob Time Cmd Sent: Wed Dec 31 16:00:00 1969 Rec.
		============= Transaction # 6 ============================================== Transaction #: 6 Transaction Code: 39 (Full Doc Window --TREC) Terminal ID: 12781888 Z39.50 Server ID: 19 (TREC) Session ID: 1 New Z39.50 Server ID: 0 (Astro/Math/Stat) Old Z39.50 Server ID: 0 (Astro/Math/Stat) Usr Interface: Prob Time Cmd Sent: Wed Dec 31 16:00:00 1969 Rec.
	www.itl.nist.gov /iaui/894.02/projects/t8i/rich/berkeley/BrkInt_RICH/P4/P4_cheshire_logs.txt

	Fixing WAIS
		This standard, known as Z39.50 version 2, is not compatible with Z39.50-1988 or the WAIS protocol.
		The current specification of Z39.50 version 2 and version 3 are both specified in the document known as Z39.50-1995.
		The draft Geospatial Profile is a superset of GILS and so is based on Z39.50-1995 as well.
	lists.w3.org /Archives/Public/www-disw/msg00058.html (670 words)

	Z39.50 Profiles
		The Bath Profile: An International Z39.50 Specification for Library Applications and Resource Discovery; Version 1.1; June 2000.
		Z Texas Profile -- A Z39.50 Specification for Library Systems Applications in Texas Release 3.0.
		Note: in conjunction with this profile an XML schema has been defined for ILL transactions transported via Z39.50 Item Order Extended Service.
	www.loc.gov /z3950/agency/profiles/profiles.html (670 words)

	YAZ
		YAZ has been widely considered the leading toolkit for building Z39.50 clients and servers since its first release in 1995.During a decade of active service, the YAZ toolkit has been battle-hardened in every conceivable type of employment, and grown in its support for even the more esoteric aspects of the Z39.50 and SRW protocols.
		Libraries and vendors can freely download YAZ and its associated toolkits to build their own Z39.50 applications.Alternatively, they can use the consultancy and support services of Index Data to take advantage of our decade of experience building and supporting Z39.50 toolkits and applications.
		YAZ is a programmers’ toolkit supporting the development of Z39.50/SRW/SRU clients and servers.
	www.indexdata.dk /yaz (220 words)

	rfc1625.txt
		WAIS Implementation of Z39.50-1988 By working with the Z39.50 Implementors Group (ZIG), the WAIS developers used a recommended subset of Z39.50-1988 and specific assumptions to fulfill its requirements.
		In this way, knowledge of the Z39.50 Attributes supported by the server was no longer required by the client or the user, as is true of many existing Z39.50 implementations.
		Use of Z39.50 over TCP is described in [4].
	www.ietf.org /rfc/rfc1625.txt (1391 words)

	Z39.50 for All, Ariadne Issue 21
		ANSI/NISO Z39.50-1995, Information Retrieval (Z39.50): Application Service Definition and Protocol Specification and ISO 23950:1998, Information and documentation — Information retrieval (Z39.50) — Application service definition and protocol specification.
		The current version of Z39.50 is more properly known as North American standard ANSI/NISO Z39.50-1995, Information Retrieval (Z39.50): Application Service Definition and Protocol Specification [ 1 ], or as the matching international standard ISO 23950:1998, Information and documentation — Information retrieval (Z39.50) — Application service definition and protocol specification.
		Use of the term in this paper always refers to version 3 of the standard, except where otherwise specified.
	www.ariadne.ac.uk /issue21/z3950/intro.html (1391 words)

	Z39.50 Maintenance Agency Page
		This page provides links to information about Z39.50 resources and about the development and maintenance of Z39.50 (existing as well as future versions) and the implementation and use of the Z39.50 protocol.
		"Z39.50" refers to the International Standard, ISO 23950: "Information Retrieval (Z39.50): Application Service Definition and Protocol Specification", and to ANSI/NISO Z39.50.
		Library of Congress Home - Other Standards Maintained by the Library - Z39.50 Gateway
	lcweb.loc.gov /z3950/agency (1391 words)

	Z39.50 Maintenance Agency Page
		This page provides links to information about Z39.50 resources and about the development and maintenance of Z39.50 (existing as well as future versions) and the implementation and use of the Z39.50 protocol.
		"Z39.50" refers to the International Standard, ISO 23950: "Information Retrieval (Z39.50): Application Service Definition and Protocol Specification", and to ANSI/NISO Z39.50.
		The Library of Congress is the Maintenance Agency and Registration Authority for both standards, which are technically identical (though with minor editorial differences).
	www.loc.gov /z3950/agency (1391 words)

	Z39.50 Maintenance Agency Page
		This page provides links to information about Z39.50 resources and about the development and maintenance of Z39.50 (existing as well as future versions) and the implementation and use of the Z39.50 protocol.
		"Z39.50" refers to the International Standard, ISO 23950: "Information Retrieval (Z39.50): Application Service Definition and Protocol Specification", and to ANSI/NISO Z39.50.
	www.loc.gov /z3950/agency (1391 words)

	Z39.50 Maintenance Agency Page
		This page provides links to information about Z39.50 resources and about the development and maintenance of Z39.50 (existing as well as future versions) and the implementation and use of the Z39.50 protocol.
		"Z39.50" refers to the International Standard, ISO 23950: "Information Retrieval (Z39.50): Application Service Definition and Protocol Specification", and to ANSI/NISO Z39.50.
		The Library of Congress is the Maintenance Agency and Registration Authority for both standards, which are technically identical (though with minor editorial differences).
	www.loc.gov /z3950/agency (1391 words)

	RFC 1625 (rfc1625)
		IIIR Working Group [Page 2] RFC 1625 WAIS over Z39.50-1988 June 1994 To achieve this, the text string entered by the user was transmitted to the server without parsing the string into a Type-1 RPN (reverse- polish notation) query, as is common for bibliographic applications.
		The WAIS server is a program that services client IIIR Working Group [Page 1] RFC 1625 WAIS over Z39.50-1988 June 1994 requests, and is available on a variety of UNIX platforms.
		Over time, many of these IIIR Working Group [Page 3] RFC 1625 WAIS over Z39.50-1988 June 1994 requirements have then gone into the definition of subsequent versions of Z39.50.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc1625.html (1391 words)

	Gate-Z - Background Analysis
		The Bath Profile is an ISO Internationally Registered Profile (IRP) of the Z39.50 Information Retrieval Protocol, intended as a basis for effective interoperability between library and cross-domain applications.
		A relevant subset of ISO ILL transactions (APDU) may be exchanged as Externals within the Z39.50 Extended Service.
		This document describes the ONE-2 Profile for use of the Z39.50-1995 Search and Retrieval (ISO 23950) standard and the ISO 10160/10161 ISO ILL Interlibrary Loan standard.
	www.rdn.ac.uk /projects/gate-z/background (1391 words)

	Emerge: Gazelle Overview
		Gazebo and Gazelle are both built around a core library called "libemerge", which contains support for Z39.50, portable socket I/O, MARC record formatting (used by some Z39.50 services), and a set of convenient data structures and routines to manipulate them.
		Gazelle calls these routines when the corresponding events occur in its interaction with the Z39.50 client.
		These record syntaxes are analogous to MIME types, and indeed Z39.50 provides a set of mappings between MIME types and record syntax identifiers, several of which are defined as constants in Gazelle.
	dlt.ncsa.uiuc.edu /archive/emerge/gazelle_overview.html (1391 words)

	Library of Congress WWW/Z39.50 Gateway
		Where applicable, the software vendor for the target Z39.50 implementation is given in parentheses after the name of the institution.
		Z39.50 Resources, maintained by Dan Brickley, Institute for Learning and Research Technology, and Z39.50 Resource Page, maintained by NISO, will provide hyperlinks to many Z39.50-related resources.
		It is also possible to access the LC server by using the appropriate search forms listed under "Search Library of Congress Catalog" above.
	www.loc.gov /z3950/gateway.html (984 words)

	Zthes - Zthes Profile for SRW, version 0.5
		The Z39.50 Zthes Profile includes specifications for the use of Z39.50 Explain facility to determine whether a given database is a Zthes database, and to locate a Zthes database suitable for use as an authority file for a particular access point of an explained database.
		This version of the SRW profile, 0.5, corresponds to version 0.5 of the Z39.50 profile.
		This document is to be read in conjunction with Section 2 of the Z39.50 profile, describing the model.
	zthes.z3950.org /srw/current.html (984 words)

	LC Voyager Z39.50/SRW/SRU Server Configuration Guidelines
		This document provides detailed technical information for Z39.50 and SRW client developers and implementors that is necessary in order to access and interwork with the LC Voyager Server (implemented August 31, 1999).
		This document assumes a general familiarity with Z39.50, SRW, or SRU.
		LC has implemented Index Data's YAZ Proxy which is functioning as an SRW/SRU/Z39.50 gateway to the Voyager Z39.50 server for the LC Online Catalog.
	lcweb.loc.gov /z3950/lcserver.html (984 words)

	port-numbers
		z39.50 210/tcp ANSI Z39.50 z39.50 210/udp ANSI Z39.50 # Mark H. Needleman
		k-block 287/tcp K-BLOCK k-block 287/udp K-BLOCK # Simon P Jackson
		iso-ill 499/tcp ISO ILL Protocol iso-ill 499/udp ISO ILL Protocol # Mark H. Needleman
	www.iana.org /assignments/port-numbers (984 words)

	Standards
		The Z39.50 standard, which has become International standard ISO 23950, has been developed to allow complex bibliographic enquiries to be exchanged between client and server computers, regardless of the database structure or brand of software running on the server computer.
		In the Z39.50 standard (and the identical international standard ISO 23950) the computer running the client software is referred to as the ‘origin’, and the computer running the server software is referred to as the ‘target’.
		Typically these may be a personal computer running Z39.50 client software and a remote computer running Z39.50 server software.
	www.csu.edu.au /special/online99/proceedings99/104a.htm (984 words)

	Library Lingo in Randall Library
		Z39.50 makes it possible for a user in one system to search and retrieve information from other computer systems (that have also implemented Z39.50) without knowing the search syntax that is used by those other systems.
		Z39.50 : Z39.50 is a national and international (ISO 23950) standard defining a protocol for computer-to-computer information retrieval.
	coast2.lib.uncwil.edu /faculty/pembertona/lingo.html (984 words)

	The Main Question (IMHO): Do the participants in the breakout session want
		Z39.50 is a communications standard describing the rules and procedures by which two or more computer systems communicate whilst searching and retrieving information from databases.
		The Bath Profile is an international Z39.50 specification supporting library applications and resource discovery.
		It describes and specifies a subset of ANSI/NISO Z39.50-1995, Information Retrieval (Z39.50): Application Service Definition and Protocol Specification (ISO 23950) ( http://lcweb.loc.gov/z3950/agency/document.html).
	www.library.yale.edu /consortia/bathprofile.htm (984 words)

	JAFER Toolkit Project - Development Web Site
		Z39.50 is a NISO standard (also ratified by ISO) for a generic search and retrieve protocol intended for searching any database or data-source.
		Another obstacle to mainstream acceptance of Z39.50 in today's WebService based environment is that fact that it uses a binary encoding for transmitting the messages between the client and server.
		The JAFER toolkit is developing a simplified XML based Application Programming Interface (API) implemented in Java above the Z39.50 protocol thus enabling Z39.50 to be used within XML frameworks such as Cocoon, JetSpeed or Java Server Page based web servers.
	www.jafer.org /publications/www2002-paper.html (984 words)

	Standards
		ANSI/NISO Z39.50–1995 (ISO 23950), is a client-server based network protocol widely deployed in the bibliographic domain and is concerned primarily with the search and retrieval of information within databases.
		Z39.50 ANSI/ NISO Z39.50-1995 (ISO 23950) is an international standards-based communications protocol for information retrieval, which is independent of database and computer environment.
		One of the major advantages of using Z39.50 is that it enables uniform access to a large number of diverse and heterogeneous information sources irrespective of the computer system, search engine, or database.
	www.csu.edu.au /special/online99/proceedings99/104b.htm (984 words)

	Ruby/ZOOM: Z39.50 support for Ruby
		Ruby/ZOOM provides a Ruby binding to the Z39.50 Object-Orientation Model (ZOOM), an abstract object-oriented programming interface to a subset of the services specified by the Z39.50 standard, also known as the international standard ISO 23950.
		To give a flavour of the Ruby binding, here is ZOOM's equivalent of the ``Hello World'' program: a tiny Z39.50 client that fetches and displays the MARC record for Farlow and Brett Surman's The Complete Dinosaur from the Library of Congress.
		This software is based (and therefore depends) on YAZ, a free-software implementation of the Z39.50/SRW/SRU standards, but could be easily ported to any ZOOM compliant implementation.
	ruby-zoom.rubyforge.org (984 words)

	Library of Congress WWW/Z39.50 Gateway
		Where applicable, the software vendor for the target Z39.50 implementation is given in parentheses after the name of the institution.
		Using a Z39.50 client, it is currently possible to search the Library of Congress bibliographic file.
		Z39.50 makes it possible for a user in one system to search and retrieve information from other computer systems (that have also implemented Z39.50) without knowing the search syntax that is used by those other systems.
	www.loc.gov /z3950 (984 words)

	Exploit Interactive Issue 3: The Z39.50 Implementor's Group
		In the midst of the world-famous water festival [1], members of the Z39.50 community's Implementor's Group gathered in the Swedish capital, Stockholm, for the 29th meeting of the group.
		The first, compiled by Ray Denenberg of the Z39.50 Maintenance Agency at Library of Congress, illustrates a range of events during the meeting [10].
		More information on Z39.50 is available from the Maintenance Agency [4] hosted by Library of Congress, and in a recent article published in Ariadne [5].
	www.exploit-lib.org /issue3/zig (459 words)

	A Cross-Domain Attribute Set
		Because qualification is native to Z39.50 attribute sets and not a topic of debate in the Z39.50 community, we are going to unilaterally resolve one of the Dublin Core issues.
		Such qualification is intrinsic to Z39.50 attribute sets and will be defined in the Dublin Core attribute set.
		If the client is willing to let the server revert to the semantics for the base Abstract attribute, the client can provide the NULL Content Authority attribute value defined in the Z39.50 Utility attribute set.
	dublincore.org /documents/1998/10/09/cross-domain-attribute (2090 words)

	Zthes - Home Page
		The main thing, of course, is the Z39.50 profile itself which includes, for historical reasons, the specification of the abstract model.
		It is intended that the abstract model described here is sufficiently general that it can also be implemented by protocols and data formats other than Z39.50.
		Zthes: a Profile for Thesaurus Navigation in Z39.50 and SRW
	zthes.z3950.org (2090 words)

Try your search on: Qwika (all wikis)

Topic: Z39.50

Ads by Google

In the News (Mon 16 Nov 09)