Search (2 results, page 1 of 1)

0.09212028 = product of:
  0.13818042 = sum of:
    0.070336305 = weight(_text_:storage in 907) [ClassicSimilarity], result of:
      0.070336305 = score(doc=907,freq=2.0), product of:
        0.23366846 = queryWeight, product of:
          5.4488444 = idf(docFreq=516, maxDocs=44218)
          0.04288404 = queryNorm
        0.30100897 = fieldWeight in 907, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.4488444 = idf(docFreq=516, maxDocs=44218)
          0.0390625 = fieldNorm(doc=907)
    0.021676896 = weight(_text_:retrieval in 907) [ClassicSimilarity], result of:
      0.021676896 = score(doc=907,freq=2.0), product of:
        0.12972058 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.04288404 = queryNorm
        0.16710453 = fieldWeight in 907, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0390625 = fieldNorm(doc=907)
    0.03164172 = weight(_text_:systems in 907) [ClassicSimilarity], result of:
      0.03164172 = score(doc=907,freq=4.0), product of:
        0.13179013 = queryWeight, product of:
          3.0731742 = idf(docFreq=5561, maxDocs=44218)
          0.04288404 = queryNorm
        0.24009174 = fieldWeight in 907, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.0731742 = idf(docFreq=5561, maxDocs=44218)
          0.0390625 = fieldNorm(doc=907)
    0.014525489 = product of:
      0.029050978 = sum of:
        0.029050978 = weight(_text_:22 in 907) [ClassicSimilarity], result of:
          0.029050978 = score(doc=907,freq=2.0), product of:
            0.1501726 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04288404 = queryNorm
            0.19345059 = fieldWeight in 907, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=907)
      0.5 = coord(1/2)
  0.6666667 = coord(4/6)

Abstract

Knowledge-containing documents and data about knowledge have been handled in stable environments by bureaucratic systems using very stable knowledge ontologies. These systems, though not always very effective in such environments, will become highly ineffective in environments where knowledge has to be updated and replaced frequently. Moreover, organizations in such dynamic environments also use knowledge from extemal resources extensively. This makes the development of a stable ontology for knowledge storage and retrieval particularly complicated. This paper describes eight context classes of knowledge ontology development and explores elements of a method for ontology development. These classes are based an the differences in contexts defined along three dimensions: knowledge dynamics, complexity and social dispersion. Ontology development matches these contexts and ontology needs defined by (logical and social) structure and ontology maturity. The classification framework and methodology are applied to two cases. The first case illustrates a descriptive use of our framework to characterize ontology development in an academic environment. The second case illustrates a normative use of our framework. The method proposed seemed to be empirically valid and rich and be useful for detecting options for ontology improvement.

Source

Knowledge management: organization competence and methodolgy. Proceedings of the Fourth International ISMICK Symposium, 21-22 October 1996, Netherlands. Ed.: J.F. Schreinemakers

0.08007109 = product of:
  0.16014218 = sum of:
    0.09847082 = weight(_text_:storage in 2840) [ClassicSimilarity], result of:
      0.09847082 = score(doc=2840,freq=2.0), product of:
        0.23366846 = queryWeight, product of:
          5.4488444 = idf(docFreq=516, maxDocs=44218)
          0.04288404 = queryNorm
        0.42141256 = fieldWeight in 2840, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.4488444 = idf(docFreq=516, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2840)
    0.030347655 = weight(_text_:retrieval in 2840) [ClassicSimilarity], result of:
      0.030347655 = score(doc=2840,freq=2.0), product of:
        0.12972058 = queryWeight, product of:
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.04288404 = queryNorm
        0.23394634 = fieldWeight in 2840, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.024915 = idf(docFreq=5836, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2840)
    0.031323705 = weight(_text_:systems in 2840) [ClassicSimilarity], result of:
      0.031323705 = score(doc=2840,freq=2.0), product of:
        0.13179013 = queryWeight, product of:
          3.0731742 = idf(docFreq=5561, maxDocs=44218)
          0.04288404 = queryNorm
        0.23767869 = fieldWeight in 2840, 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=2840)
  0.5 = coord(3/6)

Abstract

Until the 1980s, the handling of documentary information in business was usually split up among 4 unrelated independent departments: the library; archives; secretarial services; and reproduction/printing. The introduction of new technology allows the integration of these operations into a single system; comprising subsystems for: production of internal documents; acquisition and storage of external documents; information retrieval; archive creation and maintenance; and circulation of information between departments, based on local computer networks. In reality, not many businesses are making use of technology available to set up such integrated systems because of the lack of common standards for equipment and software, which makes internal and external communication unreliable. This problem may be resolved in the near future, as a result of discussions now in progress at international level.