-
Hunt, R.: ATM - protocols and architecture (1996)
0.03
0.028653976 = product of:
0.1146159 = sum of:
0.1146159 = weight(_text_:evolution in 6770) [ClassicSimilarity], result of:
0.1146159 = score(doc=6770,freq=2.0), product of:
0.19585751 = queryWeight, product of:
5.29663 = idf(docFreq=601, maxDocs=44218)
0.03697776 = queryNorm
0.5852004 = fieldWeight in 6770, product of:
1.4142135 = tf(freq=2.0), with freq of:
2.0 = termFreq=2.0
5.29663 = idf(docFreq=601, maxDocs=44218)
0.078125 = fieldNorm(doc=6770)
0.25 = coord(1/4)
- Abstract
- Describes the asynchronous transfer mode (ATM) protocol, technology and architecture, as well as the issues which it is designed to solve. Traces the evolution of ATM and examines the applications for which ATM is likely to be used. Describes comparisons made with alternative networking technologies and matters which require further solution
-
Lynch, C.A.: ¬The Z39.50 information retrieval standard : part I: a strategic view of its past, present and future (1997)
0.01
0.0121568525 = product of:
0.04862741 = sum of:
0.04862741 = weight(_text_:evolution in 1262) [ClassicSimilarity], result of:
0.04862741 = score(doc=1262,freq=4.0), product of:
0.19585751 = queryWeight, product of:
5.29663 = idf(docFreq=601, maxDocs=44218)
0.03697776 = queryNorm
0.24827953 = fieldWeight in 1262, product of:
2.0 = tf(freq=4.0), with freq of:
4.0 = termFreq=4.0
5.29663 = idf(docFreq=601, maxDocs=44218)
0.0234375 = fieldNorm(doc=1262)
0.25 = coord(1/4)
- 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.
-
Petry, W.; Werner, H.-J.: Anwendertraum: Kommunikations- und Retrieval-Software im Vergleich (1993)
0.01
0.0066799684 = product of:
0.026719874 = sum of:
0.026719874 = product of:
0.08015962 = sum of:
0.08015962 = weight(_text_:22 in 4147) [ClassicSimilarity], result of:
0.08015962 = score(doc=4147,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.25 = coord(1/4)
- Source
- Cogito. 9(1993) H.2, S.18-22
-
Petry, W.: Datenreisen billiger : wie man Telekommunikationskosten sparen kann (1994)
0.01
0.0058449726 = product of:
0.02337989 = sum of:
0.02337989 = product of:
0.07013967 = sum of:
0.07013967 = weight(_text_:22 in 8109) [ClassicSimilarity], result of:
0.07013967 = score(doc=8109,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.25 = coord(1/4)
- 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.01
0.0058449726 = product of:
0.02337989 = sum of:
0.02337989 = product of:
0.07013967 = sum of:
0.07013967 = weight(_text_:22 in 2656) [ClassicSimilarity], result of:
0.07013967 = score(doc=2656,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.25 = coord(1/4)
- Date
- 30.11.1995 20:53:22
-
Scheuerer, J.: Onlinebanking (1997)
0.01
0.005009976 = product of:
0.020039905 = sum of:
0.020039905 = product of:
0.060119715 = sum of:
0.060119715 = weight(_text_:22 in 354) [ClassicSimilarity], result of:
0.060119715 = score(doc=354,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.33333334 = coord(1/3)
0.25 = coord(1/4)
- Source
- Com!. 1997, H.8, S.22-24
-
Berezak-Lazarus, N.: ADSL - Auf der Überholspur durch die Multimedia-Welt (1999)
0.01
0.005009976 = product of:
0.020039905 = sum of:
0.020039905 = product of:
0.060119715 = sum of:
0.060119715 = weight(_text_:22 in 5935) [ClassicSimilarity], result of:
0.060119715 = score(doc=5935,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = queryNorm
0.46428138 = fieldWeight in 5935, 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=5935)
0.33333334 = coord(1/3)
0.25 = coord(1/4)
- Footnote
- Rez. in: Internet Professionell 2000, H.2, S.22
-
Cerf, V.G.: Netztechnik (1995)
0.00
0.0041749803 = product of:
0.016699921 = sum of:
0.016699921 = product of:
0.050099764 = sum of:
0.050099764 = weight(_text_:22 in 877) [ClassicSimilarity], result of:
0.050099764 = score(doc=877,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = queryNorm
0.38690117 = fieldWeight in 877, 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=877)
0.33333334 = coord(1/3)
0.25 = coord(1/4)
- Pages
- S.22-31
-
Duhm, U.: Ring frei zur nächsten Runde (1999)
0.00
0.0041749803 = product of:
0.016699921 = sum of:
0.016699921 = product of:
0.050099764 = sum of:
0.050099764 = weight(_text_:22 in 2955) [ClassicSimilarity], result of:
0.050099764 = score(doc=2955,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.33333334 = coord(1/3)
0.25 = coord(1/4)
- Date
- 19. 2.1999 20:21:22
-
Sloan, B.G.: Remote access : design implications for the online catalog (1991)
0.00
0.0029224863 = product of:
0.011689945 = sum of:
0.011689945 = product of:
0.035069834 = sum of:
0.035069834 = weight(_text_:22 in 3696) [ClassicSimilarity], result of:
0.035069834 = score(doc=3696,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.25 = coord(1/4)
- Date
- 8. 1.2007 17:22:42
-
Lazinger, S.S.; Peritz, B.C.: Reader use of a nationwide research library network : local OPAC vs. remote files (1991)
0.00
0.002504988 = product of:
0.010019952 = sum of:
0.010019952 = product of:
0.030059857 = sum of:
0.030059857 = weight(_text_:22 in 3013) [ClassicSimilarity], result of:
0.030059857 = score(doc=3013,freq=2.0), product of:
0.12948982 = queryWeight, product of:
3.5018296 = idf(docFreq=3622, maxDocs=44218)
0.03697776 = 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.25 = coord(1/4)
- Date
- 22. 2.1999 13:06:18
