[Gzz-commits] manuscripts/storm link_management.txt

[Toni Alatalo at Univ. of Oulu]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Toni Alatalo at Univ. of Oulu <address@hidden>  03/01/21 
03:12:45

Modified files:
        storm          : link_management.txt 

Log message:
        some more explanations, notes

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/link_management.txt.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

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