Search (7 results, page 1 of 1)

0.041326467 = product of:
  0.20663233 = sum of:
    0.20663233 = weight(_text_:inc in 2236) [ClassicSimilarity], result of:
      0.20663233 = score(doc=2236,freq=2.0), product of:
        0.2573945 = queryWeight, product of:
          6.0549803 = idf(docFreq=281, maxDocs=44218)
          0.042509552 = queryNorm
        0.80278456 = fieldWeight in 2236, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0549803 = idf(docFreq=281, maxDocs=44218)
          0.09375 = fieldNorm(doc=2236)
  0.2 = coord(1/5)

Imprint

Medford, NJ : Learned Information, Inc.

0.041326467 = product of:
  0.20663233 = sum of:
    0.20663233 = weight(_text_:inc in 7912) [ClassicSimilarity], result of:
      0.20663233 = score(doc=7912,freq=2.0), product of:
        0.2573945 = queryWeight, product of:
          6.0549803 = idf(docFreq=281, maxDocs=44218)
          0.042509552 = queryNorm
        0.80278456 = fieldWeight in 7912, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0549803 = idf(docFreq=281, maxDocs=44218)
          0.09375 = fieldNorm(doc=7912)
  0.2 = coord(1/5)

Imprint

White Plains, NY : Knowledge Industry Publications, Inc.

0.024107104 = product of:
  0.12053552 = sum of:
    0.12053552 = weight(_text_:inc in 3955) [ClassicSimilarity], result of:
      0.12053552 = score(doc=3955,freq=2.0), product of:
        0.2573945 = queryWeight, product of:
          6.0549803 = idf(docFreq=281, maxDocs=44218)
          0.042509552 = queryNorm
        0.46829098 = fieldWeight in 3955, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0549803 = idf(docFreq=281, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3955)
  0.2 = coord(1/5)

Imprint

Medford, NJ : Learned Information Inc.

0.009215132 = product of:
  0.04607566 = sum of:
    0.04607566 = product of:
      0.09215132 = sum of:
        0.09215132 = weight(_text_:22 in 2974) [ClassicSimilarity], result of:
          0.09215132 = score(doc=2974,freq=2.0), product of:
            0.14886121 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.042509552 = 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.2 = coord(1/5)

Source

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

0.008537469 = product of:
  0.042687345 = sum of:
    0.042687345 = product of:
      0.08537469 = sum of:
        0.08537469 = weight(_text_:management in 2973) [ClassicSimilarity], result of:
          0.08537469 = score(doc=2973,freq=2.0), product of:
            0.14328322 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.042509552 = queryNorm
            0.5958457 = fieldWeight in 2973, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.125 = fieldNorm(doc=2973)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Source

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

0.008537469 = product of:
  0.042687345 = sum of:
    0.042687345 = product of:
      0.08537469 = sum of:
        0.08537469 = weight(_text_:management in 6499) [ClassicSimilarity], result of:
          0.08537469 = score(doc=6499,freq=8.0), product of:
            0.14328322 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.042509552 = queryNorm
            0.5958457 = fieldWeight in 6499, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0625 = fieldNorm(doc=6499)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Abstract

Reports from the 1st International Conference on Information and Knowledge Management, Baltimore, Maryland, 8-11 Nov. 92. This is intended to start an annual series of meetings for researchers and practioners in retrieval, database management and artificial intelligence. The papers presented covered the categories of knowledge base / database integrating; document processing; temporal deductive logic software engineering; hypertext; object-oriented databases; database models; transaction management and query optimisation; classification-based database systems and knowledge representation and expert systems

0.0016007755 = product of:
  0.0080038775 = sum of:
    0.0080038775 = product of:
      0.016007755 = sum of:
        0.016007755 = weight(_text_:management in 1262) [ClassicSimilarity], result of:
          0.016007755 = score(doc=1262,freq=2.0), product of:
            0.14328322 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.042509552 = queryNorm
            0.11172107 = fieldWeight in 1262, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1262)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Abstract

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.