[Gzz-commits] manuscripts ./gzigzag.bib Alph1/alph.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Tuomas J. Lukka <address@hidden>        03/09/22 11:45:40

Modified files:
        .              : gzigzag.bib 
        Alph1          : alph.rst 

Log message:
        Sync

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/gzigzag.bib.diff?tr1=1.138&tr2=1.139&r1=text&r2=text
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/Alph1/alph.rst.diff?tr1=1.7&tr2=1.8&r1=text&r2=text

Patches:
Index: manuscripts/Alph1/alph.rst
diff -u manuscripts/Alph1/alph.rst:1.7 manuscripts/Alph1/alph.rst:1.8
--- manuscripts/Alph1/alph.rst:1.7      Mon Sep 22 04:25:03 2003
+++ manuscripts/Alph1/alph.rst  Mon Sep 22 11:45:40 2003
@@ -33,8 +33,6 @@
 Introduction
 ============
 
-XXX Live text [fraser90live]_ (unix grep -> editable, through remembering 
source - 
-by some unix gurus, in Software Practice & Experience)
 
 ...  Starting point: [nelson99xanalogicalneeded]_, where no references to 
tumblers &c are made.
 
@@ -43,15 +41,125 @@
 
 Udanax ...
 
-Referential fluid media
-=======================
+Text Models
+===========
+
+text as bitmap is discussed in the OHCO reference...
+
+Sequence of characters
+----------------------
+
+The OHCO text model
+-------------------
+
+Conception of "text" is slightly different from ours!!!
+
+- about representing *formatting* or *structure* of text - 
+  SGML and stuff.
+
+Gives models:
+
+- Text as bitmap
+- Text as a stream of characters
+- Text as characters and formatting instructions
+- Text as page layout
+- Text as a stream of content objects
+
+TEI!
+
+- recognizes problem of multiple hierarchies -- which RFM solves
+  (to a degree)
+
+- versioning
+
+    - claims useful, see e.g. chapter changing place
+
+    - however, if changes place *and* name, ???
+
+- BIG CLAIM: 
+
+    Text *is* an ordered hierarchy of content objects
+
+Uses quotation 
+
+    The trouble with "What You See Is What You Get"
+    is that "What You See Is All You've Got."
+
+    - Brian Kernighan
+
+As an example
+
+...
+
+SEE ALSO CRITIQUES IN SAME : 
+
+- Selber: [selberxxohcoconcerns]_
+
+    - too restrictive, no context of text, &c
+
+- Hill (not so relevant for us, I think)
+
+- Dicks [dicksxxohcothird]_
+
+    - graphics
+
+       - separate
+
+       - relationship bad
+
+       - intertwingled graphics and text!!
+
+    - typefaces &c
+       
+       - may be part of message sometimes
+
+    - large example
+
+       - immutable relations between text and graphics
+         found desirable by actual writers to get their
+         message across best
+
+- to summarize (tjl) all non-AI models have their limits!
+
+Live text
+---------
+
+Live text [fraser90live]_ (unix grep -> editable, through remembering source )
+
+Referential fluid media (RFM)
+-----------------------------
 
 The abstraction of the fundamental idea of Xanalogical 
 systems described in [nelson99xanalogicalneeded]_
 is, formally,
 
+As discussed by Nelson [nelson99xanalogicalneeded]_, 
+the most fundamental and secret idea
+of the Xanalogical model was to endow each unit of "fluid media" 
+(i.e. character of text, 
+pixel of image, sample of sound, pixel in a frame in a video) 
+with a permanent, universal
+identifier.
+
 Advantages
 
+- searching for transclusions
+
+    - copies retain identity
+
+- better understanding of versions
+
+    - visualizations
+
+    - may allow better merge algorithms!
+
+- non-breaking links - ?
+
+- transcopyright, transclusions to other contexts - ?
+
+    - content-based micropayment
+
+
 Downsides
 
 - increased resource consumption for text (for images, sound, ... it's 
unnoticeable)
@@ -60,20 +168,18 @@
 
 - central servers, content fetching, performance, ...
 
-    - we present
+    - we present an alternative solution
+
 
 Making an implementation of referential fluid media practical: Two concrete 
models
 
==================================================================================
 
-In this section, we present two different 
+In this section, we present two different directions that the basic RFM model
+can be taken towards, and argue that these different directions are suited
+for different types of media.
 
-As discussed by Nelson [nelson99xanalogicalneeded]_, 
-the most fundamental and secret idea
-of the Xanalogical model was to endow each unit of "fluid media" 
-(i.e. character of text, 
-pixel of image, sample of sound, pixel in a frame in a video) 
-with a permanent, universal
-identifier.
+- implemented: we flatten it to OHCO, with spans of letters being
+  OHCO content objects
 
 Content-addressed RFM (CARFM)
 -------------------------------------------------
@@ -146,6 +252,10 @@
 
     - cannot really do damage, as comparison is applied to *both* id *and* 
content
 
+- Transcopyright and micropayments not possible.
+
+    - direct tradeoff: *either* you need central servers and a big
+      framework, *or* you don't get these.
 
 Operability in a real-world context
 ===================================
@@ -207,6 +317,19 @@
 
 One of the major missing pieces in the Alph Fluid Media Model
 is support for web pages. Due to the variability of
+
+Future work
+
+- SVG and RFM
+
+    - could we approach what is dreamed of in [dicksxxohcothird]_?
+
+- Other alternatives: OHCO, but with permanent objects down to 
+  character level
+
+    - advantage: larger structure than a letter has its id
+
+    - "Who collected this information" ...
 
 
 ...
Index: manuscripts/gzigzag.bib
diff -u manuscripts/gzigzag.bib:1.138 manuscripts/gzigzag.bib:1.139
--- manuscripts/gzigzag.bib:1.138       Mon Sep 22 04:25:03 2003
+++ manuscripts/gzigzag.bib     Mon Sep 22 11:45:39 2003
@@ -6115,6 +6115,44 @@
  }
 
 @comment Text
+
address@hidden,
+    author = {Steven J. DeRose and  David G. Durand and  Elli Mylonas and 
Allen H. Renear},
+    title = "What is Text, Really?",
+    journal = "Journal of Computing in Higher Education",
+    volume = "1",
+    issue = "2",
+    pages = "3-26",
+    year = "1990"
+    }
+
address@hidden,
+    author = {Steven J. DeRose and  David G. Durand and  Elli Mylonas and 
Allen H. Renear},
+    title = "(Reprint:) What is Text, Really?",
+    journal = "SIGDOC Asterisk Journal of Computer Documentation",
+    volume = "21",
+    issue = "3",
+    year = "???!!!"
+}
+
address@hidden,
+    author = {Stuart A. Selber},
+    title = "The OHCO Model of Text: Merits and Concerns",
+    journal = "SIGDOC Asterisk Journal of Computer Documentation",
+    volume = "21",
+    issue = "3",
+    year = "???!!!"
+    }
+
address@hidden,
+    author = {R. Stanley Dicks},
+    title = {Third Commentary on "What is Text, Really?"},
+    journal = "SIGDOC Asterisk Journal of Computer Documentation",
+    volume = "21",
+    issue = "3",
+    year = "???!!!"
+    }
+
 @article{ fraser90live,
     author = "C. Fraser and B. Krishnamurthy",
     title = "Live Text",