Search (13 results, page 1 of 1)

0.03406465 = product of:
  0.102193944 = sum of:
    0.102193944 = product of:
      0.20438789 = sum of:
        0.20438789 = weight(_text_:2002 in 4051) [ClassicSimilarity], result of:
          0.20438789 = score(doc=4051,freq=7.0), product of:
            0.19223301 = queryWeight, product of:
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.04484573 = queryNorm
            1.0632299 = fieldWeight in 4051, product of:
              2.6457512 = tf(freq=7.0), with freq of:
                7.0 = termFreq=7.0
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.09375 = fieldNorm(doc=4051)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Year

2002

0.01486703 = product of:
  0.04460109 = sum of:
    0.04460109 = product of:
      0.08920218 = sum of:
        0.08920218 = weight(_text_:2002 in 6562) [ClassicSimilarity], result of:
          0.08920218 = score(doc=6562,freq=3.0), product of:
            0.19223301 = queryWeight, product of:
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.04484573 = queryNorm
            0.46403155 = fieldWeight in 6562, product of:
              1.7320508 = tf(freq=3.0), with freq of:
                3.0 = termFreq=3.0
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.0625 = fieldNorm(doc=6562)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Year

2002

0.01486703 = product of:
  0.04460109 = sum of:
    0.04460109 = product of:
      0.08920218 = sum of:
        0.08920218 = weight(_text_:2002 in 6962) [ClassicSimilarity], result of:
          0.08920218 = score(doc=6962,freq=3.0), product of:
            0.19223301 = queryWeight, product of:
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.04484573 = queryNorm
            0.46403155 = fieldWeight in 6962, product of:
              1.7320508 = tf(freq=3.0), with freq of:
                3.0 = termFreq=3.0
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.0625 = fieldNorm(doc=6962)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Year

2002

0.010126629 = product of:
  0.030379886 = sum of:
    0.030379886 = product of:
      0.06075977 = sum of:
        0.06075977 = weight(_text_:22 in 4806) [ClassicSimilarity], result of:
          0.06075977 = score(doc=4806,freq=2.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.38690117 = fieldWeight in 4806, 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=4806)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

22. 3.2008 12:21:28

0.010126629 = product of:
  0.030379886 = sum of:
    0.030379886 = product of:
      0.06075977 = sum of:
        0.06075977 = weight(_text_:22 in 8) [ClassicSimilarity], result of:
          0.06075977 = score(doc=8,freq=2.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.38690117 = fieldWeight in 8, 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=8)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

22.10.2006 18:22:51

0.0070886402 = product of:
  0.02126592 = sum of:
    0.02126592 = product of:
      0.04253184 = sum of:
        0.04253184 = weight(_text_:22 in 1517) [ClassicSimilarity], result of:
          0.04253184 = score(doc=1517,freq=2.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.2708308 = fieldWeight in 1517, 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=1517)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

0.0050633145 = product of:
  0.015189943 = sum of:
    0.015189943 = product of:
      0.030379886 = sum of:
        0.030379886 = weight(_text_:22 in 671) [ClassicSimilarity], result of:
          0.030379886 = score(doc=671,freq=2.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.19345059 = fieldWeight in 671, 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=671)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Footnote

Referate und Materialien der Veranstaltungen: 'Internet in Öffentlichen Bibliotheken II, 25.-27.6.1998, Germershausen bei Göttingen' und 'Neue Informationstechnologien in der Fachstellenarbeit, 22.-24.6.1998, Nürnberg'

0.004291742 = product of:
  0.012875226 = sum of:
    0.012875226 = product of:
      0.025750453 = sum of:
        0.025750453 = weight(_text_:2002 in 1796) [ClassicSimilarity], result of:
          0.025750453 = score(doc=1796,freq=4.0), product of:
            0.19223301 = queryWeight, product of:
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.04484573 = queryNorm
            0.13395438 = fieldWeight in 1796, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.015625 = fieldNorm(doc=1796)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Footnote

Unlike muck of the professional library literature, Net Effects is not an open-aimed embrace of technology. Block even suggests that it is helpful to have a Luddite or two an each library staff to identify the setbacks associated with technological advances in the library. Each of the book's 10 chapters deals with one Internet-related problem, such as "Chapter 4-The Shifted Librarian: Adapting to the Changing Expectations of Our Wired (and Wireless) Users," or "Chapter 8-Up to Our Ears in Lawyers: Legal Issues Posed by the Net." For each of these 10 problems, multiple solutions are offered. For example, for "Chapter 9-Disappearing Data," four solutions are offered. These include "Link-checking," "Have a technological disaster plan," "Advise legislators an the impact proposed laws will have," and "Standards for preservation of digital information." One article is given to explicate each of these four solutions. A short bibliography of recommended further reading is also included for each chapter. Block provides a short introduction to each chapter, and she comments an many of the entries. Some of these comments seem to be intended to provide a research basis for the proposed solutions, but they tend to be vague generalizations without citations, such as, "We know from research that students would rather ask each other for help than go to adults. We can use that (p. 91 )." The original publication dates of the entries range from 1997 to 2002, with the bulk falling into the 2000-2002 range. At up to 6 years old, some of the articles seem outdated, such as a 2000 news brief announcing the creation of the first "customizable" public library Web site (www.brarydog.net). These critiques are not intended to dismiss the volume entirely. Some of the entries are likely to find receptive audiences, such as a nuts-and-bolts instructive article for making Web sites accessible to people with disabilities. "Providing Equitable Access," by Cheryl H. Kirkpatrick and Catherine Buck Morgan, offers very specific instructions, such as how to renovate OPAL workstations to suit users with "a wide range of functional impairments." It also includes a useful list of 15 things to do to make a Web site readable to most people with disabilities, such as, "You can use empty (alt) tags (alt="') for images that serve a purely decorative function. Screen readers will skip empty (alt) tags" (p. 157). Information at this level of specificity can be helpful to those who are faced with creating a technological solution for which they lack sufficient technical knowledge or training.

0.0040506516 = product of:
  0.012151955 = sum of:
    0.012151955 = product of:
      0.02430391 = sum of:
        0.02430391 = weight(_text_:22 in 2426) [ClassicSimilarity], result of:
          0.02430391 = score(doc=2426,freq=2.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.15476047 = fieldWeight in 2426, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=2426)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

0.0040506516 = product of:
  0.012151955 = sum of:
    0.012151955 = product of:
      0.02430391 = sum of:
        0.02430391 = weight(_text_:22 in 2428) [ClassicSimilarity], result of:
          0.02430391 = score(doc=2428,freq=2.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.15476047 = fieldWeight in 2428, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=2428)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

0.00303472 = product of:
  0.00910416 = sum of:
    0.00910416 = product of:
      0.01820832 = sum of:
        0.01820832 = weight(_text_:2002 in 1832) [ClassicSimilarity], result of:
          0.01820832 = score(doc=1832,freq=2.0), product of:
            0.19223301 = queryWeight, product of:
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.04484573 = queryNorm
            0.09472004 = fieldWeight in 1832, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.015625 = fieldNorm(doc=1832)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Footnote

Rez. in: nfd - Information 54(2003) H.6, S.378-379 (T. Mandl): "Im Oktober 2001 fand erstmals eine Tagung mit dem Titel "Web Intelligence" statt. Ist dies nun eine neue Disziplin oder der Versuch analog zu "Artificial Intelligence" und "Computational Intelligence" ein neues Modewort zu kreieren? Geht es um den Einsatz sogenannter intelligenter Verfahren, um mit dem Internet umgehen zu können oder erscheint das Internet als "emerging global brain" (Goertzel 2002), also als eine unerschöpfliche Quelle von Wissen, die nur geschickt ausgebeutet werden muss? Kommt also die Intelligenz aus dem Web oder dient die Intelligenz als Werkzeug für das Web? Der Tagungsband ist seit Anfang 2003 verfügbar und bietet nun den Anlass, diesen Begriff anhand der darin präsentierten Inhalte zu bewerten. Die Herausgeber führen in ihrem einleitenden Artikel gleich die Abkürzung WI ein und versuchen tatsächlich "Web Intelligence" als neue Sub-Disziplin der Informatik zu etablieren. Zu diesem Zweck greifen sie auch auf die Anzahl der Nachweise für diese Phrase in Suchmaschinen zu. Zwar lieferten die Systeme angeblich Zahlen von über einer Million (S. 4), aber dies überzeugt sicher noch niemanden, das Studium der WI aufzunehmen. Allerdings weist dieses Vorgehen schon auf einen Kern der WI hin: man versucht, aus dem im Web gespeicherten Wissen neues Wissen zu generieren. Damit wäre man sehr nahe am Data oder eben Web-Mining, jedoch geht die Definition der Autoren darüber hinaus. Sie wollen WI verstanden wissen als die Anwendung von Künstlicher Intelligenz sowie Informationstechnologie im Internet (S. 2). Da nun Künstliche Intelligenz bei allen Meinungsverschiedenheiten sicherlich nicht ohne Informationstechnologie denkbar ist, wirkt die Definition nicht ganz überzeugend. Allerdings beschwichtigen die Autoren im gleichen Atemzug und versichern, diese Definition solle ohnehin keine Forschungsrichtung ausschließen. Somit bietet sich eher eine Umfangsdefinition an. Diese solle die wichtigsten Stoßrichtungen des Buchs und damit auch der Tagung umfassen. Als Ausgangspunkt dient dazu auch eine Liste der Herausgeber (S. 7f.), die hier aber etwas modifiziert wird: - Grundlagen von Web Informationssystemen (Protokolle, Technologien, Standards) - Web Information Retrieval, WebMining und Farming - Informationsmanagement unter WebBedingungen - Mensch-Maschine Interaktion unter Web-Bedingungen (hier "HumanMedia Engineering" S. XII) Eine grobe Einteilung wie diese ist zwar übersichtlich, führt aber zwangsläufig zu Ouerschnittsthemen. In diesem Fall zählt dazu das Semantic Web, an dem momentan sehr intensiv geforscht wird. Das Semantic Web will das Unbehagen mit der Anarchie im Netz und daraus folgenden Problemen für die Suchmaschinen überwinden, indem das gesamte Wissen im Web auch explizit als solches gekennzeichnet wird. Tauchen auf einer WebSeite zwei Namen auf und einer ist der des Autors und der andere der eines Sponsors, so erlauben neue Technologien, diese auch als solche zu bezeichnen. Noch wichtiger, wie in einer Datenbank sollen nun Abfragen möglich sein, welche andere Seiten aus dem Web liefen, die z.B. den gleichen Sponsor, aber einen anderen Autor haben. Dieser Thematik widmen sich etwa Hendler & Feigenbaum. Das Semantic Web stellt ein Ouerschnittsthema dar, da dafür neue Technologien (Mizoguchi) und ein neuartiges Informationsmanagement erforderlich sind (z.B. Stuckenschmidt & van Harmelen), die Suchverfahren angepasst werden und natürlich auch auf die Benutzer neue Herausforderungen zukommen. Diesem Aspekt, inwieweit Benutzer solche Anfragen überhaupt stellen werden, widmet sich in diesem Band übrigens niemand ernsthaft. Im Folgenden sollen die einzelnen Themengebiete anhand der im Band enthaltenen Inhalte näher bestimmt werden, bevor abschließend der Versuch eines Resümees erfolgt.

0.00303472 = product of:
  0.00910416 = sum of:
    0.00910416 = product of:
      0.01820832 = sum of:
        0.01820832 = weight(_text_:2002 in 2073) [ClassicSimilarity], result of:
          0.01820832 = score(doc=2073,freq=2.0), product of:
            0.19223301 = queryWeight, product of:
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.04484573 = queryNorm
            0.09472004 = fieldWeight in 2073, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.28654 = idf(docFreq=1652, maxDocs=44218)
              0.015625 = fieldNorm(doc=2073)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Footnote

There is some debate over what exactly constitutes a native XML database. Bourret (2003) favors the wider definition; other authors such as the Butler Group (2002) restrict the use of the term to databases systems designed and built solely for storage and manipulation of XML. Two examples of the lauer (Tamino and eXist) are covered in detailed chapters here but also included in this section is the embedded XML database system, Berkeley DB XML, considered by makers Sleepycat Software to be "native" in that it is capable of storing XML natively but built an top of the Berkeley DB engine. To the uninitiated, the revelation that schemas and DTDs are not required by either Tamino or eXist might seem a little strange. Tamino implements "loose coupling" where the validation behavior can be set to "strict," "lax" (i.e., apply only to parts of a document) or "skip" (no checking), in eXist, schemas are simply optional. Many DTDs and schemas evolve as the XML documents are acquired and so these may adhere to slightly different schemas, thus the database should support queries an similar documents that do not share the same structune. In fact, because of the difficulties in mappings between XML and database (especially relational) schemas native XML databases are very useful for storage of semi-structured data, a point not made in either chapter. The chapter an embedded databases represents a "third way," being neither native nor of the XML-enabled relational type. These databases run inside purpose-written applications and are accessed via an API or similar, meaning that the application developer does not need to access database files at the operating system level but can rely an supplied routines to, for example, fetch and update database records. Thus, end-users do not use the databases directly; the applications do not usually include ad hoc end-user query tools. This property renders embedded databases unsuitable for a large number of situations and they have become very much a niche market but this market is growing rapidly. Embedded databases share an address space with the application so the overhead of calls to the server is reduced, they also confer advantages in that they are easier to deploy, manage and administer compared to a conventional client-server solution. This chapter is a very good introduction to the subject, primers an generic embedded databases and embedded XML databases are helpfully provided before the author moves to an overview of the Open Source Berkeley system. Building an embedded database application makes far greater demands an the software developer and the remainder of the chapter is devoted to consideration of these programming issues.

0.0028642432 = product of:
  0.008592729 = sum of:
    0.008592729 = product of:
      0.017185459 = sum of:
        0.017185459 = weight(_text_:22 in 91) [ClassicSimilarity], result of:
          0.017185459 = score(doc=91,freq=4.0), product of:
            0.1570421 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04484573 = queryNorm
            0.109432176 = fieldWeight in 91, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.015625 = fieldNorm(doc=91)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Classification

303.48/33 22 (LoC)

DDC

303.48/33 22 (LoC)