[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Gzz-commits] manuscripts/storm link_management.txt
From: |
Toni Alatalo |
Subject: |
[Gzz-commits] manuscripts/storm link_management.txt |
Date: |
Mon, 27 Jan 2003 16:13:05 -0500 |
CVSROOT: /cvsroot/gzz
Module name: manuscripts
Changes by: Toni Alatalo <address@hidden> 03/01/27 16:13:05
Modified files:
storm : link_management.txt
Log message:
cleaned, corrected a typo -- where and what to put in article?
CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/storm/link_management.txt.diff?tr1=1.4&tr2=1.5&r1=text&r2=text
Patches:
Index: manuscripts/storm/link_management.txt
diff -u manuscripts/storm/link_management.txt:1.4
manuscripts/storm/link_management.txt:1.5
--- manuscripts/storm/link_management.txt:1.4 Sat Jan 25 16:51:20 2003
+++ manuscripts/storm/link_management.txt Mon Jan 27 16:13:05 2003
@@ -15,7 +15,7 @@
(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
+archives by separating the links from the documents and storing them on
dedicated linkbases [ref]. "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,
@@ -47,10 +47,6 @@
---
->#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
>#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