Search (14 results, page 1 of 1)

0.024745772 = product of:
  0.049491543 = sum of:
    0.049491543 = product of:
      0.09898309 = sum of:
        0.09898309 = weight(_text_:22 in 2656) [ClassicSimilarity], result of:
          0.09898309 = score(doc=2656,freq=2.0), product of:
            0.1827397 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052184064 = 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.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30.11.1995 20:53:22

0.01633573 = product of:
  0.03267146 = sum of:
    0.03267146 = product of:
      0.06534292 = sum of:
        0.06534292 = weight(_text_:systems in 3162) [ClassicSimilarity], result of:
          0.06534292 = score(doc=3162,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.4074492 = fieldWeight in 3162, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.09375 = fieldNorm(doc=3162)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Computer networks and ISDN systems. 27(1995) no.8, S.1211-1329

0.01633573 = product of:
  0.03267146 = sum of:
    0.03267146 = product of:
      0.06534292 = sum of:
        0.06534292 = weight(_text_:systems in 3208) [ClassicSimilarity], result of:
          0.06534292 = score(doc=3208,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.4074492 = fieldWeight in 3208, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.09375 = fieldNorm(doc=3208)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Computer networks and ISDN systems. 27(1995) no.8, S.1211-1214

0.01633573 = product of:
  0.03267146 = sum of:
    0.03267146 = product of:
      0.06534292 = sum of:
        0.06534292 = weight(_text_:systems in 3209) [ClassicSimilarity], result of:
          0.06534292 = score(doc=3209,freq=8.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.4074492 = fieldWeight in 3209, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.046875 = fieldNorm(doc=3209)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The IOS rererence model of open distributed processing (RM-ODP) consists of: an overview of the reference model, the descriptive model, the prescriptive model, and the architectural semantics. They provide the concepts and rules of distributed processing to ensure openness between interacting distributed application components. Openness is a combination of characteristics: accessibility, heterogeneity, autonomy and distribution. The RM-ODP introduces the concept of viewpoint to describe a system from a particular set of concerns, and hence to deal with the complexity of distributed systems. While all the viewpoints are relevant to the description and design of distributed systems, the computational and engineering models are the ones that bear most directly on the design and implementation of distributed systems. From a distributes software engineering point of view, the computational and engineering viewpoints are again the most important; they reflect the software structure of the distributed application most closely. Concentrates on the computational and engineering viewpoints

Source

Computer networks and ISDN systems. 27(1995) no.8, S.1215-1229

0.012372886 = product of:
  0.024745772 = sum of:
    0.024745772 = product of:
      0.049491543 = sum of:
        0.049491543 = weight(_text_:22 in 3696) [ClassicSimilarity], result of:
          0.049491543 = score(doc=3696,freq=2.0), product of:
            0.1827397 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052184064 = 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.5 = coord(1/2)
  0.5 = coord(1/2)

Date

8. 1.2007 17:22:42

0.011551105 = product of:
  0.02310221 = sum of:
    0.02310221 = product of:
      0.04620442 = sum of:
        0.04620442 = weight(_text_:systems in 7706) [ClassicSimilarity], result of:
          0.04620442 = score(doc=7706,freq=4.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.28811008 = fieldWeight in 7706, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.046875 = fieldNorm(doc=7706)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

In Sept. 1990, the US Dept. of Education's Library Technology and Cooperation Grants Program awarded a three-year grant to the Florida Center for Library Automation (FCLA), an agency of the Florida State University System, to develop software adhering to the ANSI Z39.50 Information Retrieval protocol standard. The Z39.50 software was to operate over the OSI communications protocols and be integrated with FCLA's NOTIS system, which is shared by all 9 state universities in Florida. In order to test the correctness of its Z39.50 software, FCLA sought out other library software developers who would be willing to develop Z39.50 systems of their own. As part of this process, FCLA helped to found the Z39.50 Implementor's Group (ZIG), which has since gone on to improve the standard and promote Z39.50 implementations throughout much of the North American library systems marketplace. Early on in the project, it became apparent that TCP/IP would be a more heavily used communication vehicle for Z39.50 messages than OSI. FCLA expanded its design to include TCP/IP and, by the end of the grant in Sept. 1993, will have a working Z39.50 system that can communicate over both OSI and TCP/IP networks

0.010890487 = product of:
  0.021780973 = sum of:
    0.021780973 = product of:
      0.043561947 = sum of:
        0.043561947 = weight(_text_:systems in 4758) [ClassicSimilarity], result of:
          0.043561947 = score(doc=4758,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.2716328 = fieldWeight in 4758, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0625 = fieldNorm(doc=4758)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Computer networks and ISDN systems. 28(1996) no.3, S.391-400

0.010605331 = product of:
  0.021210661 = sum of:
    0.021210661 = product of:
      0.042421322 = sum of:
        0.042421322 = weight(_text_:22 in 3013) [ClassicSimilarity], result of:
          0.042421322 = score(doc=3013,freq=2.0), product of:
            0.1827397 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052184064 = 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.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 2.1999 13:06:18

0.009529176 = product of:
  0.019058352 = sum of:
    0.019058352 = product of:
      0.038116705 = sum of:
        0.038116705 = weight(_text_:systems in 7911) [ClassicSimilarity], result of:
          0.038116705 = score(doc=7911,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.23767869 = fieldWeight in 7911, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0546875 = fieldNorm(doc=7911)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.009529176 = product of:
  0.019058352 = sum of:
    0.019058352 = product of:
      0.038116705 = sum of:
        0.038116705 = weight(_text_:systems in 1496) [ClassicSimilarity], result of:
          0.038116705 = score(doc=1496,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.23767869 = fieldWeight in 1496, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1496)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Journal of network and systems management. 2(1994) no.3, S.317-322

0.008167865 = product of:
  0.01633573 = sum of:
    0.01633573 = product of:
      0.03267146 = sum of:
        0.03267146 = weight(_text_:systems in 3669) [ClassicSimilarity], result of:
          0.03267146 = score(doc=3669,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.2037246 = fieldWeight in 3669, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.046875 = fieldNorm(doc=3669)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

ASIS '91: Systems understanding people. Proc. of the 54th Ann. Meeting of the ASIS, vol.28, Washington, D.C., 27.-31.10.1991. Ed.: J.-M. Griffiths

0.0068065543 = product of:
  0.013613109 = sum of:
    0.013613109 = product of:
      0.027226217 = sum of:
        0.027226217 = weight(_text_:systems in 8401) [ClassicSimilarity], result of:
          0.027226217 = score(doc=8401,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.1697705 = fieldWeight in 8401, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0390625 = fieldNorm(doc=8401)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Describes a layer model for networks. For each layer, one or more services are defined, and for each service a protocol is specified. 2 OSI application level protocols have been defined for library services: SR and ILL. The underlying layers are supposed to be OSI services, but some implementations are using TCP/IP, and some are using a mixture of OSI and TCP/IP. The systems based directly on TCP/IP can not communicate with those based purely on OSI. Discusses the pros and cons for choosing OSI or TCP/IP. Gateways between the OSI and TCP/IP networks are needed. The ISO protocol SR and the ANSI protocol Z39.50 are both 'search and retrieve' protocols. The SR is almost a subst of Z39.50, but they may become identical in the future. There is only one protocol for interlibrary loan, the ISO ILL protocol. It covers 3 models of interlibrary loan and all services connected with ILL. Other services such as Explain, Scan and Update are presently being discussed in ISO TC 46. Discusses the needs of the library community for network services such as file transfer, remote login, directories and electronic mail

0.0068065543 = product of:
  0.013613109 = sum of:
    0.013613109 = product of:
      0.027226217 = sum of:
        0.027226217 = weight(_text_:systems in 5155) [ClassicSimilarity], result of:
          0.027226217 = score(doc=5155,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.1697705 = fieldWeight in 5155, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5155)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Hinich and Molyneux review the literature of internet measurement and note three results consistently to be found in network traffic studies. These are "self-similarity," "long-range dependence," by which is meant that events in one time are correlated with events in a previous time and remain so through longer time periods than expected, and "heavy tails" by which they mean many small connections with low byte counts and a few long connections with large byte counts. The literature also suggests that conventional time series analysis is not helpful for network analysis. Using a single day's traffic at the Berkeley National Labs web server, cumulated TCP flows were collected, log transforms were used with the adding of .01 to all values allowing log transforms of the zero values, and providing a distribution that overcomes the heavy tail problem. However, Hinich's bicorrelation test for nonlinearity using overlapping moving windows found strong evidence of nonlinear structures. Time series analysis assumes linear systems theory and thus additivity and scalability. Spectral analysis should provide large peaks at the lowest frequencies if long range dependence is present since the power spectrum would go to infinity if the frequency goes to zero. This does not occur and so long range dependence must be questioned, at least until it is determined what effect other OSI layers may have on the TCP data.

0.0040839324 = product of:
  0.008167865 = sum of:
    0.008167865 = product of:
      0.01633573 = sum of:
        0.01633573 = weight(_text_:systems in 1262) [ClassicSimilarity], result of:
          0.01633573 = score(doc=1262,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.1018623 = fieldWeight in 1262, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1262)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.