Search (7 results, page 1 of 1)

0.1284842 = product of:
  0.2569684 = sum of:
    0.20547324 = weight(_text_:objects in 3968) [ClassicSimilarity], result of:
      0.20547324 = score(doc=3968,freq=6.0), product of:
        0.33668926 = queryWeight, product of:
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.06334615 = queryNorm
        0.6102756 = fieldWeight in 3968, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.046875 = fieldNorm(doc=3968)
    0.05149517 = weight(_text_:22 in 3968) [ClassicSimilarity], result of:
      0.05149517 = score(doc=3968,freq=2.0), product of:
        0.22182742 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06334615 = queryNorm
        0.23214069 = fieldWeight in 3968, 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=3968)
  0.5 = coord(2/4)

Abstract

We present a declarative language for the construction of hypertext views on databases. The language is based on an object-oriented data model and a simple hypertext model with reference and inclusion links. A hypertext view specification consists in a collection of parameterized node schemes which specify how to construct node and links instances from the database contents. We show how this language can express different issues in hypertext view design. These include: the direct mapping of objects to nodes; the construction of complex nodes based on sets of objects; the representation of polymorphic sets of objects; and the representation of tree and graph structures. We have defined sublanguages corresponding to particular database models (relational, semantic, object-oriented) and implemented tools to generate Web views for these database models

Date

21.10.2000 15:01:22

0.03460042 = product of:
  0.13840169 = sum of:
    0.13840169 = weight(_text_:objects in 4959) [ClassicSimilarity], result of:
      0.13840169 = score(doc=4959,freq=2.0), product of:
        0.33668926 = queryWeight, product of:
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.06334615 = queryNorm
        0.41106653 = fieldWeight in 4959, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4959)
  0.25 = coord(1/4)

Abstract

The concept of a system combining information in both textual and pictorial format was first suggested by Vannevar Bush in 1945. The present hypermedia system was originally developed by Tim Berners Lee at CERN in 1989 and provides access to brief documents, which are interlinked and contain text, images, sound and video. The system has become widely available through the WWW, which enables users to 'navigate' through related information. Recent developments include the ability to view objects in virtual reality and the automatic generation of document links

0.01977167 = product of:
  0.07908668 = sum of:
    0.07908668 = weight(_text_:objects in 5215) [ClassicSimilarity], result of:
      0.07908668 = score(doc=5215,freq=2.0), product of:
        0.33668926 = queryWeight, product of:
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.06334615 = queryNorm
        0.23489517 = fieldWeight in 5215, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.315071 = idf(docFreq=590, maxDocs=44218)
          0.03125 = fieldNorm(doc=5215)
  0.25 = coord(1/4)

Abstract

The reader of a hypertext document in a web environment, if maximum use of the document is to be obtained, must visualize the overall structure of the paths through the document as well as the document space. Graphic visualization displays of this space, produced to assist in navigation, are classified into four groups, and Heo and Hirtle compare three of these classes as to their effectiveness. Distortion displays expand regions of interest while relatively diminishing the detail of the remaining regions. This technique will show both local detail and global structure. Zoom techniques use a series of increasingly focused displays of smaller and smaller areas, and can reduce cogitative overload, but do not provide an easy movement to other parts of the total space. Expanding outline displays use a tree structure to allow movement through a hierarchy of documents, but if the organization has a wide horizontal structure, or is not particularly hierarchical in nature such display can break down. Three dimensional layouts, which are not evaluated here, place objects by location in three space, providing more information and freedom. However, the space must be represented in two dimensions resulting in difficulty in visually judging depth, size and positioning. Ten students were assigned to each of eight groups composed of viewers of the three techniques and an unassisted control group using either a large (583 selected pages) or a small (50 selected pages) web space. Sets of 10 questions, which were designed to elicit the use of a visualization tool, were provided for each space. Accuracy and time spent were extracted from a log file. Users views were also surveyed after completion. ANOVA shows significant differences in accuracy and time based upon the visualization tool in use. A Tukey test shows zoom accuracy to be significantly less than expanding outline and zoom time to be significantly greater than both the outline and control groups. Size significantly affected accuracy and time, but had no interaction with tool type. While the expanding tool class out performed zoom and distortion, its performance was not significantly different from the control group.

0.017165057 = product of:
  0.06866023 = sum of:
    0.06866023 = weight(_text_:22 in 2740) [ClassicSimilarity], result of:
      0.06866023 = score(doc=2740,freq=2.0), product of:
        0.22182742 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06334615 = queryNorm
        0.30952093 = fieldWeight in 2740, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0625 = fieldNorm(doc=2740)
  0.25 = coord(1/4)

Date

1. 8.1996 22:08:06

0.017165057 = product of:
  0.06866023 = sum of:
    0.06866023 = weight(_text_:22 in 3594) [ClassicSimilarity], result of:
      0.06866023 = score(doc=3594,freq=2.0), product of:
        0.22182742 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06334615 = queryNorm
        0.30952093 = fieldWeight in 3594, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0625 = fieldNorm(doc=3594)
  0.25 = coord(1/4)

Date

1. 8.1996 22:08:06

0.015019425 = product of:
  0.0600777 = sum of:
    0.0600777 = weight(_text_:22 in 5860) [ClassicSimilarity], result of:
      0.0600777 = score(doc=5860,freq=2.0), product of:
        0.22182742 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06334615 = queryNorm
        0.2708308 = fieldWeight in 5860, 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=5860)
  0.25 = coord(1/4)

Date

1. 8.1996 22:08:06

0.010728161 = product of:
  0.042912643 = sum of:
    0.042912643 = weight(_text_:22 in 2738) [ClassicSimilarity], result of:
      0.042912643 = score(doc=2738,freq=2.0), product of:
        0.22182742 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.06334615 = queryNorm
        0.19345059 = fieldWeight in 2738, 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=2738)
  0.25 = coord(1/4)

Date

22. 3.2009 12:51:47