Search (3 results, page 1 of 1)

0.015731411 = product of:
  0.031462822 = sum of:
    0.031462822 = product of:
      0.12585129 = sum of:
        0.12585129 = weight(_text_:author's in 4898) [ClassicSimilarity], result of:
          0.12585129 = score(doc=4898,freq=2.0), product of:
            0.33900294 = queryWeight, product of:
              6.7201533 = idf(docFreq=144, maxDocs=44218)
              0.050445713 = queryNorm
            0.3712395 = fieldWeight in 4898, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.7201533 = idf(docFreq=144, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4898)
      0.25 = coord(1/4)
  0.5 = coord(1/2)

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.

0.014308298 = product of:
  0.028616596 = sum of:
    0.028616596 = product of:
      0.057233192 = sum of:
        0.057233192 = weight(_text_:w in 3228) [ClassicSimilarity], result of:
          0.057233192 = score(doc=3228,freq=4.0), product of:
            0.19223882 = queryWeight, product of:
              3.8108058 = idf(docFreq=2659, maxDocs=44218)
              0.050445713 = queryNorm
            0.2977192 = fieldWeight in 3228, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.8108058 = idf(docFreq=2659, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3228)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

"Will Google Amerika mit einem Netz aus W-LAN-Notspots überziehen und auf diesem Weg zu einem eigenständigem InternetService-Provider (ISP) werden? Diese schon länger kolportierte Spekulation meint das US-amerikanische Wirtschafts-Magazin "Business 2.0" nun belegen zu können: Google kaufe seit einem Jahr in aller Ruhe brachliegende Übertragungskabel von anderen Zugangs-Anbietern. Sobald die Infrastruktur stehe, so das Gerücht, werde Google in Großstädten flächendeckend einen Internet-Zugang via Funk anbieten. Das Magazin hat das Angebot GoogIeNET getauft. Ortsbezogene Werbung Der eigentliche Clou am möglichen GoogIeNET: Es könnte kostenlos nutzbar sein - oder zumindest nur ein symbolisches Eintrittsgeld zum Internet verlangen. Google wird nämlichbeim Funk-Surfen wahrscheinlich Werbung einblenden, die auf den Aufenthaltsort des Users abgestimmt ist. Würde jemand in einem Einkaufszentrum den Service nutzen, so der Gedanke, erhielte er in den Google-Ads Hinweise zu den Sonderangeboten der einzelnen Läden. Die Technik im Hintergrund soll dabei Feeva, eine auf Notspots spezialisierte Firma aus San Francisco liefern. Eine Partnerschaft zwischen der Suchmaschine und Feeva existiert schon. In San Francisco schalteten die Funkspezialisten einen kostenlosen Hotspot in einem Shopping-Bezirk - und der wird von Google gesponsert. Die gekauften Übertragungskabel wären für Google auch in anderer Hinsicht hilfreich: Die Suchmaschine müsste Service Provider nicht mehr für den verursachten Traffic bezahlen, sondern könnte die Daten über die eigenen Leitungen versenden."

0.0101174945 = product of:
  0.020234989 = sum of:
    0.020234989 = product of:
      0.040469978 = sum of:
        0.040469978 = weight(_text_:w in 3813) [ClassicSimilarity], result of:
          0.040469978 = score(doc=3813,freq=2.0), product of:
            0.19223882 = queryWeight, product of:
              3.8108058 = idf(docFreq=2659, maxDocs=44218)
              0.050445713 = queryNorm
            0.21051927 = fieldWeight in 3813, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.8108058 = idf(docFreq=2659, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3813)
      0.5 = coord(1/2)
  0.5 = coord(1/2)