6 |
[ref. some missing links for the Web -paper]. (dangling link?). Many of |
[ref. some missing links for the Web -paper]. (dangling link?). Many of |
7 |
these problems were solved, or at least dealt with, in advanced hypermedia |
these problems were solved, or at least dealt with, in advanced hypermedia |
8 |
systems -- even predating the Web. Today such solutions may be used within a |
systems -- even predating the Web. Today such solutions may be used within a |
9 |
site, i.e. the system running a particular set of Web pages / a Web |
site, i.e. the system running a particular set of Web pages (sometimes |
10 |
application may handle links internally quite differently from the HTML |
called a Web application) may handle links internally quite differently from |
11 |
form, that it used to deliver the content to the browser. This, however, does |
the HTML form, that it used to deliver the content to the browser. This, |
12 |
not help when linking to or from other sites (systems). Here, a look |
however, does not help when linking to or from other sites (systems). Here, |
13 |
is taken at some of the hypermedia systems with advanced link management, to |
a look is taken at some of the hypermedia systems with advanced link |
14 |
be compared with the gzz/storm-xu approach presented. |
management, to be compared with the gzz/storm-xu approach presented. |
15 |
|
|
16 |
|
(general OHS first? like this?) Pioneering open hypermedia systems (OHSs), |
17 |
|
such as Microcosm (and?), addressed the linking problems (i.e.?) of large |
18 |
|
archives by separating the links from the documents and stroring them on |
19 |
|
dedicated linkbases [ref]. |
20 |
|
|
21 |
|
(initially misunderstood: The term "generic links" is used to refer to |
22 |
|
links (in Microcosm) relating to general content that can apppear in |
23 |
|
numerous specific locations [HymE-book, check e.g. 393!]) |
24 |
|
|
25 |
|
>#gzz> "The dangling link problem occurs when a position or document |
26 |
|
dependant |
27 |
|
+link anchors occurs in a document that has been moved or deleted without |
28 |
|
the |
29 |
|
+hypermedia document management system, or hyperbase, being informed." |
30 |
|
>#gzz> benja: i thought of searching these phrases they have used for the |
31 |
|
+stuff you/we address, link management, dangling links etc. and discussing |
32 |
|
+them in general. but it does seem that microcosm would deserve a specific |
33 |
|
+mention still |
34 |
|
<benja:#gzz> ok, seems both good |
35 |
|
*** irc.oulu.fi Monday January 20 2003 -- 18: 00 +02:00 |
36 |
|
>#gzz> and the (xanalogical?) solution to the dangling link problem seems |
37 |
|
very |
38 |
|
+elegant |
39 |
|
>#gzz> i.e. if a document moves you don't have to inform the hyperbase |
40 |
|
about |
41 |
|
+it, as the references are always location independent? |
42 |
|
note: |
43 |
|
<benja:#gzz> yes, that was my *first* thought when you quoted above |
44 |
|
<benja:#gzz> but actually, you have to inform the hyperbase (index) |
45 |
|
<benja:#gzz> of the new transclusions |
46 |
|
>#gzz> hm |
47 |
|
<benja:#gzz> ? |
48 |
|
>#gzz> hemppah and tuomasl were discussing the index, and transclusions |
49 |
|
>#gzz> i didn't quite know how the index works, just that it's some .. |
50 |
|
well |
51 |
|
+index that's there as a part of the transclusion implementation |
52 |
|
>#gzz> but good point |
53 |
|
<benja:#gzz> hm, don't you understand what it does or how it does it? |
54 |
|
>#gzz> i made a note for myself (not in the article) to work on this |
55 |
|
>#gzz> more the "how"-question, i guess |
56 |
|
|