Search (242 results, page 1 of 13)

0.06842672 = product of:
  0.13685344 = sum of:
    0.13685344 = product of:
      0.4105603 = sum of:
        0.4105603 = weight(_text_:3a in 1826) [ClassicSimilarity], result of:
          0.4105603 = score(doc=1826,freq=2.0), product of:
            0.43830654 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.051699217 = queryNorm
            0.93669677 = fieldWeight in 1826, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.078125 = fieldNorm(doc=1826)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)

Source

http://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=5&ved=0CDQQFjAE&url=http%3A%2F%2Fdigbib.ubka.uni-karlsruhe.de%2Fvolltexte%2Fdocuments%2F3131107&ei=HzFWVYvGMsiNsgGTyoFI&usg=AFQjCNE2FHUeR9oQTQlNC4TPedv4Mo3DaQ&sig2=Rlzpr7a3BLZZkqZCXXN_IA&bvm=bv.93564037,d.bGg&cad=rja

0.054741375 = product of:
  0.10948275 = sum of:
    0.10948275 = product of:
      0.32844824 = sum of:
        0.32844824 = weight(_text_:3a in 230) [ClassicSimilarity], result of:
          0.32844824 = score(doc=230,freq=2.0), product of:
            0.43830654 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.051699217 = queryNorm
            0.7493574 = fieldWeight in 230, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.0625 = fieldNorm(doc=230)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)

Source

https%3A%2F%2Ftannerlectures.utah.edu%2F_documents%2Fa-to-z%2Fp%2Fpopper80.pdf&usg=AOvVaw3f4QRTEH-OEBmoYr2J_c7H

0.049055643 = product of:
  0.09811129 = sum of:
    0.09811129 = sum of:
      0.05608411 = weight(_text_:searching in 4649) [ClassicSimilarity], result of:
        0.05608411 = score(doc=4649,freq=2.0), product of:
          0.2091384 = queryWeight, product of:
            4.0452914 = idf(docFreq=2103, maxDocs=44218)
            0.051699217 = queryNorm
          0.26816747 = fieldWeight in 4649, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.0452914 = idf(docFreq=2103, maxDocs=44218)
            0.046875 = fieldNorm(doc=4649)
      0.04202718 = weight(_text_:22 in 4649) [ClassicSimilarity], result of:
        0.04202718 = score(doc=4649,freq=2.0), product of:
          0.18104185 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051699217 = queryNorm
          0.23214069 = fieldWeight in 4649, 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=4649)
  0.5 = coord(1/2)

Abstract

More and more cultural heritage institutions publish their collections, vocabularies and metadata on the Web. The resulting Web of linked cultural data opens up exciting new possibilities for searching and browsing through these cultural heritage collections. We report on ongoing work in which we investigate the estimation of relevance in this Web of Culture. We study existing measures of semantic distance and how they apply to two use cases. The use cases relate to the structured, multilingual and multimodal nature of the Culture Web. We distinguish between measures using the Web, such as Google distance and PMI, and measures using the Linked Data Web, i.e. the semantic structure of metadata vocabularies. We perform a small study in which we compare these semantic distance measures to human judgements of relevance. Although it is too early to draw any definitive conclusions, the study provides new insights into the applicability of semantic distance measures to the Web of Culture, and clear starting points for further research.

Date

26.12.2011 13:40:22

0.03751494 = product of:
  0.07502988 = sum of:
    0.07502988 = sum of:
      0.028042056 = weight(_text_:searching in 1752) [ClassicSimilarity], result of:
        0.028042056 = score(doc=1752,freq=2.0), product of:
          0.2091384 = queryWeight, product of:
            4.0452914 = idf(docFreq=2103, maxDocs=44218)
            0.051699217 = queryNorm
          0.13408373 = fieldWeight in 1752, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.0452914 = idf(docFreq=2103, maxDocs=44218)
            0.0234375 = fieldNorm(doc=1752)
      0.04698782 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
        0.04698782 = score(doc=1752,freq=10.0), product of:
          0.18104185 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051699217 = queryNorm
          0.2595412 = fieldWeight in 1752, product of:
            3.1622777 = tf(freq=10.0), with freq of:
              10.0 = termFreq=10.0
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.0234375 = fieldNorm(doc=1752)
  0.5 = coord(1/2)

Content

"Although the Dewey Decimal Classification is currently available on the web to subscribers as WebDewey and Abridged WebDewey in the OCLC Connexion service and in an XML version to licensees, OCLC does not provide any "web services" based on the DDC. By web services, we mean presentation of the DDC to other machines (not humans) for uses such as searching, browsing, classifying, mapping, harvesting, and alerting. In order to build web-accessible services based on the DDC, several elements have to be considered. One of these elements is the design of an appropriate Uniform Resource Identifier (URI) structure for Dewey. The design goals of mapping the entity model of the DDC into an identifier space can be summarized as follows: * Common locator for Dewey concepts and associated resources for use in web services and web applications * Use-case-driven, but not directly related to and outlasting a specific use case (persistency) * Retraceable path to a concept rather than an abstract identification, reusing a means of identification that is already present in the DDC and available in existing metadata. We have been working closely with our colleagues in the OCLC Office of Research (especially Andy Houghton as well as Eric Childress, Diane Vizine-Goetz, and Stu Weibel) on a preliminary identifier syntax. The basic identifier format we are currently exploring is: http://dewey.info/{aspect}/{object}/{locale}/{type}/{version}/{resource} where * {aspect} is the aspect associated with an {object}-the current value set of aspect contains "concept", "scheme", and "index"; additional ones are under exploration * {object} is a type of {aspect} * {locale} identifies a Dewey translation * {type} identifies a Dewey edition type and contains, at a minimum, the values "edn" for the full edition or "abr" for the abridged edition * {version} identifies a Dewey edition version * {resource} identifies a resource associated with an {object} in the context of {locale}, {type}, and {version}
Some examples of identifiers for concepts follow: <http://dewey.info/concept/338.4/en/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the English-language version of Edition 22. <http://dewey.info/concept/338.4/de/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the German-language version of Edition 22. <http://dewey.info/concept/333.7-333.9/> This identifier is used to retrieve or identify the 333.7-333.9 concept across all editions and language versions. <http://dewey.info/concept/333.7-333.9/about.skos> This identifier is used to retrieve a SKOS representation of the 333.7-333.9 concept (using the "resource" element). There are several open issues at this preliminary stage of development: Use cases: URIs need to represent the range of statements or questions that could be submitted to a Dewey web service. Therefore, it seems that some general questions have to be answered first: What information does an agent have when coming to a Dewey web service? What kind of questions will such an agent ask? Placement of the {locale} component: It is still an open question if the {locale} component should be placed after the {version} component instead (<http://dewey.info/concept/338.4/edn/22/en>) to emphasize that the most important instantiation of a Dewey class is its edition, not its language version. From a services point of view, however, it could make more sense to keep the current arrangement, because users are more likely to come to the service with a present understanding of the language version they are seeking without knowing the specifics of a certain edition in which they are trying to find topics. Identification of other Dewey entities: The goal is to create a locator that does not answer all, but a lot of questions that could be asked about the DDC. Which entities are missing but should be surfaced for services or user agents? How will those services or agents interact with them? Should some entities be rendered in a different way as presented? For example, (how) should the DDC Summaries be retrievable? Would it be necessary to make the DDC Manual accessible through this identifier structure?"

0.03738941 = product of:
  0.07477882 = sum of:
    0.07477882 = product of:
      0.14955764 = sum of:
        0.14955764 = weight(_text_:searching in 3167) [ClassicSimilarity], result of:
          0.14955764 = score(doc=3167,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.7151132 = fieldWeight in 3167, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.125 = fieldNorm(doc=3167)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.03421336 = product of:
  0.06842672 = sum of:
    0.06842672 = product of:
      0.20528015 = sum of:
        0.20528015 = weight(_text_:3a in 4388) [ClassicSimilarity], result of:
          0.20528015 = score(doc=4388,freq=2.0), product of:
            0.43830654 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.051699217 = queryNorm
            0.46834838 = fieldWeight in 4388, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4388)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)

Footnote

Vgl. unter: https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&cad=rja&uact=8&ved=2ahUKEwizweHljdbcAhVS16QKHXcFD9QQFjABegQICRAB&url=https%3A%2F%2Fwww.researchgate.net%2Fpublication%2F271200105_Die_Autonomie_des_Menschen_und_der_Maschine_-_gegenwartige_Definitionen_von_Autonomie_zwischen_philosophischem_Hintergrund_und_technologischer_Umsetzbarkeit_Redigierte_Version_der_Magisterarbeit_Karls&usg=AOvVaw06orrdJmFF2xbCCp_hL26q.

0.03421336 = product of:
  0.06842672 = sum of:
    0.06842672 = product of:
      0.20528015 = sum of:
        0.20528015 = weight(_text_:3a in 5669) [ClassicSimilarity], result of:
          0.20528015 = score(doc=5669,freq=2.0), product of:
            0.43830654 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.051699217 = queryNorm
            0.46834838 = fieldWeight in 5669, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5669)
      0.33333334 = coord(1/3)
  0.5 = coord(1/2)

Content

"Die Englischsprachige Wikipedia verfügt jetzt über mehr als 6 Millionen Artikel. An zweiter Stelle kommt die deutschsprachige Wikipedia mit 2.3 Millionen Artikeln, an dritter Stelle steht die französischsprachige Wikipedia mit 2.1 Millionen Artikeln (via Researchbuzz: Firehose <https://rbfirehose.com/2020/01/24/techcrunch-wikipedia-now-has-more-than-6-million-articles-in-english/> und Techcrunch <https://techcrunch.com/2020/01/23/wikipedia-english-six-million-articles/?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Techcrunch+%28TechCrunch%29&guccounter=1&guce_referrer=aHR0cHM6Ly9yYmZpcmVob3NlLmNvbS8yMDIwLzAxLzI0L3RlY2hjcnVuY2gtd2lraXBlZGlhLW5vdy1oYXMtbW9yZS10aGFuLTYtbWlsbGlvbi1hcnRpY2xlcy1pbi1lbmdsaXNoLw&guce_referrer_sig=AQAAAK0zHfjdDZ_spFZBF_z-zDjtL5iWvuKDumFTzm4HvQzkUfE2pLXQzGS6FGB_y-VISdMEsUSvkNsg2U_NWQ4lwWSvOo3jvXo1I3GtgHpP8exukVxYAnn5mJspqX50VHIWFADHhs5AerkRn3hMRtf_R3F1qmEbo8EROZXp328HMC-o>). 250120 via digithek ch = #fineBlog s.a.: Angesichts der Veröffentlichung des 6-millionsten Artikels vergangene Woche in der englischsprachigen Wikipedia hat die Community-Zeitungsseite "Wikipedia Signpost" ein Moratorium bei der Veröffentlichung von Unternehmensartikeln gefordert. Das sei kein Vorwurf gegen die Wikimedia Foundation, aber die derzeitigen Maßnahmen, um die Enzyklopädie gegen missbräuchliches undeklariertes Paid Editing zu schützen, funktionierten ganz klar nicht. *"Da die ehrenamtlichen Autoren derzeit von Werbung in Gestalt von Wikipedia-Artikeln überwältigt werden, und da die WMF nicht in der Lage zu sein scheint, dem irgendetwas entgegenzusetzen, wäre der einzige gangbare Weg für die Autoren, fürs erste die Neuanlage von Artikeln über Unternehmen zu untersagen"*, schreibt der Benutzer Smallbones in seinem Editorial <https://en.wikipedia.org/wiki/Wikipedia:Wikipedia_Signpost/2020-01-27/From_the_editor> zur heutigen Ausgabe."

0.03271573 = product of:
  0.06543146 = sum of:
    0.06543146 = product of:
      0.13086292 = sum of:
        0.13086292 = weight(_text_:searching in 3231) [ClassicSimilarity], result of:
          0.13086292 = score(doc=3231,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.6257241 = fieldWeight in 3231, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.109375 = fieldNorm(doc=3231)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.03271573 = product of:
  0.06543146 = sum of:
    0.06543146 = product of:
      0.13086292 = sum of:
        0.13086292 = weight(_text_:searching in 3961) [ClassicSimilarity], result of:
          0.13086292 = score(doc=3961,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.6257241 = fieldWeight in 3961, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.109375 = fieldNorm(doc=3961)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.03238018 = product of:
  0.06476036 = sum of:
    0.06476036 = product of:
      0.12952071 = sum of:
        0.12952071 = weight(_text_:searching in 5966) [ClassicSimilarity], result of:
          0.12952071 = score(doc=5966,freq=6.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.61930627 = fieldWeight in 5966, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.0625 = fieldNorm(doc=5966)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

My presentation is about the HILT, High Level Thesaurus Project, which is looking, very roughly speaking, at how we might deal with interoperability problems relating to cross-searching distributed services by subject. The aims of HILT are to study and report on the problem of cross-searching and browsing by subject across a range of communities, services, and service or resource types in the UK given the wide range of subject schemes and associated practices in place

0.028042056 = product of:
  0.05608411 = sum of:
    0.05608411 = product of:
      0.11216822 = sum of:
        0.11216822 = weight(_text_:searching in 3169) [ClassicSimilarity], result of:
          0.11216822 = score(doc=3169,freq=2.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.53633493 = fieldWeight in 3169, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.09375 = fieldNorm(doc=3169)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.028042056 = product of:
  0.05608411 = sum of:
    0.05608411 = product of:
      0.11216822 = sum of:
        0.11216822 = weight(_text_:searching in 940) [ClassicSimilarity], result of:
          0.11216822 = score(doc=940,freq=8.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.53633493 = fieldWeight in 940, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=940)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Traditional on-line search services such as Dialog, DataStar and Lexis provide a wide range of search features (boolean and proximity operators, truncation, etc). This paper discusses the use of these features for effective searching, and argues that these features are required, regardless of advances in search engine technology. The literature on on-line searching is reviewed, identifying features that searchers find desirable for effective searching. A selective survey of current digital libraries available on the Web was undertaken, identifying which search features are present. The survey indicates that current digital libraries do not implement a wide range of search features. For instance: under half of the examples included controlled vocabulary, under half had proximity searching, only one enabled browsing of term indexes, and none of the digital libraries enable searchers to refine an initial search. Suggestions are made for enhancing the search effectiveness of digital libraries; for instance, by providing a full range of search operators, enabling browsing of search terms, enhancement of records with controlled vocabulary, enabling the refining of initial searches, etc.

0.028042056 = product of:
  0.05608411 = sum of:
    0.05608411 = product of:
      0.11216822 = sum of:
        0.11216822 = weight(_text_:searching in 2131) [ClassicSimilarity], result of:
          0.11216822 = score(doc=2131,freq=8.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.53633493 = fieldWeight in 2131, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.046875 = fieldNorm(doc=2131)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This is a preprint to be published in the Extensions & Corrections to the UDC. The paper explains the basic functions of browsing and searching that need to be supported in relation to analytico-synthetic classifications such as Universal Decimal Classification (UDC), irrespective of any specific, real-life implementation. UDC is an example of a semi-faceted system that can be used, for instance, for both post-coordinate searching and hierarchical/facet browsing. The advantages of using a classification for IR, however, depend on the strength of the GUI, which should provide a user-friendly interface to classification browsing and searching. The power of this interface is in supporting visualisation that will 'convert' what is potentially a user-unfriendly indexing language based on symbols, to a subject presentation that is easy to understand, search and navigate. A summary of the basic functions of searching and browsing a classification that may be provided on a user-friendly interface is given and examples of classification browsing interfaces are provided.

0.02801812 = product of:
  0.05603624 = sum of:
    0.05603624 = product of:
      0.11207248 = sum of:
        0.11207248 = weight(_text_:22 in 5449) [ClassicSimilarity], result of:
          0.11207248 = score(doc=5449,freq=2.0), product of:
            0.18104185 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051699217 = queryNorm
            0.61904186 = fieldWeight in 5449, 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=5449)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 2.1997 19:26:34

0.02801812 = product of:
  0.05603624 = sum of:
    0.05603624 = product of:
      0.11207248 = sum of:
        0.11207248 = weight(_text_:22 in 5837) [ClassicSimilarity], result of:
          0.11207248 = score(doc=5837,freq=2.0), product of:
            0.18104185 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051699217 = queryNorm
            0.61904186 = fieldWeight in 5837, 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=5837)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30.11.1996 13:22:37

0.02801812 = product of:
  0.05603624 = sum of:
    0.05603624 = product of:
      0.11207248 = sum of:
        0.11207248 = weight(_text_:22 in 4085) [ClassicSimilarity], result of:
          0.11207248 = score(doc=4085,freq=2.0), product of:
            0.18104185 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051699217 = queryNorm
            0.61904186 = fieldWeight in 4085, 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=4085)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

7.11.1999 18:22:39

0.027409561 = product of:
  0.054819122 = sum of:
    0.054819122 = product of:
      0.109638244 = sum of:
        0.109638244 = weight(_text_:22 in 1936) [ClassicSimilarity], result of:
          0.109638244 = score(doc=1936,freq=10.0), product of:
            0.18104185 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051699217 = queryNorm
            0.6055961 = fieldWeight in 1936, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1936)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Dewey Decimal Classification and Relative Index, Edition 22 (DDC 22) will be issued simultaneously in print and web versions in July 2003. The new edition is the first full print update to the Dewey Decimal Classification system in seven years-it includes several significant updates and many new numbers and topics. DDC 22 also features some fundamental structural changes that have been introduced with the goals of promoting classifier efficiency and improving the DDC for use in a variety of applications in the web environment. Most importantly, the content of the new edition has been shaped by the needs and recommendations of Dewey users around the world. The worldwide user community has an important role in shaping the future of the DDC.

Object

DDC-22

0.026438305 = product of:
  0.05287661 = sum of:
    0.05287661 = product of:
      0.10575322 = sum of:
        0.10575322 = weight(_text_:searching in 1250) [ClassicSimilarity], result of:
          0.10575322 = score(doc=1250,freq=4.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.5056614 = fieldWeight in 1250, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.0625 = fieldNorm(doc=1250)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This article describes a scalable system for searching heterogeneous multilingual collections on the World Wide Web. It details a markup language for describing the characteristics of a search engine and its interface, and a protocol for requesting word translations between languages.

0.026438305 = product of:
  0.05287661 = sum of:
    0.05287661 = product of:
      0.10575322 = sum of:
        0.10575322 = weight(_text_:searching in 1258) [ClassicSimilarity], result of:
          0.10575322 = score(doc=1258,freq=4.0), product of:
            0.2091384 = queryWeight, product of:
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.051699217 = queryNorm
            0.5056614 = fieldWeight in 1258, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.0452914 = idf(docFreq=2103, maxDocs=44218)
              0.0625 = fieldNorm(doc=1258)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Current user interfaces for textual database searching leave much to be desired: individually, they are often confusing, and as a group, they are seriously inconsistent. We propose a four- phase framework for user-interface design: the framework provides common structure and terminology for searching while preserving the distinct features of individual collections and search mechanisms. Users will benefit from faster learning, increased comprehension, and better control, leading to more effective searches and higher satisfaction.

0.024764754 = product of:
  0.049529508 = sum of:
    0.049529508 = product of:
      0.099059016 = sum of:
        0.099059016 = weight(_text_:22 in 3925) [ClassicSimilarity], result of:
          0.099059016 = score(doc=3925,freq=4.0), product of:
            0.18104185 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051699217 = queryNorm
            0.54716086 = fieldWeight in 3925, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=3925)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 7.2006 15:22:28