Search (66 results, page 4 of 4)

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 4288) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=4288,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 4288, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=4288)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Journal of the American Society for Information Science. 51(2000) no.1, S.5-13

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 4811) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=4811,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 4811, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=4811)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Library hi tech. 19(2001) no.1, S.63-76

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 2024) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=2024,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 2024, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=2024)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Information processing and management. 44(2008) no.1, S.82-91

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 4434) [ClassicSimilarity], result of:
          0.007856515 = score(doc=4434,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 4434, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4434)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Abstract

Digital libraries need to facilitate the use of digital information in a variety of settings. One approach to making information useful is to enable its application to situations unanticipated by the original author. Walden's Path is designed to enable authors to collect, organize, and annotate information from on-line collections for presentaion to their readers. Experiences with the use of Walden's Paths in high-school classrooms have identified 4 needs/issues: (1) better support for the gradual authoring of paths by teachers, (2) support for student authoring of paths including the ability for students to collaborate on paths, (3) more obvious distinction between content of the original source materials and that added by the path author, and (4) support for maintaining paths over an evolving set of source documents. These observed needs have driven the development of new versions of Walden's Paths. Additionally, the experiences with path authoring have led to a conceptualization of metadocuments, documents whose components include complete documents, as a general domain where issues of collaboration, intellectual property, and maintenance are decidedly different form traditional document publication

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 2594) [ClassicSimilarity], result of:
          0.007856515 = score(doc=2594,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 2594, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2594)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Date

1. 1.2009 10:02:19

1.4492337E-4 = product of:
  0.0033332373 = sum of:
    0.0033332373 = product of:
      0.0066664745 = sum of:
        0.0066664745 = weight(_text_:1 in 3719) [ClassicSimilarity], result of:
          0.0066664745 = score(doc=3719,freq=4.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.11514856 = fieldWeight in 3719, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0234375 = fieldNorm(doc=3719)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Abstract

A natural language interface to an expert system is a program that enables the user to communicate with the system in English or some other human language. It is designed to spare the user from learning some special programming language or command input language. Today this input is almost always typed at a keyboard or assembled with a mouse. Only a few research systems understand spoken input and produce spoken output. The precise definition of an expert system is a matter of argument. For the purposes of this article an expert system is a computer system that is capable of providing expert advice or otherwise performing at an expert level, usually in a rather narrow area. An excellent discussion of the controversy surrounding this term is given in Ref. 1. A typical expert system has at least three different kinds of interfaces. Some have four. One interface is designed to understand user queries and commands, another to generate answers and explanations. The knowledge-engineering interface provides a way for a human expert to endow the system with the expertise it needs to function. This may be a natural language interface as well. Some expert systems also produce documents, such as medical case reports or legal wills or petitions for divorce. The first paradigm expert system, Shortliffe's MYCIN system (2), provided natural language interfaces for both the end user and the engineer. The first widely used expert system that Shortliffe developed, ONCOCIN (3, 4), not only provided natural language interfaces for the end user and the knowledge engineer, it also generated the lengthy patient reports required by complex drug trials. In this article we will concentrate mainly an the natural language understanding and generation required to communicate with the end user, but we will also discuss interfaces for the knowledge engineer. We will describe some document generation techniques briefly.

Date

1. 8.2010 19:04:20