-
Petry, W.; Werner, H.-J.: Anwendertraum: Kommunikations- und Retrieval-Software im Vergleich (1993)
0.03
0.025163336 = product of:
0.088071674 = sum of:
0.06087649 = weight(_text_:retrieval in 4147) [ClassicSimilarity], result of:
0.06087649 = score(doc=4147,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.5347345 = fieldWeight in 4147, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.125 = fieldNorm(doc=4147)
0.027195185 = product of:
0.081585556 = sum of:
0.081585556 = weight(_text_:22 in 4147) [ClassicSimilarity], result of:
0.081585556 = score(doc=4147,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.61904186 = fieldWeight in 4147, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.125 = fieldNorm(doc=4147)
0.33333334 = coord(1/3)
0.2857143 = coord(2/7)
- Source
- Cogito. 9(1993) H.2, S.18-22
-
Lynch, C.: ¬The Z39.50 information retrieval protocol : an overview and status report (1991)
0.02
0.020344833 = product of:
0.07120691 = sum of:
0.017939983 = weight(_text_:information in 6524) [ClassicSimilarity], result of:
0.017939983 = score(doc=6524,freq=2.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.27153665 = fieldWeight in 6524, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.109375 = fieldNorm(doc=6524)
0.053266928 = weight(_text_:retrieval in 6524) [ClassicSimilarity], result of:
0.053266928 = score(doc=6524,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.46789268 = fieldWeight in 6524, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.109375 = fieldNorm(doc=6524)
0.2857143 = coord(2/7)
-
Peters, T.A.: ¬The online catalog : A critical examination of public use (1991)
0.02
0.016441107 = product of:
0.05754387 = sum of:
0.014497695 = weight(_text_:information in 818) [ClassicSimilarity], result of:
0.014497695 = score(doc=818,freq=4.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.21943474 = fieldWeight in 818, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0625 = fieldNorm(doc=818)
0.043046176 = weight(_text_:retrieval in 818) [ClassicSimilarity], result of:
0.043046176 = score(doc=818,freq=4.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.37811437 = fieldWeight in 818, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0625 = fieldNorm(doc=818)
0.2857143 = coord(2/7)
- COMPASS
- Information retrieval / Use of / On-line computers
- Subject
- Information retrieval / Use of / On-line computers
-
Moen, W.: Information retrieval protocols : Z39.50 and Search & Retrieve via URL (2009)
0.02
0.015815146 = product of:
0.055353012 = sum of:
0.012814272 = weight(_text_:information in 3813) [ClassicSimilarity], result of:
0.012814272 = score(doc=3813,freq=8.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.19395474 = fieldWeight in 3813, product of:
2.828427 = tf(freq=8.0), with freq of:
8.0 = termFreq=8.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0390625 = fieldNorm(doc=3813)
0.04253874 = weight(_text_:retrieval in 3813) [ClassicSimilarity], result of:
0.04253874 = score(doc=3813,freq=10.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.37365708 = fieldWeight in 3813, product of:
3.1622777 = tf(freq=10.0), with freq of:
10.0 = termFreq=10.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0390625 = fieldNorm(doc=3813)
0.2857143 = coord(2/7)
- Abstract
- Information retrieval (IR) protocols support effective and interoperable intersystem search and retrieval. Although intersystem search methods have been envisioned and under development since the 1970s, it was the Z39.50 IR protocol, first released in 1988, that demonstrated real-world possibilities for such search and retrieval. As the networked information environment changed with the emergence of the World Wide Web, the need for standard IR protocols did not disappear, and one can argue the need is even more compelling given both the visible and invisible Web. A new protocol, based on the experience from Z39.50 but simpler and more comprehensible than Z39.50, is now being used for Web search and retrieval. Search and retrieve via URL (SRU) uses Web technologies and standards resulting in a Web friendly protocol that provides standard search access to existing Z39.50 resources and a wide-range of new non-catalog digital resources. This entry provides both an overview of the two protocols and technical details to understand both. A brief discussion of IR and communications protocols provides background to the specifics of these two IR protocols. Although communication protocols are by their nature technical specifications, this entry focuses on an overview of the functions and capabilities of the protocols. It uses technical concepts and terminology from the protocols to help explain how the protocols work but limits discussion of technical details.
- Source
- Encyclopedia of library and information sciences. 3rd ed. Ed.: M.J. Bates
-
Deussen, N.: Sogar der Mars könnte bald eine virutelle Heimat bekommen : Gut 4,2 Milliarden sind nicht genug: Die sechste Version des Internet-Protokolls schafft viele zusätzliche Online-Adressen (2001)
0.01
0.014010864 = product of:
0.049038023 = sum of:
0.044750202 = weight(_text_:kongress in 5729) [ClassicSimilarity], result of:
0.044750202 = score(doc=5729,freq=2.0), product of:
0.24693015 = queryWeight, product of:
6.5610886 = idf(docFreq=169, maxDocs=44218)
0.037635546 = queryNorm
0.18122616 = fieldWeight in 5729, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
6.5610886 = idf(docFreq=169, maxDocs=44218)
0.01953125 = fieldNorm(doc=5729)
0.0042878194 = product of:
0.012863458 = sum of:
0.012863458 = weight(_text_:29 in 5729) [ClassicSimilarity], result of:
0.012863458 = score(doc=5729,freq=2.0), product of:
0.13239008 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.037635546 = queryNorm
0.097163305 = fieldWeight in 5729, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.01953125 = fieldNorm(doc=5729)
0.33333334 = coord(1/3)
0.2857143 = coord(2/7)
- Abstract
- Der neue 128-Bit-Header treibt die Möglichkeiten ins Astronomische: 3,4 mal zehn hoch 38 Adressen, eine 3,4 mit 38 Nullen. -Das IPv6-Forum zerhackte den Zahlentrumm in anschauliche Stücke: Pro Quadratmillimeter Erdoberfläche stehen nun zirka 667 Billiarden, pro Mensch 6,5 mal zehn hoch 28 Adressen, bereit." Eine Billiarde bringt es immerhin auf respektable 15 Nullen. Schon kurz darauf ging ein Aufschrei durch die Netzgemeinde. Das neue Protokoll schrieb die weltweit eindeutigen Seriennummern bestimmter Netzwerkkarten auf den virtuellen Adressaufkleber. Die Ethernet-Adapter bewerkstelligen den Datentransport bei Computern, die über eine Standleitung, ein Koaxialkabel, dauernd online sind. Die Spur von Ethernet-Usern wäre damit leicht zu verfolgen gewesen, ihre Nutzerprofile, ihre Surfgewohnheiten einsehbar wie offene Bücher. Das Problem, ließ Icann nun wissen, sei behoben: Es gebe keine festen Kennzahlen mehr in den Adressköpfen. Bei jedem Hochfahren eines Rechners oder sogar noch öfter werden die Nummern neu durchgemischt", erläutert Hans Petter Dittler, stellvertretender Vorsitzender der deutschen Sektion der Internet Society. Das Betriebssystem Linux kann bereits mit dem IPv6 arbeiten. Microsoft will den Standard in das nächste Windows-Betriebssystem einbauen: "Wir denken, der vorgeschlagene Standard ist wichtig zum Schutz der Privatsphäre der Internet-Nutzer", sagt Jawad Khaki, Vizepräsident für Netzwerke. Seit einigen Tagen steht auf der Microsoft-Homepage eine Vorab-Version von lPv6 für Windows 2000 zum Herunterladen bereit. Geradezu euphorisch gibt sich Protokoll-Chef Vint Cerf. Mit IPv6 haben wir die Grundlage dafür", philosophierte der Internet-Daddy auf dem ersten lPv6-Kongress 1999 in Berlin, "das Internet von unserem Planeten über den Mars und die Asteroiden bis in den Weltraum hinaus auszudehnen." Doch im Internet-Alltag wird das alte Protokoll noch lange Vorrang haben. Grund sind handfeste Programmier-Probleme. Denn Software, die sich explizit auf die vierte IP-Version bezieht, muss umgeschrieben werden - etwa um mit den längeren Adressfeldern umgehen zu können. Hubert Martens vom Münchner Multinet Services befürchtet gar einen InternetCrash: "Das Jahr-2000-Problem war harmlos gegen das, was uns mit lPv6 droht."
- Source
- Frankfurter Rundschau. Nr.79 vom 3.4.2001, S.29
-
Scheuerer, J.: Onlinebanking (1997)
0.01
0.011707978 = product of:
0.08195584 = sum of:
0.08195584 = product of:
0.12293376 = sum of:
0.061744597 = weight(_text_:29 in 354) [ClassicSimilarity], result of:
0.061744597 = score(doc=354,freq=2.0), product of:
0.13239008 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.037635546 = queryNorm
0.46638384 = fieldWeight in 354, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.09375 = fieldNorm(doc=354)
0.061189163 = weight(_text_:22 in 354) [ClassicSimilarity], result of:
0.061189163 = score(doc=354,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.46428138 = fieldWeight in 354, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.09375 = fieldNorm(doc=354)
0.6666667 = coord(2/3)
0.14285715 = coord(1/7)
- Date
- 1. 8.1997 14:03:29
- Source
- Com!. 1997, H.8, S.22-24
-
Joy, F.; Murray, R.: ¬The World-Wide Web and Z39.50 : which way for libraries? (1995)
0.01
0.011625619 = product of:
0.040689662 = sum of:
0.010251419 = weight(_text_:information in 3997) [ClassicSimilarity], result of:
0.010251419 = score(doc=3997,freq=2.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.1551638 = fieldWeight in 3997, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0625 = fieldNorm(doc=3997)
0.030438244 = weight(_text_:retrieval in 3997) [ClassicSimilarity], result of:
0.030438244 = score(doc=3997,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.26736724 = fieldWeight in 3997, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0625 = fieldNorm(doc=3997)
0.2857143 = coord(2/7)
- Abstract
- The function of the W3, like that of Z39.50, is to offer access to networked information, and they appear to have similar client/server architectures. However, libraries need both because of the W3's lack of support for the advanced search, retrieval and management facilities that are expected of modern OPACs and are offered by Z39.50. Current research is involved in developing hybrid W3/Z39.50 services
-
Duhm, U.: Ring frei zur nächsten Runde (1999)
0.01
0.009756649 = product of:
0.06829654 = sum of:
0.06829654 = product of:
0.102444805 = sum of:
0.051453833 = weight(_text_:29 in 2955) [ClassicSimilarity], result of:
0.051453833 = score(doc=2955,freq=2.0), product of:
0.13239008 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.037635546 = queryNorm
0.38865322 = fieldWeight in 2955, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.078125 = fieldNorm(doc=2955)
0.050990973 = weight(_text_:22 in 2955) [ClassicSimilarity], result of:
0.050990973 = score(doc=2955,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.38690117 = fieldWeight in 2955, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.078125 = fieldNorm(doc=2955)
0.6666667 = coord(2/3)
0.14285715 = coord(1/7)
- Date
- 1. 8.1997 14:03:29
19. 2.1999 20:21:22
-
Corey, J.F.: ¬A grant for Z39.50 (1994)
0.01
0.008719213 = product of:
0.030517247 = sum of:
0.007688564 = weight(_text_:information in 7706) [ClassicSimilarity], result of:
0.007688564 = score(doc=7706,freq=2.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.116372846 = fieldWeight in 7706, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.046875 = fieldNorm(doc=7706)
0.022828683 = weight(_text_:retrieval in 7706) [ClassicSimilarity], result of:
0.022828683 = score(doc=7706,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.20052543 = fieldWeight in 7706, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.046875 = fieldNorm(doc=7706)
0.2857143 = coord(2/7)
- Abstract
- In Sept. 1990, the US Dept. of Education's Library Technology and Cooperation Grants Program awarded a three-year grant to the Florida Center for Library Automation (FCLA), an agency of the Florida State University System, to develop software adhering to the ANSI Z39.50 Information Retrieval protocol standard. The Z39.50 software was to operate over the OSI communications protocols and be integrated with FCLA's NOTIS system, which is shared by all 9 state universities in Florida. In order to test the correctness of its Z39.50 software, FCLA sought out other library software developers who would be willing to develop Z39.50 systems of their own. As part of this process, FCLA helped to found the Z39.50 Implementor's Group (ZIG), which has since gone on to improve the standard and promote Z39.50 implementations throughout much of the North American library systems marketplace. Early on in the project, it became apparent that TCP/IP would be a more heavily used communication vehicle for Z39.50 messages than OSI. FCLA expanded its design to include TCP/IP and, by the end of the grant in Sept. 1993, will have a working Z39.50 system that can communicate over both OSI and TCP/IP networks
-
Lynch, C.A.: ¬The Z39.50 information retrieval standard : part I: a strategic view of its past, present and future (1997)
0.01
0.007845367 = product of:
0.027458783 = sum of:
0.007688564 = weight(_text_:information in 1262) [ClassicSimilarity], result of:
0.007688564 = score(doc=1262,freq=8.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.116372846 = fieldWeight in 1262, product of:
2.828427 = tf(freq=8.0), with freq of:
8.0 = termFreq=8.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0234375 = fieldNorm(doc=1262)
0.01977022 = weight(_text_:retrieval in 1262) [ClassicSimilarity], result of:
0.01977022 = score(doc=1262,freq=6.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.17366013 = fieldWeight in 1262, product of:
2.4494898 = tf(freq=6.0), with freq of:
6.0 = termFreq=6.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0234375 = fieldNorm(doc=1262)
0.2857143 = coord(2/7)
- Abstract
- The Z39.50 standard for information retrieval is important from a number of perspectives. While still not widely known within the computer networking community, it is a mature standard that represents the culmination of two decades of thinking and debate about how information retrieval functions can be modeled, standardized, and implemented in a distributed systems environment. And - importantly -- it has been tested through substantial deployment experience. Z39.50 is one of the few examples we have to date of a protocol that actually goes beyond codifying mechanism and moves into the area of standardizing shared semantic knowledge. The extent to which this should be a goal of the protocol has been an ongoing source of controversy and tension within the developer community, and differing views on this issue can be seen both in the standard itself and the way that it is used in practice. Given the growing emphasis on issues such as "semantic interoperability" as part of the research agenda for digital libraries (see Clifford A. Lynch and Hector Garcia-Molina. Interoperability, Scaling, and the Digital Libraries Research Agenda, Report on the May 18-19, 1995 IITA Libraries Workshop, <http://www- diglib.stanford.edu/diglib/pub/reports/iita-dlw/main.html>), the insights gained by the Z39.50 community into the complex interactions among various definitions of semantics and interoperability are particularly relevant. The development process for the Z39.50 standard is also of interest in its own right. Its history, dating back to the 1970s, spans a period that saw the eclipse of formal standards-making agencies by groups such as the Internet Engineering Task Force (IETF) and informal standards development consortia. Moreover, in order to achieve meaningful implementation, Z39.50 had to move beyond its origins in the OSI debacle of the 1980s. Z39.50 has also been, to some extent, a victim of its own success -- or at least promise. Recent versions of the standard are highly extensible, and the consensus process of standards development has made it hospitable to an ever-growing set of new communities and requirements. As this process of extension has proceeded, it has become ever less clear what the appropriate scope and boundaries of the protocol should be, and what expectations one should have of practical interoperability among implementations of the standard. Z39.50 thus offers an excellent case study of the problems involved in managing the evolution of a standard over time. It may well offer useful lessons for the future of other standards such as HTTP and HTML, which seem to be facing some of the same issues.
This paper, which will appear in two parts, starting with this issue of D-Lib, looks at several strategic issues surrounding Z39.50. After a relatively brief overview of the function and history of the protocol, I will examine some of the competing visions of the protocol's role, with emphasis on issues of interoperability and the incorporation of semantics. The second installment of the paper will look at questions related to the management of the standard and the standards development process, with emphasis on the scope of the protocol and how that relates back again to interoperability questions. The paper concludes with a discussion of the adoption and deployment of the standard, its relationship to other standards, and some speculations on future directions for the protocol. This paper is not intended to be a tutorial on the details of how current or past versions of Z39.50 work. These technical details are covered not only in the standard itself (which can admittedly be rather difficult reading) but also in an array of tutorial and review papers (see <http://lcweb.loc.gov/z3950/agency> for bibliographies and pointers to on-line information on Z39.50). Instead, the paper's focus is on how and why Z39.50 developed the way it did, and the conceptual debates that have influenced its evolution and use. While a detailed technical knowledge of the operation of Z39.50 is certainly helpful, it should not be necessary in order to follow most of the material here. Some disclaimers are in order. I have been actively involved in the development of Z39.50 since the early 1980s and have been a participant -- and on occasion, even an instigator -- of some of the activities described here. This paper is an attempt to make a critical assessment of the current state of Z39.50 and a review of its development with the full benefit of hindsight. It recounts a number of debates that occurred within the developer community over the past years. In many of these, I advocated specific positions or approaches, sometimes successfully and sometimes unsuccessfully. What is presented here is one person's perspective - mine --, which is sometimes at odds with the current consensus with the developer community; I've tried to represent opposing views fairly, and to differentiate my opinions from fact or consensus. However, others will undoubtedly disagree with many of the comments here.
-
Werner, H.-J.: ¬Die Werkzeuge liegen bereit : Infoface - eine neue Benutzeroberfläche oder ein neues Retrieval-Software-Konzept? (1993)
0.01
0.0076095616 = product of:
0.053266928 = sum of:
0.053266928 = weight(_text_:retrieval in 5680) [ClassicSimilarity], result of:
0.053266928 = score(doc=5680,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.46789268 = fieldWeight in 5680, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.109375 = fieldNorm(doc=5680)
0.14285715 = coord(1/7)
-
Needleman, M.: Z39.50: a review, analysis and some thoughts on the future (2000)
0.01
0.0072660116 = product of:
0.025431039 = sum of:
0.006407136 = weight(_text_:information in 4898) [ClassicSimilarity], result of:
0.006407136 = score(doc=4898,freq=2.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.09697737 = fieldWeight in 4898, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0390625 = fieldNorm(doc=4898)
0.019023903 = weight(_text_:retrieval in 4898) [ClassicSimilarity], result of:
0.019023903 = score(doc=4898,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.16710453 = fieldWeight in 4898, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0390625 = fieldNorm(doc=4898)
0.2857143 = coord(2/7)
- Abstract
- This article will examine the Z39.50 Information Retrieval protocol. It will look at some of the history of the protocol, its operation, and some of the major projects that have made use of it. There has been enough written (perhaps too much) about Z39.50 in the last several years so it is not intended to be a tutorial or detailed description of the protocol. The material that will be presented will try and put some context around the discussion. For those readers who are interested in delving into Z39.50 in a more technical manner, references to much of the material that has been written about it over the years will be provided at the end. Finally, the article will conclude with some thoughts on how technology and technological infrastructure have changed in the years since Z39.50 was initially developed and deployed, and where the protocol has so far lived up to its goals, and where it has perhaps failed to meet some of the high expectations that at least some people involved in the Z39.50 community held for it. The article will conclude with some of the author's speculations (and they are really no more than that) of what the future role of Z39.50 is likely to be.
-
Bradley, P.: Towards a common user interface (1995)
0.01
0.0070546796 = product of:
0.024691377 = sum of:
0.012685482 = weight(_text_:information in 3133) [ClassicSimilarity], result of:
0.012685482 = score(doc=3133,freq=4.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.1920054 = fieldWeight in 3133, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0546875 = fieldNorm(doc=3133)
0.0120058935 = product of:
0.03601768 = sum of:
0.03601768 = weight(_text_:29 in 3133) [ClassicSimilarity], result of:
0.03601768 = score(doc=3133,freq=2.0), product of:
0.13239008 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.037635546 = queryNorm
0.27205724 = fieldWeight in 3133, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.0546875 = fieldNorm(doc=3133)
0.33333334 = coord(1/3)
0.2857143 = coord(2/7)
- Abstract
- Discusses the advantages and disadvantages of a common user interface to enable searching of all databases regardless of producer, supplier or location, such as local CD-ROM, or network. Explains client server architecture, the basic component of a common user interface and outlines current developments including the Z39.50 application layer protocol. A common user interface will result in greater synergy between information providers, technology providers, distributors and information professionals. It will also be able to search across the Internet and make that huge wealth of data much more available than it currently is. Predicts that a common user interface will be in operation by the turn of the century
- Date
- 29. 1.1996 19:28:01
-
Sloan, B.G.: Remote access : design implications for the online catalog (1991)
0.01
0.005962253 = product of:
0.020867884 = sum of:
0.0089699915 = weight(_text_:information in 3696) [ClassicSimilarity], result of:
0.0089699915 = score(doc=3696,freq=2.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.13576832 = fieldWeight in 3696, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.0546875 = fieldNorm(doc=3696)
0.011897894 = product of:
0.03569368 = sum of:
0.03569368 = weight(_text_:22 in 3696) [ClassicSimilarity], result of:
0.03569368 = score(doc=3696,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.2708308 = fieldWeight in 3696, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.0546875 = fieldNorm(doc=3696)
0.33333334 = coord(1/3)
0.2857143 = coord(2/7)
- Date
- 8. 1.2007 17:22:42
- Footnote
- Simultaneously published as Enhancing Access to Information: Designing Catalogs for the 21st Century
-
Lazinger, S.S.; Peritz, B.C.: Reader use of a nationwide research library network : local OPAC vs. remote files (1991)
0.01
0.0051105022 = product of:
0.017886758 = sum of:
0.007688564 = weight(_text_:information in 3013) [ClassicSimilarity], result of:
0.007688564 = score(doc=3013,freq=2.0), product of:
0.066068366 = queryWeight, product of:
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.037635546 = queryNorm
0.116372846 = fieldWeight in 3013, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
1.7554779 = idf(docFreq=20772, maxDocs=44218)
0.046875 = fieldNorm(doc=3013)
0.0101981945 = product of:
0.030594582 = sum of:
0.030594582 = weight(_text_:22 in 3013) [ClassicSimilarity], result of:
0.030594582 = score(doc=3013,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.23214069 = fieldWeight in 3013, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.046875 = fieldNorm(doc=3013)
0.33333334 = coord(1/3)
0.2857143 = coord(2/7)
- Date
- 22. 2.1999 13:06:18
- Source
- Information technology and libraries. 10(1991), S.192-200
-
Lewontin, A.: Intracampus sharing of online resources by end users (1991)
0.00
0.004348321 = product of:
0.030438244 = sum of:
0.030438244 = weight(_text_:retrieval in 3108) [ClassicSimilarity], result of:
0.030438244 = score(doc=3108,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.26736724 = fieldWeight in 3108, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0625 = fieldNorm(doc=3108)
0.14285715 = coord(1/7)
- Abstract
- Describes the cooperative efforts of computer centre staff and library staff at Bentley College, Massachusetts, to create end user interfaces to enable the locally loaded data bases on the on-line catalogue to be searched off-campus by remote users as well as by library users on campus. Describes the success obtained using 2 data bases: LEXIS and Dow Jones News Retrieval Service
-
Gottswinter, E.; Mönnich, M.W.: Brücken bauen zwischen EDV-Systemen : Einführung in die SR-Normen (1994)
0.00
0.004348321 = product of:
0.030438244 = sum of:
0.030438244 = weight(_text_:retrieval in 8358) [ClassicSimilarity], result of:
0.030438244 = score(doc=8358,freq=2.0), product of:
0.11384433 = queryWeight, product of:
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.037635546 = queryNorm
0.26736724 = fieldWeight in 8358, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.024915 = idf(docFreq=5836, maxDocs=44218)
0.0625 = fieldNorm(doc=8358)
0.14285715 = coord(1/7)
- Abstract
- Explains the basic principles of the ISO Search and Retrieve (SR) standard which facilitates the searching and retrieval of data from computers via electronic networks regardless of the hardware and software used. Provides an introduction to SR and addresses the parameters of SR servies. Abstract Syntax Notation 1 and the preliminary implementation of an SR Update Service in the KARIN cataloguing system
-
Eberl, U.: UMTS++ : Perspektiven (2001)
0.00
0.0034302555 = product of:
0.024011787 = sum of:
0.024011787 = product of:
0.07203536 = sum of:
0.07203536 = weight(_text_:29 in 6124) [ClassicSimilarity], result of:
0.07203536 = score(doc=6124,freq=2.0), product of:
0.13239008 = queryWeight, product of:
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.037635546 = queryNorm
0.5441145 = fieldWeight in 6124, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5176873 = idf(docFreq=3565, maxDocs=44218)
0.109375 = fieldNorm(doc=6124)
0.33333334 = coord(1/3)
0.14285715 = coord(1/7)
- Date
- 31.12.1996 19:29:41
-
Petry, W.: Datenreisen billiger : wie man Telekommunikationskosten sparen kann (1994)
0.00
0.0033993984 = product of:
0.023795787 = sum of:
0.023795787 = product of:
0.07138736 = sum of:
0.07138736 = weight(_text_:22 in 8109) [ClassicSimilarity], result of:
0.07138736 = score(doc=8109,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.5416616 = fieldWeight in 8109, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.109375 = fieldNorm(doc=8109)
0.33333334 = coord(1/3)
0.14285715 = coord(1/7)
- Source
- Cogito. 10(1994) H.4, S.17-22
-
Matthews, J.R.; Parker, M.R.: Local Area Networks and Wide Area Networks for libraries (1995)
0.00
0.0033993984 = product of:
0.023795787 = sum of:
0.023795787 = product of:
0.07138736 = sum of:
0.07138736 = weight(_text_:22 in 2656) [ClassicSimilarity], result of:
0.07138736 = score(doc=2656,freq=2.0), product of:
0.13179328 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.037635546 = queryNorm
0.5416616 = fieldWeight in 2656, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.109375 = fieldNorm(doc=2656)
0.33333334 = coord(1/3)
0.14285715 = coord(1/7)
- Date
- 30.11.1995 20:53:22
