[Gzz-commits] gzz/doc/pegboard/xu_text--benja peg.rst

[Benja Fallenstein]

CVSROOT:        /cvsroot/gzz
Module name:    gzz
Changes by:     Benja Fallenstein <address@hidden>      03/02/21 09:50:33

Modified files:
        doc/pegboard/xu_text--benja: peg.rst 

Log message:
        split

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/gzz/doc/pegboard/xu_text--benja/peg.rst.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: gzz/doc/pegboard/xu_text--benja/peg.rst
diff -u gzz/doc/pegboard/xu_text--benja/peg.rst:1.1 
gzz/doc/pegboard/xu_text--benja/peg.rst:1.2
--- gzz/doc/pegboard/xu_text--benja/peg.rst:1.1 Mon Feb 17 13:10:15 2003
+++ gzz/doc/pegboard/xu_text--benja/peg.rst     Fri Feb 21 09:50:33 2003
@@ -4,17 +4,15 @@
 
 :Author:       Benja Fallenstein
 :Date:         2003-02-17
-:Revision:     $Revision: 1.1 $
-:Last-Modified: $Date: 2003/02/17 18:10:15 $
+:Revision:     $Revision: 1.2 $
+:Last-Modified: $Date: 2003/02/21 14:50:33 $
 :Type:         Architecture
 :Scope:                Major
 :Status:       Current
 
 
-This PEG proposes two things: First, use random ids 
-instead of Storm blocks for xu text; second, make
-text enfilades a data type disjoint from "media"
-(images, PDF, etc.).
+This PEG proposes to use random ids 
+instead of Storm blocks for xu text.
 
 Storm is good for saving space when transcluding "media"
 in multiple places by refering to a single block
@@ -28,34 +26,14 @@
 
 Let's drop text blocks.
 
-Second, XML-based formats (as well as e.g. YAML or RDF) 
-know plain-text strings, but not images and the like embedded
-in the strings; they refer to images through URIs 
-(but not to text, which they include directly).
-We would like to enhance XML-based formats with Xanalogical
-text and images. For text, it makes sense to have special tags;
-for images, it makes sense to refer to them using Storm URIs
-using the current URI-based transclusion mechanisms.
-
-Giving Xanalogical identities to the character content in an XML file
-seems like a much less intrusive change than using an enfilade format
-which can include e.g. audio as well as characters, so that you could
-say ``<tag>`` *10000 audio units* ``</tag>``.
-
-The two proposals are in one PEG, because they make more sense
-together; if we don't use the same enfilade class for text
-and media, it doesn't seem so strange to handle text through
-a very different mechanism (random ids rather than Storm blocks).
-
 
 Changes
 =======
 
+A new kind of text span is introduced: (uri, offset, string) triples.
 
-Xu text model
--------------
-
-Text spans are (uri, offset, string) triples.
+We will keep the old kind at least for now. (We may reconsider this
+when we have more experience.)
 
 For example, ("urn:urn-5:...", 17, "foo") would be a span
 with offset 17 and length 3 in the 'block' ``urn:urn-5:...``,
@@ -79,25 +57,18 @@
 Finding links is similar, since it is defined in terms of
 finding transclusions.
 
+API changes
+-----------
+
+In ``Span``, ``getScrollBlock()`` will be made optional (may return
+``null``). We still want to use a hashtable when searching for
+overlaps; for that, we'll add ``getScrollId()`` (used as the hashtable
+key -> no two spans with different scroll ids may intersect).
+To determine whether two spans overlap, their ``intersects()`` method
+must be used. 
 
-Interface
----------
+Two text spans as described above overlap iff their ranges overlap
+and the substrings in the overlapping range are equal.
 
-I'd say, let's have enfilades only for text, for now. (We may
-want them for video and audio later, or maybe we won't, but we
-only need them for text right now.) To refer to images or PDFs,
-refer to the Storm URI (once it's registered).
-
-If we move to RDF, we could transclude a PDF as follows:
-Create a node to represent the image; refer to the block
-through a 'load-from' property (the block is a RDF node, by virtue
-of having a URI); also give the page number(s) and coordinates
-you want to transclude, as other properties, if you don't
-want to transclude the whole block.
-
-Then, we don't need a special index for finding the transclusions
-of the PDF inside our space. We can find all transclusions 
-from a Storm block by going to the block's node and following 
-the 'load-from' property backwards.
 
 \- Benja