Search (3 results, page 1 of 1)

  • × author_ss:"Brown, P.J."
  • × theme_ss:"Hypertext"
  1. Brown, P.J.: Higher level hypertext facilities : procedures with arguments (1991) 0.00 
    0.0033826875 = product of:
  0.006765375 = sum of:
    0.006765375 = product of:
      0.01353075 = sum of:
        0.01353075 = weight(_text_:a in 3682) [ClassicSimilarity], result of:
          0.01353075 = score(doc=3682,freq=8.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.25478977 = fieldWeight in 3682, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.078125 = fieldNorm(doc=3682)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    For authors to write and maintain large hyperdocuments, hypertext systems must provide abstractions at a higher level than a link. Presents an axample of such an abstraction: the hypertext equivalent of the procedure call with arguments. Describes why such a facility is needed, and how it has been implemented in the UNIX implementation of the Guide hypertext system
    Type
    a
  2. Brown, P.J.; Brown, H.: Embedded or separate hypertext mark-up : is it an issue? (1995) 0.00 
    0.0023435948 = product of:
  0.0046871896 = sum of:
    0.0046871896 = product of:
      0.009374379 = sum of:
        0.009374379 = weight(_text_:a in 3514) [ClassicSimilarity], result of:
          0.009374379 = score(doc=3514,freq=6.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.17652355 = fieldWeight in 3514, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0625 = fieldNorm(doc=3514)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    Most hypertext systems embed some form of mark up in each hyperdocument in order to represent the hypertext structure. While most document preparation systems use this approach, hypertext researchers say that the structure of a hyperdocument should be separate from its content. Investigates whether the 2 approaches, embedded versus separate, are really at odds with one another, and describes a technology for combining some of the benefits of both
    Type
    a
  3. Brown, P.J.: Using logical objetcs to control hypertext appearence (1991) 0.00 
    0.001674345 = product of:
  0.00334869 = sum of:
    0.00334869 = product of:
      0.00669738 = sum of:
        0.00669738 = weight(_text_:a in 5909) [ClassicSimilarity], result of:
          0.00669738 = score(doc=5909,freq=4.0), product of:
            0.053105544 = queryWeight, product of:
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.046056706 = queryNorm
            0.12611452 = fieldWeight in 5909, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.153047 = idf(docFreq=37942, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5909)
      0.5 = coord(1/2)
  0.5 = coord(1/2)
    Abstract
    It is accepted wisdom that documents should be represented in terms of their logical structure rather than their appearance. Nevertheless most of the popular document processing systems concentrate on appearance rather than structure, mainly because most users opt for a user interface that is interactive, simple and direct. Considers issues related to fonts and other appearance attributes within hypertext documents. Presents the relevant differences between hypertext systems and document preparation systems whose end product is paper Describes schemes for representing appearance through logical structure. The scheme aims to meet the extra needs of hypertext systems, and yet still to be simple enough to attract wide usage.
    Type
    a