Search (7 results, page 1 of 1)

0.018950384 = product of:
  0.07580154 = sum of:
    0.07580154 = weight(_text_:library in 2975) [ClassicSimilarity], result of:
      0.07580154 = score(doc=2975,freq=4.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.57517654 = fieldWeight in 2975, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.109375 = fieldNorm(doc=2975)
  0.25 = coord(1/4)

Imprint

Urbana-Champaign, Ill. : Graduate School of Library and Information Science

Source

Virtual libraries: implications for the research library. Ed.: Brett Sutton u. Charles H. Davis

0.015314223 = product of:
  0.061256893 = sum of:
    0.061256893 = weight(_text_:library in 2973) [ClassicSimilarity], result of:
      0.061256893 = score(doc=2973,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.46481284 = fieldWeight in 2973, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.125 = fieldNorm(doc=2973)
  0.25 = coord(1/4)

Source

The evolution of library automation: management issues and future perspectives. Ed.: Gary M. Pitkin

0.013581533 = product of:
  0.054326132 = sum of:
    0.054326132 = product of:
      0.108652264 = sum of:
        0.108652264 = weight(_text_:22 in 2974) [ClassicSimilarity], result of:
          0.108652264 = score(doc=2974,freq=2.0), product of:
            0.17551683 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.050121464 = queryNorm
            0.61904186 = fieldWeight in 2974, 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=2974)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Source

Electronic networking: research, applications, and policy. 2(1992) no.1, S.10-22

0.011604695 = product of:
  0.04641878 = sum of:
    0.04641878 = weight(_text_:library in 5365) [ClassicSimilarity], result of:
      0.04641878 = score(doc=5365,freq=6.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.3522223 = fieldWeight in 5365, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5365)
  0.25 = coord(1/4)

Imprint

Illinois : University at Urbana-Champaign, Graduate School of Library and Information Science

Source

Emerging communities: integrating networked information into library services. Proceedings of the Clinic on Library Applications of Data Processing, Illinois University at Urbana-Champaign, 4-6 April 1993. Ed.: A.P. Bishop

0.009139037 = product of:
  0.036556147 = sum of:
    0.036556147 = weight(_text_:digital in 1262) [ClassicSimilarity], result of:
      0.036556147 = score(doc=1262,freq=4.0), product of:
        0.19770671 = queryWeight, product of:
          3.944552 = idf(docFreq=2326, maxDocs=44218)
          0.050121464 = queryNorm
        0.18490088 = fieldWeight in 1262, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.944552 = idf(docFreq=2326, 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.

0.0076571116 = product of:
  0.030628446 = sum of:
    0.030628446 = weight(_text_:library in 6499) [ClassicSimilarity], result of:
      0.030628446 = score(doc=6499,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.23240642 = fieldWeight in 6499, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.0625 = fieldNorm(doc=6499)
  0.25 = coord(1/4)

Source

Library hi tech news. 1993, no.102, May, S.7-8

0.0057428335 = product of:
  0.022971334 = sum of:
    0.022971334 = weight(_text_:library in 1506) [ClassicSimilarity], result of:
      0.022971334 = score(doc=1506,freq=2.0), product of:
        0.1317883 = queryWeight, product of:
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.050121464 = queryNorm
        0.17430481 = fieldWeight in 1506, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.6293786 = idf(docFreq=8668, maxDocs=44218)
          0.046875 = fieldNorm(doc=1506)
  0.25 = coord(1/4)

Source

Library trends. 45(1997) no.3, S.448-461