Search (46 results, page 1 of 3)

0.031115947 = product of:
  0.04667392 = sum of:
    0.02769504 = weight(_text_:information in 7911) [ClassicSimilarity], result of:
      0.02769504 = score(doc=7911,freq=10.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.3035872 = fieldWeight in 7911, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=7911)
    0.01897888 = product of:
      0.03795776 = sum of:
        0.03795776 = weight(_text_:systems in 7911) [ClassicSimilarity], result of:
          0.03795776 = score(doc=7911,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

Abstract

Examined two groups of online catalogue users segregated by their method of access to the system: terminals in the library or remote workstations. An online survey collected demographic data, perceptions on source and terminal accessibility, and information on usage, task variety and search satisfaction. Transaction logs furnished data on browsing behavious, while interviews of both groups provided additional information about remote use. Results indicate that remote use is comparable to traditional use

Imprint

Medford, NJ : Learned Information

Source

Integrating technologies - converging professions: proceedings of the 56th Annual Meeting of the American Society for Information Science, Columbus, OH, 24-28 October 1993. Ed.: S. Bonzi

0.029886318 = product of:
  0.044829477 = sum of:
    0.01415497 = weight(_text_:information in 5082) [ClassicSimilarity], result of:
      0.01415497 = score(doc=5082,freq=2.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.1551638 = fieldWeight in 5082, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0625 = fieldNorm(doc=5082)
    0.030674506 = product of:
      0.061349012 = sum of:
        0.061349012 = weight(_text_:systems in 5082) [ClassicSimilarity], result of:
          0.061349012 = score(doc=5082,freq=4.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = queryNorm
            0.38414678 = fieldWeight in 5082, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0625 = fieldNorm(doc=5082)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Open System Interconnection (OSI) Standard 7498 appeared in 1984. Open systems of PCs and workstations decentralize information processing and divide it between several computers, based on the client-server concept. Relevant terminology is explained, including application protocol, bases of the SR/Z39.50 model, data transmission, search request services, query types, attribute sets, transmission format, transfer syntax, solution models and cooperation between library systems

0.024685455 = product of:
  0.037028182 = sum of:
    0.012385598 = weight(_text_:information in 3696) [ClassicSimilarity], result of:
      0.012385598 = score(doc=3696,freq=2.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.13576832 = fieldWeight in 3696, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3696)
    0.024642585 = product of:
      0.04928517 = sum of:
        0.04928517 = weight(_text_:22 in 3696) [ClassicSimilarity], result of:
          0.04928517 = score(doc=3696,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

Date

8. 1.2007 17:22:42

Footnote

Simultaneously published as Enhancing Access to Information: Designing Catalogs for the 21st Century

0.022414736 = product of:
  0.033622105 = sum of:
    0.010616227 = weight(_text_:information in 7706) [ClassicSimilarity], result of:
      0.010616227 = score(doc=7706,freq=2.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.116372846 = fieldWeight in 7706, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=7706)
    0.023005879 = product of:
      0.046011757 = sum of:
        0.046011757 = weight(_text_:systems in 7706) [ClassicSimilarity], result of:
          0.046011757 = score(doc=7706,freq=4.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

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.021158962 = product of:
  0.03173844 = sum of:
    0.010616227 = weight(_text_:information in 3013) [ClassicSimilarity], result of:
      0.010616227 = score(doc=3013,freq=2.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.116372846 = fieldWeight in 3013, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=3013)
    0.021122215 = product of:
      0.04224443 = sum of:
        0.04224443 = weight(_text_:22 in 3013) [ClassicSimilarity], result of:
          0.04224443 = score(doc=3013,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

Date

22. 2.1999 13:06:18

Source

Information technology and libraries. 10(1991), S.192-200

0.020909652 = product of:
  0.03136448 = sum of:
    0.012385598 = weight(_text_:information in 1496) [ClassicSimilarity], result of:
      0.012385598 = score(doc=1496,freq=2.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.13576832 = fieldWeight in 1496, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1496)
    0.01897888 = product of:
      0.03795776 = sum of:
        0.03795776 = weight(_text_:systems in 1496) [ClassicSimilarity], result of:
          0.03795776 = score(doc=1496,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

Abstract

The rapid growth of the Internet TCP/IP networks has encouraged the deployment of management products based on the Internet's Simple Network Management Protocol (SNMP). However, many organizations, including most telecommunications service providers, continue to define enterprise management solutions based on ISO/CCITT standard management and underlying Common Management Information Protocol (CMIP). Concludes that the key to achieving timely, effective, integrated management is to encourage a transition process aimed away from existing commercial investment in both ISO/CCITT and Internet based management technologies through deployment of common methods and tools which support integration

Source

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

0.02085415 = product of:
  0.031281225 = sum of:
    0.015013612 = weight(_text_:information in 3669) [ClassicSimilarity], result of:
      0.015013612 = score(doc=3669,freq=4.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.16457605 = fieldWeight in 3669, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.046875 = fieldNorm(doc=3669)
    0.016267613 = product of:
      0.032535225 = sum of:
        0.032535225 = weight(_text_:systems in 3669) [ClassicSimilarity], result of:
          0.032535225 = score(doc=3669,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

Abstract

This study aimed to determine if the searching behaviour of remote users of LIAS, Penn State's online catalogue differed from those using the OPAC within the library. More than 1.000 searches done by remote users (those accessing the system via either dial-access or the university's computer network) were compared to more than 1.000 searches done by in-house users. Each search was duplicated step by step and analysed according to a pre-determined set of criteria. Although few dramatic differences were found between the 2 groups, there were enough subtle differences to generate interest. In general, remote users are the more sophisticated searchers, bearing out the assumption that remote users seem to have a better conceptual knowledge of how an information system should operate. On the other hand, they struggle more with the procedural details of how to use the OPAC. Dial-access users seem to constitute a unique group of users: their searches are often quite different than those done by either network or in-house users

Imprint

Medford : Learned Information Inc.

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.018775303 = product of:
  0.05632591 = sum of:
    0.05632591 = product of:
      0.11265182 = sum of:
        0.11265182 = weight(_text_:22 in 4147) [ClassicSimilarity], result of:
          0.11265182 = score(doc=4147,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = queryNorm
            0.61904186 = fieldWeight in 4147, 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=4147)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Cogito. 9(1993) H.2, S.18-22

0.01737846 = product of:
  0.026067689 = sum of:
    0.012511344 = weight(_text_:information in 5155) [ClassicSimilarity], result of:
      0.012511344 = score(doc=5155,freq=4.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.13714671 = fieldWeight in 5155, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5155)
    0.013556344 = product of:
      0.027112689 = sum of:
        0.027112689 = weight(_text_:systems in 5155) [ClassicSimilarity], result of:
          0.027112689 = score(doc=5155,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

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.

Source

Journal of the American Society for Information Science and technology. 54(2003) no.2, S.161-168

0.01642839 = product of:
  0.04928517 = sum of:
    0.04928517 = product of:
      0.09857034 = sum of:
        0.09857034 = weight(_text_:22 in 8109) [ClassicSimilarity], result of:
          0.09857034 = score(doc=8109,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = queryNorm
            0.5416616 = fieldWeight in 8109, 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=8109)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Cogito. 10(1994) H.4, S.17-22

0.01642839 = product of:
  0.04928517 = sum of:
    0.04928517 = product of:
      0.09857034 = sum of:
        0.09857034 = weight(_text_:22 in 2656) [ClassicSimilarity], result of:
          0.09857034 = score(doc=2656,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = 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.33333334 = coord(1/3)

Date

30.11.1995 20:53:22

0.014081477 = product of:
  0.04224443 = sum of:
    0.04224443 = product of:
      0.08448886 = sum of:
        0.08448886 = weight(_text_:22 in 354) [ClassicSimilarity], result of:
          0.08448886 = score(doc=354,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = queryNorm
            0.46428138 = fieldWeight in 354, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=354)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Com!. 1997, H.8, S.22-24

0.014081477 = product of:
  0.04224443 = sum of:
    0.04224443 = product of:
      0.08448886 = sum of:
        0.08448886 = weight(_text_:22 in 5935) [ClassicSimilarity], result of:
          0.08448886 = score(doc=5935,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = queryNorm
            0.46428138 = fieldWeight in 5935, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=5935)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Footnote

Rez. in: Internet Professionell 2000, H.2, S.22

0.0125000235 = product of:
  0.018750034 = sum of:
    0.010616227 = weight(_text_:information in 1262) [ClassicSimilarity], result of:
      0.010616227 = score(doc=1262,freq=8.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.116372846 = fieldWeight in 1262, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1262)
    0.008133806 = product of:
      0.016267613 = sum of:
        0.016267613 = weight(_text_:systems in 1262) [ClassicSimilarity], result of:
          0.016267613 = score(doc=1262,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.6666667 = coord(2/3)

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.
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.

0.011734564 = product of:
  0.03520369 = sum of:
    0.03520369 = product of:
      0.07040738 = sum of:
        0.07040738 = weight(_text_:22 in 877) [ClassicSimilarity], result of:
          0.07040738 = score(doc=877,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = queryNorm
            0.38690117 = fieldWeight in 877, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=877)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Pages

S.22-31

0.011734564 = product of:
  0.03520369 = sum of:
    0.03520369 = product of:
      0.07040738 = sum of:
        0.07040738 = weight(_text_:22 in 2955) [ClassicSimilarity], result of:
          0.07040738 = score(doc=2955,freq=2.0), product of:
            0.1819777 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051966466 = queryNorm
            0.38690117 = fieldWeight in 2955, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=2955)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

19. 2.1999 20:21:22

0.010845075 = product of:
  0.032535225 = sum of:
    0.032535225 = product of:
      0.06507045 = sum of:
        0.06507045 = weight(_text_:systems in 3162) [ClassicSimilarity], result of:
          0.06507045 = score(doc=3162,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.33333334 = coord(1/3)

Source

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

0.010845075 = product of:
  0.032535225 = sum of:
    0.032535225 = product of:
      0.06507045 = sum of:
        0.06507045 = weight(_text_:systems in 3208) [ClassicSimilarity], result of:
          0.06507045 = score(doc=3208,freq=2.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.33333334 = coord(1/3)

Source

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

0.010845075 = product of:
  0.032535225 = sum of:
    0.032535225 = product of:
      0.06507045 = sum of:
        0.06507045 = weight(_text_:systems in 3209) [ClassicSimilarity], result of:
          0.06507045 = score(doc=3209,freq=8.0), product of:
            0.159702 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.051966466 = 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.33333334 = coord(1/3)

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.0094366465 = product of:
  0.02830994 = sum of:
    0.02830994 = weight(_text_:information in 5241) [ClassicSimilarity], result of:
      0.02830994 = score(doc=5241,freq=2.0), product of:
        0.09122598 = queryWeight, product of:
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.051966466 = queryNorm
        0.3103276 = fieldWeight in 5241, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          1.7554779 = idf(docFreq=20772, maxDocs=44218)
          0.125 = fieldNorm(doc=5241)
  0.33333334 = coord(1/3)

Source

Information technology and libraries. 12(1993) no.2, S.227-230