Search (3 results, page 1 of 1)

  • × author_ss:"Lynch, C.A."
  • × language_ss:"e"
  • × year_i:[1990 TO 2000}
  1. Lynch, C.A.; Preston, C.M.: Describing and classifying networked information resources (1992) 0.03
    0.027504025 = product of:
      0.05500805 = sum of:
        0.05500805 = product of:
          0.1100161 = sum of:
            0.1100161 = weight(_text_:22 in 2974) [ClassicSimilarity], result of:
              0.1100161 = score(doc=2974,freq=2.0), product of:
                0.17771997 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.050750602 = 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.5 = coord(1/2)
    
    Source
    Electronic networking: research, applications, and policy. 2(1992) no.1, S.10-22
  2. Lynch, C.A.: Building the infrastructure of resource sharing : union catalogs, distributed search, and cross database linkage (1997) 0.03
    0.025637524 = product of:
      0.05127505 = sum of:
        0.05127505 = product of:
          0.1025501 = sum of:
            0.1025501 = weight(_text_:assessment in 1506) [ClassicSimilarity], result of:
              0.1025501 = score(doc=1506,freq=2.0), product of:
                0.2801951 = queryWeight, product of:
                  5.52102 = idf(docFreq=480, maxDocs=44218)
                  0.050750602 = queryNorm
                0.36599535 = fieldWeight in 1506, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  5.52102 = idf(docFreq=480, maxDocs=44218)
                  0.046875 = fieldNorm(doc=1506)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Effective resourcesharing presupposes an infrastructure which permits users to locate materials of interest in both print and electronic formats. 2 approaches for providing this are union catalogues and Z39.50 based distributed search systems and computer to computer information retrieval protocols. The advantages and limitations of each approach are considered, paying particular attention to a relaistic assessment of Z39.50 implementations. Argues that the union catalogue is far from obsolete and the 2 approaches should be considered complementary rather than competitive. Technologies to create links between the bibliographic apparatus of catalogues and abstracting and indexing databases and primary content in electronic form, such as the new Serial Item and Contribution Identifier (SICI) standard are also discussed as key elements in the infrastructure to support resource sharing
  3. Lynch, C.A.: ¬The Z39.50 information retrieval standard : part I: a strategic view of its past, present and future (1997) 0.01
    0.012818762 = product of:
      0.025637524 = sum of:
        0.025637524 = product of:
          0.05127505 = sum of:
            0.05127505 = weight(_text_:assessment in 1262) [ClassicSimilarity], result of:
              0.05127505 = score(doc=1262,freq=2.0), product of:
                0.2801951 = queryWeight, product of:
                  5.52102 = idf(docFreq=480, maxDocs=44218)
                  0.050750602 = queryNorm
                0.18299767 = fieldWeight in 1262, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  5.52102 = idf(docFreq=480, maxDocs=44218)
                  0.0234375 = fieldNorm(doc=1262)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    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.