From MAILER-DAEMON Tue Jul 01 03:39:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19XFj5-0000Rh-BT
	for mharc-gzz-dev@gnu.org; Tue, 01 Jul 2003 03:38:55 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19XFiv-0008HS-Do
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 01 Jul 2003 03:38:45 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19XFib-0007IQ-Qc
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 01 Jul 2003 03:38:29 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19XFiN-0006ep-Dr
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 01 Jul 2003 03:38:11 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h617c1SL007190
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 1 Jul 2003 10:38:01 +0300
Received: from localhost (atsoukka@localhost)h617c1fC007186
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 1 Jul 2003 10:38:01 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Tue, 1 Jul 2003 10:38:01 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <Pine.LNX.4.44.0307011026280.6173-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Gzz] MM bundle
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 01 Jul 2003 07:38:52 -0000

Hi,

If somebody hasn't read these yet (fenfire/docs/dartboard/). I'm now three 
days totally unavailable, but when I come back I would be eager to get 
some feedback / read discussion about these.

Hmm... I seem to forgot to write about "special canvases". Canvases / 
papers, which would have special background pattern on top of the 
normal texture. Mudyc has already done that calendar paper. Some patters 
relevant for note taking could be bases fo "mandala" and "vee diagram". I 
reallys should scan some examples of those...

======================
MindMapping on Fenfire
======================

$Id: idea.rst,v 1.1 2003/06/27 10:48:39 humppake Exp $

Structure
=========

- data nodes (may contain arbitrary amount of multiline text or an image)
- paper nodes (identifies paper canvases with unique textures)

Naming connections and storing coordinates needs something
extra... Could connection names and placing coordinates be added
afterwards by reificating connection/statement (*"A is linked to B"*
or *"A is placed on B"*)?

2D structure view
=================

- shows vanishing focus+context network of the plain structure
- if reified statements are used, they should be abstracted
- data nodes are represented by multiline vobs
- paper nodes are represented by vobs with their papers' unique background
- connections between vobs are filleted (`named connections`_?)
- if direction of the connection matters, form of fillet could show the 
direction
- non-connected data nodes could be entered into `floating buffer`_
- some special key / button / action for creating connected / 
non-connected paper node,
  maybe also some `special papers`_ are supported
- nodes from buffer could be connected to accursed node
- nodes could be marked into `marked node list`_
- nodes from marked node list could be linked to accursed node
- when accursed data node is placed on any paper, teared part of that 
paper
  (focused to accursed node) is floating as a buoy
- when a paper node is accursed, teared part of its 2D paper canvas
  (focused to accursed node) is floating as a buoy
- 2D canvas buoys are shown as distorted_
- besides keybindings, mouse / pen could be used with `RMB action switch`_ 
method

.. _`named connections`: 
../naming_filleted_connections--humppake/idea.gen.html
.. _`floating buffer`: ../floating_buffer--humppake/idea.gen.html
.. _`marked node list`: ../marked_node_list--humppake/idea.gen.html
.. _`RMB action switch`: ../rmb_action_switch--humppake/idea.gen.html
.. _distorted: ../distorting_2d_canvas--humppake/idea.gen.html
.. _`special papers`: ../special_canvases--humppake/idea.gen.html

- adding new nodes, removing old nodes, marking nodes, creating 
connections between nodes etc...

2D paper canvas view
====================

- every 2D paper canvas has representative paper node in the structure
- on single 2D paper canvas is shown only data nodes that are connected
  to its representative paper node in the structure
- data nodes are shown as multiline vobs
- connections within the nodes shown on paper canvas are shown as
  filleted connections on canvas (`named connections`_?)
- if direction of the connection matters, form of fillet could show the 
direction
- connections to nodes that are not on canvas are shown as connections
  to buoys
  
  + buoys can be teared parts of other papers (shown as distorted_),
    focused to target node
  + one buoy for every paper where target node is placed on
  + if target node is not placed on any paper a focused and vanishing 
    `2D structure view is shown as buoy`_

- nodes from floating buffer can be dragged & dropped onto canvas
- nodes from marked node list can be dragged & dropped onto canvas
- when a single data node is accursed, a 2D structured view focused
  to that node is shown as a buoy
- like canvas can be zoomed, it can also be distorted_ to see the big 
picture

- adding new nodes: nodes added to canvas will be connected to 
representing
  paper node on the structure
- removing old nodes: node will be removed from the structure only if it 
has
  no connections to any other node but the paper node representing
  active canvas
- moving nodes on canvas
- creating and removing connection between nodes on canvas

.. _`2D structure view is shown as buoy`: 
../views_as_buoys--humppake/idea.gen.html

Transition between views is done via buoys.

Special keybinding to hide buoys (and floating buffer, and marked node
list), but only as long as the key is pressed.

Topic map
=========

.. UML:: mindmap_topicmap
   :menu: 0

   page (distorted) "Distorting 2D canvas"
	link
		../distorting_2d_canvas--humppake/idea.gen.html
   page (buffer) "Floating buffer"
	link
		../floating_buffer--humppake/idea.gen.html
   page (nodelist) "Marked node list"
	link
		../marked_node_list--humppake/idea.gen.html
   page (named) "Naming filleted connections"
	link
		../naming_filleted_connections--humppake/idea.gen.html
   page (rmb) "RMB action switch"
	link
		../rmb_action_switch--humppake/idea.gen.html
   page (buoys) "Views as buoys"
	link
		../views_as_buoys--humppake/idea.gen.html
  
   page MindMap
	link
		idea.gen.html
	use distorted
	use buffer
	use nodelist
	use named
	use rmb
	use buoys

   ---
   horizontally(25, hor_a, buoys, distorted, named);
   horizontally(25, hor_b, nodelist, MindMap, buffer);
   vertically(25, vert, distorted, MindMap, rmb);

==============================
New nodes onto floating buffer
==============================

$Id: idea.rst,v 1.3 2003/06/30 11:27:59 humppake Exp $

When writing notes, it would be useful to first enter the data and
then (reprocess and) connect it to an existing structure.

Mudyc developed a nice solution demo for this. 

 1. press 'tab' to 'lost the focus'
 2. enter the data and a new node is created

    Note: entering multi-line content should be allowed

 3. press 'tab' to enter a new node
 4. previously entered node remains non-connected and
    floats on view's nadir
 
Later the floating nodes can be connected to structure using mouse
(keybindings should be possible, but mouse would be the most natural
way).

In mudyc's demo connections were created in special mode with only
mouse (using `rmb_action_switch`__). Of course something like CTRL +
mouse could also be considered.

.. _rmb: ../rmb_action_switch--humppake/idea.gen.html
__ rmb_

.. image:: floating-example-2.png

.. image:: floating-example-1.png


Discussion
==========

Would it be a problem that nodes would float among buoys?

==============
Views as buoys
==============

$Id: idea.rst,v 1.1 2003/06/27 10:48:39 humppake Exp $

As long as there are need for only a few number of different views,
those views could be accessible using mouse, if they were presented as
buoys.

Idea of Fenfire's MindMap applitude is a good example:

 - when on 2D structure view, there would be one 2D canvas buoy for every 
   paper, where accursed node is placed

 - when on 2D canvas view, there would be one buoy with 2D structure view

Transition between views happens, of course, when a buoy is clicked.

===========================
Naming filleted connections
===========================

$Id: idea.rst,v 1.1 2003/06/27 10:48:39 humppake Exp $

In RDF every connection has a property and in concept map every
connection should have a name. Normally in RDF properties are only to
help computer to interpret connection. But if we want to edit plain
RDF or use RDF to represent concept map, all properties should be shown
and editable.

As fillet technology is currently advancing fast, in filleted
connections the fillet itself could be natural place for the
connection property/name.

.. image:: sketch.png

The property/name could also be changed by clicking the old name or
the fillet.

=====================
List for marked nodes
=====================

$Id: idea.rst,v 1.1 2003/06/27 10:48:39 humppake Exp $

To allow connecting faraway nodes which cannot be shown on the same
focus+context view, we need to allow marking of those nodes.

Benja had already developed a list for marked nodes into GZZ client,
but after abandoning GZZ this feature was kind of lost. Of course,
this will be a feature of full working Loom, but this would also be
useful in Fenfire's MindMap (later MM) applitude.

.. image:: gzz-marked-node-list.png

MM has a 2D structure view, where marked node list could work as it
worked in GZZ: marked nodes can be connected to accursed node.

In MM nodes created in 2D structure view must also be able to place 
on 2D canvases. When on 2D canvas view, marked nodes in list should
be able to drag & drop onto canvas.

New features:

- nodes can be dragged & dropped onto 2D canvas

  + in MM this will cause a connection between marked node and paper node
    representing that canvas, also dropping coordinates are added into
    connection


==================================
Distortion attribute for 2D canvas
==================================

$Id: idea.rst,v 1.1 2003/06/27 10:48:39 humppake Exp $

How should 2D canvases be distorted?

Since generally distortable/diceable vob architecture is still *under
development* for some time, FishEye transformation wouldn't work with
vobs.

One solution could be that we won't even try to distort single vobs,
but only their relative sizes and distances. The focused vob would be
in it's original size, but step by step vobs would be drawn smaller
and closer each other. This distortation way is a bit familiar from
vanishing views in GZZ.

.. image:: distortion-example.png

Distorted 2D canvases could be useful i.e. in buoys.

Discussion
==========

As this distortation wouldn't be continuous, could background be
distorted at all?

==============================
RightMouseButton action switch
==============================

$Id: idea.rst,v 1.1 2003/06/27 10:48:39 humppake Exp $

In Sierra's SCUMM interfaces user first selected an action from a
action command list and then pointed some item for the selected
action. As the next step the actiom command list was hidden behind
right mouse button and selected action was shown as more or less
descriptive mouse cursor.

 1. user pressed RMB -> mouse cursor changed to the next action
 2. user repeats 1. until mouse cursor
    shows the correct action
 4. user points the item for action

Discussion
==========

Can we create efficiently (and how platform independently) our own
descriptive mouse cursors?

If we remain using only available default mouse cursors, what would be
a extra cue good enough with them? I.e. showing name of the selected
action in some corner?

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Wed Jul 02 21:04:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19XsW0-0000Cw-S3
	for mharc-gzz-dev@gnu.org; Wed, 02 Jul 2003 21:04:00 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19XsVw-0008SX-Tc
	for gzz-dev@nongnu.org; Wed, 02 Jul 2003 21:03:56 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19XsVo-0007zi-AZ
	for gzz-dev@nongnu.org; Wed, 02 Jul 2003 21:03:52 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19XsVk-0007rk-Ra
	for gzz-dev@nongnu.org; Wed, 02 Jul 2003 21:03:44 -0400
Received: (qmail 2406 invoked by uid 65534); 3 Jul 2003 01:03:41 -0000
Received: from pD9E12280.dip.t-dialin.net (EHLO gmx.de) (217.225.34.128)
  by mail.gmx.net (mp002) with SMTP; 03 Jul 2003 03:03:41 +0200
Message-ID: <3F0380A8.7080406@gmx.de>
Date: Thu, 03 Jul 2003 03:02:32 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: GZZ developers <gzz-dev@nongnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gzz] A public demo of the HTTP gateway can be found at:
 PEG: Alter Canvas2D vocab to support transclusions
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 03 Jul 2003 01:03:58 -0000

==================================================
PEG: Alter Canvas2D vocab to support transclusions
==================================================

:Authors:       Benja Fallenstein
:Date-Created:  2003-07-03
:Last-Modified: $Date: 2003/04/25 12:29:33 $
:Revision:      $Revision: 1.2 $
:Status:        Incomplete
:Scope:         Minor
:Type:          Interface


The Canvas2D vocabulary (``http://fenfire.org/rdf-v/2003/05/canvas2d``)
specifies properties and classes for placing things on 2D canvases.

This vocabulary does not, however, take into account that
a node's coordinates on some paper are not properties of that node;
e.g., when we have a node "The Fenfire system," then this system
does not have x coordinate 145 and y coordinate -32; rather, a
rendition of the node representing the Fenfire system is placed
at these coordinates.

The failure of taking this into account means that there cannot
be transclusions of a node, i.e. one node cannot be placed
on multiple papers; in Fenfire, transclusion must be supported
for *anything*, i.e., whenever some thing is in a "context,"
it must be possible to place it in more than one context.

In order to make nodes transcludable, the vocabulary
must be changed.


Issues
======

- Should the definition of the existing namespace be changed,
   or should we create a new namespace?

   RESOLVED: New namespace. Three out of four URIs in the
   namespace cannot be used with their existing definition
   (and changing the definition of an existing URI is
   bad practice); retaining the last URI (``#Canvas``)
   simply isn't worth it.

- Do we need a converter?

   RESOLVED: As save/load hasn't worked for FenPDF so far,
   we can expect that nobody has data in it yet; unless
   somebody speaks up, we'll assume we need no converter.

Changes
=======

Create a new namespace,
``http://fenfire.org/rdf-v/2003/07/canvas2d-bis``,
containing the following names and definitions:

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#Canvas``
     The RDF class of spatial 2D canvases.
     Canvases contain (with the ``#contains`` property)
     node transclusions, which may have the ``#x`` and ``#y``
     properties, depending on the type of canvas.

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#NodeOnCanvas``
     A transclusion of a node onto a canvas. This represents
     one instance of a node on a specific canvas. The node
     transcluded is related to this node through the
     ``#transcludes`` property.

     Having this is necessary so that a single node can be
     placed on more than one canvas.

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#contains``
     A property relating a canvas to the node transclusions
     it contains.

     :Domain:      ``#Canvas``
     :Range:       ``#NodeOnCanvas``
     :Cardinality: ``1:n``

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#transcludes``
     A property relating a transclusion to the node it is
     a transclusion of.

     :Domain:      ``#NodeOnCanvas``
     :Range:       ``#Resource``
     :Cardinality: ``n:1``

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#x`` and
``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#y``
     The x and y coordinates of a node on a canvas.
     (node, x, literal), where the literal is parseable
     as a floating-point number (similar to Java doubles).
     Note that these are the *default* coordinate
     properties: later on, we might make it possible for a Canvas2D
     to define its own coordinate attributes, which would take
     use close to Ted's floating world ideas.

Change ``org.fenfire.vocab.CANVAS2D`` to use this namespace.
Make the necessary changes in the other code so that the
rules of this namespace are respected.

\- Benja




From MAILER-DAEMON Wed Jul 02 21:17:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19XsjL-00072z-Ad
	for mharc-gzz-dev@gnu.org; Wed, 02 Jul 2003 21:17:47 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19XsjJ-00070s-87
	for gzz-dev@nongnu.org; Wed, 02 Jul 2003 21:17:45 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19XsjH-0006zt-JB
	for gzz-dev@nongnu.org; Wed, 02 Jul 2003 21:17:44 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19XsjH-0006zl-24
	for gzz-dev@nongnu.org; Wed, 02 Jul 2003 21:17:43 -0400
Received: (qmail 28554 invoked by uid 65534); 3 Jul 2003 01:17:41 -0000
Received: from pD9E12280.dip.t-dialin.net (EHLO gmx.de) (217.225.34.128)
  by mail.gmx.net (mp015) with SMTP; 03 Jul 2003 03:17:41 +0200
Message-ID: <3F0383F0.8000607@gmx.de>
Date: Thu, 03 Jul 2003 03:16:32 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Benja Fallenstein <b.fallenstein@gmx.de>
References: <3F0380A8.7080406@gmx.de>
In-Reply-To: <3F0380A8.7080406@gmx.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: GZZ developers <gzz-dev@nongnu.org>
Subject: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 03 Jul 2003 01:17:45 -0000

WARGH! Not only did something mess up my subject: line, I also forgot to 
give domain/range/cardinality on the x and y property and mention data 
types there.

==================================================
PEG: Alter Canvas2D vocab to support transclusions
==================================================

:Authors:       Benja Fallenstein
:Date-Created:  2003-07-03
:Last-Modified: $Date: 2003/07/03 01:01:33 $
:Revision:      $Revision: 1.1 $
:Status:        Incomplete
:Scope:         Minor
:Type:          Interface


The Canvas2D vocabulary (``http://fenfire.org/rdf-v/2003/05/canvas2d``)
specifies properties and classes for placing things on 2D canvases.

This vocabulary does not, however, take into account that
a node's coordinates on some paper are not properties of that node;
e.g., when we have a node "The Fenfire system," then this system
does not have x coordinate 145 and y coordinate -32; rather, a
rendition of the node representing the Fenfire system is placed
at these coordinates.

The failure of taking this into account means that there cannot
be transclusions of a node, i.e. one node cannot be placed
on multiple papers; in Fenfire, transclusion must be supported
for *anything*, i.e., whenever some thing is in a "context,"
it must be possible to place it in more than one context.

In order to make nodes transcludable, the vocabulary
must be changed.


Issues
======

- Should the definition of the existing namespace be changed,
   or should we create a new namespace?

   RESOLVED: New namespace. Three out of four URIs in the
   namespace cannot be used with their existing definition
   (and changing the definition of an existing URI is
   bad practice); retaining the last URI (``#Canvas``)
   simply isn't worth it.

- Do we need a converter?

   RESOLVED: As save/load hasn't worked for FenPDF so far,
   we can expect that nobody has data in it yet; unless
   somebody speaks up, we'll assume we need no converter.

Changes
=======

Create a new namespace,
``http://fenfire.org/rdf-v/2003/07/canvas2d-bis``,
containing the following names and definitions:

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#Canvas``
     The RDF class of spatial 2D canvases.
     Canvases contain (with the ``#contains`` property)
     node transclusions, which may have the ``#x`` and ``#y``
     properties, depending on the type of canvas.

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#NodeOnCanvas``
     A transclusion of a node onto a canvas. This represents
     one instance of a node on a specific canvas. The node
     transcluded is related to this node through the
     ``#transcludes`` property.

     Having this is necessary so that a single node can be
     placed on more than one canvas.

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#contains``
     A property relating a canvas to the node transclusions
     it contains.

     :Domain:      ``#Canvas``
     :Range:       ``#NodeOnCanvas``
     :Cardinality: ``1:n``

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#transcludes``
     A property relating a transclusion to the node it is
     a transclusion of.

     :Domain:      ``#NodeOnCanvas``
     :Range:       ``#Resource``
     :Cardinality: ``n:1``

``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#x`` and
``http://fenfire.org/rdf-v/2003/07/canvas2d-bis#y``
     The x and y coordinates of a node on a canvas.
     Note that these are the *default* coordinate
     properties: later on, we might make it possible for a Canvas2D
     to define its own coordinate attributes, which would take
     use close to Ted's floating world ideas.

     The objects in this namespace are literals
     of type `xsd:double`_.

     :Domain:      ``#NodeOnCanvas``
     :Range:       `xsd:double`_
     :Cardinality: ``n:1``

     __ http://www.w3.org/TR/xmlschema-2/#double

Change ``org.fenfire.vocab.CANVAS2D`` to use this namespace.

Make the necessary changes in the other code so that the
rules of this namespace are respected; in particular,
the coordinate literals need to be of type `xsd:double`_.

\- Benja




From MAILER-DAEMON Thu Jul 03 04:36:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19XzZa-0000bd-2c
	for mharc-gzz-dev@gnu.org; Thu, 03 Jul 2003 04:36:10 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19XzZI-0008GO-QK
	for gzz-dev@nongnu.org; Thu, 03 Jul 2003 04:35:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19XzXq-00071l-QB
	for gzz-dev@nongnu.org; Thu, 03 Jul 2003 04:34:24 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19XzWu-0006Ii-D7
	for gzz-dev@nongnu.org; Thu, 03 Jul 2003 04:33:24 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h638XIND025043;
	Thu, 3 Jul 2003 11:33:19 +0300
Received: from localhost (majukati@localhost)h638XIeh025039;
	Thu, 3 Jul 2003 11:33:18 +0300
Date: Thu, 3 Jul 2003 11:33:18 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
In-Reply-To: <3F0383F0.8000607@gmx.de>
Message-ID: <Pine.LNX.4.44.0307031122120.31128-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 03 Jul 2003 08:36:08 -0000

On Thu, 3 Jul 2003, Benja Fallenstein wrote:
> ==================================================
> PEG: Alter Canvas2D vocab to support transclusions
> ==================================================
> 
> :Authors:       Benja Fallenstein
> :Date-Created:  2003-07-03
> :Last-Modified: $Date: 2003/07/03 01:01:33 $
> :Revision:      $Revision: 1.1 $
> :Status:        Incomplete
> :Scope:         Minor
> :Type:          Interface
> 
> 
> The Canvas2D vocabulary (``http://fenfire.org/rdf-v/2003/05/canvas2d``)
> specifies properties and classes for placing things on 2D canvases.
> 
> This vocabulary does not, however, take into account that
> a node's coordinates on some paper are not properties of that node;
> e.g., when we have a node "The Fenfire system," then this system
> does not have x coordinate 145 and y coordinate -32; rather, a
> rendition of the node representing the Fenfire system is placed
> at these coordinates.
> 
> The failure of taking this into account means that there cannot
> be transclusions of a node, i.e. one node cannot be placed
> on multiple papers; in Fenfire, transclusion must be supported
> for *anything*, i.e., whenever some thing is in a "context,"
> it must be possible to place it in more than one context.
> 
> In order to make nodes transcludable, the vocabulary
> must be changed.

Making clones is something what I wouldn't do in word-processing.
Same with pictures. If you are talkking about mindmap thing we should not 
mess it up with canvas2d which is "making notes" - not "making clone 
notes".

If you really want to do clones, you also need to make a new api for it 
(similar like ppactions) because pp should not do a such thing.

CanvasView2D can be programmed to render also these clone notes.


   -Matti





From MAILER-DAEMON Thu Jul 03 10:35:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19Y5Ap-00029X-Rv
	for mharc-gzz-dev@gnu.org; Thu, 03 Jul 2003 10:34:59 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19Y5A9-00017Y-Sz
	for gzz-dev@nongnu.org; Thu, 03 Jul 2003 10:34:17 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Y59B-0008Vd-7j
	for gzz-dev@nongnu.org; Thu, 03 Jul 2003 10:33:23 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19Y58v-0008F8-HP
	for gzz-dev@nongnu.org; Thu, 03 Jul 2003 10:33:01 -0400
Received: (qmail 16169 invoked by uid 65534); 3 Jul 2003 14:33:00 -0000
Received: from p5082CFE9.dip.t-dialin.net (EHLO gmx.de) (80.130.207.233)
  by mail.gmx.net (mp027) with SMTP; 03 Jul 2003 16:33:00 +0200
Message-ID: <3F043E57.4000600@gmx.de>
Date: Thu, 03 Jul 2003 16:31:51 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
References: <Pine.LNX.4.44.0307031122120.31128-100000@verso.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307031122120.31128-100000@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Thu, 03 Jul 2003 14:34:57 -0000

Matti Katila wrote:
> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
>>The failure of taking this into account means that there cannot
>>be transclusions of a node, i.e. one node cannot be placed
>>on multiple papers; in Fenfire, transclusion must be supported
>>for *anything*, i.e., whenever some thing is in a "context,"
>>it must be possible to place it in more than one context.
>>
>>In order to make nodes transcludable, the vocabulary
>>must be changed.
> 
> Making clones is something what I wouldn't do in word-processing.
> Same with pictures. If you are talkking about mindmap thing we should not 
> mess it up with canvas2d which is "making notes" - not "making clone 
> notes".
> 
> If you really want to do clones, you also need to make a new api for it 
> (similar like ppactions) because pp should not do a such thing.
> 
> CanvasView2D can be programmed to render also these clone notes.


We have discussed this at length on IRC, without coming to an agreement. 
Here's my summary (keep in mind that it's from *my* POV):

- Mudyc agrees that transclusion of nodes is needed for some things, 
e.g. mindmapping, but not for some other applications of 2D canvases, 
such as 'general "text"'.

- Mudyc thinks that there should be two vocabularies, Canvas2D and 
MindMap, which do the same thing except that MindMap allows for 
transclusion of notes and Canvas2D doesn't.

- I believe that there should be only one vocabulary; if transclusion 
isn't needed, use the same vocabulary, and simply don't put a node on 
more than one canvas / position on a single canvas.

- In e.g. PP, if you decide you do not need transclusions of nodes, 
simply don't make it available through the UI. The vocabulary should 
still support it.

- In particular, I think it's important that the computer doesn't make a 
difference between "transcludable" and "not transcludable" nodes. In a 
UI that supports transclusions (such as the full Fenfire system) it 
should be possible to transclude any node if the user says "transclude."

(If one node used a vocabulary that doesn't allow for transclusion, then 
  that node could not be transcluded.)

- Changing Canvas2D now doesn't mean that we'll need to change it again 
if we want to, e.g., use named connections in half a year; this can be 
implemented orthogonally in another vocab. Transclusions are special 
because they cannot be implemented in an orthogonal vocabulary; this is 
generally the case for RDF vocabs (if you design a vocab that places 
some node into some context, you need to take transclusion into account).

- I have always assumed that there'll be a single vocabulary for 
"placing something on a spatial canvas," and that it's up to the user to 
use this general tool for mindmapping, text editing, note taking, or 
whatever. I still think there should be a single vocabulary allowing for 
all that, and at least some of these uses definitely use transclusions.

- Benja




From MAILER-DAEMON Fri Jul 04 03:30:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19YL0Z-0001yp-OE
	for mharc-gzz-dev@gnu.org; Fri, 04 Jul 2003 03:29:27 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19YKzu-00017M-08
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 04 Jul 2003 03:28:46 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19YKyt-0000Xq-Ta
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 04 Jul 2003 03:27:46 -0400
Received: from posti1.jyu.fi ([130.234.4.32])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19YKyf-0000OD-GU
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 04 Jul 2003 03:27:29 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	h647RPqO014413	for <gzz-dev@mail.freesoftware.fsf.org>;
	Fri, 4 Jul 2003 10:27:26 +0300
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Content-Type: multipart/mixed; boundary="=-Kgqa7r2axnR6nHGtxeH6"
Organization: 
Message-Id: <1057303645.1183.0.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 04 Jul 2003 10:27:25 +0300
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Subject: [Gzz] [Fwd: announcing Tapestry 2.0 release]
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Fri, 04 Jul 2003 07:29:25 -0000


--=-Kgqa7r2axnR6nHGtxeH6
Content-Type: text/plain
Content-Transfer-Encoding: 7bit



--=-Kgqa7r2axnR6nHGtxeH6
Content-Disposition: inline
Content-Description: Forwarded message - announcing Tapestry 2.0 release
Content-Type: message/rfc822

Return-Path: <owner-oceanstore@kubi.cs.berkeley.edu>
Received: from posti1.jyu.fi (posti1.jyu.fi [130.234.4.32]) by
	h640JReu010991
	for <hemppah@cc.jyu.fi>; Fri, 4 Jul 2003 03:19:27 +0300 (EEST)
	(envelope-from owner-oceanstore@kubi.cs.berkeley.edu)
Received: from kubi.cs.berkeley.edu (kubi.CS.Berkeley.EDU [128.32.168.212])
	h640JOqO014039 for
	<hemppah@cc.jyu.fi>; Fri, 4 Jul 2003 03:19:25 +0300
Received: (from majordomo@localhost) by kubi.cs.berkeley.edu
	(8.11.6/8.11.6) id h6402od07349 for oceanstore-announce-list;
	Thu, 3 Jul	2003 17:02:50 -0700
X-Authentication-Warning: kubi.cs.berkeley.edu: majordomo set sender to
	owner-oceanstore@kubi.cs.berkeley.edu using -f
Received: from mailhost.ens-lyon.fr (pluvier.ens-lyon.fr [140.77.167.5]) by
	kubi.cs.berkeley.edu (8.11.6/8.11.6) with ESMTP id h6402nF07346 for
	<oceanstore-announce@kubi.cs.berkeley.edu>;
	Thu, 3 Jul 2003 17:02:49 -0700
Received: from oceanite.ens-lyon.fr ([140.77.1.22]) by mailhost.ens-lyon.fr
	with esmtp (Exim 3.35 #1 (Debian)) id 19YE2K-0006hZ-00 for
	<oceanstore-announce@kubi.cs.berkeley.edu>;
	Fri, 04 Jul 2003 02:02:48 +0200
Received: by oceanite.ens-lyon.fr (Postfix, from userid 1502) id
	909EF32005F; Fri,  4 Jul 2003 02:02:46 +0200 (CEST)
Received: from mailhost.ens-lyon.fr (pluvier.ens-lyon.fr [140.77.167.5]) by
	oceanite.ens-lyon.fr (Postfix) with SMTP id 515AC320058 for
	<Martin.Quinson@ens-lyon.fr>; Fri,  4 Jul 2003 02:02:46 +0200 (CEST)
Received: from kubi.cs.berkeley.edu ([128.32.168.212]) by
	19YE2E-0006gi-00
	for <Martin.Quinson@ens-lyon.fr>; Fri, 04 Jul 2003 02:02:42 +0200
Received: (from majordomo@localhost) by kubi.cs.berkeley.edu
	(8.11.6/8.11.6) id h63Nqa405058 for oceanstore-announce-list;
	Thu, 3 Jul	2003 16:52:36 -0700
X-Authentication-Warning: kubi.cs.berkeley.edu: majordomo set sender to
	owner-oceanstore@kubi.cs.berkeley.edu using -f
Received: from mailhost.ens-lyon.fr (pluvier.ens-lyon.fr [140.77.167.5]) by
	kubi.cs.berkeley.edu (8.11.6/8.11.6) with ESMTP id h63NqZF05055 for
	<oceanstore-announce@kubi.cs.berkeley.edu>;
	Thu, 3 Jul 2003 16:52:35 -0700
Received: from oceanite.ens-lyon.fr ([140.77.1.22]) by mailhost.ens-lyon.fr
	with esmtp (Exim 3.35 #1 (Debian)) id 19YDsQ-00049B-00 for
	<oceanstore-announce@kubi.cs.berkeley.edu>;
	Fri, 04 Jul 2003 01:52:34 +0200
Received: by oceanite.ens-lyon.fr (Postfix, from userid 1502) id
	315DA32005C; Fri,  4 Jul 2003 01:52:33 +0200 (CEST)
Received: from mailhost.ens-lyon.fr (pluvier.ens-lyon.fr [140.77.167.5]) by
	oceanite.ens-lyon.fr (Postfix) with SMTP id ECA6B320058 for
	<Martin.Quinson@ens-lyon.fr>; Fri,  4 Jul 2003 01:52:32 +0200 (CEST)
Received: from kubi.cs.berkeley.edu ([128.32.168.212]) by
	19YDsL-00046y-00
	for <Martin.Quinson@ens-lyon.fr>; Fri, 04 Jul 2003 01:52:29 +0200
Received: (from majordomo@localhost) by kubi.cs.berkeley.edu
	(8.11.6/8.11.6) id h63NiRT04966 for oceanstore-announce-list;
	Thu, 3 Jul	2003 16:44:27 -0700
X-Authentication-Warning: kubi.cs.berkeley.edu: majordomo set sender to
	owner-oceanstore@kubi.cs.berkeley.edu using -f
Received: from mailhost.ens-lyon.fr (pluvier.ens-lyon.fr [140.77.167.5]) by
	kubi.cs.berkeley.edu (8.11.6/8.11.6) with ESMTP id h63NiQF04963 for
	<oceanstore-announce@kubi.cs.berkeley.edu>;
	Thu, 3 Jul 2003 16:44:26 -0700
Received: from oceanite.ens-lyon.fr ([140.77.1.22]) by mailhost.ens-lyon.fr
	with esmtp (Exim 3.35 #1 (Debian)) id 19YDkW-0001ja-00 for
	<oceanstore-announce@kubi.cs.berkeley.edu>;
	Fri, 04 Jul 2003 01:44:24 +0200
Received: by oceanite.ens-lyon.fr (Postfix, from userid 1502) id
	3EF2032005C; Fri,  4 Jul 2003 01:44:19 +0200 (CEST)
Received: from mailhost.ens-lyon.fr (pluvier.ens-lyon.fr [140.77.167.5]) by
	oceanite.ens-lyon.fr (Postfix) with SMTP id 07647320058 for
	<Martin.Quinson@ens-lyon.fr>; Fri,  4 Jul 2003 01:44:19 +0200 (CEST)
Received: from kubi.cs.berkeley.edu ([128.32.168.212]) by
	19YDkN-0001j4-00
	for <Martin.Quinson@ens-lyon.fr>; Fri, 04 Jul 2003 01:44:15 +0200
Received: (from majordomo@localhost) by kubi.cs.berkeley.edu
	(8.11.6/8.11.6) id h63NVNO04834 for oceanstore-announce-list;
	Thu, 3 Jul	2003 16:31:23 -0700
X-Authentication-Warning: kubi.cs.berkeley.edu: majordomo set sender to
	owner-oceanstore@kubi.cs.berkeley.edu using -f
Received: from relay2.EECS.Berkeley.EDU (relay2.EECS.Berkeley.EDUid
	h63NVNF04831 for <oceanstore-announce@kubi.CS.Berkeley.EDU>;
	Thu, 3 Jul	2003 16:31:23 -0700
Received: from relay3.EECS.Berkeley.EDU (localhost [127.0.0.1]) byfor
	<oceanstore-announce@kubi.CS.Berkeley.EDU>;
	Thu, 3 Jul 2003 16:31:22 -0700	(PDT)
Received: from joker.cs.berkeley.edu (joker.CS.Berkeley.EDUESMTP id
	h63NVLnL004931 for <oceanstore-announce@oceanstore.cs.berkeley.edu>;
	Thu, 3	Jul 2003 16:31:22 -0700 (PDT)
Date: Thu, 3 Jul 2003 16:31:21 -0700 (PDT)
From: "Ben Y. Zhao" <ravenben@cs.berkeley.edu>
To: oceanstore-announce@kubi.cs.berkeley.edu
Subject: announcing Tapestry 2.0 release
Message-ID: <Pine.LNX.4.44.0307031606130.27209-100000@joker.cs.berkeley.edu>
MIME-Version: 1.0
X-Spam-Status: No, hits=-0.4 required=5.0
	tests=USER_AGENT_PINE,X_AUTH_WARNING version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)
X-Spam-Report: ---- Start SpamAssassin results -0.40 points, 5 required;
	*  0.0 -- Message-Id indicates a non-spam MUA (Pine) * -0.4 -- Has a
	X-Authentication-Warning header ---- End of SpamAssassin results
Sender: owner-oceanstore@cs.berkeley.edu
Precedence: bulk
Reply-To: "Ben Y. Zhao" <ravenben@cs.berkeley.edu>
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Content-Type: text/plain; CHARSET=US-ASCII
Content-Transfer-Encoding: 7bit

Hi everyone.

I'm happy to announce that we have finally finished putting together a new
release of Tapestry.  When you downloaded Tapestry 1.0, you indicated a
desire to be notified when the next version came out, hence this email.

Tapestry 2.0 is now ready for download at the Tapestry website, or you can
go to this URL: http://www.cs.berkeley.edu/~ravenben/tapestry/html/download.html

I'll give a short summary of what's new in this release.  All of this
information is included in documentation inside the distribution.  The key
change from 1.0 to 2.0 is stability and adaptivity to changes in the
network.  In particular, we've implemented the very stable parallel
insertion algorithms in the SPAA 2002 paper, and gone through a rigorous
process of debugging and testing the software under a variety of
conditions and on a number of different test/simulation platforms.

Tapestry has also been augmented with a set of fault-resilience
algorithms, anchored by a component called Patchwork that uses periodic
heartbeats to monitor link quality to neighbor nodes.  Tapestry keeps a
small # (3) nodes in each routing table entry. By default, Tapestry will
route messages through the closest one in the set that has a link quality
better than some defined minimum threshold.  As link qualities change and
link and node failures are detected, Tapestry swaps entries to maintain
high delivery rate, and replaces dead nodes with backups, replenishing
when necessary.

In addition to resiliency, we've added both a distributed testing
framework and a centralized simulation platform to the distribution.
Nodes in the distributed framework take control messages from a central
experiment driver to perform all operations, and report back with results.
The simulation platform abstracts the network layer into a set of queues
driven by logical clocks, enabling a large number (up to 400) of node
instances to be run on a single machine.

Finally, we've included a couple of simple applications.  Interweave is a
simple file sharing protocol on top of Tapestry that provides kazaa like
properties.  Shuttle provides decentralized instant messaging for
users across a wide area network. Both applications are relatively new,
and still relatively unpolished.  Detailed documentation for them are in
the works.

All of the information you need to install and run Tapestry is included
with the distribution. Also inside is a PDF version of our recent journal
paper on Tapestry, which provides a good overview of Tapestry and its
goals as well as detailed performance measurements.

Thanks for using Tapestry.  If you have questions, feel free to check out
the website or email me.  Also, if you are using Tapestry to develop
applications, we would love to hear from you, and would be happy to put a
link to your application homepage from the Tapestry site.

Ben Zhao
and the Tapestry developers team
7/03/2003

--=-Kgqa7r2axnR6nHGtxeH6--




From MAILER-DAEMON Sun Jul 06 15:34:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZFHE-0005y3-4F
	for mharc-gzz-dev@gnu.org; Sun, 06 Jul 2003 15:34:24 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZFHB-0005tu-JX
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 15:34:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZFHA-0005th-1F
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 15:34:20 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZFH9-0005oX-Go
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 15:34:19 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h66JYEND030143;
	Sun, 6 Jul 2003 22:34:14 +0300
Received: from localhost (majukati@localhost)h66JYE2l030139;
	Sun, 6 Jul 2003 22:34:14 +0300
Date: Sun, 6 Jul 2003 22:34:14 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
In-Reply-To: <3F043E57.4000600@gmx.de>
Message-ID: <Pine.LNX.4.44.0307032318090.31128-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 06 Jul 2003 19:34:22 -0000

On Thu, 3 Jul 2003, Benja Fallenstein wrote:
> Matti Katila wrote:
>> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
>>>The failure of taking this into account means that there cannot
>>>be transclusions of a node, i.e. one node cannot be placed
>>>on multiple papers; in Fenfire, transclusion must be supported
>>>for *anything*, i.e., whenever some thing is in a "context,"
>>>it must be possible to place it in more than one context.
>>>
>>>In order to make nodes transcludable, the vocabulary
>>>must be changed.
>> 
>> Making clones is something what I wouldn't do in word-processing.
>> Same with pictures. If you are talkking about mindmap thing we should not 
>> mess it up with canvas2d which is "making notes" - not "making clone 
>> notes".
>> 
>> If you really want to do clones, you also need to make a new api for it 
>> (similar like ppactions) because pp should not do a such thing.
>> 
>> CanvasView2D can be programmed to render also these clone notes.
> 
> 
> We have discussed this at length on IRC, without coming to an agreement. 
> Here's my summary (keep in mind that it's from *my* POV):
> 
> - Mudyc agrees that transclusion of nodes is needed for some things, 
> e.g. mindmapping, but not for some other applications of 2D canvases, 
> such as 'general "text"'.

And my biggest point is that user should recognize if node is clone or 
not, on canvas. 

Clones are really dangerous in general text but very good in mindmaps.

You talked a system like:
-user selects area of nodes
-by pressing "A" he/she takes content copy
 or
-by pressing "B" he/she makes clone tranclusion.

I think this is not good because this sounds like clone is something what 
would you do in your everyday copying.

Making clone copy is not just copying, you really have to make the node to 
clone node to do that. It's like cloning sheeps, the original way to make 
baby sheeps doesn't need doctors with biology knowledge =) blaah blaah.. :)

In a system where I suppose cloning is available user has to make a node 
to clone node before copying. That might prevent unwanted clones. Of 
course in mindmap part of system this would be turned off by default.

 
> - Mudyc thinks that there should be two vocabularies, Canvas2D and 
> MindMap, which do the same thing except that MindMap allows for 
> transclusion of notes and Canvas2D doesn't.

That is one solution although I don't like that much of it after I though 
the NodeFuntion solution :)

The normal way is:
  
   Canvas --contains--> Coordinates

And the Coordinates is also the node which has the content. We can say 
that that node is clone if we notice it i.e., from rdf type.
So, now we can use CloneNodeFunction to handle the cloned node.


class CloneNodeFunction {

Object f(ConstGrahp g, Object node) {
    if (RDFUtil.isNodeType(fen.graph, node, CLONE.Instance))
        return nodefunc.f(fen.graph, 
                          fen.graph.find1_11X(node, CLONE.tranclusion));
    else return nodefunc.f(fen.graph, node);
}

}

Modifications to AlphContent is also needed to support clone nodes.

 
> - I believe that there should be only one vocabulary; if transclusion 
> isn't needed, use the same vocabulary, and simply don't put a node on 
> more than one canvas / position on a single canvas.

You are assuming that cloning is needed. Is it needed?

We have no real user case testing. I'd propose that we make this simple 
modification in structure if it will be more than 5% of use cases in our 
own use. Doing something for because it's doable isn't really a good 
cause.
 
> - In particular, I think it's important that the computer doesn't make a 
> difference between "transcludable" and "not transcludable" nodes. In a 
> UI that supports transclusions (such as the full Fenfire system) it 
> should be possible to transclude any node if the user says "transclude."
>
> (If one node used a vocabulary that doesn't allow for transclusion, then 
>   that node could not be transcluded.)

You should be very exact when you talk about transcluding in node or span 
level, since everyting we use in fenfire is already transclusion of the
enfilade.
 
> - Changing Canvas2D now doesn't mean that we'll need to change it again 
> if we want to, e.g., use named connections in half a year; this can be 
> implemented orthogonally in another vocab. Transclusions are special 
> because they cannot be implemented in an orthogonal vocabulary; this is 
> generally the case for RDF vocabs (if you design a vocab that places 
> some node into some context, you need to take transclusion into account).
 
> - I have always assumed that there'll be a single vocabulary for 
> "placing something on a spatial canvas," and that it's up to the user to 
> use this general tool for mindmapping, text editing, note taking, or 
> whatever. I still think there should be a single vocabulary allowing for 
> all that, and at least some of these uses definitely use transclusions.

Are you defining now "fenfire's general structure"?

 Canvas --contains--> Coordinates --transcludes--> CloneContentNode 
                         -x,y

   -Matti





From MAILER-DAEMON Sun Jul 06 16:07:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZFn7-0008MI-RU
	for mharc-gzz-dev@gnu.org; Sun, 06 Jul 2003 16:07:21 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZFn5-0008Cq-9b
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:07:19 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZFn1-00082g-V8
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:07:16 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19ZFmr-0007sT-B3
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:07:05 -0400
Received: (qmail 24300 invoked by uid 65534); 6 Jul 2003 20:07:03 -0000
Received: from p5082D33B.dip.t-dialin.net (EHLO gmx.de) (80.130.211.59)
  by mail.gmx.net (mp007) with SMTP; 06 Jul 2003 22:07:03 +0200
Message-ID: <3F088116.2000301@gmx.de>
Date: Sun, 06 Jul 2003 22:05:42 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
References: <Pine.LNX.4.44.0307032318090.31128-100000@verso.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307032318090.31128-100000@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 06 Jul 2003 20:07:20 -0000

Matti Katila wrote:
> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
>>- Mudyc agrees that transclusion of nodes is needed for some things, 
>>e.g. mindmapping, but not for some other applications of 2D canvases, 
>>such as 'general "text"'.
> 
> And my biggest point is that user should recognize if node is clone or 
> not, on canvas. 

Having a visual indicator that there are clones of a node is entirely 
fine with me.

Note that by default, transclusions are always shown as buoys. So when 
you edit a clone, normally you see immediately that the other clones 
(shown as buoys) change, too.

> Clones are really dangerous in general text but very good in mindmaps.

I still don't have the faintest idea of what you mean by "general text," 
can you explain?

I agree that the UI should be so that the user doesn't accidentally make 
clones.

> You talked a system like:
> -user selects area of nodes
> -by pressing "A" he/she takes content copy
>  or
> -by pressing "B" he/she makes clone tranclusion.
> 
> I think this is not good because this sounds like clone is something what 
> would you do in your everyday copying.

In Gzz, I found it to be pretty much everyday.

> Making clone copy is not just copying, you really have to make the node to 
> clone node to do that.

I don't understand this.

If you simply mean that "clone" is a different menu item than "copy," 
that's ok. My original idea about the UI made cloning very similar to 
copying (select a strip of text vs. select the whole node); I agree that 
it would be better to have them more different (two different menu items).

> In a system where I suppose cloning is available user has to make a node 
> to clone node before copying. That might prevent unwanted clones.

You mean that the user says, "make this a clone node," and after this, 
saying "copy" makes a clone instead of a copy of the content?

I think it's better to have separate "copy" and "clone" actions 
available to the user.

> Of 
> course in mindmap part of system this would be turned off by default.

What would be?

>>- I believe that there should be only one vocabulary; if transclusion 
>>isn't needed, use the same vocabulary, and simply don't put a node on 
>>more than one canvas / position on a single canvas.
> 
> You are assuming that cloning is needed. Is it needed?

You have agreed to its usefulness in "mindmapping".

I assume that canvases are normally used to make a spatial arrangement 
of things. Whenever they are used for this, it is useful to have more 
than one spatial arrangement of the same things. Whenever this is 
useful, you need clones.

> We have no real user case testing.

We have years of experience with Gzz, where it has proven very useful.

> I'd propose that we make this simple 
> modification in structure if it will be more than 5% of use cases in our 
> own use. Doing something for because it's doable isn't really a good 
> cause.

I'm not proposing to do it because it is doable. You have agreed that it 
is useful.

>>- In particular, I think it's important that the computer doesn't make a 
>>difference between "transcludable" and "not transcludable" nodes. In a 
>>UI that supports transclusions (such as the full Fenfire system) it 
>>should be possible to transclude any node if the user says "transclude."
>>
>>(If one node used a vocabulary that doesn't allow for transclusion, then 
>>  that node could not be transcluded.)
> 
> You should be very exact when you talk about transcluding in node or span 
> level, since everyting we use in fenfire is already transclusion of the
> enfilade.

Fine. I have tried to be clear in this mail.

>>- I have always assumed that there'll be a single vocabulary for 
>>"placing something on a spatial canvas," and that it's up to the user to 
>>use this general tool for mindmapping, text editing, note taking, or 
>>whatever. I still think there should be a single vocabulary allowing for 
>>all that, and at least some of these uses definitely use transclusions.
> 
> 
> Are you defining now "fenfire's general structure"?

I'm sorry, I don't understand that question...

>  Canvas --contains--> Coordinates --transcludes--> CloneContentNode 
>                          -x,y

This is what I propose as the vocabulary for spatial canvases.

Ok, if you meant above, "are you now defining fenfire's single 
vocabulary for spatial canvases," well, yes, my PEG proposes the above 
to be that.

- Benja




From MAILER-DAEMON Sun Jul 06 16:10:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZFpl-0006uk-8e
	for mharc-gzz-dev@gnu.org; Sun, 06 Jul 2003 16:10:05 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZFpi-0006rH-I3
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:10:02 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZFpg-0006mr-EV
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:10:01 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZFpf-0006Qh-Te
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:10:00 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h66K9pND030713;
	Sun, 6 Jul 2003 23:09:51 +0300
Received: from localhost (atsoukka@localhost)h66K9p7M030709;
	Sun, 6 Jul 2003 23:09:51 +0300
X-Authentication-Warning: verso.st.jyu.fi: atsoukka owned process doing -bs
Date: Sun, 6 Jul 2003 23:09:51 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@verso.st.jyu.fi
To: Matti Katila <majukati@cc.jyu.fi>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
In-Reply-To: <Pine.LNX.4.44.0307032318090.31128-100000@verso.st.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307062259070.29631-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: GZZ developers <gzz-dev@nongnu.org>
cc: Benja Fallenstein <b.fallenstein@gmx.de>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 06 Jul 2003 20:10:03 -0000

Hi,

Sorry, that I'm a bit late on that conversation. So, the structure after 
Benja's PEG would look something like:

             1:n                                 1:1
(Canvas) --contains-- (NodeOnCanvas)(x)(y) --transcludes-- (Node)

Basically, we would have made connection into a node. Did I understand the
PEG right?

As Tuomas told me, this could be done alternatively using reification. The 
term is still quite abstract for me (though, tried to learn it), so, 
probably you can tell me how it works :)

In my MindMap vision, connections between nodes and canvases could be 
shown/created/removed also on 2D structure view (Loom alike). Of course, 
the view should abstract the structure in these both solutions...

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Sun Jul 06 16:21:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZG1B-0001xr-TL
	for mharc-gzz-dev@gnu.org; Sun, 06 Jul 2003 16:21:53 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZG10-0001Pc-Fe
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:21:42 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZG0w-0001Ek-5z
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:21:39 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19ZG0t-00011M-UZ
	for gzz-dev@nongnu.org; Sun, 06 Jul 2003 16:21:36 -0400
Received: (qmail 32151 invoked by uid 65534); 6 Jul 2003 20:21:34 -0000
Received: from p5082D33B.dip.t-dialin.net (EHLO gmx.de) (80.130.211.59)
  by mail.gmx.net (mp013) with SMTP; 06 Jul 2003 22:21:34 +0200
Message-ID: <3F088484.60603@gmx.de>
Date: Sun, 06 Jul 2003 22:20:20 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
References: <Pine.LNX.4.44.0307062259070.29631-100000@verso.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307062259070.29631-100000@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: Matti Katila <majukati@cc.jyu.fi>
cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Sun, 06 Jul 2003 20:21:51 -0000

Asko Soukka wrote:
> Hi,
> 
> Sorry, that I'm a bit late on that conversation. So, the structure after 
> Benja's PEG would look something like:
> 
>              1:n                                 1:1
> (Canvas) --contains-- (NodeOnCanvas)(x)(y) --transcludes-- (Node)

No, no, the second cardinality is n:1! There can be an arbitrary number 
of NodeOnCanvas (maybe better called Coordinates) resources for each 
individual Node!

> Basically, we would have made connection into a node. Did I understand the
> PEG right?

Yes.

> As Tuomas told me, this could be done alternatively using reification. The 
> term is still quite abstract for me (though, tried to learn it), so, 
> probably you can tell me how it works :)

That's not a good idea for this, but FWIW, it would be like this--

reification --subject--> Canvas
reification --property--> contains
reification --object--> Node
reification --type--> Statement

I.e., the "reification" resource represents the statement which has 
'Canvas' as the subject; 'contains' as the property; and 'Node' as the 
object.

> In my MindMap vision, connections between nodes and canvases could be 
> shown/created/removed also on 2D structure view (Loom alike). Of course, 
> the view should abstract the structure in these both solutions...

Yes.

I don't like the term "2D structure view" btw: it's not a 2-dimensional 
plane, although it is shown on a 2-dimensional screen (which is IMHO the 
only sense it is '2D' -- in that sense, Quake is '2D' also...).

- Benja




From MAILER-DAEMON Mon Jul 07 04:28:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZRM3-00081E-KF
	for mharc-gzz-dev@gnu.org; Mon, 07 Jul 2003 04:28:11 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZRM0-00080A-VK
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 07 Jul 2003 04:28:08 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZRLy-0007yJ-T4
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 07 Jul 2003 04:28:07 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZRLy-0007xx-Cd
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 07 Jul 2003 04:28:06 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h678S2SL013134
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 7 Jul 2003 11:28:02 +0300
Received: from localhost (atsoukka@localhost)h678S1VN013130
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 7 Jul 2003 11:28:02 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Mon, 7 Jul 2003 11:28:01 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
In-Reply-To: <3F088484.60603@gmx.de>
Message-ID: <Pine.LNX.4.44.0307071102170.11631-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 07 Jul 2003 08:28:09 -0000

Hi,

Thanks, I'm for that PEG.

Mudyc is worried about the amount of buoys, when clones are also shown as 
them. And that is necessary to see, what all changes, when editing a 
cloned node. Well, the amount could really be a problem if all the 
clones of nodes on a single canvas are shown simultaneously.

Would it work in way that only clones of the node selected for editing are 
shown at once. I guess, showing clones of a single node is the most 
relevant, when editing that node.

Sun, 6 Jul 2003, Benja Fallenstein kirjoitti:
> > Sorry, that I'm a bit late on that conversation. So, the structure after 
> > Benja's PEG would look something like:
> > 
> >              1:n                                 1:1
> > (Canvas) --contains-- (NodeOnCanvas)(x)(y) --transcludes-- (Node)
> 
> No, no, the second cardinality is n:1! There can be an arbitrary number 
> of NodeOnCanvas (maybe better called Coordinates) resources for each 
> individual Node!

Oh, of course :)

> I don't like the term "2D structure view" btw: it's not a 2-dimensional 
> plane, although it is shown on a 2-dimensional screen (which is IMHO the 
> only sense it is '2D' -- in that sense, Quake is '2D' also...).

Would only "structure view" make enough difference for canvas views?

And AFAIK Loom Views are currently 2D because our nodeview won't scale
yet. Maybe I should discuss and work first for that. Now I'm going to farm
work again, but maybe on Thursday, or next week at the last.

That would make also the WheelView to be more useful.

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Mon Jul 07 18:27:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZePU-0002nB-P3
	for mharc-gzz-dev@gnu.org; Mon, 07 Jul 2003 18:24:36 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZeOl-0002Dq-VF
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 07 Jul 2003 18:23:51 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZeL3-0000sK-Jt
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 07 Jul 2003 18:20:02 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZeKA-0000aA-KZ
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 07 Jul 2003 18:19:06 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h67MJ2ND018151
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 8 Jul 2003 01:19:02 +0300
Received: from localhost (majukati@localhost)h67MJ2Ku018147
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 8 Jul 2003 01:19:02 +0300
Date: Tue, 8 Jul 2003 01:19:02 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <Pine.LNX.4.44.0307080058570.31128-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Gzz] View2D enhancing.
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Mon, 07 Jul 2003 22:24:34 -0000


Hi boys and girls,


I run into problems with View2D. I would like to make it use faster way 
to change scene i.e., through setParams. As you already know we have more 
than one main node with FenPDF. I have made a simple interface to change 
scene's parameters but it doesn't work because no one keeps track of all 
possible coordinate systems since recursive view2ds can be just one 
instance in the whole view. 

So can we add a new parameter to View2D?

    public abstract void render(VobScene vs, 
-		Object plane,
+		Object plane, Object key,
		int matchingParent,
		    int box2screen, int box2plane
			);


With this change and simple helper class:


/** Very simple util to save integer in map.
 */
public class CoordsysCache {
    private Map coords = new WeakHashMap(10);
    public void set(Object key, int cs) {
	coords.put(key, new Integer(cs));
    }
    
    public int get(Object key) {
	return ((Integer)coords.get(key)).intValue();
    }
}


We could use setParams easily and make things faster.


   -Matti




From MAILER-DAEMON Tue Jul 08 03:17:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZmjJ-0002GC-4I
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 03:17:37 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZmjG-0002FN-7y
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:17:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZmjE-0002F2-Qm
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:17:33 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZmjE-0002En-Ax
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:17:32 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h687HRUA008065
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 8 Jul 2003 10:17:27 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h687I0DP028996
	for gzz-dev@mail.freesoftware.fsf.org;
	Tue, 8 Jul 2003 10:18:00 +0300 (EETDST)
Date: Tue, 8 Jul 2003 10:18:00 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030708071800.GA28929@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Subject: [Gzz] [Lloyd.Rutledge@cwi.nl: Your Hypertext Short Paper submission
 invited as Poster]
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 07:17:34 -0000

----- Forwarded message from Lloyd Rutledge <Lloyd.Rutledge@cwi.nl> -----

To: "Tuomas J. Lukka" <lukka@iki.fi>
Subject: Your Hypertext Short Paper submission invited as Poster
Date: Sat, 05 Jul 2003 16:12:50 +0200
From: Lloyd Rutledge <Lloyd.Rutledge@cwi.nl>
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi


Hello,

I am pleased to inform you that although your submission "Bridging
Javadoc and design documentation via UML diagram image maps" for
Hypertext 2003 Short Papers was not accepted as such, it has instead
been, as recommended by the review committee, invited for
participation in the Poster and Demo Session.

To prepare your Poster/Demo, you will need to provide six things:

1) Confirmation of intention to attend and present the poster/demo (ASAP)
2) An abstract for the Website and conference handout (due July 23rd)
3) Two pages for the Website (due July 23rd)
4) The poster itself (bring to the conference)
5) Confirm that you will also give a demo with your poster
6) Registration for the conference

The abstract and two page description need to be sent to me by
Wednesday, July 23rd, in three weeks.  The format instructions for the
two page description are available at
http://www.ht03.org/submissions.html#formatting.  Please address the
comments you received from the Short Paper reviews to improve the
poster's two page description, as well as the conceptual content of
the poster display itself, and perhaps even the demo itself, if
possible.

The board for displaying your poster at the conference will be 140cm
wide and 180 cm high.  This you will need to print yourself and bring
to the conference.  We will provide adhesive Velcro tabs for hanging
them.  Let me know if you plan on giving a demo as well.  If you are
giving a demo, we assume you will bring all equipment you need
(including power adapters!).  We will provide electricity, of course.
I will send you more details as they become available.

Don't forget to register for the conference before Friday July 11th,
because that's when the Early registration rate ends.

See you there,
Lloyd Rutledge, Hypertext 2003 Posters and Demonstrations Chair

--
Lloyd Rutledge  vox: +31 20 592 40 93       fax: +31 20 592 43 12
CWI             net: Lloyd.Rutledge@cwi.nl  Web: http://www.cwi.nl/~lloyd
Post:   PO Box 94079    |  NL-1090 GB Amsterdam  |  The Netherlands
Street: Kruislaan 413/C |  NL-1098 SJ Amsterdam  |  The Netherlands

----- End forwarded message -----



From MAILER-DAEMON Tue Jul 08 03:26:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZmrT-0008Bw-Qa
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 03:26:03 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19Zmpn-0007AD-DV
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:24:19 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Zmpa-00075l-1C
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:24:06 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZmoT-0006De-H9
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:22:57 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h687MpUA008316;
	Tue, 8 Jul 2003 10:22:51 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h687NPLf029016;
	Tue, 8 Jul 2003 10:23:25 +0300 (EETDST)
Date: Tue, 8 Jul 2003 10:23:25 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Message-ID: <20030708072325.GB28929@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Subject: [Gzz] UMLLink paper
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 07:25:54 -0000

(to Benja, Cc'd to list)

Hi, could you let me know ASAP if you could take care of the UMLLink
paper (it was accepted as a poster). Asko and I are on holiday,
and Tuukka is in Poland, apparently.

If not, I can do it but I'd prefer to stay on holiday.

BTW: what were the copyright forms, when do I need to mail them?

	Tuomas



From MAILER-DAEMON Tue Jul 08 03:30:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZmvI-0003yR-Da
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 03:30:00 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZmuX-0002Ks-Jy
	for gzz-dev@nongnu.org; Tue, 08 Jul 2003 03:29:13 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Zmrm-0000FR-3v
	for gzz-dev@nongnu.org; Tue, 08 Jul 2003 03:26:23 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19Zmrc-00005Q-Ba
	for gzz-dev@nongnu.org; Tue, 08 Jul 2003 03:26:12 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h687Q9UA008536;
	Tue, 8 Jul 2003 10:26:09 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h687QgDL029031;
	Tue, 8 Jul 2003 10:26:42 +0300 (EETDST)
Date: Tue, 8 Jul 2003 10:26:42 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] REPOST: PEG: Alter Canvas2D vocab to support transclusions
Message-ID: <20030708072642.GD28929@tarzan.it.jyu.fi>
References: <3F043E57.4000600@gmx.de>
	<Pine.LNX.4.44.0307032318090.31128-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307032318090.31128-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
cc: GZZ developers <gzz-dev@nongnu.org>
cc: Benja Fallenstein <b.fallenstein@gmx.de>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 07:29:58 -0000

On Sun, Jul 06, 2003 at 10:34:14PM +0300, Matti Katila wrote:
> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
> > Matti Katila wrote:
> >> On Thu, 3 Jul 2003, Benja Fallenstein wrote:
> >>>The failure of taking this into account means that there cannot
> >>>be transclusions of a node, i.e. one node cannot be placed
> >>>on multiple papers; in Fenfire, transclusion must be supported
> >>>for *anything*, i.e., whenever some thing is in a "context,"
> >>>it must be possible to place it in more than one context.
> >>>
> >>>In order to make nodes transcludable, the vocabulary
> >>>must be changed.
> >> 
> >> Making clones is something what I wouldn't do in word-processing.
> >> Same with pictures. If you are talkking about mindmap thing we should not 
> >> mess it up with canvas2d which is "making notes" - not "making clone 
> >> notes".
> >> 
> >> If you really want to do clones, you also need to make a new api for it 
> >> (similar like ppactions) because pp should not do a such thing.
> >> 
> >> CanvasView2D can be programmed to render also these clone notes.
> > 
> > 
> > We have discussed this at length on IRC, without coming to an agreement. 
> > Here's my summary (keep in mind that it's from *my* POV):
> > 
> > - Mudyc agrees that transclusion of nodes is needed for some things, 
> > e.g. mindmapping, but not for some other applications of 2D canvases, 
> > such as 'general "text"'.
> 
> And my biggest point is that user should recognize if node is clone or 
> not, on canvas. 

Actually, one thing I recently realized is that clones are dangerous,
*if* the user interface doesn't show all the other contexts into which
something has been cloned.

If it does, no problem.

	Tuomas



From MAILER-DAEMON Tue Jul 08 03:34:20 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZmzS-00067C-Bx
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 03:34:18 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZmyL-0005Z1-0H
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:33:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Zmy9-0005Uv-GO
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:33:00 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19Zmx3-00052b-Gy
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 03:31:49 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h687VkUA008707;
	Tue, 8 Jul 2003 10:31:46 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h687WKrf029123;
	Tue, 8 Jul 2003 10:32:20 +0300 (EETDST)
Date: Tue, 8 Jul 2003 10:32:20 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] View2D enhancing.
Message-ID: <20030708073220.GE28929@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307080058570.31128-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307080058570.31128-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
cc: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 07:34:16 -0000

On Tue, Jul 08, 2003 at 01:19:02AM +0300, Matti Katila wrote:
> 
> Hi boys and girls,
> 
> 
> I run into problems with View2D. I would like to make it use faster way 
> to change scene i.e., through setParams. As you already know we have more 
> than one main node with FenPDF. I have made a simple interface to change 
> scene's parameters but it doesn't work because no one keeps track of all 
> possible coordinate systems since recursive view2ds can be just one 
> instance in the whole view. 
> 
> So can we add a new parameter to View2D?
> 
>     public abstract void render(VobScene vs, 
> -		Object plane,
> +		Object plane, Object key,
> 		int matchingParent,
> 		    int box2screen, int box2plane
> 			);
> 
> 
> With this change and simple helper class:

Umm, I'm not at all in the clear about what you're trying to achieve
and how.

You need to give lots more detail about this so that everyone can understand
the issues.

> 
> /** Very simple util to save integer in map.
>  */
> public class CoordsysCache {
>     private Map coords = new WeakHashMap(10);
>     public void set(Object key, int cs) {
> 	coords.put(key, new Integer(cs));
>     }
>     
>     public int get(Object key) {
> 	return ((Integer)coords.get(key)).intValue();
>     }
> }
> 
> 
> We could use setParams easily and make things faster.

This is very bad on Kaffe and possibly others, creating lots of
Integer objects for the GC to worry about.

	Tuomas



From MAILER-DAEMON Tue Jul 08 06:14:21 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZpUD-0002B8-SF
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 06:14:13 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZpTv-00021Z-8n
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 06:13:55 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZpPf-0001Qz-Ox
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 06:09:33 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZpOu-00011p-Br
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 06:08:44 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h68A8fND004787
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 8 Jul 2003 13:08:41 +0300
Received: from localhost (majukati@localhost)h68A8enX004783
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 8 Jul 2003 13:08:41 +0300
Date: Tue, 8 Jul 2003 13:08:40 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
Subject: Re: [Gzz] View2D enhancing.
In-Reply-To: <20030708073220.GE28929@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307081215040.31128-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 10:14:12 -0000


On Tue, 8 Jul 2003, Tuomas Lukka wrote:
> On Tue, Jul 08, 2003 at 01:19:02AM +0300, Matti Katila wrote:
> > I run into problems with View2D. I would like to make it use faster way 
> > to change scene i.e., through setParams. As you already know we have more 
> > than one main node with FenPDF. I have made a simple interface to change 
> > scene's parameters but it doesn't work because no one keeps track of all 
> > possible coordinate systems since recursive view2ds can be just one 
> > instance in the whole view. 
> > 
> > So can we add a new parameter to View2D?
> > 
> >     public abstract void render(VobScene vs, 
> > -		Object plane,
> > +		Object plane, Object key,
> > 		int matchingParent,
> > 		    int box2screen, int box2plane
> > 			);
> > 
> > 
> > With this change and simple helper class:
> 
> Umm, I'm not at all in the clear about what you're trying to achieve
> and how.

View2D is one big instance and it renders all viewports shown in screen, 
main nodes and buoys currently. Dragging of main node can be made fast 
because we can save the coordsys number in the main node instance.
We can't use fast dragging(using the same vobscene and changing coordsys 
parameters) with: moving notes, selecting area because they are a part of 
View2D chain instance and saving the coordsys number there is ridiculous 
in the current View2D chain layer as I noticed it. So if we want speed - 
we need to save that coordsystem to somewhere.


> > /** Very simple util to save integer in map.
> >  */
> > public class CoordsysCache {
> >     private Map coords = new WeakHashMap(10);
> >     public void set(Object key, int cs) {
> > 	coords.put(key, new Integer(cs));
> >     }
> >     
> >     public int get(Object key) {
> > 	return ((Integer)coords.get(key)).intValue();
> >     }
> > }
> > 
> > 
> > We could use setParams easily and make things faster.
> 
> This is very bad on Kaffe and possibly others, creating lots of
> Integer objects for the GC to worry about.

Other possibility is to create a new View2D chain instance for every 
viewport.


   -Matti




From MAILER-DAEMON Tue Jul 08 09:43:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19Zsk1-0004nm-7p
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 09:42:45 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19Zsit-00045G-KW
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 09:41:35 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Zsby-00020u-Lu
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 09:34:27 -0400
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19ZsUX-0007Dz-Ef
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 09:26:45 -0400
Received: (qmail 26585 invoked by uid 65534); 8 Jul 2003 13:26:40 -0000
Received: from pD9588997.dip.t-dialin.net (EHLO gmx.de) (217.88.137.151)
  by mail.gmx.net (mp007) with SMTP; 08 Jul 2003 15:26:40 +0200
Message-ID: <3F0AC643.206@gmx.de>
Date: Tue, 08 Jul 2003 15:25:23 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Eric Armstrong <eric.armstrong@sun.com>
Subject: Re: [Gzz] Re: the Storm article
References: <Pine.LNX.4.44.0303070805040.29578-100000@tols16.oulu.fi>
	<3E6923C6.60500@gmx.de> <3E693B64.F683DBA7@sun.com>
In-Reply-To: <3E693B64.F683DBA7@sun.com>
Content-Type: multipart/mixed;
 boundary="------------040008000200030306060304"
cc: Oinas-Kukkonen Harri <hok@tols16.oulu.fi>
cc: Alatalo Toni <antont@tols16.oulu.fi>
cc: gzz-dev@mail.freesoftware.fsf.org
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 13:42:42 -0000

This is a multi-part message in MIME format.
--------------040008000200030306060304
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Hi Eric,

Eric Armstrong wrote:
> Benja Fallenstein wrote:
 >>>
>>>I look forward to "Taking the World by Storm".
>>
>>And I'm looking forward to that article! ;)
>>
> 
> I wrote up a starter page. I'll be needing a pointer
> to wherever this paper gets published. Then I'll need to do
> a close read of the final version and come up with a big 
> picture summary that explains why this will be the best thing
> since sliced bread -- and find a publisher. (The fact that its
> written in Java will help, since I'm in touch with several
> editors....)

Our original submission was rejected, because some of the reviewers 
strongly believed that there would be hash collisions (we didn't say in 
the paper how unlikely that is, mathematically, as you remember :) ). We 
were encouraged to re-submit as a short paper, and that was accepted. 
I've attached it.

It will be published in: http://www.ht03.org/

I currently use Storm to store my own notes (written in emacs) and I'm 
already quite satisfied with it, so I think we're nearing the point 
where we can make a first public release.

However, pointers (i.e., documents that you can change) aren't yet in a 
state where we could make the persistency commitment on them, and thus I 
don't feel ready to make a public release yet. :( Because, if people 
saved data in Storm using the current format, later versions of Storm 
wouldn't be able to read it. So I wouldn't feel confident asking people 
to start using it in its current form.

Currently doing research on the problem (lots of thinking), and I hope 
to get something done "real soon now" ;-)

(The research problem with pointers is that it's not really good enough 
to bind pointers to cryptographic public keys-- you want to be able to 
change keys when your original key gets leaked to the public, for 
example, and have your pointers continue to work. If you want, I can 
give you an update with the details.)

Cheers,
- Benja

--------------040008000200030306060304
Content-Type: application/postscript;
 name="pp192-fallenstein.ps"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="pp192-fallenstein.ps"

%!PS-Adobe-2.0
%%Creator: dvips(k) 5.92b Copyright 2002 Radical Eye Software
%%Title: short-paper.gen.dvi
%%Pages: 2
%%PageOrder: Ascend
%%BoundingBox: 0 0 612 792
%%DocumentFonts: Helvetica-Bold Helvetica Times-Bold Times-Roman
%%+ Times-Italic CMR6 CMR9 CMTT9
%%EndComments
%DVIPSWebPage: (www.radicaleye.com)
%DVIPSCommandLine: dvips -P cmz -t letter short-paper.gen.dvi -o
%+ short-paper.gen.ps
%DVIPSParameters: dpi=600, compressed
%DVIPSSource:  TeX output 2003.06.22:1242
%%BeginProcSet: texc.pro
%!
/TeXDict 300 dict def TeXDict begin/N{def}def/B{bind def}N/S{exch}N/X{S
N}B/A{dup}B/TR{translate}N/isls false N/vsize 11 72 mul N/hsize 8.5 72
mul N/landplus90{false}def/@rigin{isls{[0 landplus90{1 -1}{-1 1}ifelse 0
0 0]concat}if 72 Resolution div 72 VResolution div neg scale isls{
landplus90{VResolution 72 div vsize mul 0 exch}{Resolution -72 div hsize
mul 0}ifelse TR}if Resolution VResolution vsize -72 div 1 add mul TR[
matrix currentmatrix{A A round sub abs 0.00001 lt{round}if}forall round
exch round exch]setmatrix}N/@landscape{/isls true N}B/@manualfeed{
statusdict/manualfeed true put}B/@copies{/#copies X}B/FMat[1 0 0 -1 0 0]
N/FBB[0 0 0 0]N/nn 0 N/IEn 0 N/ctr 0 N/df-tail{/nn 8 dict N nn begin
/FontType 3 N/FontMatrix fntrx N/FontBBox FBB N string/base X array
/BitMaps X/BuildChar{CharBuilder}N/Encoding IEn N end A{/foo setfont}2
array copy cvx N load 0 nn put/ctr 0 N[}B/sf 0 N/df{/sf 1 N/fntrx FMat N
df-tail}B/dfs{div/sf X/fntrx[sf 0 0 sf neg 0 0]N df-tail}B/E{pop nn A
definefont setfont}B/Cw{Cd A length 5 sub get}B/Ch{Cd A length 4 sub get
}B/Cx{128 Cd A length 3 sub get sub}B/Cy{Cd A length 2 sub get 127 sub}
B/Cdx{Cd A length 1 sub get}B/Ci{Cd A type/stringtype ne{ctr get/ctr ctr
1 add N}if}B/id 0 N/rw 0 N/rc 0 N/gp 0 N/cp 0 N/G 0 N/CharBuilder{save 3
1 roll S A/base get 2 index get S/BitMaps get S get/Cd X pop/ctr 0 N Cdx
0 Cx Cy Ch sub Cx Cw add Cy setcachedevice Cw Ch true[1 0 0 -1 -.1 Cx
sub Cy .1 sub]/id Ci N/rw Cw 7 add 8 idiv string N/rc 0 N/gp 0 N/cp 0 N{
rc 0 ne{rc 1 sub/rc X rw}{G}ifelse}imagemask restore}B/G{{id gp get/gp
gp 1 add N A 18 mod S 18 idiv pl S get exec}loop}B/adv{cp add/cp X}B
/chg{rw cp id gp 4 index getinterval putinterval A gp add/gp X adv}B/nd{
/cp 0 N rw exit}B/lsh{rw cp 2 copy get A 0 eq{pop 1}{A 255 eq{pop 254}{
A A add 255 and S 1 and or}ifelse}ifelse put 1 adv}B/rsh{rw cp 2 copy
get A 0 eq{pop 128}{A 255 eq{pop 127}{A 2 idiv S 128 and or}ifelse}
ifelse put 1 adv}B/clr{rw cp 2 index string putinterval adv}B/set{rw cp
fillstr 0 4 index getinterval putinterval adv}B/fillstr 18 string 0 1 17
{2 copy 255 put pop}for N/pl[{adv 1 chg}{adv 1 chg nd}{1 add chg}{1 add
chg nd}{adv lsh}{adv lsh nd}{adv rsh}{adv rsh nd}{1 add adv}{/rc X nd}{
1 add set}{1 add clr}{adv 2 chg}{adv 2 chg nd}{pop nd}]A{bind pop}
forall N/D{/cc X A type/stringtype ne{]}if nn/base get cc ctr put nn
/BitMaps get S ctr S sf 1 ne{A A length 1 sub A 2 index S get sf div put
}if put/ctr ctr 1 add N}B/I{cc 1 add D}B/bop{userdict/bop-hook known{
bop-hook}if/SI save N @rigin 0 0 moveto/V matrix currentmatrix A 1 get A
mul exch 0 get A mul add .99 lt{/QV}{/RV}ifelse load def pop pop}N/eop{
SI restore userdict/eop-hook known{eop-hook}if showpage}N/@start{
userdict/start-hook known{start-hook}if pop/VResolution X/Resolution X
1000 div/DVImag X/IEn 256 array N 2 string 0 1 255{IEn S A 360 add 36 4
index cvrs cvn put}for pop 65781.76 div/vsize X 65781.76 div/hsize X}N
/p{show}N/RMat[1 0 0 -1 0 0]N/BDot 260 string N/Rx 0 N/Ry 0 N/V{}B/RV/v{
/Ry X/Rx X V}B statusdict begin/product where{pop false[(Display)(NeXT)
(LaserWriter 16/600)]{A length product length le{A length product exch 0
exch getinterval eq{pop true exit}if}{pop}ifelse}forall}{false}ifelse
end{{gsave TR -.1 .1 TR 1 1 scale Rx Ry false RMat{BDot}imagemask
grestore}}{{gsave TR -.1 .1 TR Rx Ry scale 1 1 false RMat{BDot}
imagemask grestore}}ifelse B/QV{gsave newpath transform round exch round
exch itransform moveto Rx 0 rlineto 0 Ry neg rlineto Rx neg 0 rlineto
fill grestore}B/a{moveto}B/delta 0 N/tail{A/delta X 0 rmoveto}B/M{S p
delta add tail}B/b{S p tail}B/c{-4 M}B/d{-3 M}B/e{-2 M}B/f{-1 M}B/g{0 M}
B/h{1 M}B/i{2 M}B/j{3 M}B/k{4 M}B/w{0 rmoveto}B/l{p -4 w}B/m{p -3 w}B/n{
p -2 w}B/o{p -1 w}B/q{p 1 w}B/r{p 2 w}B/s{p 3 w}B/t{p 4 w}B/x{0 S
rmoveto}B/y{3 2 roll p a}B/bos{/SS save N}B/eos{SS restore}B end

%%EndProcSet
%%BeginProcSet: 8r.enc
% File  8r.enc as of 2002-03-12 for PSNFSS 9
%
% This is the encoding vector for Type1 and TrueType fonts to be used
% with TeX.  This file is part of the PSNFSS bundle, version 9
% 
% Authors: S. Rahtz, P. MacKay, Alan Jeffrey, B. Horn, K. Berry, W. Schmidt
%
% Idea is to have all the characters normally included in Type 1 fonts
% available for typesetting. This is effectively the characters in Adobe
% Standard Encoding + ISO Latin 1 + extra characters from Lucida + Euro.
% 
% Character code assignments were made as follows:
% 
% (1) the Windows ANSI characters are almost all in their Windows ANSI
% positions, because some Windows users cannot easily reencode the
% fonts, and it makes no difference on other systems. The only Windows
% ANSI characters not available are those that make no sense for
% typesetting -- rubout (127 decimal), nobreakspace (160), softhyphen
% (173). quotesingle and grave are moved just because it's such an
% irritation not having them in TeX positions.
% 
% (2) Remaining characters are assigned arbitrarily to the lower part
% of the range, avoiding 0, 10 and 13 in case we meet dumb software.
% 
% (3) Y&Y Lucida Bright includes some extra text characters; in the
% hopes that other PostScript fonts, perhaps created for public
% consumption, will include them, they are included starting at 0x12.
% 
% (4) Remaining positions left undefined are for use in (hopefully)
% upward-compatible revisions, if someday more characters are generally
% available.
% 
% (5) hyphen appears twice for compatibility with both ASCII and Windows.
%
% (6) /Euro is assigned to 128, as in Windows ANSI
% 
/TeXBase1Encoding [
% 0x00 (encoded characters from Adobe Standard not in Windows 3.1)
  /.notdef /dotaccent /fi /fl
  /fraction /hungarumlaut /Lslash /lslash
  /ogonek /ring /.notdef
  /breve /minus /.notdef 
% These are the only two remaining unencoded characters, so may as
% well include them.
  /Zcaron /zcaron 
% 0x10
 /caron /dotlessi 
% (unusual TeX characters available in, e.g., Lucida Bright)
 /dotlessj /ff /ffi /ffl 
 /.notdef /.notdef /.notdef /.notdef
 /.notdef /.notdef /.notdef /.notdef
 % very contentious; it's so painful not having quoteleft and quoteright
 % at 96 and 145 that we move the things normally found there down to here.
 /grave /quotesingle 
% 0x20 (ASCII begins)
 /space /exclam /quotedbl /numbersign
 /dollar /percent /ampersand /quoteright
 /parenleft /parenright /asterisk /plus /comma /hyphen /period /slash
% 0x30
 /zero /one /two /three /four /five /six /seven
 /eight /nine /colon /semicolon /less /equal /greater /question
% 0x40
 /at /A /B /C /D /E /F /G /H /I /J /K /L /M /N /O
% 0x50
 /P /Q /R /S /T /U /V /W
 /X /Y /Z /bracketleft /backslash /bracketright /asciicircum /underscore
% 0x60
 /quoteleft /a /b /c /d /e /f /g /h /i /j /k /l /m /n /o
% 0x70
 /p /q /r /s /t /u /v /w
 /x /y /z /braceleft /bar /braceright /asciitilde
 /.notdef % rubout; ASCII ends
% 0x80
 /Euro /.notdef /quotesinglbase /florin
 /quotedblbase /ellipsis /dagger /daggerdbl
 /circumflex /perthousand /Scaron /guilsinglleft
 /OE /.notdef /.notdef /.notdef
% 0x90
 /.notdef /.notdef /.notdef /quotedblleft
 /quotedblright /bullet /endash /emdash
 /tilde /trademark /scaron /guilsinglright
 /oe /.notdef /.notdef /Ydieresis
% 0xA0
 /.notdef % nobreakspace
 /exclamdown /cent /sterling
 /currency /yen /brokenbar /section
 /dieresis /copyright /ordfeminine /guillemotleft
 /logicalnot
 /hyphen % Y&Y (also at 45); Windows' softhyphen
 /registered
 /macron
% 0xD0
 /degree /plusminus /twosuperior /threesuperior
 /acute /mu /paragraph /periodcentered
 /cedilla /onesuperior /ordmasculine /guillemotright
 /onequarter /onehalf /threequarters /questiondown
% 0xC0
 /Agrave /Aacute /Acircumflex /Atilde /Adieresis /Aring /AE /Ccedilla
 /Egrave /Eacute /Ecircumflex /Edieresis
 /Igrave /Iacute /Icircumflex /Idieresis
% 0xD0
 /Eth /Ntilde /Ograve /Oacute
 /Ocircumflex /Otilde /Odieresis /multiply
 /Oslash /Ugrave /Uacute /Ucircumflex
 /Udieresis /Yacute /Thorn /germandbls
% 0xE0
 /agrave /aacute /acircumflex /atilde
 /adieresis /aring /ae /ccedilla
 /egrave /eacute /ecircumflex /edieresis
 /igrave /iacute /icircumflex /idieresis
% 0xF0
 /eth /ntilde /ograve /oacute
 /ocircumflex /otilde /odieresis /divide
 /oslash /ugrave /uacute /ucircumflex
 /udieresis /yacute /thorn /ydieresis
] def

%%EndProcSet
%%BeginProcSet: texps.pro
%!
TeXDict begin/rf{findfont dup length 1 add dict begin{1 index/FID ne 2
index/UniqueID ne and{def}{pop pop}ifelse}forall[1 index 0 6 -1 roll
exec 0 exch 5 -1 roll VResolution Resolution div mul neg 0 0]FontType 0
ne{/Metrics exch def dict begin Encoding{exch dup type/integertype ne{
pop pop 1 sub dup 0 le{pop}{[}ifelse}{FontMatrix 0 get div Metrics 0 get
div def}ifelse}forall Metrics/Metrics currentdict end def}{{1 index type
/nametype eq{exit}if exch pop}loop}ifelse[2 index currentdict end
definefont 3 -1 roll makefont/setfont cvx]cvx def}def/ObliqueSlant{dup
sin S cos div neg}B/SlantFont{4 index mul add}def/ExtendFont{3 -1 roll
mul exch}def/ReEncodeFont{CharStrings rcheck{/Encoding false def dup[
exch{dup CharStrings exch known not{pop/.notdef/Encoding true def}if}
forall Encoding{]exch pop}{cleartomark}ifelse}if/Encoding exch def}def
end

%%EndProcSet
%%BeginProcSet: special.pro
%!
TeXDict begin/SDict 200 dict N SDict begin/@SpecialDefaults{/hs 612 N
/vs 792 N/ho 0 N/vo 0 N/hsc 1 N/vsc 1 N/ang 0 N/CLIP 0 N/rwiSeen false N
/rhiSeen false N/letter{}N/note{}N/a4{}N/legal{}N}B/@scaleunit 100 N
/@hscale{@scaleunit div/hsc X}B/@vscale{@scaleunit div/vsc X}B/@hsize{
/hs X/CLIP 1 N}B/@vsize{/vs X/CLIP 1 N}B/@clip{/CLIP 2 N}B/@hoffset{/ho
X}B/@voffset{/vo X}B/@angle{/ang X}B/@rwi{10 div/rwi X/rwiSeen true N}B
/@rhi{10 div/rhi X/rhiSeen true N}B/@llx{/llx X}B/@lly{/lly X}B/@urx{
/urx X}B/@ury{/ury X}B/magscale true def end/@MacSetUp{userdict/md known
{userdict/md get type/dicttype eq{userdict begin md length 10 add md
maxlength ge{/md md dup length 20 add dict copy def}if end md begin
/letter{}N/note{}N/legal{}N/od{txpose 1 0 mtx defaultmatrix dtransform S
atan/pa X newpath clippath mark{transform{itransform moveto}}{transform{
itransform lineto}}{6 -2 roll transform 6 -2 roll transform 6 -2 roll
transform{itransform 6 2 roll itransform 6 2 roll itransform 6 2 roll
curveto}}{{closepath}}pathforall newpath counttomark array astore/gc xdf
pop ct 39 0 put 10 fz 0 fs 2 F/|______Courier fnt invertflag{PaintBlack}
if}N/txpose{pxs pys scale ppr aload pop por{noflips{pop S neg S TR pop 1
-1 scale}if xflip yflip and{pop S neg S TR 180 rotate 1 -1 scale ppr 3
get ppr 1 get neg sub neg ppr 2 get ppr 0 get neg sub neg TR}if xflip
yflip not and{pop S neg S TR pop 180 rotate ppr 3 get ppr 1 get neg sub
neg 0 TR}if yflip xflip not and{ppr 1 get neg ppr 0 get neg TR}if}{
noflips{TR pop pop 270 rotate 1 -1 scale}if xflip yflip and{TR pop pop
90 rotate 1 -1 scale ppr 3 get ppr 1 get neg sub neg ppr 2 get ppr 0 get
neg sub neg TR}if xflip yflip not and{TR pop pop 90 rotate ppr 3 get ppr
1 get neg sub neg 0 TR}if yflip xflip not and{TR pop pop 270 rotate ppr
2 get ppr 0 get neg sub neg 0 S TR}if}ifelse scaleby96{ppr aload pop 4
-1 roll add 2 div 3 1 roll add 2 div 2 copy TR .96 dup scale neg S neg S
TR}if}N/cp{pop pop showpage pm restore}N end}if}if}N/normalscale{
Resolution 72 div VResolution 72 div neg scale magscale{DVImag dup scale
}if 0 setgray}N/psfts{S 65781.76 div N}N/startTexFig{/psf$SavedState
save N userdict maxlength dict begin/magscale true def normalscale
currentpoint TR/psf$ury psfts/psf$urx psfts/psf$lly psfts/psf$llx psfts
/psf$y psfts/psf$x psfts currentpoint/psf$cy X/psf$cx X/psf$sx psf$x
psf$urx psf$llx sub div N/psf$sy psf$y psf$ury psf$lly sub div N psf$sx
psf$sy scale psf$cx psf$sx div psf$llx sub psf$cy psf$sy div psf$ury sub
TR/showpage{}N/erasepage{}N/setpagedevice{pop}N/copypage{}N/p 3 def
@MacSetUp}N/doclip{psf$llx psf$lly psf$urx psf$ury currentpoint 6 2 roll
newpath 4 copy 4 2 roll moveto 6 -1 roll S lineto S lineto S lineto
closepath clip newpath moveto}N/endTexFig{end psf$SavedState restore}N
/@beginspecial{SDict begin/SpecialSave save N gsave normalscale
currentpoint TR @SpecialDefaults count/ocount X/dcount countdictstack N}
N/@setspecial{CLIP 1 eq{newpath 0 0 moveto hs 0 rlineto 0 vs rlineto hs
neg 0 rlineto closepath clip}if ho vo TR hsc vsc scale ang rotate
rwiSeen{rwi urx llx sub div rhiSeen{rhi ury lly sub div}{dup}ifelse
scale llx neg lly neg TR}{rhiSeen{rhi ury lly sub div dup scale llx neg
lly neg TR}if}ifelse CLIP 2 eq{newpath llx lly moveto urx lly lineto urx
ury lineto llx ury lineto closepath clip}if/showpage{}N/erasepage{}N
/setpagedevice{pop}N/copypage{}N newpath}N/@endspecial{count ocount sub{
pop}repeat countdictstack dcount sub{end}repeat grestore SpecialSave
restore end}N/@defspecial{SDict begin}N/@fedspecial{end}B/li{lineto}B
/rl{rlineto}B/rc{rcurveto}B/np{/SaveX currentpoint/SaveY X N 1
setlinecap newpath}N/st{stroke SaveX SaveY moveto}N/fil{fill SaveX SaveY
moveto}N/ellipse{/endangle X/startangle X/yrad X/xrad X/savematrix
matrix currentmatrix N TR xrad yrad scale 0 0 1 startangle endangle arc
savematrix setmatrix}N end

%%EndProcSet
TeXDict begin @defspecial

 /DvipsToPDF { 72.27 mul Resolution div } def /PDFToDvips { 72.27 div
Resolution mul } def /HyperBorder { 1 PDFToDvips } def /H.V {pdf@hoff
pdf@voff null} def /H.B {/Rect[pdf@llx pdf@lly pdf@urx pdf@ury]} def
/H.S { currentpoint HyperBorder add /pdf@lly exch def dup DvipsToPDF
/pdf@hoff exch def HyperBorder sub /pdf@llx exch def } def /H.L { 2
sub dup /HyperBasePt exch def PDFToDvips /HyperBaseDvips exch def currentpoint
HyperBaseDvips sub /pdf@ury exch def /pdf@urx exch def } def /H.A {
H.L currentpoint exch pop vsize 72 sub exch DvipsToPDF HyperBasePt
sub sub /pdf@voff exch def } def /H.R { currentpoint HyperBorder sub
/pdf@ury exch def HyperBorder add /pdf@urx exch def currentpoint exch
pop vsize 72 sub exch DvipsToPDF sub /pdf@voff exch def } def systemdict
/pdfmark known not {userdict /pdfmark systemdict /cleartomark get put}
if
 
@fedspecial end
%%BeginFont: CMTT9
%!PS-AdobeFont-1.1: CMTT9 1.0
%%CreationDate: 1991 Aug 20 16:46:24
% Copyright (C) 1997 American Mathematical Society. All Rights Reserved.
11 dict begin
/FontInfo 7 dict dup begin
/version (1.0) readonly def
/Notice (Copyright (C) 1997 American Mathematical Society. All Rights Reserved) readonly def
/FullName (CMTT9) readonly def
/FamilyName (Computer Modern) readonly def
/Weight (Medium) readonly def
/ItalicAngle 0 def
/isFixedPitch true def
end readonly def
/FontName /CMTT9 def
/PaintType 0 def
/FontType 1 def
/FontMatrix [0.001 0 0 0.001 0 0] readonly def
/Encoding 256 array
0 1 255 {1 index exch /.notdef put} for
dup 46 /period put
dup 47 /slash put
dup 58 /colon put
dup 97 /a put
dup 99 /c put
dup 101 /e put
dup 103 /g put
dup 104 /h put
dup 106 /j put
dup 108 /l put
dup 109 /m put
dup 110 /n put
dup 111 /o put
dup 112 /p put
dup 114 /r put
dup 115 /s put
dup 116 /t put
dup 117 /u put
dup 118 /v put
readonly def
/FontBBox{-6 -233 542 698}readonly def
/UniqueID 5000831 def
currentdict end
currentfile eexec
D9D66F633B846A97B686A97E45A3D0AA052A014267B7904EB3C0D3BD0B83D891
016CA6CA4B712ADEB258FAAB9A130EE605E61F77FC1B738ABC7C51CD46EF8171
9098D5FEE67660E69A7AB91B58F29A4D79E57022F783EB0FBBB6D4F4EC35014F
D2DECBA99459A4C59DF0C6EBA150284454E707DC2100C15B76B4C19B84363758
469A6C558785B226332152109871A9883487DD7710949204DDCF837E6A8708B8
2BDBF16FBC7512FAA308A093FE5F00F963068B8232429ED8B7CF6A3D879A2D1E
2931CE5F5D18C658602059F07BE66E6EFC9239D7AB2FB8A4CBD41675B8ECF279
650C29E53B14AC0E392A664848C1844B1CECBB2D5CFB72D0916B675C9A9A1E35
F12696A6F628473C604A95376468E06E295AD6F76CEB939D94113532050B9D5A
D2F41A9EFB9424D986612313B89EFE9C8A71313340B248F6853B1EDBF02B7F9E
F447220FE131D7D54CFB8AA1281DBAEA73E665BACB1F164552CC0CEDB63BD4B1
4A9AE8AC6FA02242DBE8DA46B64B6BFC11762F0784F216FC8B9120D688D1705A
438B14F5E5DEAF2A98408B3B64620DE3732A4DAE6D08D5D97E34C75DAE19EABD
BA0796165C1151BCBFB1DF8D29A63A8300DBDB9E3323CB82D0337598B83F4F2B
A97CF5196D4D1CEC1EDB8966E548C0D9C194C932319610FB43EA1B86322FE641
AB48770FF13BD475A7267E142388563D1A400419C585B22A9886074687BEDF74
D905BE8EE440BA2ABF28EAB673399B7F129B9729DD5564C681954621903B84BB
CAF89AC5ADB2932472DF29ADA2BDBDB4D05F65F28F5F4C529613D61858E0074A
082A852710A62A147C966F2B85B51B0BE85F11D2057C66FDD61F6C5755367980
9F4DE680601D4DA41B46F8D2148450000413C27AA39B586B74B977B25F0FD3C0
4BA1EBFAFDBEC531EA13DFBD6700E53818CE04D23886B8AE75DCC36BCD3189B1
0D55FAE27D0D126E82AEF31D7B5DF27E58C30BB0867D6D7AC1DA9EFB8A2DF095
B5B934A68EE122DA0A83B36C952431586B957990206194E89339048AA6EE4C53
703763505ED57C494DD907D0EEA04F6B1D4C8F3BA778F4E7AA832AAB4D75F024
61E91C6D25FD6823CB24FC863B545568B81CF5BDD00BB653944D15A513A204C4
6DB6366497AE9F7D1BD42213016D53BBBF57A87F74086C9494AE1A4C968F277F
E0FD7DD5608A88B18196E8E5E3F7BE544512B8D76EED9A22C4072C29A1FECC91
56A03A5C13374B6866AE4FA710F766E898299272DEC12CF461B8607E86A7E456
21CEB9C88DF4D81169B481F70FADE6390FB4B455EDACC2B053018F383CA5E144
D9B4B8DBAC7A551CF13073E9F81E28E7A383A17AD1A5C38D2B5BD5CBBC96ACA3
20F1B20EF6F7AD8B3F2214123B1A12C86E33E5F332854CDE9C7D4C8D28CB80CE
0785524D7CB5C26279BFAA797A270BF41B7A19D95C415E09A5A316A82F1D5C4C
752494BA1A3414B5733A393DB70F16BE2DA57F8C499BF1FFCBB81B5A37C35F43
81B72CCE0ACEC3C3D1A4739903FEB68F346D2C60FC76BECBA671168B6AFF6539
226621F5BFF2B4D460C7D7EEDF635EFE523DA92286404F953B16CF62CA1EFCAB
066C395C134B2494D73658BDC00459E6FD744D71ECF09031812E7C5DE0360339
6012E8B21665B52D06F0F0748B61B40CBB6C8151E37F2B9B057FE9A5160604F3
3788F05BD185830FC1BC3013C0526F99360C1FCEB9DBE18F94596C2998C5E071
033BC38072A4A9CAFE55FA866FDF0007DB17C4330F37127E7992D50D93DFCBC2
574E83EC0914E72FC53B559EC91BB1F006CF9162DB4EAE1B5E1C711EDFBB4E6D
55AD2624C8564AA30336A7992B405B632107079C6C6F2700BBC6768DB610CC45
C53B6F2D927C699495B6E927E869609601A893C4FD837212591EDDC015C1B057
65EE20B5EF29B802A050CF390AC0D4F4E551A01C35D88C1DB2BDC240CA83B2AB
ED7230D1A3DFC072CB493E09AC6B16E984BE72715C4E64DC27CB0428E19219B4
76E254B26B038E65EA7D9338C7DF427366765C8AAF8C7F7CC72C36F48A661048
CE4D399FDA8A80555A2E6F251813AD45234B735938AA5C99DB8C4D105107052B
57AD02DB008E6B0E78519AD8909C859A91925FB7F853552FB5E26775C108D927
34508F016EBF839C1DA00F872C623A3ABF92C05DCE05409D0D9549B9ADAE843E
A342148F451D99036EF1D0C5E290105658DDA2A3B92E2B396805AB2D6C0A7C22
7E224AF8EDB3AEC0D4E190827027FC41DE9870C81B210974001260DE8A0CCCAA
D72086F7931C70E75876DD1E1DB4E4549DBD9C42C2C9994D7CF253CE2A6F50D3
1BF88305A37F7DC8788F1120A4B1C01441527486639351E6808823CF0A2E023B
5A7B515E49134194AF8EA061D6724C76F3C77F4F167B9506AE9B7A5F2DB49BD1
843FE3E6ED956467F3D79D847B055E4E762FC0543EC4ADA16B9591C5405CFD08
E2BEC0E8FD534CA3F8ECC6807A80A0E66F0397B9A82CFF627C073B31CFD3E440
C6924973F615251477F346025015AADAEBB4ECF26C2A8ECC72059877A8BAB7A9
F67BBF6FA999BF2E779F1E3A75EE6961FED15AD67E0AAD5121E2D9F1B3B7A95A
5D34DE229FC589DA2B2262FEDF34A2764FD16A76333D55939A6BB85BC2A37C63
DE5239B2E0A1FB5516F1E7C0EB60EDE25174DF150264A350235FCD22CB268F14
22F0ED092282257C76DAFE74A9064B5C4CD0E1C51379122D8159E7CABD80EE73
CB858CFDD673A832893BD37C825D6A47A41E34ED71A286486DDDE89DE594D5E4
CE557614517F77601742A1A6A8757B159DB0733367A31E00717F6D6F3157B1C1
9F1316B910A764594B7B908572662B152D0B4F4073D4B5BE6466F8ACC8AAD955
6825F8A8E08E876A88307C651B9540F5DD23ECEB17D0D5CBD52CC309B2F43617
D61D1E87567575E5B6A7B26854130F307C08601404B743B0F1F3D01EE09EE409
ACC3A3D305D656E548ECBF48B641FDFE88200054EB1A586E621773DEE083A0F7
F0C467AD1FD73421F8D1FF9F71365FA0ABCEEF03EF994C64770B04C4BDC06B7F
D3AD5EF546AB2D2E399A68CD94F8125D4CFF45AD5C40B41CFCE5F2DB222DD0D6
61A0AAF7591DDF00DDDE15283DB0B16249BCF6A91A1ED3455882FFEB1D12259E
9A11C2797826AC1F08615D2587BF9D72602769BCBC014DD3EE92DC6ECAB6582C
0267AD2934C356D6737473843C7E5D7C659B7597EC6AEB04A7EBB8EC8FBE9516
C50FF43C616AF73508C7B9C878E5F87B4C0F066C17C5FF15CF21B230E398C443
494B58DC9907AB7F5427E0D524EEDEA5CAEA042E4CD81B5074509DF5E5EC58D7
70B9CFBE2FC7A26BCFACE06ECD42FFC259E4C3C926E6B9E3E73A7883FF58BF2C
D13B8BAD27FBB60AB5F36161488D08089895BA4F17D5B3E1809D5F512A23D99E
3ADEB1B5CA7704EED645809CB0166EDC288E4401B5DC7A9F70C6B2E28DBC2845
20029ED72E9FAEFE59781077A2476B0D4B9D968C94FB6A11FEB81091C9EF4866
41F4AB04C22A6316364262AB9405B016502D9C0A82BA8BF763F08D2CD7500928
9BCDB7159B44EA8D7141F09060F6B635FCCCC14380921AEC57EF2E02734F06DC
1CDD329BE1583DD1E4B301F4B1955203AC42B79CA0385F132AB10C8F31F20437
E73466457C81C065F2187164350BAFF8EC21F4C6AEE7D914FFAFB8AFC0CA5D47
F8E1E1C54D3F7C14514CBFE5DD7B1B888194C9206C255285C92F2F0E659BFBC8
AB396F59C3AF76A788508A72E0AAFC5549B671C4C2E48308815C655D202FB018
18B7C543900AD5102EDF212639ABEC21172CA0760535FF3A0C0F13EEB4081F12
BA4AD9206FD00178446046DF69BF3FFF3E94DB839E1B7A0995F963D230E80833
BDE5D6910209BCB7664907FF463CC4ECA1F28B8278F5571D1295BFE13285E8C7
0B0F681836F12A6A9CC7D5EC2211CC8D4B4D336935D49E961CFC61EEC7F3D6EB
8A63D88FEA13160C3BC3501C39F9BC15DCB0E639CE60ED86BBCABA8AC0C70459
FEFB0B2EFDE783CE018E20809A5780BB76A008ABD7F6B63A9AF7F232ECDBBA89
E00DD341115BD78CCA7D89D183C312E5F4483D260F91D0299B5EDF646D2F88B2
68AA2BBB9CB01264BE7E29DF22797F49DF389F94445B7D4B63DC0812129CDC6B
F60F38CB4DECD77398CE7B0A014034EFEE1B65B2A2BE714F027364A2B0907D32
F304DD09E057F3BCD4CB089BC4C2F8F6004ABCC8A877B27FEFE568ABC1B93371
0F84FE02F29A6D13F06574D8196760C997F86E2AC0BF25278F26BE4FB9615A29
C9803F79E32B7A891B68EC3F33F81796B058B2C2805CF7C6AD97717F1D160994
D61B5E833CDB2A45858EB3A00E4DC7DC21E14EF4085947DBADF652BB9A237F81
5798852F9653771DBF48E84642E1F25C9F51FD1F856BBA35D9471381BE700173
0B7EB5FC346A507A468A15E6297C90C33183A0503543F80A7FCFFFFD2ECDC80E
86D3FD70A78737C033CC575ECAC57A883B491EF092E8B85CCE59AF4746C8EE45
6E8C35823FA51987919DAC567F73F346454CF4E8FF2EB1CDC6B5408FB1D92DC6
5435F82EE127CA76B120372AFB9279D1C06D3AC4EA114CCE003A8EF609BFC12A
76E77718E7D940137694133A0B5201909CE5E01878D73C4A21063CCA92A903FD
D484B7758459F2ECFF7D08E6C0BFC855EE6998EB7CF1A1995E87C20AA0C32B93
DD1A27187A066518F83BE2AEDB385999F6DFF1B6967078F8020FA88500920D66
5DAA00EFF69D2ECAAC025604F07FD0FC7211872320CA8D4AD209B10D9EECD669
3ADCE84546FF0ED85A901DB664861413408FA91539C5BB6F3E610BCBCEAE1B1E
AD34C15D465DB9F72B578E3FD0C1F2C17CAB64D1668E88612E3E67F699B12276
5713B931523907FCD37D5861A163A70C7C0EFCEA8C5A789E60568A89F1A764D6
006FB1E75300871F526C3355399C4AFAD7849DBD73832284
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
cleartomark
%%EndFont 
%%BeginFont: CMR9
%!PS-AdobeFont-1.1: CMR9 1.0
%%CreationDate: 1991 Aug 20 16:39:59
% Copyright (C) 1997 American Mathematical Society. All Rights Reserved.
11 dict begin
/FontInfo 7 dict dup begin
/version (1.0) readonly def
/Notice (Copyright (C) 1997 American Mathematical Society. All Rights Reserved) readonly def
/FullName (CMR9) readonly def
/FamilyName (Computer Modern) readonly def
/Weight (Medium) readonly def
/ItalicAngle 0 def
/isFixedPitch false def
end readonly def
/FontName /CMR9 def
/PaintType 0 def
/FontType 1 def
/FontMatrix [0.001 0 0 0.001 0 0] readonly def
/Encoding 256 array
0 1 255 {1 index exch /.notdef put} for
dup 50 /two put
readonly def
/FontBBox{-39 -250 1036 750}readonly def
/UniqueID 5000792 def
currentdict end
currentfile eexec
D9D66F633B846A97B686A97E45A3D0AA052A014267B7904EB3C0D3BD0B83D891
016CA6CA4B712ADEB258FAAB9A130EE605E61F77FC1B738ABC7C51CD46EF8171
9098D5FEE67660E69A7AB91B58F29A4D79E57022F783EB0FBBB6D4F4EC35014F
D2DECBA99459A4C59DF0C6EBA150284454E707DC2100C15B76B4C19B84363758
469A6C558785B226332152109871A9883487DD7710949204DDCF837E6A8708B8
2BDBF16FBC7512FAA308A093FE5CF7158F1163BC1F3352E22A1452E73FECA8A4
87100FB1FFC4C8AF409B2067537220E605DA0852CA49839E1386AF9D7A1A455F
D1F017CE45884D76EF2CB9BC5821FD25365DDEA6E45F332B5F68A44AD8A530F0
92A36FADB679CF58BAFDD3E51DFDD314B91A605515D729EE20C42505FD4E0835
3C9D365B14C003BC6DD352F0228A8C161F172D2551CD1C67CD0B1B21DED53203
046FAFF9B1129167921DD82C5964F9DDDFE0D2686875BD075FC81831A941F20E
C5CD90040A092E559F6D1D3B0E9BB71733595AE0EA6093F986377A96060BF12A
A1B525CD9FA741FE051DD54A32BECD55A868DD63119A4370F8322CCBEC889BC2
A723CB4015FC4AA90AE873EA14DE13382CA9CF0D8DFB65F0ABEDFD9A64BB3F4D
731E2E1C9A1789228FF44116230A70C339C9819676022AB31B5C9C589AE9094B
09882051AD4637C1710D93E8DD117B4E7B478493B91EA6306FDB3FA6D738AAB1
49FBB21A00AC2A999C21445DE3177F21D8B6AAB33869C882613EA6B5EC56476B
5634181ECBF03BFEDB57F079EACE3B334F6F384BDF9D70AEBD592C8ECF21378B
54A8B5DBF7CB9282E16AA517E14843909339B5E7C55B038BF3BB493F3B884A1C
C25F9E8FB912CBE23199AD9D2C3E573727701BA301526C66C3617B9514D6F11F
11930B1D97C17816C85B1BFD9B973A191B33CC3B391815AD14F1CBE935942AEC
D4004E6BEF379066FD72209DC88D2E634E79BCC2B98C766CBD92C561F2703F8A
109E6C6CEC7B866F2FC7ADF646BF492E520319F3B949AB5D84AE990B33344A40
3971F58DFDF8D8D67FA0B8F2A0D884F8C09A5A721319B911DBA0A35903877343
C37BC36C5EB32353272D1E6ED5FCA611BE319A7E1E842CB7576E7CDAD2416819
11B86BC0CFA2D1D39AED352298D3971E81EC820105B2816152D9226C86FBD6FB
BB55CBD83475125962D6B1088E94DC76B77960BAACF621F91580CA4625FECFB5
B135FDE724C45885831C618E67AD940DA5E669CCE4DA119BCF67681D17356E4B
897A59C812258F25CF089C3DE9694C0BF90D9708E6618C7C6A5A99C3CAB26FDC
56B6673F934A3302B91C3FAD55BB02B963AAE02291A581DB9AB231070DB7ABA9
73600DA4B499ACD4F3E43F40803BFEAA4DA7E8FB51BCC61B14ADB124522020B2
C6176925C58F69E9CD66AAC3C7C04FD6C5ED1E32FECA1F8E17A4AFC81B85C315
A792DC63FBDE78545C2588E3684BF062EC50271EEE75F1461E39E8CDEF58259F
C5753AA5587576148F9008D0368675EA0764FB2ED6BB4A1DC9BE65678790CBE2
85A7926E8EF7306D14622FAA62F8
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
cleartomark
%%EndFont 
%%BeginFont: CMR6
%!PS-AdobeFont-1.1: CMR6 1.0
%%CreationDate: 1991 Aug 20 16:39:02
% Copyright (C) 1997 American Mathematical Society. All Rights Reserved.
11 dict begin
/FontInfo 7 dict dup begin
/version (1.0) readonly def
/Notice (Copyright (C) 1997 American Mathematical Society. All Rights Reserved) readonly def
/FullName (CMR6) readonly def
/FamilyName (Computer Modern) readonly def
/Weight (Medium) readonly def
/ItalicAngle 0 def
/isFixedPitch false def
end readonly def
/FontName /CMR6 def
/PaintType 0 def
/FontType 1 def
/FontMatrix [0.001 0 0 0.001 0 0] readonly def
/Encoding 256 array
0 1 255 {1 index exch /.notdef put} for
dup 48 /zero put
dup 49 /one put
dup 50 /two put
dup 51 /three put
dup 56 /eight put
readonly def
/FontBBox{-20 -250 1193 750}readonly def
/UniqueID 5000789 def
currentdict end
currentfile eexec
D9D66F633B846A97B686A97E45A3D0AA052A014267B7904EB3C0D3BD0B83D891
016CA6CA4B712ADEB258FAAB9A130EE605E61F77FC1B738ABC7C51CD46EF8171
9098D5FEE67660E69A7AB91B58F29A4D79E57022F783EB0FBBB6D4F4EC35014F
D2DECBA99459A4C59DF0C6EBA150284454E707DC2100C15B76B4C19B84363758
469A6C558785B226332152109871A9883487DD7710949204DDCF837E6A8708B8
2BDBF16FBC7512FAA308A093FE5CF4E9D2405B169CD5365D6ECED5D768D66D6C
68618B8C482B341F8CA38E9BB9BAFCFAAD9C2F3FD033B62690986ED43D9C9361
3645B82392D5CAE11A7CB49D7E2E82DCD485CBA17D1AFFF95F4224CF7ECEE45C
BFB7C8C77C22A01C345078D28D3ECBF804CDC2FE5025FA0D05CCC5EFC0C4F87E
CBED13DDDF8F34E404F471C6DD2E43331D73E89BBC71E7BF889F6293793FEF5A
C9DD3792F032E37A364C70914843F7AA314413D022AE3238730B420A7E9D0CF5
D0E24F501451F9CDECE10AF7E14FF15C4F12F3FCA47DD9CD3C7AEA8D1551017D
23131C09ED104C052054520268A4FA3C6338BA6CF14C3DE3BAF2EA35296EE3D8
D6496277E11DFF6076FE64C8A8C3419FA774473D63223FFA41CBAE609C3D976B
93DFB4079ADC7C4EF07303F93808DDA9F651F61BCCF79555059A44CBAF84A711
6D98083CEF58230D54AD486C74C4A257FC703ACF918219D0A597A5F680B606E4
EF94ADF8BF91A5096A806DB64EC96636A98397D22A74932EB7346A9C4B5EE953
CB3C80AA634BFC28AA938C704BDA8DC4D13551CCFE2B2784BE8BF54502EBA9AF
D49B79237B9C56310550BC30E9108BB06EAC755D6AA4E688EFE2A0AAB17F20FE
00CD0BFF1B9CB6BDA0FA3A29A3117388B6686657A150CE6421FD5D420F4F7FB5
B0DAA1BA19D638676E9CF159AC7325EF17B9F74E082BEF75E10A31C7011C0FFA
99B797CE549B5C45238DD0FADD6B99D233AC69282DF0D91EA2DBD08CE0083904
A6D968D5AE3BD159D01BDFF42D16111BC0A517C66B43972080D9DD4F3B9AE7FB
11B035CE715C1218B2D779761D8D7E9DEBE277531BD58F313EBD27E33BEF9DC5
50C7821A8BBC3B9FDF899D7EAA0B94493B97AFEAC503EB5ED7A7AB62FBEFBEFA
AD08ADD6648E354B05E584C970AACB6E015F56F3482678504279F10E01CDA446
6F6E039511BE0576EC00ACDBBDE8DAD593121F1D855D175D616711DB93645AB6
03227673BAF4CCF593EB7EF23AFEB7B2CB7AB053C26530E564BC01C2F74A3D1A
4C1279D91F1EF1383E34E8218B3A9918341FE9E346EB3EBFE627E7518D6AB787
8DC227C39FAF27D969769756B98A0A078058A6D04DBC5A18344ED6EC71C98E00
7996DD675B953CBDA5AAECA2AB8819E1FFFE61F2A2C48F13B70F8334E9A2CDAB
4603C68292AD8A93E29A04D262AFE205293FC10AD70F360DC07DC03E00CD12A1
5213BFEA869BE17CB485E81907A09B54E11FDBD10D0F96A93331A1C67F567735
D8103CDD80521A3C99A41D027814CF6D405E1ECCE56AD06878ED9DD601EC3D5F
77DFB141832D6A1205CD020AE2DC7F1184765AB81CB90EFD36FAAB3EBD0DD796
C157BF3E867C5BF7500CA0265053574EC2B493943E894ECBDD4FEECDCA195DEE
68A3F72351CE5732F1E466EF31F1454572113E8098A3433CB162DF809F6DFEFD
69F5D0C8050740755A41B1AFBAC031CB876EC4D1C8EEF3E35D9566BDA93F2AC3
55EB2BF661A9111BAE2534E4A8DFC1A37148F928D7F6D8DE1F4B4C5A32752F24
F22035330C53BF5999089DCEA2578E92512D265EAEB3A6E150EF343E22033DB8
A6B7CCBABA52215BF69218756FE289F3825F4650796FE1E23C575132F99FE2E9
E7919B06E71FBC1ED75F74DA20E4A0720D0023DDA270A6F104B03BE9775AB5C7
716C017D25245F778FBD409BD200B45217D2BE5573D15CECF99A6C94DF4717E0
1AE54B7651AC2E8D9C75FBD8D4C52671DA743A4A2C2FC7BCDAA07D1324FD54F4
02802A68267D6A35E576E2C39DF54832CB07434E2F90C573E8CBF78977F5236D
37447A4849E56B0B42385A93581790F7CABFE7080DFC34E61A5EF0E4F591AD00
215FD4F26E6A557E5D700DF9E67690372EC9DF1C46ABB0D97ACE01D355732052
A76149607D2E99863B7D7D6766B614D76D0CCF8F9E03DDFFAFA2C0A35C31E61D
332D598314D4C44DA427ECF5BFAFBE1EEDB13EE60CE64EAA9AEC723A91F703E5
0BEF4798878E6BE9B3354AD3B8AA96DDBD4D29C062115DB447E3C4FA705EBF12
209DB2C360F36D37A960121AA96BBD580D75F5E893E9C4F9CDAEE982660454E1
197891AB5E55AA7D8FCED60287C83AB1ADA08AE467B9D9BA2CF9A1F1CF445486
A9400C2AE788ECFFEC4ADC992FC7C6E04F470DDDE1A6BEA85365561EC158AC2A
35E03F0A7B131E98E6D7DBCC597DEC673799EA469E93CB19DFF5C84D21BAC5ED
E172D54378D33494
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
0000000000000000000000000000000000000000000000000000000000000000
cleartomark
%%EndFont 
TeXDict begin 40258431 52099146 1000 600 600 (short-paper.gen.dvi)
@start /Fa 137[39 39 39 39 39 1[39 39 39 39 39 1[39 1[39
39 1[39 1[39 1[39 38[39 10[39 39 46[{}19 74.7198 /CMTT9
rf /Fb 205[38 50[{}1 74.7198 /CMR9 rf /Fc 199[30 4[30
30 30 30 48[{}5 49.8132 /CMR6 rf /Fd 204[25 25 25 49[{
 TeXBase1Encoding ReEncodeFont }3 49.8132 /Times-Roman
rf /Fe 171[37 11[48 20[33 2[33 3[17 4[22 39[{
 TeXBase1Encoding ReEncodeFont }6 66.4176 /Times-Italic
rf /Ff 82[22 22[33 28[33 1[48 1[33 18 26 22 1[33 33 33
52 18 2[18 33 33 1[29 33 1[33 29 11[48 6[48 59 1[48 7[44
1[48 8[33 33 33 33 33 33 33 33 33 18 17 1[17 44[{
 TeXBase1Encoding ReEncodeFont }38 66.4176 /Times-Roman
rf /Fg 134[33 33 50 1[37 21 29 29 1[37 37 37 54 21 33
1[21 37 37 21 33 37 33 37 37 7[42 46 3[42 37 2[46 54
1[62 3[25 54 54 1[46 54 50 1[46 7[37 4[37 37 37 37 37
1[19 25 19 2[25 25 25 39[{ TeXBase1Encoding ReEncodeFont }48
74.7198 /Times-Italic rf /Fh 134[37 1[54 1[42 25 29 33
1[42 37 42 62 21 1[25 21 1[37 1[33 42 33 42 37 12[50
42 7[58 3[58 2[54 54 8[25 58[{ TeXBase1Encoding ReEncodeFont }26
74.7198 /Times-Bold rf /Fi 75[25 28[75 37 1[33 33 24[33
37 37 54 37 37 21 29 25 37 37 37 37 58 21 37 21 21 37
37 25 33 37 33 37 33 3[25 1[25 46 54 54 71 54 54 46 42
50 1[42 54 54 66 46 54 29 25 54 54 42 46 54 50 50 54
5[21 21 37 37 37 37 37 37 37 37 37 37 21 19 25 19 2[25
25 25 58 34[42 42 2[{ TeXBase1Encoding ReEncodeFont }80
74.7198 /Times-Roman rf /Fj 168[100 1[72 66 55 72 2[78
72 94 66 78 1[39 1[78 61 66 72 72 66 72 10[50 50 50 50
50 50 2[25 46[{ TeXBase1Encoding ReEncodeFont }25 99.6264
/Times-Bold rf /Fk 82[28 4[28 46[42 42 1[42 46 23 42
28 1[46 46 46 69 18 42 1[18 1[46 23 46 46 42 1[46 11[60
51 55 2[55 65 60 3[42 23 60 65 51 1[60 60 55 55 6[23
46 46 1[46 46 46 46 46 46 46 1[23 1[23 48 43[{
 TeXBase1Encoding ReEncodeFont }50 83.022 /Helvetica
rf /Fl 87[33 46[50 50 2[55 28 50 33 1[55 55 55 83 22
50 22 22 55 55 28 55 55 50 55 55 12[61 7[55 1[50 1[72
1[61 3[66 66 101 17[28 1[28 41[50 2[{ TeXBase1Encoding ReEncodeFont }34
99.6264 /Helvetica rf /Fm 139[50 83 58 1[91 91 91 133
1[83 1[42 91 91 50 83 2[91 83 9[141 1[108 1[100 2[100
2[124 8[108 9[50 7[83 50[{ TeXBase1Encoding ReEncodeFont }23
149.44 /Helvetica-Bold rf end
%%EndProlog
%%BeginSetup
%%Feature: *Resolution 600dpi
TeXDict begin
%%BeginPaperSize: Letter
letter
%%EndPaperSize
 end
%%EndSetup
%%Page: 1 1
TeXDict begin 1 0 bop 0 0 a
SDict begin /product where{pop product(Distiller)search{pop pop pop
version(.)search{exch pop exch pop(3011)eq{gsave newpath 0 0 moveto
closepath clip/Courier findfont 10 scalefont setfont 72 72 moveto(.)show
grestore}if}{pop}ifelse}{pop}ifelse}if end
 0 0 a 0 0 a
SDict begin [ /Title () /Subject () /Creator (LaTeX with hyperref package)
/Author () /Producer (dvips + Distiller) /Keywords () /DOCINFO pdfmark
end
 0 0 a -152 -359
a
SDict begin H.S end
 -152 -359 a -152 -359 a
SDict begin H.R end
 -152 -359 a -152 -359 a
SDict begin [ /View [/XYZ H.V] /Dest (page.1) cvn H.B /DEST pdfmark
end
 -152
-359 a -12 107 a Fm(Storm:)58 b(Using)42 b(P2P)f(to)g(Make)i(the)e
(Desktop)h(P)l(ar)s(t)f(of)h(the)f(W)-5 b(eb)123 445
y Fl(Benja)29 b(F)-5 b(allenstein,)30 b(T)-12 b(uomas)28
b(J)m(.)f(Lukka)i(and)591 545 y(Her)r(manni)h(Hyyti)11
b(\250)-44 b(al)11 b(\250)-44 b(a)599 632 y Fk(Hyperstr)q(ucture)22
b(Group)313 719 y(Agor)o(a)i(Center)l(,)f(Univ)n(ersity)f(of)h(Jyv)9
b(\250)-37 b(askyl)9 b(\250)-37 b(a)375 807 y(P)-15 b(.O)m(.)23
b(Bo)n(x)g(35,)g(FIN\25540014)g(Jyv)9 b(\250)-37 b(askyl)9
b(\250)-37 b(a)571 894 y(T)-10 b(el.:)33 b(+358)24 b(14)g(260)f(1211)
229 1014 y Fl(b)l(.f)m(allenstein@gmx.de)o(,)30 b(lukka@iki.\002,)575
1117 y(hemppah@cc.jyu.\002)2625 445 y(T)-12 b(oni)28
b(Alatalo)2001 532 y Fk(Depar)s(tment)d(of)e(Inf)n(or)r(mation)h
(Processing)f(Sciences)2396 619 y(Univ)n(ersity)g(of)g(Oulu,)g(Finland)
2315 707 y(P)-15 b(.O)m(.Bo)n(x)23 b(3000,)h(FIN\25590100)f(Oulu)2477
794 y(T)-10 b(el.:)33 b(+358)24 b(8)f(553)h(1900)2560
914 y Fl(antont@oulu.\002)-152 1332 y
SDict begin [ /Count -0 /Dest (section.1) cvn /Title (Introduction)
/OUT pdfmark end
 -152 1332 a -152
1332 a
SDict begin [ /Count -0 /Dest (section.2) cvn /Title (Storm) /OUT pdfmark
end
 -152 1332 a -152 1332 a
SDict begin [ /Count -0 /Dest (section.3) cvn /Title (Interfacing)
/OUT pdfmark end
 -152 1332 a -152 1332
a
SDict begin [ /Count -0 /Dest (section.4) cvn /Title (Conclusions)
/OUT pdfmark end
 -152 1332 a -152 1332 a
SDict begin [ /Count -0 /Dest (section.5) cvn /Title (Acknowledgements)
/OUT pdfmark end
 -152 1332 a -152 1332 a
SDict begin [ /Count -0 /Dest (section.6) cvn /Title (REFERENCES -9pt )
/OUT pdfmark end
 -152
1332 a -152 1332 a
SDict begin [ /Page 1 /View [ /Fit ] /PageMode /UseOutlines  /DOCVIEW
pdfmark end
 -152 1332 a -152 1332 a
SDict begin [ {Catalog} << /ViewerPreferences << >> >> /PUT pdfmark
end
 -152 1332
a -152 1332 a
SDict begin H.S end
 -152 1332 a -152 1332 a
SDict begin 10.5 H.A end
 -152 1332 a -152
1332 a
SDict begin [ /View [/XYZ H.V] /Dest (Doc-Start) cvn H.B /DEST pdfmark
end
 -152 1332 a 83 x Fj(ABSTRA)-5 b(CT)-152 1450 y
SDict begin H.S end

-152 1450 a -152 1450 a
SDict begin 10.5 H.A end
 -152 1450 a -152 1450 a
SDict begin [ /View [/XYZ H.V] /Dest (section*.1) cvn H.B /DEST pdfmark
end
 -152
1450 a 85 x Fi(W)f(e)21 b(present)g(Storm,)g(a)g(storage)g(system)g
(which)h(uni\002es)f(the)g(desktop)h(and)-152 1622 y(the)c(public)h
(netw)o(ork,)g(making)f(W)-6 b(eb)18 b(links)g(between)h(desktop)g
(documents)-152 1710 y(more)j(practical.)31 b(Storm)22
b(assigns)g(each)g(document)h(a)f(permanent)g(unique)-152
1797 y(URI)30 b(when)g(it)g(is)f(created.)57 b(Using)30
b(peer)o(-to-peer)h(technology)-5 b(,)34 b(we)c(can)-152
1884 y(locate)f(documents)h(e)n(v)o(en)g(though)g(our)f(URIs)f(do)i
(not)f(include)g(location)-152 1971 y(information.)37
b(Links)23 b(continue)h(to)f(w)o(ork)h(unchanged)h(when)f(documents)
-152 2058 y(are)e(emailed)g(or)g(published)h(on)f(the)g(netw)o(ork.)32
b(W)-6 b(e)21 b(ha)o(v)o(e)h(e)o(xtended)h(KDE)-152 2145
y(to)c(understand)h(Storm)e(URIs.)23 b(Other)18 b(systems)i(such)f(as)g
(GNU)f(Emacs)h(are)-152 2233 y(able)g(to)g(use)h(Storm)e(through)i(an)f
(HTTP)f(gate)n(w)o(ay)-5 b(.)-152 2343 y Fh(Categories)21
b(and)e(Subject)f(Descriptors:)24 b Fi(H.3.4)19 b([Information)i
(Storage)-152 2431 y(and)h(Retriev)n(al]:)k(Systems)20
b(and)h(Softw)o(are\227)p Fg(distrib)o(uted)f(systems,)h(infor)o(-)-152
2518 y(mation)f(networks)-152 2629 y Fh(General)f(T)-7
b(erms:)24 b Fi(Design,)19 b(Reliability)-5 b(,)18 b(Performance)-152
2739 y Fh(K)n(eyw)o(ords:)37 b Fi(dangling)27 b(links,)g
(location-independent)h(identi\002ers,)e(con-)-152 2827
y(tent)19 b(addressable)h(netw)o(orks,)g(peer)o(-to-peer)-152
2922 y
SDict begin H.S end
 -152 2922 a -152 2922 a
SDict begin 10.5 H.A end
 -152 2922 a -152 2922
a
SDict begin [ /View [/XYZ H.V] /Dest (section.1) cvn H.B /DEST pdfmark
end
 -152 2922 a 100 x Fj(1.)100 b(INTR)m(ODUCTION)-77 3130
y Fi(While)19 b(man)o(y)i(W)-6 b(eb)19 b(pages)i(are)f(densely)h
(interlink)o(ed)f(today)-5 b(,)21 b(hyperme-)-152 3217
y(dia)16 b(functionality)h(is)f(still)f(only)h(rarely)g(used)h(in)f
(desktop)h(documents.)24 b(Hy-)-152 3304 y(permedia)f(on)g(the)f
(desktop)i(w)o(ould)f(be)f(useful)h(for)f(k)o(eeping)i(hyperlink)o(ed)
-152 3392 y(notes,)18 b(for)f(referring)g(to)h(pieces)f(of)g(documents)
i(in)e(discussion,)i(or)e(to)g(refer)-152 3479 y(from)i(a)g(short)g
(memo)g(to)g(a)f(document)i(with)f(more)g(in-depth)g(information.)-152
3566 y(Ev)o(en)k(though)h(documents)g(written)e(with)g(Microsoft)g(W)-6
b(ord)23 b(or)f(OpenOf-)-152 3653 y(\002ce.or)o(g)d(can)g(no)n(w)o
(adays)h(be)f(link)o(ed)h(just)e(lik)o(e)h(HTML)f(\002les,)g(users)h
(almost)-152 3740 y(ne)n(v)o(er)h(seem)f(to)g(do)g(so.)-77
3827 y(A)e(major)h(obstacle)g(to)g(hypermedia)h(on)f(the)f(desktop)i
(are)f(brok)o(en)h(links.)-152 3915 y(A)30 b(user)g(recei)n(ving)h
(hyperlink)o(ed)h(documents)f(by)g(email,)h(for)e(e)o(xample,)-152
4002 y(w)o(ould)f(ha)o(v)o(e)f(to)g(reconstruct)g(the)g(original)g
(directory)h(structure;)j(other)o(-)-152 4089 y(wise,)26
b(the)e(links)h(will)e(not)i(w)o(ork.)40 b(Man)o(y)25
b(hypermedia)h(systems)f(assume)-152 4176 y(that)17 b(identi\002ers)f
(either)h(e)o(xpose)g(where)g(a)g(document)h(can)f(be)g(found)g(on)h
(the)-152 4263 y(netw)o(ork,)e(or)f(the)o(y)g(cannot)h(be)f(ef)n
(\002ciently)f(resolv)o(ed)i(on)f(a)g(global)g(scale.)22
b(In-)-152 4350 y(deed,)16 b(Berners-Lee)f([)432 4350
y
SDict begin H.S end
 432 4350 a Fi(2)469 4300 y
SDict begin H.R end
 469 4300 a 469 4350 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.name-myth) cvn H.B /ANN pdfmark end
 469
4350 a Fi(])f(ar)o(gues)i(that)e(using)h(unique)h(and)f(random-looking)
-152 4438 y(numbers)20 b(to)f(identify)g(documents)i(is)d(not)h
(possible)h(on)f(a)g(global)h(scale.)-77 4525 y(Ho)n(we)n(v)o(er)m(,)e
(recent)g(de)n(v)o(elopments)i(in)d(peer)o(-to-peer)h(systems)g(ha)o(v)
o(e)g(ren-)-152 4612 y(dered)g(this)f(assumption)h(obsolete.)24
b(Distrib)o(uted)16 b(hashtables)j(\(DHTs\))d(and)-152
4699 y(other)23 b(content-addressable)h(netw)o(ork)f(algorithms)g([)
1272 4700 y
SDict begin H.S end
 1272 4700 a -1 x Fi(6)1309 4648 y
SDict begin H.R end
 1309 4648
a 1309 4699 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.kato02gisp) cvn H.B /ANN pdfmark end
 1309 4699 a Fi(,)1351 4700 y
SDict begin H.S end
 1351 4700
a -1 x Fi(8)1388 4648 y
SDict begin H.R end
 1388 4648 a 1388 4699 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.malkhi02viceroy) cvn H.B /ANN pdfmark end
 1388
4699 a Fi(,)1430 4701 y
SDict begin H.S end
 1430 4701 a -2 x Fi(9)1467 4648
y
SDict begin H.R end
 1467 4648 a 1467 4699 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.maymounkov02kademlia) cvn H.B /ANN pdfmark end
 1467 4699 a Fi(,)1509 4700
y
SDict begin H.S end
 1509 4700 a -1 x Fi(10)1583 4648 y
SDict begin H.R end
 1583 4648 a 1583
4699 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.ratnasamy01can) cvn H.B /ANN pdfmark end
 1583 4699 a Fi(,)1625 4699 y
SDict begin H.S end
 1625 4699 a Fi(12)1700
4648 y
SDict begin H.R end
 1700 4648 a 1700 4699 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.stoica01chord) cvn H.B /ANN pdfmark end
 1700 4699 a Fi(,)1741
4700 y
SDict begin H.S end
 1741 4700 a -1 x Fi(15)1816 4648 y
SDict begin H.R end
 1816 4648 a
1816 4699 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.zhao01tapestry) cvn H.B /ANN pdfmark end
 1816 4699 a Fi(])-152 4786 y(allo)n(w)28
b(location-independent)j(identi\002ers)d(to)g(be)g(resolv)o(ed)h(on)g
(a)f(global)-152 4874 y(scale.)38 b(The)24 b(use)h(of)e(peer)o
(-to-peer)i(technology)g(in)f(hypermedia)h(systems)-152
4961 y(is)17 b(the)h(topic)f(of)g(an)h(ongoing)h(discussion)f(in)g(the)
f(hypermedia)h(community)-152 5048 y([)-127 5049 y
SDict begin H.S end
 -127
5049 a -1 x Fi(3)-89 4997 y
SDict begin H.R end
 -89 4997 a -89 5048 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.bouvin02open) cvn H.B /ANN pdfmark end
 -89
5048 a Fi(,)-52 5049 y
SDict begin H.S end
 -52 5049 a -1 x Fi(7)-15 4998
y
SDict begin H.R end
 -15 4998 a -15 5048 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.lukka02guids) cvn H.B /ANN pdfmark end
 -15 5048 a Fi(,)23 5049 y
SDict begin H.S end
 23
5049 a -1 x Fi(13)97 4997 y
SDict begin H.R end
 97 4997 a 97 5048 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.thompson01coincidence) cvn H.B /ANN pdfmark end
 97 5048
a Fi(,)135 5048 y
SDict begin H.S end
 135 5048 a Fi(14)209 4997 y
SDict begin H.R end
 209 4997
a 209 5048 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.p2p-hypertext-panel) cvn H.B /ANN pdfmark end
 209 5048 a Fi(].)-152 5246 y Ff(Cop)o(yright)i(is)d(held)h
(by)f(the)g(author/o)n(wner)l(.)-152 5321 y Fe(HT'03,)g
Ff(August)g(26\22630,)h(2003,)f(Nottingham,)h(United)h(Kingdom.)-152
5396 y(A)m(CM)f(1\25558113\255704\2554/03/0008.)2115
1415 y Fi(Balakrishnan)j(et)e(al.)25 b([)2725 1415 y
SDict begin H.S end

2725 1415 a Fi(1)2763 1364 y
SDict begin H.R end
 2763 1364 a 2763 1415 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.balakrishnan03semanticfree) cvn H.B /ANN pdfmark end

2763 1415 a Fi(])19 b(ar)o(gue)h(that)g(DHTs)f(are)h(suitable)g(for)f
(the)h(ne)o(xt)2040 1502 y(generation)27 b(Reference)f(Resolution)g
(Services)f(\(RRS\))3528 1470 y Fd(1)3556 1502 y Fi(.)g(DHTs)g(can)h
(not)2040 1589 y(only)i(be)f(used)g(to)g(ef)n(\002ciently)g(retrie)n(v)
o(e)f(documents,)k(b)o(ut)d(also)g(metadata)2040 1676
y Fg(about)19 b Fi(documents.)24 b(F)o(or)15 b(e)o(xample,)j(unlik)o(e)
f(man)o(y)g(link)g(services)g(that)f(only)2040 1764 y(query)22
b(a)f(limited)f(set)g(of)h(serv)o(ers)g(for)g(links)g(\(e.g.,)f([)3405
1765 y
SDict begin H.S end
 3405 1765 a -1 x Fi(5)3442 1713 y
SDict begin H.R end
 3442 1713 a
3442 1764 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.hill94extending) cvn H.B /ANN pdfmark end
 3442 1764 a Fi(]\),)h(all)f(published)i(e)o(x-)2040
1851 y(ternal)d(links)g(to)g(a)g(document)h(can)f(be)h(found)g(ef)n
(\002ciently)e(using)i(a)f(DHT)-6 b(.)2115 1938 y(Location-independent)
33 b(identi\002ers)c(enable)i(non-breaking)i(links)d(on)2040
2025 y(the)d(desktop)g(and)h(the)e(W)-6 b(eb:)38 b(When)27
b(a)f(document)i(is)e(published)i(on)f(the)2040 2112
y(W)-6 b(eb,)26 b(it)f(will)f(ha)o(v)o(e)i(the)f(same)h(URI)e(as)h(on)h
(the)f(author')l(s)h(local)f(desktop;)2040 2199 y(when)f(a)e(link)h(to)
g(a)g(document)h(is)f(emailed,)h(the)f(recei)n(v)o(er)g(can)g(follo)n
(w)g(the)2040 2287 y(link)i(as)h(long)g(as)f(their)g(softw)o(are)h(can)
g(locate)f(the)g(link)o(ed-to)i(document\226)2040 2374
y(on)f(its)e(local)h(harddisk,)i(attached)f(to)f(another)g(email,)h(on)
g(a)f(w)o(ork)g(group)2040 2461 y(serv)o(er)20 b(or)f(on)h(the)g
(public)g(Internet.)25 b(In)20 b(Freenet)f([)3359 2461
y
SDict begin H.S end
 3359 2461 a Fi(4)3397 2410 y
SDict begin H.R end
 3397 2410 a 3397 2461
a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.freenet-ieee) cvn H.B /ANN pdfmark end
 3397 2461 a Fi(],)g(an)g(anon)o(ymous)j(P2P)2040 2548
y(publication)32 b(system,)j Fg(crypto)o(gr)o(aphic)e(hashes)3322
2516 y Fd(2)3384 2548 y Fi(are)e(used)h(as)f(location-)2040
2635 y(independent)21 b(identi\002ers)e(of)f(document)j(v)o(ersions.)
2115 2722 y(This)j(paper)g(describes)h(Storm,)g(a)f(library)g(for)g
(storing)g(and)h(retrie)n(ving)2040 2810 y(data)19 b(using)h
(location-independent)h(URIs.)2040 2915 y
SDict begin H.S end
 2040 2915 a
2040 2915 a
SDict begin 10.5 H.A end
 2040 2915 a 2040 2915 a
SDict begin [ /View [/XYZ H.V] /Dest (section.2) cvn H.B /DEST pdfmark
end
 2040 2915 a 100 x
Fj(2.)99 b(ST)n(ORM)2115 3123 y Fi(Storm)18 b(\(for)h(ST)o(ORage)f
(Module\))i(is)e(a)h(library)g(for)g(both)g(local)g(and)h(dis-)2040
3210 y(trib)o(uted)g(storage)h(and)g(publishing.)29 b(On)21
b(the)f(lo)n(west)h(le)n(v)o(el,)f(data)h(is)f(stored)2040
3297 y(in)30 b Fg(bloc)o(ks)p Fi(,)i(which)e(are)f(immutable)h(byte)g
(sequences.)57 b(As)29 b(opposed)i(to)2040 3385 y(\002le)24
b(systems,)i(Freenet-lik)o(e)f(cryptographic)h(identi\002ers)e(are)h
(used.)41 b(This)2040 3472 y(may)20 b(seem)g(lik)o(e)g(a)f(bad)h
(tradeof)n(f:)25 b(while)19 b(these)h(identi\002ers)f(enable)i(secure)
2040 3559 y(location-independent)31 b(references,)h(the)o(y)c(do)h(not)
g(allo)n(w)g(the)f(identi\002ed)2040 3646 y(documents)22
b(to)f(change)h(and)g(are)f(also)f(less)h(comprehensible)i(to)d
(humans.)2040 3733 y(Ho)n(we)n(v)o(er)m(,)i(these)f(do)n(wnsides)h(are)
f(dealt)g(with)g(by)g(the)g(higher)h(abstraction)2040
3820 y(le)n(v)o(els)d(of)g(Storm.)2115 3908 y(One)25
b(of)f(the)h(k)o(e)o(y)h(inno)o(v)n(ations)g(here)f(is)f(the)h(use)g
(of)f Fg(pointer)i(bloc)o(ks)e Fi(to)2040 3995 y(b)o(uild)i(mutable)h
(documents)h(on)f(top)g(of)g(the)f(lo)n(west)h(layer)f(append-and-)2040
4082 y(delete-only)f(model.)41 b(A)24 b(pointer)h(block)g(is)f(a)g
(Storm)g(block)h(which)g(says,)2040 4169 y(\223The)19
b(current)h(v)o(ersion)g(of)f(document)h Fg(X)i Fi(is)d(block)h
Fg(Y)p Fi(.)e(Pointer)h(blocks)h Fg(a,b)p Fi(,)2040 4256
y(specifying)k(pre)n(vious)g(v)o(ersions)f(of)g(this)f(document,)j(are)
e(no)n(w)g(obsolete.)-5 b(\224)2040 4343 y(Additionally)g(,)19
b(it)g(contains)g(a)g(digital)g(signature)g(of)g(the)g(abo)o(v)o(e.)
2115 4431 y(The)31 b(pointer)g Fg(X)i Fi(contains)f(the)f(public)g(k)o
(e)o(y)h(used)g(for)e(signatures)i(\227)2040 4518 y(this)27
b(allo)n(ws)g(only)h(the)f(author)g(of)g(the)h(document)g(to)f(v)n
(alidate)h(ne)n(w)f(v)o(er)o(-)2040 4605 y(sions.)63
b(Since)32 b(a)g(pointer)g(block)h(can)g(o)o(v)o(erride)f(more)h(than)f
(one)h(older)2040 4692 y(pointer)24 b(block,)g(this)f(implements)h(a)f
(nonlinear)h(\(branching\))g(v)o(ersioning)p 2040 4744
797 4 v 2043 4798 a Fc(1)2077 4829 y Fi(The)f(Domain)g(Name)f(System)h
(\(DNS,)e(RFC)g(1101\))j(is)e(an)h(RRS)e(system)2040
4904 y(widely)e(used)h(on)f(the)g(Internet.)2043 4959
y Fc(2)2077 4990 y Fi(A)f(cryptographic)h(hash)g(is)e(short)h
(bit-string)g(\(often)g(160)h(bits\))e(computed)2040
5065 y(from)g(a)f(document,)j(so)d(that)h(it)f(is)g(practically)h
(impossible)g(that)f(tw)o(o)h(dif)n(fer)o(-)2040 5140
y(ent)23 b(published)h(documents)g(will)e(e)n(v)o(er)h(ha)o(v)o(e)f
(the)h(same)g(hash.)35 b(F)o(or)22 b(a)h(160)2040 5228
y(bit)h(hash,)h(hash)g(collisions)f(are)g(e)o(xpected)h(to)f(appear)g
(at)g(about)h Fb(2)3807 5196 y Fc(80)3896 5228 y Fi(pub-)2040
5303 y(lished)h(documents;)k(that')l(s)25 b(about)h(60)g(trillion)e
(per)i(human)g(li)n(ving.)43 b(See,)2040 5378 y(e.g.,)18
b([)2210 5378 y
SDict begin H.S end
 2210 5378 a Fi(11)2285 5327 y
SDict begin H.R end
 2285 5327
a 2285 5378 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.schneier96appliedcryptography) cvn H.B /ANN pdfmark end
 2285 5378 a Fi(].)p eop end
%%Page: 2 2
TeXDict begin 2 1 bop 0 0 a
SDict begin /product where{pop product(Distiller)search{pop pop pop
version(.)search{exch pop exch pop(3011)eq{gsave newpath 0 0 moveto
closepath clip/Courier findfont 10 scalefont setfont 72 72 moveto(.)show
grestore}if}{pop}ifelse}{pop}ifelse}if end
 0 0 a -152 -359 a
SDict begin H.S end
 -152 -359
a -152 -359 a
SDict begin H.R end
 -152 -359 a -152 -359 a
SDict begin [ /View [/XYZ H.V] /Dest (page.2) cvn H.B /DEST pdfmark
end
 -152 -359 a 290
x Fi(model.)23 b(More)16 b(than)g(one)g(v)o(ersion)h(of)e(a)h(document)
h(can)f(be)g(\223current\224)g(\(e.g.,)-152 19 y(when)24
b(dif)n(ferent)g(people)g(in)f(a)h(w)o(orking)g(group)h(edit)e(the)g
(document)i(con-)-152 106 y(currently\).)33 b(There)22
b(is)g(also)g(a)g(scheme)h(for)f(storing)g(only)h(the)f(dif)n(ferences)
-152 193 y(between)29 b(consecuti)n(v)o(e)g(v)o(ersions,)h(b)o(ut)d
(there)g(is)h(no)g(space)g(to)f(e)o(xplain)h(it)-152
280 y(here.)-77 367 y(Storm)16 b(in)g(itself)f(is)g Fg(not)j
Fi(a)e(P2P)f(system,)i(b)o(ut)f(a)g(data)g(model)h(and)g(a)f(library)
-152 454 y(for)k(using)g(that)f(data)h(model)g(with)f(se)n(v)o(eral)h
(dif)n(ferent)f(back)o(ends.)27 b(Because)-152 542 y(of)g(the)g
(simplicity)g(of)g(the)g(lo)n(west-le)n(v)o(el)g(data)g(model,)i(it)e
(is)f(able)h(to)g(use)-152 629 y(se)n(v)o(eral)17 b(dif)n(ferent)f
(modes)i(of)e(netw)o(orking,)i(from)e(simply)h(cop)o(ying)h(blocks)-152
716 y(to)27 b(using)g(a)f(full-\003edged)h(P2P)e(system)i(as)f(a)g
(library)h(\227)e(as)i(of)f(no)n(w)-5 b(,)29 b(we)-152
803 y(are)19 b(already)h(successfully)g(transferring)f(blocks)g
(between)h(Storm)e(serv)o(ers)-152 890 y(using)i(the)f(GISP)e(DHT)i([)
517 891 y
SDict begin H.S end
 517 891 a -1 x Fi(6)554 839 y
SDict begin H.R end
 554 839 a 554
890 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.kato02gisp) cvn H.B /ANN pdfmark end
 554 890 a Fi(].)-152 991 y
SDict begin H.S end
 -152 991 a -152 991
a
SDict begin 10.5 H.A end
 -152 991 a -152 991 a
SDict begin [ /View [/XYZ H.V] /Dest (section.3) cvn H.B /DEST pdfmark
end
 -152 991 a 100 x Fj(3.)100 b(INTERF)-9
b(A)k(CING)-77 1199 y Fi(Storm)14 b(uses)h(an)g(e)o(xperimental)h(URN)e
(namespace)i(\(Uniform)f(Resource)-152 1287 y(Name,)20
b(a)g(persistent)g(kind)g(of)g(URI\))f(and)i(we)e(are)h(preparing)h
(the)f(re)o(gistra-)-152 1374 y(tion)e(of)f(a)g(real)g(namespace)i
(with)e(IAN)m(A.)g(The)g(URN)g(is)g(constructed)h(anal-)-152
1461 y(ogously)24 b(to)e(a)g(data)g(URL)f(\(RFC)g(2397\))i(from)f(the)g
(MIME)h(content-type,)-152 1548 y(using)d(the)f(hash)h(of)e(the)h(data)
h(instead)f(of)g(the)g(data)g(itself.)-77 1635 y(At)k(the)h(moment,)h
(Storm)f(URNs)f(can)h(be)g(used)h(as)e(a)h(replacement)h(for)-152
1722 y(both)17 b(\002le)d(names)j(and)f(HTTP)e(URLs)h(as)h(document)h
(identi\002ers.)22 b(Bro)n(wsers)-152 1810 y(and)h(applications)g(can)g
(access)g(Storm)e(either)h(by)h(using)g(the)f(Ja)o(v)n(a)h(library)-152
1897 y(directly)f(or)f(through)i(an)f(HTTP)e(gate)n(w)o(ay)-5
b(,)23 b(which)f(locates)g(and)g(returns)g(a)-152 1984
y(block)16 b(gi)n(v)o(en)g(its)e(Storm)g(URN.)g(Documents)i(can)g(be)f
(uploaded)h(into)f(Storm)-152 2071 y(through)i(the)e(gate)n(w)o(ay)-5
b(,)16 b(using)g(HTTP)e(PUT)-6 b(.)14 b(Using)i(the)f(gate)n(w)o(ay)-5
b(,)16 b(we)f(ha)o(v)o(e)-152 2158 y(made)21 b(the)e(K)m(onqueror)j
(web)e(bro)n(wser)g(as)f(well)g(as)h(Netscape)g(Na)o(vigator)f(4)-152
2245 y(understand)25 b(Storm)d(URNs.)34 b(Using)23 b(our)g(e)o
(xtension,)i(an)o(y)e(KDE)f(applica-)-152 2333 y(tion)i(can)h(load)g
(from)f(and)h(sa)o(v)o(e)f(to)g(Storm)f(URNs.)39 b(KDE)23
b(automatically)-152 2420 y(uploads)f(changed)g(documents)g(into)e
(Storm)g(when)h(the)f(user)g(hits)g(\223Sa)o(v)o(e.)-5
b(\224)-152 2507 y(The)26 b(Emacs)g(te)o(xt)g(editor)g(does)g(not)g
(understand)i(Storm)d(URNs)g(yet,)j(b)o(ut)-152 2594
y(can)f(load)f(and)h(sa)o(v)o(e)f(documents)h(in)f(Storm)g(using)g(the)
g(HTTP)f(gate)n(w)o(ay)-5 b(.)-152 2681 y(OpenOf)n(\002ce.or)o(g)30
b(can)f(load)h(documents)h(through)f(the)f(HTTP)f(gate)n(w)o(ay)-5
b(,)-152 2769 y(b)o(ut)27 b(cannot)h(sa)o(v)o(e)f(changes,)k(since)c
(the)g(gate)n(w)o(ay)h(does)g(not)f(yet)h(support)-152
2856 y(W)-6 b(ebD)m(A)c(V)19 b(\(HTTP-based)f(distrib)o(uted)h
(authoring)h(and)g(v)o(ersioning\).)-77 2943 y(The)f(HTTP)e(gate)n(w)o
(ay)j(also)f(pro)o(vides)g(a)g(W)-6 b(eb)19 b(interf)o(ace)g(to)f
(Storm,)g(gi)n(v-)-152 3030 y(ing)k(the)g(user)g(a)g(list)f(of)h(all)f
(documents)i(stored)g(on)f(their)f(local)h(hard)h(disk,)-152
3117 y(and)h(allo)n(wing)g(them)f(to)h(conduct)g(searches)g(o)o(v)o(er)
g(the)f(titles)g(of)g(all)g(docu-)-152 3204 y(ments)h(published)h(on)g
(the)f(underlying)h(P2P)e(netw)o(ork.)38 b(F)o(or)24
b(HTML,)f(the)-152 3292 y(serv)o(er)17 b(is)f(also)h(able)f(to)h
(dynamically)g(insert)f(backlinks:)24 b(links)16 b(to)g(all)g(other)
-152 3379 y(HTML)j(pages)g(on)h(the)f(netw)o(ork)h(that)e(link)h(to)g
Fg(this)g Fi(page.)-77 3466 y(The)14 b(most)h(important)g(do)n(wnside)g
(of)g(using)g(Storm)f(in)g(lieu)g(of)h(\002le)f(names)-152
3553 y(and)22 b(URLs)f(are)g(the)g(long,)h(cryptic)g(URIs)f(which)g(w)o
(ould)h(ideally)g(be)f(han-)-152 3640 y(dled)e(through)h(some)f(user)g
(interf)o(ace)g(changes)h(to)f(the)f(\002le)g(selector)h(dialog)-152
3727 y(box)o(es.)-152 3813 y
SDict begin H.S end
 -152 3813 a -152 3813 a
SDict begin 10.5 H.A end

-152 3813 a -152 3813 a
SDict begin [ /View [/XYZ H.V] /Dest (section.4) cvn H.B /DEST pdfmark
end
 -152 3813 a 116 x Fj(4.)100 b(CONCLUSIONS)-77
4037 y Fi(W)-6 b(e)19 b(ha)o(v)o(e)i(presented)f(Storm,)g(a)g(storage)g
(system)g(unifying)h(the)f(names-)-152 4124 y(paces)h(for)f(pri)n(v)n
(ate)h(and)g(published)g(documents,)h(making)f(hyperlinks)g(be-)-152
4211 y(tween)28 b(desktop)i(documents)f(more)f(practical.)51
b(While)27 b(the)h(core)h(of)f(the)-152 4298 y(system)18
b(has)g(been)h(in)e(use)h(for)f(almost)h(three)g(years,)g(the)f(peer)o
(-to-peer)h(sub-)-152 4385 y(system)24 b(has)g(only)g(recently)g(been)g
(implemented.)38 b(Currently)-5 b(,)24 b(a)g(number)-152
4472 y(of)17 b(systems)g(can)g(use)h(Storm)e(through)i(an)f(HTTP)e
(gate)n(w)o(ay)j(or)f(the)f(KDE)g(li-)-152 4560 y(braries.)23
b(It)17 b(can)g(also)h(be)g(used)g(to)f(implement)g(the)h(more)f
(ambitious)h(Xana-)-152 4647 y(logical)24 b(hyperte)o(xt)g(model)565
4615 y Fd(3)618 4647 y Fi([)643 4648 y
SDict begin H.S end
 643 4648 a -1
x Fi(7)681 4597 y
SDict begin H.R end
 681 4597 a 681 4647 a
SDict begin [ /Color [0 1 0] /H /I /Border [0 0 12] /Subtype /Link
/Dest (cite.lukka02guids) cvn H.B /ANN pdfmark end
 681 4647 a Fi(].)36
b(Storm)23 b(is)g(a)o(v)n(ailable)h(as)g(Free)f(Softw)o(are)-152
4734 y(from)c Fa(http://sv.gnu.org/projects/s)q(torm)q
Fi(.)-77 4821 y(The)d(main)f(ne)n(w)h(features)g(o)o(v)o(er)g(pre)n
(vious)h(systems)f(are)f(the)h(use)g(of)f(cryp-)-152
4908 y(tographic)k(identi\002ers)e(for)h(v)o(ersioned)g(hypermedia)h
(storage)f(on)g(the)g(desk-)-152 4995 y(top;)30 b(smooth)c(inte)o
(gration)g(with)g(ordinary)g(of)n(\002ce)g(applications;)k(pointer)-152
5083 y(blocks)24 b(for)e(nonlinear)h(v)o(ersioning;)j(and)d(the)f(use)h
(of)g(a)f(DHT)g(for)g(\002nding)-152 5170 y(e)o(xternal)e(hypermedia)g
(links.)p -152 5217 797 4 v -149 5271 a Fc(3)-114 5303
y Fi(Our)51 b(implementation)i(of)f(Xanalogical)g(storage)h(is)e(a)o(v)
n(ailable)h(at)-152 5378 y Fa(http://sv.gnu.org/projects/a)q(lph)p
Fi(.)2115 -69 y(Storm)26 b(is)f(by)i(no)g(means)g(\002nished:)38
b(more)27 b(w)o(ork)f(is)g(needed)i(on,)g(e.g.,)2040
19 y(v)o(ersioning)23 b(when)g(a)e(pointer)i(is)e(editable)h(by)h(more)
f(than)g(one)h(person.)33 b(A)2040 106 y(practical)c(impro)o(v)o(ement)
g(will)f(be)h(W)-6 b(ebD)m(A)c(V)28 b(support,)k(allo)n(wing)d(man)o(y)
2040 193 y(additional)20 b(systems)f(to)g(sa)o(v)o(e)g(data)g(in)g
(Storm.)2040 292 y
SDict begin H.S end
 2040 292 a 2040 292 a
SDict begin 10.5 H.A end
 2040 292 a 2040
292 a
SDict begin [ /View [/XYZ H.V] /Dest (section.5) cvn H.B /DEST pdfmark
end
 2040 292 a 100 x Fj(5.)99 b(A)-5 b(CKNO)g(WLEDGEMENTS)2115
500 y Fi(This)21 b(w)o(ork)i(w)o(as)f(funded)h(by)f(the)g(Agora)g
(Center)g(InBCT)f(project.)32 b(W)-6 b(e)2040 587 y(w)o(ould)30
b(lik)o(e)e(to)h(thank)g(Jukka)h(Honk)o(ela,)i(Erno)d(K)o(uusela,)i
(Harri)d(Oinas-)2040 674 y(K)o(ukk)o(onen,)21 b(and)e(Sarah)g(Stehlig)g
(for)f(comments)i(and)g(discussions.)2040 774 y
SDict begin H.S end
 2040
774 a 2040 774 a
SDict begin 10.5 H.A end
 2040 774 a 2040 774 a
SDict begin [ /View [/XYZ H.V] /Dest (section.6) cvn H.B /DEST pdfmark
end
 2040 774 a 100
x Fj(6.)99 b(REFERENCES)2040 896 y
SDict begin H.S end
 2040 896 a 2040 896
a
SDict begin 10.5 H.A end
 2040 896 a 2040 896 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.balakrishnan03semanticfree)
cvn H.B /DEST pdfmark end
 2040 896 a 2077 983 a Fi([1])38
b(H.)18 b(Balakrishnan,)i(S.)e(Shenk)o(er)m(,)h(and)h(M.)f(W)-6
b(al\002sh.)17 b(Semantic-free)2202 1070 y(referencing)j(in)f(link)o
(ed)g(distrib)o(uted)g(systems.)g(In)g Fg(Pr)m(oc.)f(IPTPS03)p
Fi(,)2202 1158 y(February)h(2003.)2040 1182 y
SDict begin H.S end
 2040 1182
a 2040 1182 a
SDict begin 10.5 H.A end
 2040 1182 a 2040 1182 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.name-myth) cvn H.B /DEST
pdfmark end
 2040 1182 a 2077
1253 a Fi([2])38 b(T)-6 b(.)18 b(Berners-Lee.)h(Axioms)g(of)g(web)g
(architecture)h(2:)j(The)c(myth)g(of)2202 1340 y(names)h(and)f
(addresses.)2202 1427 y(http://www)-5 b(.w3.or)o
(g/DesignIssues/NameMyth.html,)20 b(Dec.)2202 1515 y(1996.)2040
1525 y
SDict begin H.S end
 2040 1525 a 2040 1525 a
SDict begin 10.5 H.A end
 2040 1525 a 2040 1525
a
SDict begin [ /View [/XYZ H.V] /Dest (cite.bouvin02open) cvn H.B /DEST
pdfmark end
 2040 1525 a 2077 1610 a Fi([3])38 b(N.)18 b(O.)h(Bouvin.)g(Open)g
(hypermedia)i(in)d(a)h(peer)o(-to-peer)g(conte)o(xt.)h(In)2202
1697 y Fg(Pr)m(oceedings)g(of)f(the)g(thirteenth)g(confer)m(ence)i(on)e
(Hyperte)o(xt)g(and)2202 1784 y(hypermedia)p Fi(,)h(pages)g
(138\226139.)h(A)m(CM)e(Press,)f(2002.)2040 1809 y
SDict begin H.S end
 2040
1809 a 2040 1809 a
SDict begin 10.5 H.A end
 2040 1809 a 2040 1809 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.freenet-ieee) cvn H.B /DEST
pdfmark end
 2040 1809
a 2077 1880 a Fi([4])38 b(I.)18 b(Clark)o(e,)h(S.)f(G.)g(Miller)m(,)g
(T)-6 b(.)19 b(W)-7 b(.)18 b(Hong,)h(O.)g(Sandber)o(g,)g(and)2202
1967 y(B.)f(W)m(ile)o(y)-5 b(.)18 b(Protecting)h(free)g(e)o(xpression)h
(online)f(with)g(Freenet.)2202 2054 y Fg(IEEE)e(Internet)j(Computing)p
Fi(,)f(6\(1\):40\22649,)i(2002.)2040 2078 y
SDict begin H.S end
 2040 2078
a 2040 2078 a
SDict begin 10.5 H.A end
 2040 2078 a 2040 2078 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.hill94extending) cvn H.B
/DEST pdfmark end
 2040 2078 a 2077
2150 a Fi([5])38 b(G.)18 b(Hill)g(and)i(W)-7 b(.)18 b(Hall.)g
(Extending)i(the)f(Microcosm)h(model)f(to)g(a)2202 2237
y(distrib)o(uted)g(en)m(vironment.)h(In)f Fg(Pr)m(oceedings)h(of)e(the)
h(Eur)m(opean)2202 2324 y(Confer)m(ence)h(on)g(Hyperte)o(xt)f
(\(ECHT'94\))p Fi(,)e(pages)j(32\22640,)g(1994.)2040
2349 y
SDict begin H.S end
 2040 2349 a 2040 2349 a
SDict begin 10.5 H.A end
 2040 2349 a 2040 2349
a
SDict begin [ /View [/XYZ H.V] /Dest (cite.kato02gisp) cvn H.B /DEST
pdfmark end
 2040 2349 a 2077 2420 a Fi([6])38 b(D.)18 b(Kato.)h(GISP:)e(Global)i
(information)h(sharing)f(protocol)h(-)f(a)2202 2507 y(distrib)o(uted)g
(inde)o(x)g(for)g(peer)o(-to-peer)g(systems.)g(In)g Fg(Pr)m(oc.)g
(P2P'02)p Fi(,)2202 2594 y(pages)h(65\22673,)g(2002.)2040
2618 y
SDict begin H.S end
 2040 2618 a 2040 2618 a
SDict begin 10.5 H.A end
 2040 2618 a 2040 2618
a
SDict begin [ /View [/XYZ H.V] /Dest (cite.lukka02guids) cvn H.B /DEST
pdfmark end
 2040 2618 a 2077 2689 a Fi([7])38 b(T)-6 b(.)18 b(J.)h(Lukka)g(and)h
(B.)e(F)o(allenstein.)g(Freenet-lik)o(e)h(guids)h(for)2202
2777 y(implementing)g(xanalogical)g(hyperte)o(xt.)f(In)g
Fg(Pr)m(oc.)f(Hyperte)o(xt'02)p Fi(,)2202 2864 y(pages)i(194\226195.)h
(A)m(CM)e(Press,)f(2002.)2040 2888 y
SDict begin H.S end
 2040 2888 a 2040
2888 a
SDict begin 10.5 H.A end
 2040 2888 a 2040 2888 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.malkhi02viceroy) cvn H.B
/DEST pdfmark end
 2040 2888 a 2077 2959
a Fi([8])38 b(D.)18 b(Malkhi,)h(M.)g(Naor)m(,)g(and)h(D.)e(Ratajczak.)h
(V)l(icero)o(y:)k(a)c(scalable)2202 3046 y(and)h(dynamic)g(emulation)f
(of)g(the)g(b)o(utter\003y)-5 b(.)18 b(In)h Fg(Pr)m(oc.)f(PODC)2202
3133 y(2002)p Fi(,)i(pages)g(183\226192.)g(A)m(CM)f(Press,)f(2002.)2040
3158 y
SDict begin H.S end
 2040 3158 a 2040 3158 a
SDict begin 10.5 H.A end
 2040 3158 a 2040 3158
a
SDict begin [ /View [/XYZ H.V] /Dest (cite.maymounkov02kademlia) cvn
H.B /DEST pdfmark end
 2040 3158 a 2077 3229 a Fi([9])38 b(P)-8 b(.)18 b(Maymounk)o(o)o(v)k
(and)d(D.)f(Mazi)t(\264)-29 b(eres.)20 b(Kademlia:)j(A)c(Peer)o
(-to-peer)2202 3316 y(Information)h(System)e(Based)i(on)f(the)g(XOR)f
(metric.)h(In)g Fg(Pr)m(oc.)2202 3403 y(IPTPS02)p Fi(,)f(2002.)2040
3422 y
SDict begin H.S end
 2040 3422 a 2040 3422 a
SDict begin 10.5 H.A end
 2040 3422 a 2040 3422
a
SDict begin [ /View [/XYZ H.V] /Dest (cite.ratnasamy01can) cvn H.B
/DEST pdfmark end
 2040 3422 a 77 x Fi([10])38 b(S.)18 b(Ratnasamy)-5
b(,)19 b(P)-8 b(.)18 b(Francis,)g(M.)h(Handle)o(y)-5
b(,)20 b(R.)e(Karp,)h(and)2202 3586 y(S.)f(Schenk)o(er)l(.)h(A)g
(scalable)g(content-addressable)i(netw)o(ork.)f(In)2202
3673 y Fg(Pr)m(oc.)e(SIGCOMM)h(2001)p Fi(,)h(pages)g(161\226172.)h(A)m
(CM)e(Press,)f(2001.)2040 3698 y
SDict begin H.S end
 2040 3698 a 2040 3698
a
SDict begin 10.5 H.A end
 2040 3698 a 2040 3698 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.schneier96appliedcryptography)
cvn H.B /DEST pdfmark end
 2040 3698 a 71 x Fi([11])38
b(B.)18 b(Schneier)l(.)h Fg(Applied)g(Crypto)o(gr)o(aphy)p
Fi(.)i(John)f(W)m(ile)o(y)e(&)h(Sons,)2202 3856 y(1996.)2040
3866 y
SDict begin H.S end
 2040 3866 a 2040 3866 a
SDict begin 10.5 H.A end
 2040 3866 a 2040 3866
a
SDict begin [ /View [/XYZ H.V] /Dest (cite.stoica01chord) cvn H.B /DEST
pdfmark end
 2040 3866 a 85 x Fi([12])38 b(I.)18 b(Stoica,)g(R.)h(Morris,)f(D.)h
(Kar)o(ger)m(,)f(M.)h(F)-6 b(.)18 b(Kaashoek,)i(and)2202
4038 y(H.)e(Balakrishnan.)i(Chord:)k(A)18 b(scalable)i(peer)o(-to-peer)
f(lookup)2202 4126 y(service)g(for)g(internet)g(applications.)g(In)g
Fg(Pr)m(oc.)g(SIGCOMM)g(2001)p Fi(,)2202 4213 y(pages)h(149\226160.)h
(A)m(CM)e(Press,)f(2001.)2040 4237 y
SDict begin H.S end
 2040 4237 a 2040
4237 a
SDict begin 10.5 H.A end
 2040 4237 a 2040 4237 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.thompson01coincidence) cvn
H.B /DEST pdfmark end
 2040 4237 a 71 x Fi([13])38
b(M.)19 b(K.)f(Thompson)i(and)g(D.)e(C.)g(De)h(Roure.)g(Hypermedia)h
(by)2202 4395 y(coincidence.)g(In)f Fg(Pr)m(oceedings)h(of)f(the)g
(twelfth)f(A)n(CM)g(confer)m(ence)2202 4483 y(on)h(Hyperte)o(xt)g(and)h
(Hypermedia)p Fi(,)g(pages)f(129\226130.)i(A)m(CM)e(Press,)2202
4570 y(2001.)2040 4579 y
SDict begin H.S end
 2040 4579 a 2040 4579 a
SDict begin 10.5 H.A end
 2040
4579 a 2040 4579 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.p2p-hypertext-panel) cvn
H.B /DEST pdfmark end
 2040 4579 a 86 x Fi([14])38 b(U.)18
b(K.)h(W)m(iil,)e(N.)h(O.)g(Bouvin,)i(D.)e(Larsen,)h(D.)f(C.)g(De)h
(Roure,)g(and)2202 4752 y(M.)g(K.)f(Thompson.)i(Peer)o(-to-peer)e
(hyperte)o(xt.)i(In)e Fg(Pr)m(oceedings)i(of)2202 4840
y(the)f(thirteenth)g(confer)m(ence)i(on)e(Hyperte)o(xt)g(and)h
(hypermedia)p Fi(,)2202 4927 y(pages)g(69\22671.)g(A)m(CM)f(Press,)f
(2002.)2040 4951 y
SDict begin H.S end
 2040 4951 a 2040 4951 a
SDict begin 10.5 H.A end
 2040 4951
a 2040 4951 a
SDict begin [ /View [/XYZ H.V] /Dest (cite.zhao01tapestry) cvn H.B
/DEST pdfmark end
 2040 4951 a 71 x Fi([15])38 b(B.)18 b(Y)-10
b(.)19 b(Zhao,)g(J.)f(D.)g(K)o(ubiato)n(wicz,)i(and)f(A.)g(D.)f
(Joseph.)i(T)-6 b(apestry:)2202 5109 y(An)19 b(infrastructure)g(for)g
(f)o(ault-tolerant)g(wide-area)g(location)h(and)2202
5197 y(routing.)f(T)-5 b(echnical)19 b(Report)g(UCB/CSD-01-1141,)g
(Computer)2202 5284 y(Science)g(Di)n(vision,)g(U.)f(C.)g(Berk)o(ele)o
(y)-5 b(,)20 b(2001.)p eop end
%%Trailer

userdict /end-hook known{end-hook}if
%%EOF

--------------040008000200030306060304--




From MAILER-DAEMON Tue Jul 08 09:49:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZskP-00050W-5D
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 09:43:09 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19Zsjb-0004WJ-UF
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 09:42:19 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZsOQ-0005Fa-Te
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 09:20:27 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19ZsEO-0002Cd-D9
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 09:10:04 -0400
Received: (qmail 16314 invoked by uid 65534); 8 Jul 2003 13:10:03 -0000
Received: from pD9588997.dip.t-dialin.net (EHLO gmx.de) (217.88.137.151)
  by mail.gmx.net (mp022) with SMTP; 08 Jul 2003 15:10:03 +0200
Message-ID: <3F0AC25B.5030003@gmx.de>
Date: Tue, 08 Jul 2003 15:08:43 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] UMLLink paper
References: <20030708072325.GB28929@tarzan.it.jyu.fi>
In-Reply-To: <20030708072325.GB28929@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 13:43:07 -0000

Tuomas Lukka wrote:
> Hi, could you let me know ASAP if you could take care of the UMLLink
> paper (it was accepted as a poster). Asko and I are on holiday,
> and Tuukka is in Poland, apparently.

I can do simple changes and administrative stuff, but I don't feel up to 
the more creative stuff. In particular, I can do:

- confirm intention to send demo/poster
- make abstract
- address low-level referee comments (there seem to be none, tho ^.^)
- rework paper to address poster/demo, if I know the poster/demo
- confirm that I'll give a demo (if we want)

I don't feel up to the task of making the poster, though. I also cannot 
print it; not sure about the logistics (I'm supposed to bring it to the 
conference).

> BTW: what were the copyright forms, when do I need to mail them?

http://www.cloznet.com/ht03/copyright_std.cfm?id=192

-b




From MAILER-DAEMON Tue Jul 08 10:39:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19Ztbv-00029g-AS
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 10:38:27 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19ZtWK-0000oD-Fl
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 10:32:40 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19ZtVn-0000YU-BA
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 10:32:09 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZtV2-0000II-5Q
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 10:31:20 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h68EVFUA005591;
	Tue, 8 Jul 2003 17:31:15 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h68EVnDx011230;
	Tue, 8 Jul 2003 17:31:49 +0300 (EETDST)
Date: Tue, 8 Jul 2003 17:31:49 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] UMLLink paper
Message-ID: <20030708143149.GF28929@tarzan.it.jyu.fi>
References: <20030708072325.GB28929@tarzan.it.jyu.fi>
	<3F0AC25B.5030003@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <3F0AC25B.5030003@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.it.jyu.fi id
	h68EVFUA005591
cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 14:38:25 -0000

On Tue, Jul 08, 2003 at 03:08:43PM +0200, Benja Fallenstein wrote:
> Tuomas Lukka wrote:
> >Hi, could you let me know ASAP if you could take care of the UMLLink
> >paper (it was accepted as a poster). Asko and I are on holiday,
> >and Tuukka is in Poland, apparently.
>=20
> I can do simple changes and administrative stuff, but I don't feel up t=
o=20
> the more creative stuff. In particular, I can do:
>=20
> - confirm intention to send demo/poster
> - make abstract
> - address low-level referee comments (there seem to be none, tho ^.^)
> - rework paper to address poster/demo, if I know the poster/demo
> - confirm that I'll give a demo (if we want)
>=20
> I don't feel up to the task of making the poster, though. I also cannot=
=20
> print it; not sure about the logistics (I'm supposed to bring it to the=
=20
> conference).

Ok, I can do the poster text and get it to you as .ps.

Could you go to a printing shop in Germany and give it to them on a flopp=
y?
Or do we need to get someone to print it in Jyv=E4skyl=E4 and mail it sna=
il-mail
to you ?=20

> >BTW: what were the copyright forms, when do I need to mail them?
>=20
> http://www.cloznet.com/ht03/copyright_std.cfm?id=3D192

And when - do I need to worry about this before end of holiday?

	Tuomas



From MAILER-DAEMON Tue Jul 08 10:48:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19Zti9-00040V-RQ
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 10:44:53 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19Zthv-0003u6-VQ
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 10:44:39 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Ztgp-0003QY-7j
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 10:43:31 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20)
	id 19ZtXh-0001LM-Gp
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 10:34:05 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h68EY3UA005672;
	Tue, 8 Jul 2003 17:34:03 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h68EYbCM011242;
	Tue, 8 Jul 2003 17:34:37 +0300 (EETDST)
Date: Tue, 8 Jul 2003 17:34:37 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] View2D enhancing.
Message-ID: <20030708143437.GG28929@tarzan.it.jyu.fi>
References: <20030708073220.GE28929@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307081215040.31128-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307081215040.31128-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
cc: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 14:44:51 -0000

On Tue, Jul 08, 2003 at 01:08:40PM +0300, Matti Katila wrote:
> 
> On Tue, 8 Jul 2003, Tuomas Lukka wrote:
> > On Tue, Jul 08, 2003 at 01:19:02AM +0300, Matti Katila wrote:
> > > I run into problems with View2D. I would like to make it use faster way 
> > > to change scene i.e., through setParams. As you already know we have more 
> > > than one main node with FenPDF. I have made a simple interface to change 
> > > scene's parameters but it doesn't work because no one keeps track of all 
> > > possible coordinate systems since recursive view2ds can be just one 
> > > instance in the whole view. 
> > > 
> > > So can we add a new parameter to View2D?
> > > 
> > >     public abstract void render(VobScene vs, 
> > > -		Object plane,
> > > +		Object plane, Object key,
> > > 		int matchingParent,
> > > 		    int box2screen, int box2plane
> > > 			);
> > > 
> > > 
> > > With this change and simple helper class:
> > 
> > Umm, I'm not at all in the clear about what you're trying to achieve
> > and how.
> 
> View2D is one big instance and it renders all viewports shown in screen, 
> main nodes and buoys currently. Dragging of main node can be made fast 
> because we can save the coordsys number in the main node instance.
> We can't use fast dragging(using the same vobscene and changing coordsys 
> parameters) with: moving notes, selecting area because they are a part of 
> View2D chain instance and saving the coordsys number there is ridiculous 
> in the current View2D chain layer as I noticed it. So if we want speed - 
> we need to save that coordsystem to somewhere.

I still don't understand how the ``key`` parameter would help.

Please be 10x more explicit and clear than usual, because I'm in holiday mode.

Why not just use matchingparent and the View2D's known internal structure?

> > > /** Very simple util to save integer in map.
> > >  */
> > > public class CoordsysCache {
> > >     private Map coords = new WeakHashMap(10);
> > >     public void set(Object key, int cs) {
> > > 	coords.put(key, new Integer(cs));
> > >     }
> > >     
> > >     public int get(Object key) {
> > > 	return ((Integer)coords.get(key)).intValue();
> > >     }
> > > }
> > > 
> > > 
> > > We could use setParams easily and make things faster.
> > 
> > This is very bad on Kaffe and possibly others, creating lots of
> > Integer objects for the GC to worry about.
> 
> Other possibility is to create a new View2D chain instance for every 
> viewport.

... which is not a particularly nice option.

	Tuomas



From MAILER-DAEMON Tue Jul 08 14:16:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ZwxM-0005eE-Ee
	for mharc-gzz-dev@gnu.org; Tue, 08 Jul 2003 14:12:48 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19Zww8-0004VN-J6
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 14:11:32 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19Zwt3-0002zY-Sa
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 14:08:22 -0400
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20)
	id 19ZwsX-0002hS-Hv
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 08 Jul 2003 14:07:49 -0400
Received: (qmail 24500 invoked by uid 65534); 8 Jul 2003 18:07:48 -0000
Received: from p5082CF64.dip.t-dialin.net (EHLO gmx.de) (80.130.207.100)
  by mail.gmx.net (mp012) with SMTP; 08 Jul 2003 20:07:48 +0200
Message-ID: <3F0B0826.9050907@gmx.de>
Date: Tue, 08 Jul 2003 20:06:30 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.3.1) Gecko/20030618 Debian/1.3.1-3
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] UMLLink paper
References: <20030708072325.GB28929@tarzan.it.jyu.fi>
	<3F0AC25B.5030003@gmx.de> <20030708143149.GF28929@tarzan.it.jyu.fi>
In-Reply-To: <20030708143149.GF28929@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1b5
Precedence: list
List-Id: Gzz developers <gzz-dev.nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
X-List-Received-Date: Tue, 08 Jul 2003 18:12:46 -0000

Tuomas Lukka wrote:
> On Tue, Jul 08, 2003 at 03:08:43PM +0200, Benja Fallenstein wrote:
>>I don't feel up to the task of making the poster, though. I also cannot 
>>print it; not sure about the logistics (I'm supposed to bring it to the 
>>conference).
> 
> Ok, I can do the poster text and get it to you as .ps.

Ok.

> Could you go to a printing shop in Germany and give it to them on a floppy?

I think so. I'll take care of printing.

>>>BTW: what were the copyright forms, when do I need to mail them?
>>
>>http://www.cloznet.com/ht03/copyright_std.cfm?id=192
> 
> And when - do I need to worry about this before end of holiday?

August 15th, 2003.

Here's the details:
http://www.sheridanprinting.com/typedept/ht2.htm

- Benja




From MAILER-DAEMON Wed Jul 09 15:03:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19aKBF-00054d-7R
	for mharc-gzz-dev@gnu.org; Wed, 09 Jul 2003 15:00:41 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19aJoU-0007Xf-Px
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 09 Jul 2003 14:37:10 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19aJXb-0002q2-TT
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 09 Jul 2003 14:19:44 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19aIsL-0001qv-Rh
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 09 Jul 2003 13:37:06 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h69HavUA016876
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Wed, 9 Jul 2003 20:36:57 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h69HbWRn020113
	for gzz-dev@mail.freesoftware.fsf.org;
	Wed, 9 Jul 2003 20:37:32 +0300 (EETDST)
Date: Wed, 9 Jul 2003 20:37:32 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030709173732.GC19812@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] Posters
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Jul 2003 19:00:27 -0000

Everybody should read this, even if you're not going
to the conferences:

	http://www.swarthmore.edu/NatSci/cpurrin1/posteradvice.htm

	Tuomas



From MAILER-DAEMON Sun Jul 13 11:50:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bj79-0007bj-OW
	for mharc-gzz-dev@gnu.org; Sun, 13 Jul 2003 11:50:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bj72-0007DT-Ix
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 11:50:08 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bj6g-0005qJ-EU
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 11:49:46 -0400
Received: from posti2.jyu.fi ([130.234.4.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19bj6L-0004o3-DW
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 11:49:25 -0400
Received: from tukki.cc.jyu.fi (daemon@tukki.cc.jyu.fi [130.234.4.100])
	by posti2.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6DFnMdc001734
	for <gzz-dev@mail.freesoftware.fsf.org>; Sun, 13 Jul 2003 18:49:22 +0300
Received: (from jvkujala@localhost)
	by tukki.cc.jyu.fi (8.11.6+Sun/8.10.2) id h6DFnM502179
	for gzz-dev@mail.freesoftware.fsf.org;
	Sun, 13 Jul 2003 18:49:22 +0300 (EEST)
Date: Sun, 13 Jul 2003 18:49:22 +0300
From: Janne Kujala <jvkujala@cc.jyu.fi>
To: gzz-dev@mail.freesoftware.fsf.org
Message-ID: <20030713184921.A1834@cc.jyu.fi>
Mail-Followup-To: gzz-dev@mail.freesoftware.fsf.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2.5i
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Cc: 
Subject: [Gzz] Demoing FenPDF and fenfire doesn't compile
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2003 15:50:14 -0000

We would like to show FenPDF in IV'03 as part of the 
paper paper presentation. 

A single-focus view to a structure of interconnected PDF 
files would probably be best for demonstrating the need for 
unique textures. Could someone (benja?) help with obtaining this?
We are leaving on tuesday. 

fenfire does not compile:

org/fenfire/util/RDFList.java:7: cannot resolve symbol
symbol  : class LIST 
location: package lava
import org.fenfire.vocab.lava.LIST;

Someone forgot to add vocab/LIST.java? 
I got it to compile by deleting util/RDFList.*

	jvk



From MAILER-DAEMON Sun Jul 13 14:59:08 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bm3Z-0007ib-RK
	for mharc-gzz-dev@gnu.org; Sun, 13 Jul 2003 14:58:45 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bm3U-0007LI-Iv
	for gzz-dev@nongnu.org; Sun, 13 Jul 2003 14:58:40 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bm3G-0006kz-AG
	for gzz-dev@nongnu.org; Sun, 13 Jul 2003 14:58:26 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19bm3C-0005ol-NJ
	for gzz-dev@nongnu.org; Sun, 13 Jul 2003 14:58:22 -0400
Received: (qmail 7156 invoked by uid 65534); 13 Jul 2003 18:58:11 -0000
Received: from pD9E1297D.dip.t-dialin.net (EHLO gmx.de) (217.225.41.125)
	by mail.gmx.net (mp004) with SMTP; 13 Jul 2003 20:58:11 +0200
Message-ID: <3F11AB4F.90105@gmx.de>
Date: Sun, 13 Jul 2003 20:56:15 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Matti Katila <majukati@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@nongnu.org>
Subject: [Gzz] org/fenfire/util/RDFList.java
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2003 18:58:44 -0000


Dear Matti,

just saw your RDFList class in CVS because of Janne's mail. You probably 
haven't seen that is a standard list vocabulary for RDF already:

     http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab

If you need lists, please change your code to use that. Thank you!

- Benja




From MAILER-DAEMON Sun Jul 13 15:19:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bmNc-0001vc-Cb
	for mharc-gzz-dev@gnu.org; Sun, 13 Jul 2003 15:19:28 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bmNV-0001bA-4O
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 15:19:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bmNR-0001LS-FZ
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 15:19:17 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19bmMw-0000Y7-Su
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 15:18:47 -0400
Received: (qmail 25086 invoked by uid 65534); 13 Jul 2003 19:18:45 -0000
Received: from pD9E1297D.dip.t-dialin.net (EHLO gmx.de) (217.225.41.125)
	by mail.gmx.net (mp015) with SMTP; 13 Jul 2003 21:18:45 +0200
Message-ID: <3F11B027.5030307@gmx.de>
Date: Sun, 13 Jul 2003 21:16:55 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Janne Kujala <jvkujala@cc.jyu.fi>
Subject: Re: [Gzz] Demoing FenPDF and fenfire doesn't compile
References: <20030713184921.A1834@cc.jyu.fi>
In-Reply-To: <20030713184921.A1834@cc.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gzz-dev@mail.freesoftware.fsf.org
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2003 19:19:26 -0000


Hi,

Janne Kujala wrote:
> We would like to show FenPDF in IV'03 as part of the 
> paper paper presentation. 
> 
> A single-focus view to a structure of interconnected PDF 
> files would probably be best for demonstrating the need for 
> unique textures.

That would be a lot of work AFAIK. I would suggest a structure of
interconnected canvases; this can be done with the code we have now.

The single-focus should be possible with little change to buoyoing.py. 
Currently that doesn't seem to accept *any* user input, though. I don't 
know what caused that.

> Could someone (benja?) help with obtaining this?

I can try looking into why buoyoing doesn't accept input...

> fenfire does not compile:
> 
> org/fenfire/util/RDFList.java:7: cannot resolve symbol
> symbol  : class LIST 
> location: package lava
> import org.fenfire.vocab.lava.LIST;
> 
> Someone forgot to add vocab/LIST.java? 
> I got it to compile by deleting util/RDFList.*

Just delete that before compiling then, I suggest.

- Benja





From MAILER-DAEMON Sun Jul 13 15:51:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bmsJ-00083Y-3m
	for mharc-gzz-dev@gnu.org; Sun, 13 Jul 2003 15:51:11 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bmrz-00072u-P2
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 15:50:51 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bmrs-0006Wg-3W
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 15:50:44 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.20) id 19bmrj-0006KK-9N
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 13 Jul 2003 15:50:35 -0400
Received: (qmail 30176 invoked by uid 65534); 13 Jul 2003 19:50:33 -0000
Received: from pD9E1297D.dip.t-dialin.net (EHLO gmx.de) (217.225.41.125)
	by mail.gmx.net (mp002) with SMTP; 13 Jul 2003 21:50:33 +0200
Message-ID: <3F11B7B5.4000904@gmx.de>
Date: Sun, 13 Jul 2003 21:49:09 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] Demoing FenPDF and fenfire doesn't compile
References: <20030713184921.A1834@cc.jyu.fi> <3F11B027.5030307@gmx.de>
In-Reply-To: <3F11B027.5030307@gmx.de>
Content-Type: multipart/mixed; boundary="------------090903040509030105050707"
Cc: Janne Kujala <jvkujala@cc.jyu.fi>, gzz-dev@mail.freesoftware.fsf.org
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2003 19:51:09 -0000

This is a multi-part message in MIME format.
--------------090903040509030105050707
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit


Benja Fallenstein wrote:
> That would be a lot of work AFAIK. I would suggest a structure of
> interconnected canvases; this can be done with the code we have now.
> 
> The single-focus should be possible with little change to buoyoing.py. 
> Currently that doesn't seem to accept *any* user input, though. I don't 
> know what caused that.

I don't know what caused this, but now it's gone. I probably did 
something wrong, didn't clean something or so.

Attached is a diff to make the whole thing single-focus. Hope this works 
for you.

- Benja

--------------090903040509030105050707
Content-Type: text/plain;
 name="singlefocus.diff"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline;
 filename="singlefocus.diff"

Index: org/fenfire/demo/buoyoing.py
===================================================================
RCS file: /cvsroot/fenfire/fenfire/org/fenfire/demo/buoyoing.py,v
retrieving revision 1.89
diff -u -r1.89 buoyoing.py
--- org/fenfire/demo/buoyoing.py	7 Jul 2003 22:56:06 -0000	1.89
+++ org/fenfire/demo/buoyoing.py	13 Jul 2003 19:48:48 -0000
@@ -234,8 +234,8 @@
         #h0 = (self.split+.25) * h
         #h1 = (1-self.split) * h
 
-        w0 = w*2/3
-        h0 = w/2 - 40
+        w0 = w*3/4
+        h0 = h - 40
 
         w1 = w+100
         h1 = h/5+100
@@ -259,35 +259,36 @@
 		      s0, s0, 
 		      w0, h0)
 
-	vs.coords.setOrthoBoxParams(self.into2, 1, 
-		      -50,
-                      h-h1+50,
-		      s1, s1, 
-		      w1/s1, h1/s1)
+	#vs.coords.setOrthoBoxParams(self.into2, 1, 
+	#	      -50,
+        #              h-h1+50,
+	#	      s1, s1, 
+	#	      w1/s1, h1/s1)
 
 	vs.coords.setOrthoBoxParams(self.buoyinto1, 1, 
 		      ctrx - .5*buoywidth0, 0 +  .5*h0 - .5*buoyheight0,
 		      s0, s0, 
 		      buoywidth0/s0, buoyheight0/s0)
 
-	vs.coords.setOrthoBoxParams(self.buoyinto2, 1, 
-		      ctrx - .5*buoywidth1, h-h1+50,
-		      s1, s1, 
-		      buoywidth1/s1, buoyheight1/s1)
+	#vs.coords.setOrthoBoxParams(self.buoyinto2, 1, 
+	#	      ctrx - .5*buoywidth1, h-h1+50,
+	#	      s1, s1, 
+	#	      buoywidth1/s1, buoyheight1/s1)
 
 	
     def place(self, vs):
 	self.height = vs.size.height
 	self.width = vs.size.width
 	self.into1 = vs.orthoBoxCS(0, "FocusFrame1", 0, 0, 0, 0, 0, 0, 0)
-	self.into2 = vs.orthoBoxCS(0, "FocusFrame2", 0, 0, 0, 0, 0, 0, 0)
+	#self.into2 = vs.orthoBoxCS(0, "FocusFrame2", 0, 0, 0, 0, 0, 0, 0)
 
 	self.buoyinto1 = vs.orthoBoxCS(0, "BuoyFrame1", 0, 0, 0, 0, 0, 0, 0)
-	self.buoyinto2 = vs.orthoBoxCS(0, "BuoyFrame2", 0, 0, 0, 0, 0, 0, 0)
+	#self.buoyinto2 = vs.orthoBoxCS(0, "BuoyFrame2", 0, 0, 0, 0, 0, 0, 0)
 
 	self._doset(vs)
 
-	return [(self.into1, self.buoyinto1), (self.into2, self.buoyinto2)]
+	#return [(self.into1, self.buoyinto1), (self.into2, self.buoyinto2)]
+	return [(self.into1, self.buoyinto1)]
 
     def mouse(self, ev, oldvs):
         if dbg: pa(ev)
@@ -366,7 +367,7 @@
 class Scene(vob.buoy.buoymanager.MultiBuoyManager):
     def __init__(self):
 	vob.buoy.buoymanager.MultiBuoyManager.__init__(self, 
-		[mainNode, mainNode2], [ppconnector, tconnector],
+		[mainNode], [ppconnector, tconnector],
 		DoubleGeometer(self, context, nodeview),
                 context=context)
         w.setCursor('default')

--------------090903040509030105050707--




From MAILER-DAEMON Sun Jul 13 18:01:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bouc-0001tS-Fs
	for mharc-gzz-dev@gnu.org; Sun, 13 Jul 2003 18:01:42 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bouO-0000xs-6C
	for gzz-dev@nongnu.org; Sun, 13 Jul 2003 18:01:28 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bou7-0000IF-Nf
	for gzz-dev@nongnu.org; Sun, 13 Jul 2003 18:01:13 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.20) id 19bou0-0008Gu-9U
	for gzz-dev@nongnu.org; Sun, 13 Jul 2003 18:01:04 -0400
Received: (qmail 30817 invoked by uid 65534); 13 Jul 2003 22:01:02 -0000
Received: from pD9E1297D.dip.t-dialin.net (EHLO gmx.de) (217.225.41.125)
	by mail.gmx.net (mp002) with SMTP; 14 Jul 2003 00:01:02 +0200
Message-ID: <3F11D64A.7060503@gmx.de>
Date: Sun, 13 Jul 2003 23:59:38 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: GZZ developers <gzz-dev@nongnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gzz] Dart: xml_text_markup--benja
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Jul 2003 22:01:41 -0000

===============
XML text markup
===============

One of those ideas that come relatively
"out of the blue."

We have been `thinking about how to represent
styled text in XML in RDF`__. XHTML seemed
like a first possibility. Here's something
that goes far beyond, in a sense.

__ ../../pegboard/markup_xhtmlmodules--tjl/peg.gen.html

We want to allow for "semantic markup:"
markup that says what the author *means*.
WYGIWYM-- what you get is what you mean.

However, we don't want that *only*. We
also want presentational markup, because
people will want to use it, and if there
is no other way they will do presentational
markup through semantic markup-- they'll
"emphasize" whenever they want to italicize,
just to get the effect they want. This
is a really bad thing.

Semantic markup should be extensible; you
should be able to make up new, meaningful
'styles' as you go.

Here's an example from Tim Bray (source__)::

      <chunk xmlns="http://www.tbray.org/ns/22">The essays found
      on the web at <address>http://www.tbray.org</address> are
      <adj>boring</adj> <adj>pedantic</adj> ravings
      <adverb>clumsily</adverb> authored by a
      <adj>self-styled</adj> technologist.</chunk>

__ http://www.tbray.org/ongoing/When/200x/2003/04/09/SemanticMarkup

He says he made the namespace up when he typed
the above. (It's for example purposes.)

Now, that got me thinking. I propose that the
above could be written pretty much like that
in our system::

      <chunk xmlns="http://example.org/namespace/22#"
             xmlns:tag="http://example.org/namespace/tag#"
             tag:type="para">The essays found on the web
      at <address tag:type="span">http://www.tbray.org</address>
      are <adj tag:type="span">boring</adj>
      <adj tag:type="span">pedantic</adj> ravings
      <adverb tag:type="span">clumsily</adverb> authored by a
      <adj tag:type="span">self-styled</adj>
      technologist.</chunk>

This is, admittedly, clunkier, but it would be
auto-generated by the computer. -- Hmm. No, probably
it would be better to explicitly declare the type
of each tag somewhere; so, ok, something like this::

     <ff:text xmlns="..." xmlns:ff="..." xmlns:tags="...">
         <tags:paragraph-tag name="chunk"/>
         <tags:span-tag      name="address"/>
         <tags:span          name="adj"/>
         <tags:span          name="adverb"/>

         <chunk>The essays found on the web at
         <address>http://www.tbray.org</address> are
         <adj>boring</adj> <adj>pedantic</adj> ravings
         <adverb>clumsily</adverb> authored by a
         <adj>self-styled</adj> technologist.</chunk>
     </ff:text>

(Assume the namespace to be as in the previous example.)
Like that, this would be feasible to write by hand.
I like it.

*Now*, every tag declared through ``tags:paragraph-tag``
or ``tags:span-tag`` would have a URI formed in the
usual RDF way::

     chunk   = http://example.org/namespace/22#chunk
     address = http://example.org/namespace/22#address
     adj     = http://example.org/namespace/22#adj
     adverb  = http://example.org/namespace/22#adverb

And *then*, you could both use this with an XSLT
or CSS style sheet, and with a style definition
connected to the URI through RDF. We would normally
use the latter.

For presentational markup, we'd use something
straight-forward, like::

     <span foo:font-face="sans-serif"
           foo:font-size="18">...</span>

The semantic markup with special tags, as shown above,
should only be done at explicit user request.
If we only need to associate some text with a URI
to connect it to something, we'd do::

     <span bla:uri="urn:urn-5:..."/>


The point of all this is: If a user consciously uses
the semantic markup technology and user interface,
they *create a new XML vocabulary*. A user in the know
could also trivially use an existing vocabulary,
like XHTML or DocBook. The result will be XML markup
as you expect good XML markup to be. A great win.

\- Benja




From MAILER-DAEMON Mon Jul 14 00:21:55 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19buqV-0003bA-3r
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 00:21:51 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19buqJ-00037x-Ia
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 00:21:39 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19buqA-0002aP-VQ
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 00:21:31 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19buq8-0002Jk-Dh
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 00:21:28 -0400
Received: (qmail 12944 invoked by uid 65534); 14 Jul 2003 04:21:26 -0000
Received: from pD9E1297D.dip.t-dialin.net (EHLO gmx.de) (217.225.41.125)
	by mail.gmx.net (mp002) with SMTP; 14 Jul 2003 06:21:26 +0200
Message-ID: <3F122F70.7090502@gmx.de>
Date: Mon, 14 Jul 2003 06:20:00 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: GZZ developers <gzz-dev@nongnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gzz] 
	PEG: Wherever you need a cryptographic hash, use a Storm block
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 04:21:49 -0000


(This is Storm PEG 'only_hash_blocks--benja'.)

==========================================================================
Wherever you need a cryptographic hash, use a Storm block
==========================================================================

:Authors:  Benja Fallenstein
:Date-Created: 2003-07-14
:Last-Modified: $Date: 2003/04/25 12:29:33 $
:Revision: $Revision: 1.2 $
:Status:   Incomplete
:Scope:    Major
:Type:     Architecture


When designing cryptographic protocols, you often need to
use cryptographic hashes in one way or another.

Cryptographic hash functions may be broken. As a precaution,
current Storm block URIs include two hashes: a SHA-1 and
a TigerTree hash.

If one but not both of these is broken, we can select
a new, third hash function and `extend the lifetime of
our URIs through timestamping`__. (That's `patented`__,
but maybe we get lucky and the patent will have expired
by the time our first hash function breaks...)

__ http://www.math.columbia.edu/~bayer/papers/Timestamp_BHS93.pdfp
__ 
http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1=5373561.WKU.&OS=PN/5373561&RS=PN/5373561

Now, in such a situation, *all* the (hash, hashed data)
pairs *must* be timestamped in order to remain valid.

If different protocols built on top of Storm store
hashed data in different, application-specific ways
each, all these protocols must be known in order to
reliably do the timestamping. If, however, Storm blocks
are always used then a whole pool can be secured
by simply timestamping each block in the pool through
a simple algorithm.

Therefore, whenever you need a cryptographic hash
to be verified, it is best to put the hashed data
into its own Storm block.

(An additional benefit is that then, Storm will do
the hash checking for you; you don't need to
worry about it.)


Issues
======

None.


Changes
=======

It is best current practice that a protocol which is
part of or based on Storm will, if it needs to verify
the cryptographic hash of some piece of data,

- put that data in its own Storm block;
- refer to it using a Storm URI which contains
   the hash;
- use the Storm interfaces to retrieve the block,
   which ensures that the hash has been checked.

\- Benja




From MAILER-DAEMON Mon Jul 14 01:55:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bwIm-0006Zm-N3
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 01:55:08 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bwIW-0005qA-9a
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 14 Jul 2003 01:54:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bwIL-0005Ho-8T
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 14 Jul 2003 01:54:43 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19bwHW-0004Mn-Fc
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 14 Jul 2003 01:53:50 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6E5ri8K014191;
	Mon, 14 Jul 2003 08:53:44 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6E5sVEI010610;
	Mon, 14 Jul 2003 08:54:31 +0300 (EETDST)
Date: Mon, 14 Jul 2003 08:54:31 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] Demoing FenPDF and fenfire doesn't compile
Message-ID: <20030714055431.GA7780@tarzan.it.jyu.fi>
References: <20030713184921.A1834@cc.jyu.fi> <3F11B027.5030307@gmx.de>
	<3F11B7B5.4000904@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F11B7B5.4000904@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Janne Kujala <jvkujala@cc.jyu.fi>, gzz-dev@mail.freesoftware.fsf.org
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 05:55:06 -0000

On Sun, Jul 13, 2003 at 09:49:09PM +0200, Benja Fallenstein wrote:
> 
> Benja Fallenstein wrote:
> >That would be a lot of work AFAIK. I would suggest a structure of
> >interconnected canvases; this can be done with the code we have now.
> >
> >The single-focus should be possible with little change to buoyoing.py. 
> >Currently that doesn't seem to accept *any* user input, though. I don't 
> >know what caused that.
> 
> I don't know what caused this, but now it's gone. I probably did 
> something wrong, didn't clean something or so.
> 
> Attached is a diff to make the whole thing single-focus. Hope this works 
> for you.

Would be nice to have this as an option or a separate, simpler program.

	Tuomas





From MAILER-DAEMON Mon Jul 14 03:41:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19bxxh-0005yw-Sq
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 03:41:29 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19bxx6-0005Aq-T6
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 03:40:52 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19bxx2-000521-AU
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 03:40:48 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19bxww-0004WI-1g
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 03:40:42 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6E7ed8K018230;
	Mon, 14 Jul 2003 10:40:39 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6E7fRd6011125;
	Mon, 14 Jul 2003 10:41:27 +0300 (EETDST)
Date: Mon, 14 Jul 2003 10:41:27 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
Message-ID: <20030714074127.GB7780@tarzan.it.jyu.fi>
References: <3F11AB4F.90105@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F11AB4F.90105@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Matti Katila <majukati@verso.st.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 07:41:27 -0000

On Sun, Jul 13, 2003 at 08:56:15PM +0200, Benja Fallenstein wrote:
> 
> Dear Matti,
> 
> just saw your RDFList class in CVS because of Janne's mail. You probably 
> haven't seen that is a standard list vocabulary for RDF already:
> 
>     http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
> 
> If you need lists, please change your code to use that. Thank you!

Also, before you start using lists, please discuss it here, as there are 
several important versioning issues which we need to think about.

	Tuomas



From MAILER-DAEMON Mon Jul 14 08:09:36 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c277-0003jN-Rc
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 08:07:29 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c23p-0002lX-CW
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:04:05 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c209-0002Eg-Q0
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:00:18 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19c1zR-00025D-Ad
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 07:59:33 -0400
Received: (qmail 31841 invoked by uid 65534); 14 Jul 2003 11:59:32 -0000
Received: from pD9588F82.dip.t-dialin.net (EHLO gmx.de) (217.88.143.130)
	by mail.gmx.net (mp023) with SMTP; 14 Jul 2003 13:59:32 +0200
Message-ID: <3F129AC9.107@gmx.de>
Date: Mon, 14 Jul 2003 13:58:01 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
References: <3F11AB4F.90105@gmx.de> <20030714074127.GB7780@tarzan.it.jyu.fi>
In-Reply-To: <20030714074127.GB7780@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Matti Katila <majukati@verso.st.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 12:07:28 -0000

Tuomas Lukka wrote:
> On Sun, Jul 13, 2003 at 08:56:15PM +0200, Benja Fallenstein wrote:
> 
>>Dear Matti,
>>
>>just saw your RDFList class in CVS because of Janne's mail. You probably 
>>haven't seen that is a standard list vocabulary for RDF already:
>>
>>    http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
>>
>>If you need lists, please change your code to use that. Thank you!
> 
> 
> Also, before you start using lists, please discuss it here, as there are 
> several important versioning issues which we need to think about.

You're thinking of bags. Read the documentation above.

Or state what versioning issues you're talking about. The last time you 
were talking about versioning issues, you were talking about bags.

- Benja




From MAILER-DAEMON Mon Jul 14 08:20:34 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c2JW-0007bc-A4
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 08:20:18 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c2J7-0007Rs-JU
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:19:53 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c2Ah-0005UB-W4
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:11:12 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19c29t-00056t-Gj
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:10:21 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6ECAEND032379;
	Mon, 14 Jul 2003 15:10:14 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6ECAEs4032375; 
	Mon, 14 Jul 2003 15:10:14 +0300
Date: Mon, 14 Jul 2003 15:10:14 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
In-Reply-To: <3F11AB4F.90105@gmx.de>
Message-ID: <Pine.LNX.4.44.0307141425470.31128-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 12:20:16 -0000

On Sun, 13 Jul 2003, Benja Fallenstein wrote:
> just saw your RDFList class in CVS because of Janne's mail. You probably 
> haven't seen that is a standard list vocabulary for RDF already:
> 
>      http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
> 
> If you need lists, please change your code to use that. Thank you!

I read the vocabulary definition of list from the link you refer to and it 
was not a list?! 

    http://www.nist.gov/dads/HTML/linkedList.html

Ok, 'RDFList' is not list according to that definition but is closer 
than one found from collectionvocab.


   -Matti




From MAILER-DAEMON Mon Jul 14 08:36:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c2Ob-0000cv-9Q
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 08:25:33 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c2Kq-00088P-K2
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:21:40 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c2EL-0006Dh-Ii
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:14:58 -0400
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19c2Co-000604-6w
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 08:13:22 -0400
Received: (qmail 6422 invoked by uid 65534); 14 Jul 2003 12:13:20 -0000
Received: from pD9588F82.dip.t-dialin.net (EHLO gmx.de) (217.88.143.130)
	by mail.gmx.net (mp023) with SMTP; 14 Jul 2003 14:13:20 +0200
Message-ID: <3F129E0B.3090504@gmx.de>
Date: Mon, 14 Jul 2003 14:11:55 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
References: <Pine.LNX.4.44.0307141425470.31128-100000@verso.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307141425470.31128-100000@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 12:25:31 -0000

Matti Katila wrote:
> On Sun, 13 Jul 2003, Benja Fallenstein wrote:
> 
>>just saw your RDFList class in CVS because of Janne's mail. You probably 
>>haven't seen that is a standard list vocabulary for RDF already:
>>
>>     http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
>>
>>If you need lists, please change your code to use that. Thank you!
> 
> 
> I read the vocabulary definition of list from the link you refer to and it 
> was not a list?! 

I don't understand. It is absolutely a list. It was constructed by 
analogy with LISP cons lists.

Please use it.

- Benja




From MAILER-DAEMON Mon Jul 14 09:20:33 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c3Fl-0007mX-Ug
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 09:20:29 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c3Fh-0007aU-UG
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:20:25 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c3FL-0007OK-ME
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:20:04 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19c3FG-0007ED-KA
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:19:58 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6EDJt8K002129;
	Mon, 14 Jul 2003 16:19:55 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6EDKi8g016336;
	Mon, 14 Jul 2003 16:20:44 +0300 (EETDST)
Date: Mon, 14 Jul 2003 16:20:44 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
Message-ID: <20030714132044.GE11686@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307141425470.31128-100000@verso.st.jyu.fi>
	<3F129E0B.3090504@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F129E0B.3090504@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Matti Katila <majukati@verso.st.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 13:20:28 -0000

On Mon, Jul 14, 2003 at 02:11:55PM +0200, Benja Fallenstein wrote:
> Matti Katila wrote:
> >On Sun, 13 Jul 2003, Benja Fallenstein wrote:
> >
> >>just saw your RDFList class in CVS because of Janne's mail. You probably 
> >>haven't seen that is a standard list vocabulary for RDF already:
> >>
> >>    http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
> >>
> >>If you need lists, please change your code to use that. Thank you!
> >
> >
> >I read the vocabulary definition of list from the link you refer to and it 
> >was not a list?! 
> 
> I don't understand. It is absolutely a list. It was constructed by 
> analogy with LISP cons lists.
> 
> Please use it.

Let's talk first about *for what* is it going to be used.

Different types of lists need different versioning constraints.

	Tuomas



From MAILER-DAEMON Mon Jul 14 09:22:27 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c3Go-00011t-3M
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 09:21:34 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c3Gk-0000pa-L2
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:21:30 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c3GL-0008Re-OO
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:21:06 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19c3EP-0006fF-Hs
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:19:05 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6EDJ18K002119;
	Mon, 14 Jul 2003 16:19:01 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6EDJoZP016330;
	Mon, 14 Jul 2003 16:19:50 +0300 (EETDST)
Date: Mon, 14 Jul 2003 16:19:50 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
Message-ID: <20030714131949.GD11686@tarzan.it.jyu.fi>
References: <3F11AB4F.90105@gmx.de> <20030714074127.GB7780@tarzan.it.jyu.fi>
	<3F129AC9.107@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F129AC9.107@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Matti Katila <majukati@verso.st.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 13:21:32 -0000

On Mon, Jul 14, 2003 at 01:58:01PM +0200, Benja Fallenstein wrote:
> Tuomas Lukka wrote:
> >On Sun, Jul 13, 2003 at 08:56:15PM +0200, Benja Fallenstein wrote:
> >
> >>Dear Matti,
> >>
> >>just saw your RDFList class in CVS because of Janne's mail. You probably 
> >>haven't seen that is a standard list vocabulary for RDF already:
> >>
> >>   http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
> >>
> >>If you need lists, please change your code to use that. Thank you!
> >
> >
> >Also, before you start using lists, please discuss it here, as there are 
> >several important versioning issues which we need to think about.
> 
> You're thinking of bags. Read the documentation above.

Well, the versioning of lists is very intricate, and also depends
very much on the internal representation.

For linked lists, two sets of incompatible changes can get you
a loop, if not dealt with properly (see the gzz/Documentation/VersioningMerge).

For the RDF _1, _2, ... types of lists, it's worse: an insertion
maps to O(n) tuple changes.

> Or state what versioning issues you're talking about. The last time you 
> were talking about versioning issues, you were talking about bags.

?

	Tuomas



From MAILER-DAEMON Mon Jul 14 09:24:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c3Ju-0004Jr-OW
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 09:24:46 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c3Ie-0003lX-Db
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:23:28 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c3IE-0003XE-VZ
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:23:03 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19c3I3-0003ON-55
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:22:51 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6EDMjND003266;
	Mon, 14 Jul 2003 16:22:45 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6EDMjrq003262; 
	Mon, 14 Jul 2003 16:22:45 +0300
Date: Mon, 14 Jul 2003 16:22:45 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
In-Reply-To: <3F129E0B.3090504@gmx.de>
Message-ID: <Pine.LNX.4.44.0307141614480.31128-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 13:24:46 -0000

On Mon, 14 Jul 2003, Benja Fallenstein wrote:

> Matti Katila wrote:
> > On Sun, 13 Jul 2003, Benja Fallenstein wrote:
> > 
> >>just saw your RDFList class in CVS because of Janne's mail. You probably 
> >>haven't seen that is a standard list vocabulary for RDF already:
> >>
> >>     http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
> >>
> >>If you need lists, please change your code to use that. Thank you!
> > 
> > 
> > I read the vocabulary definition of list from the link you refer to and it 
> > was not a list?! 
> 
> I don't understand. It is absolutely a list. It was constructed by 
> analogy with LISP cons lists.
> 
> Please use it.

While reading fifth time, I'm convinced it is a list. Yep, it 
should be used. Such a formal language was a bit strongly written to be 
understood without being mathematician or perhaps I have summer 
feelings =)


   -Matti




From MAILER-DAEMON Mon Jul 14 09:54:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c3mT-000491-UB
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 09:54:17 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c3mA-0002z6-Ok
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:53:58 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c3ll-0002Ip-Gn
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:53:34 -0400
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19c3la-0001zN-Jt
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 09:53:22 -0400
Received: (qmail 23962 invoked by uid 65534); 14 Jul 2003 13:53:21 -0000
Received: from pD9588F82.dip.t-dialin.net (EHLO gmx.de) (217.88.143.130)
	by mail.gmx.net (mp025) with SMTP; 14 Jul 2003 15:53:21 +0200
Message-ID: <3F12B57A.1000900@gmx.de>
Date: Mon, 14 Jul 2003 15:51:54 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
References: <Pine.LNX.4.44.0307141614480.31128-100000@verso.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307141614480.31128-100000@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 13:54:16 -0000

Matti Katila wrote:
> On Mon, 14 Jul 2003, Benja Fallenstein wrote:
> 
> 
>>Matti Katila wrote:
>>
>>>On Sun, 13 Jul 2003, Benja Fallenstein wrote:
>>>
>>>
>>>>just saw your RDFList class in CVS because of Janne's mail. You probably 
>>>>haven't seen that is a standard list vocabulary for RDF already:
>>>>
>>>>    http://www.w3.org/TR/2003/WD-rdf-schema-20030123/#ch_collectionvocab
>>>>
>>>>If you need lists, please change your code to use that. Thank you!
>>>
>>>
>>>I read the vocabulary definition of list from the link you refer to and it 
>>>was not a list?! 
>>
>>I don't understand. It is absolutely a list. It was constructed by 
>>analogy with LISP cons lists.
>>
>>Please use it.
> 
> 
> While reading fifth time, I'm convinced it is a list. Yep, it 
> should be used. Such a formal language was a bit strongly written to be 
> understood without being mathematician or perhaps I have summer 
> feelings =)

=)

I hadn't actually read when referring, because I knew already how it 
worked 8-)

- Benja




From MAILER-DAEMON Mon Jul 14 10:08:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c3wN-0002Nv-Nz
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 10:04:31 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c3wH-0002Ln-CI
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 10:04:25 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c3wF-0002L4-P7
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 10:04:24 -0400
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19c3uq-0001nn-HD
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 10:02:56 -0400
Received: (qmail 27940 invoked by uid 65534); 14 Jul 2003 14:02:55 -0000
Received: from pD9588F82.dip.t-dialin.net (EHLO gmx.de) (217.88.143.130)
	by mail.gmx.net (mp021) with SMTP; 14 Jul 2003 16:02:55 +0200
Message-ID: <3F12B7B9.4020901@gmx.de>
Date: Mon, 14 Jul 2003 16:01:29 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
References: <3F11AB4F.90105@gmx.de> <20030714074127.GB7780@tarzan.it.jyu.fi>
	<3F129AC9.107@gmx.de> <20030714131949.GD11686@tarzan.it.jyu.fi>
In-Reply-To: <20030714131949.GD11686@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Matti Katila <majukati@verso.st.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 14:04:26 -0000


Tuomas Lukka wrote:
> On Mon, Jul 14, 2003 at 01:58:01PM +0200, Benja Fallenstein wrote:
>>You're thinking of bags. Read the documentation above.
> 
> Well, the versioning of lists is very intricate, and also depends
> very much on the internal representation.
> 
> For linked lists, two sets of incompatible changes can get you
> a loop, if not dealt with properly (see the gzz/Documentation/VersioningMerge).

Ok, true, for merge it's a problem.

Last time you raised this, you were talking about--

> For the RDF _1, _2, ... types of lists, it's worse: an insertion
> maps to O(n) tuple changes.

which is bags, not "collections" (lists); this is about diff/patch, and 
I assumed again you were talking about problems when doing diff/patch, 
not merge.

In CVS, we can probably represent lists through the special RDF syntax:

     <hasAuthors rdf:parseType="Collection">
         <rdf:Description rdf:about="http://ex.org/foo"/>
         <rdf:Description rdf:about="http://ex.org/bar"/>
     </hasAuthors>

(This is a list with two elements.) CVS will then handle merge just fine.

When doing a triple-wise diff, the merge will indeed have to handle 
lists specially. I think the partial order stuff would probably be fine.

[other mail]
> Let's talk first about *for what* is it going to be used.
> 
> Different types of lists need different versioning constraints.

Ok, how so? (Which types of lists need different merge handling?)

- Benja




From MAILER-DAEMON Mon Jul 14 13:00:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19c6gg-0006m6-9f
	for mharc-gzz-dev@gnu.org; Mon, 14 Jul 2003 13:00:30 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19c6gd-0006li-Hd
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 13:00:27 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19c6gc-0006lX-0k
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 13:00:26 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19c6gb-0006kr-Hh
	for gzz-dev@nongnu.org; Mon, 14 Jul 2003 13:00:25 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6EH0G8K010735;
	Mon, 14 Jul 2003 20:00:16 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6EH15lZ016881;
	Mon, 14 Jul 2003 20:01:05 +0300 (EETDST)
Date: Mon, 14 Jul 2003 20:01:05 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] org/fenfire/util/RDFList.java
Message-ID: <20030714170105.GF11686@tarzan.it.jyu.fi>
References: <3F11AB4F.90105@gmx.de> <20030714074127.GB7780@tarzan.it.jyu.fi>
	<3F129AC9.107@gmx.de> <20030714131949.GD11686@tarzan.it.jyu.fi>
	<3F12B7B9.4020901@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F12B7B9.4020901@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Matti Katila <majukati@verso.st.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jul 2003 17:00:28 -0000

On Mon, Jul 14, 2003 at 04:01:29PM +0200, Benja Fallenstein wrote:
> 
> Tuomas Lukka wrote:
> >On Mon, Jul 14, 2003 at 01:58:01PM +0200, Benja Fallenstein wrote:
> >>You're thinking of bags. Read the documentation above.
> >
> >Well, the versioning of lists is very intricate, and also depends
> >very much on the internal representation.
> >
> >For linked lists, two sets of incompatible changes can get you
> >a loop, if not dealt with properly (see the 
> >gzz/Documentation/VersioningMerge).
> 
> Ok, true, for merge it's a problem.
> 
> Last time you raised this, you were talking about--
> 
> >For the RDF _1, _2, ... types of lists, it's worse: an insertion
> >maps to O(n) tuple changes.
> 
> which is bags, not "collections" (lists); this is about diff/patch, and 
> I assumed again you were talking about problems when doing diff/patch, 
> not merge.
> 
> In CVS, we can probably represent lists through the special RDF syntax:
> 
>     <hasAuthors rdf:parseType="Collection">
>         <rdf:Description rdf:about="http://ex.org/foo"/>
>         <rdf:Description rdf:about="http://ex.org/bar"/>
>     </hasAuthors>
> 
> (This is a list with two elements.) CVS will then handle merge just fine.

Well, fine for some definitions of fine - at least you'll get a conflict
if two people reorganize the list.

However, what I'd like is some ability to go by the IDs, i.e. do merge
based on sets of triples.

The atoms and molecules stuff I did has bearing on this: it essentially
solved the diff-merge problem for linked lists, I think.

> When doing a triple-wise diff, the merge will indeed have to handle 
> lists specially. I think the partial order stuff would probably be fine.

Yes. And that's one reason I wouldn't like to take in lists 
before we have a clear picture of merge; I'd prefer to first have merge
and then add lists and add support for them to merge at the same time,
so as to not make merge even more difficult at first ;)

> [other mail]
> >Let's talk first about *for what* is it going to be used.
> >
> >Different types of lists need different versioning constraints.
> 
> Ok, how so? (Which types of lists need different merge handling?)

It depends on how important order is.

	Tuomas



From MAILER-DAEMON Wed Jul 16 09:23:59 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19cmDK-0003gP-Iz
	for mharc-gzz-dev@gnu.org; Wed, 16 Jul 2003 09:20:58 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19cmBc-0002vS-5S
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 16 Jul 2003 09:19:12 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19cm7N-0001Qd-2P
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 16 Jul 2003 09:14:49 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19cm4E-0000U2-Ch
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 16 Jul 2003 09:11:34 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6GDBOND010511
	for <gzz-dev@mail.freesoftware.fsf.org>; Wed, 16 Jul 2003 16:11:24 +0300
Received: from localhost (atsoukka@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6GDBO9B010507
	for <gzz-dev@mail.freesoftware.fsf.org>; Wed, 16 Jul 2003 16:11:24 +0300
X-Authentication-Warning: verso.st.jyu.fi: atsoukka owned process doing -bs
Date: Wed, 16 Jul 2003 16:11:24 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@verso.st.jyu.fi
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <Pine.LNX.4.44.0307161608540.10352-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: [Gzz] RDF elements in Navidoc UML
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2003 13:20:57 -0000

Hi,

I added elements "rdf-literal" and "rdf-resource" into Navidoc UML
language. I guess, these could be used with "assoc" to clarify new 
vocabulary in the future.

An example soon at himalia:
http://himalia.it.jyu.fi/ffdoc/navidoc/rdf.gen.html

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Wed Jul 16 09:28:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19cmK2-0007kp-Lw
	for mharc-gzz-dev@gnu.org; Wed, 16 Jul 2003 09:27:54 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19cmJd-0007PI-1H
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 16 Jul 2003 09:27:29 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19cmGQ-0005Iz-SN
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 16 Jul 2003 09:24:11 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.20) id 19cmG3-000538-RE
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 16 Jul 2003 09:23:47 -0400
Received: (qmail 18985 invoked by uid 65534); 16 Jul 2003 13:23:46 -0000
Received: from pD9E12BA5.dip.t-dialin.net (EHLO gmx.de) (217.225.43.165)
	by mail.gmx.net (mp010) with SMTP; 16 Jul 2003 15:23:46 +0200
Message-ID: <3F155189.8090504@gmx.de>
Date: Wed, 16 Jul 2003 15:22:17 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: [Gzz] RDF elements in Navidoc UML
References: <Pine.LNX.4.44.0307161608540.10352-100000@verso.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307161608540.10352-100000@verso.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 16 Jul 2003 13:27:53 -0000

Asko Soukka wrote:
> Hi,
> 
> I added elements "rdf-literal" and "rdf-resource" into Navidoc UML
> language. I guess, these could be used with "assoc" to clarify new 
> vocabulary in the future.
> 
> An example soon at himalia:
> http://himalia.it.jyu.fi/ffdoc/navidoc/rdf.gen.html

Cool!
- Benja




From MAILER-DAEMON Wed Jul 16 23:04:10 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19cz3x-0000A6-MH
	for mharc-gzz-dev@gnu.org; Wed, 16 Jul 2003 23:04:09 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19cz3w-00005T-6K
	for gzz-dev@nongnu.org; Wed, 16 Jul 2003 23:04:08 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19cz3s-0008T5-G9
	for gzz-dev@nongnu.org; Wed, 16 Jul 2003 23:04:05 -0400
Received: from gnuftp.gnu.org ([199.232.41.6])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19cz3s-0008Rm-6i
	for gzz-dev@nongnu.org; Wed, 16 Jul 2003 23:04:04 -0400
Received: from [212.97.188.187] (helo=mail.ru)
	by gnuftp.gnu.org with smtp (Exim 4.20) id 19cz3n-000839-BR
	for gzz-dev@nongnu.org; Wed, 16 Jul 2003 23:04:02 -0400
Date: Thu, 17 Jul 2003 02:59:50 +0000
From: adelton@asc.on.ca
To: Gzz-dev <gzz-dev@nongnu.org>
References: <G992A6FHBJJCFFC9@nongnu.org>
In-Reply-To: <G992A6FHBJJCFFC9@nongnu.org>
Message-ID: <0ILJCJA181ECHJGB@asc.on.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=Windows-1251
Content-Transfer-Encoding: 8bit
Subject: [Gzz] new mail            ieGdbiEB
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2003 03:04:09 -0000

Ìû ðàäû ïðåäëîæèòü âàì íîâûé áåñïëàòíûé ïî÷òîâûé ñåðâèñ http://www.mail15.com. Åãî îòëè÷èòåëüíûå îñîáåííîñòè:
1) ðàçìåð ÿùèêà 15 ìá;
2) çàùèùåííîñòü è íàäåæíîñòü;
3) âîçìîæíîñòü èñïîëüçîâàíèÿ ëþáûõ ïî÷òîâûõ ïðîãðàìì(POP,IMAP,SMTP);
4) äîñòóï èç ëþáîãî ìåñòà â ëþáîå âðåìÿ;
5) ïðîñòîé è äîñòóïíûé âåáèíòåðôåéñ ñ ÏÎËÍÛÌ ÎÒÑÓÒÑÒÂÈÅÌ ÐÅÊËÀÌÛ;
6) àíòèâèðóñíûé è àíòèñïàìîâûé êîíòðîëü;
7) ìãíîâåííàÿ ïåðåñûëêà ïî÷òû.

Åñëè âû íå õîòèòå ïîëó÷àòü áîëåå äàííóþ ðàññûëêó, ïèøèòå mailto:unsubscribe@mail15.com?subject=unsubscribe

*************

 We are glad to invite you at new free mail service http://www.mail15.com. The advantages of this service are:
 1) mailbox, up to 15 Mb;
 2) absolute privacy and high reliability;
 3) ability to use mail clients (POP3, IMAP4, SMTP);
 4) access from anywhere, anytime;
 5) flexible light-weight web interface without advertising banners;
 6) antivirus and antispam control;
 7) fast mail transfer;
 8) high speed network channel;
 9) flexible light-weight web interface;
 10) wide spread ability of mail filtering and forwarding mail;
 11) clock around support;

 If you wish to be removed:
mailto:unsubscribe@mail15.com?subject=unsubscrib

3GmeJUn4G0




From MAILER-DAEMON Thu Jul 17 14:47:35 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19dDmb-0001oZ-7k
	for mharc-gzz-dev@gnu.org; Thu, 17 Jul 2003 14:47:13 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19dDby-0006Dm-Cx
	for gzz-dev@nongnu.org; Thu, 17 Jul 2003 14:36:14 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19dDbJ-0005sc-IE
	for gzz-dev@nongnu.org; Thu, 17 Jul 2003 14:35:35 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19dDbH-0005rO-JA
	for gzz-dev@nongnu.org; Thu, 17 Jul 2003 14:35:31 -0400
Received: (qmail 26169 invoked by uid 65534); 17 Jul 2003 18:35:29 -0000
Received: from p5082D860.dip.t-dialin.net (EHLO gmx.de) (80.130.216.96)
	by mail.gmx.net (mp013) with SMTP; 17 Jul 2003 20:35:29 +0200
Message-ID: <3F16EC19.3060606@gmx.de>
Date: Thu, 17 Jul 2003 20:34:01 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: GZZ developers <gzz-dev@nongnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gzz] Dart: Digital archives without patented techology
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2003 18:47:11 -0000


(note: also submitted this to shouldexist.org to establish prior art)
- Benja

===========================================
Digital archives without patented techology
===========================================

:Author:    Benja Fallenstein <b.fallenstein@gmx.de>
:Created:   2003-07-17
:Modified:  $Date: 2003/07/17 17:17:31 $

The Web isn't made to last. If you browse a mail archive
from 1999, many links have already ceased to work.
How can we stand on the shoulders on giants if those
shoulders are rotting away?

The Internet Archive is a good thing, but it would
be even better if links to documents would continue
to work normally as long as there is *anybody*
on the network who still has a copy. With P2P lookup
services, we can do that-- if we can authenticate
old documents. We want to know what *really* was at
``foo.com`` in 2003, not what somebody we don't even know
only claims was there. We need a new addressing scheme
for Web pages that continues to work after the publisher
has stopped publishing the page.

We could use digital signatures: Any page signed
by the original publisher would be acceptable.
But digital signatures are only valid as long as
the key that gave them hasn't expired-- two years
are often recommended. To solve this problem, timestamping
is used. But digital timestamping technology is
heavily `patented`_.

.. _patented: http://www.surety.com/patents.php

This idea describes a lasting digital verification
system which provides a service similar to digital
signatures, but (AFAIK) doesn't use patented techology.



Introduction
============

First off, I should probably mention that my main
motivation for this writeup is not to get people
excited about it, but to prevent this from being
patented, even though I'm certainly trying to make
it interesting to read. ;-)

I'm also not a
professional cryptologist; I'll be gladful to hear
of all security holes, fundamental or in details,
that people discover in this system.

With that out of the way, I'll first briefly
describe the "classic" way of archiving digital
signatures, based on patented technology.

This discussion
is useful for two reasons; firstly because it allows
me to show how my system appears to be just as secure
(because possible attacks on my system have equivalents
in the "classic" system), and secondly because
it's good to know how close my system is technically
to a timestamping system, even though it doesn't do
timestamping (and thus doesn't infringe on the
patents!).

But if you want, you can `skip over`__ this part.

__ #digital-signatures-without-timestamping


Public-key infrastructure
-------------------------

First off, cryptographic keys don't last forever,
for two reasons. First, your private key can be
stolen, e.g. by someone hacking into your computer.
Second, with most signature algorithms, if you give
a lot of signatures with the same private key,
it becomes less expensive for an attacker to compute
the private key from the signatures.

Therefore, there must be a way for every participant
in the system to *revoke* an old key (say that it's
not valid any more) and to acquire a new key.

Because of this, it's not a good idea to put
public keys in document identifiers; we want
the identifiers to remain valid even after the
public keys have been revoked.

Instead, we have *certificate authorities* (CAs).
A CA binds a public key to a name that is unique
inside the CA's domain.

For example, we could have
a document identifier ``addr:foo/bar/baz``,
indicating a hierarchy. First we would look
for a certificate for ``foo``, signed by the
root CA. Then we would look for a certificate
for ``bar``, signed by the public key
indicated in the previous certificate. Then
we would look for a version of ``addr:foo/bar/baz``
signed by the key from the ``bar`` certificate.

(A CA also publishes a Certificate Revocation
List (CRL), which is a list of certificates
for which the certified keys have been revoked.
A verifier can be sure that

The root CA's public key needs to be transmitted
out-of-bounds; for SSL (``https:`` URIs), it's
often embedded in the code of your browser.

When a key is revoked, the key holder can ask
their CA to issue a new certificate with a new
public key. The key holder can then continue
to sign messages. However, signatures given
with the old key will no longer be valid.


Timestamping
------------

To solve this problem, digital timestamping
is used. A timestamping service (TSS) is an entity
you can submit documents to, and get back a
certificate that the given document existed
at a given time. If a signature is timestamped,
you can prove that it existed before the key
that gave it was revoked.

There are a number of different ways to
timestamp a digital document. Here is a simple
way, which isn't patented (there was a patent,
but it has been overturned):

     There is a Trusted Third Party (TTP) which is
     trusted by everybody. To obtain a timestamp,
     submit a cryptographic hash of your document to the TTP.
     The TTP will sign a statement like, "Hash H
     was submitted on 2003-07-10." Showing the
     TTP's signature proves that the document
     really existed on that date.

Of course, you're really putting a lot of trust
in the TTP, here: It can arbitrarily back-date
or forward-date documents.

Here's a much better system:

     There is a central timestamping service (TSS).
     To obtain a timestamp, submit its hash to the TSS.
     The TSS operates in a sequence of "rounds," say,
     one second long. It builds a Merkle hash tree of all
     documents submitted in one round. Showing the chain
     of hashes required to authenticate your document
     as part of the hash proves that your document
     existed during that timestamping round.

     Each round includes the hash of the previous round,
     so each round certifies the previous round. Once
     a week or so, the TSS publishes the current round's
     hash in a widely-witnessed manner (e.g., in an
     important newspaper). Thus, even if one doesn't trust
     the TSS or anybody on the network at all, the age
     of a document can be proven (well enough that it
     should stand up in court) with a resolution of
     one week (in the example).

Unfortunately, this one's patented.


Key archival
------------

The final component of the system is a Key
Archival Service (KAS) which stores the public key
of the root CA (or root CAs, if there is more than
one root) at any given time. Using the KAS, it is
possible to authenticate a past signature by
checking that all the necessary certificates
existed and were signed by keys that were correct
at the time.

I'll omit detailed discussion about how a KAS
could work. The notion of a KAS has been
`introduced relatively recently`__, in a
`FAST 2002`__ paper.

__ http://mosquitonet.stanford.edu/publications/FAST2002/
__ http://www.usenix.org/publications/library/proceedings/fast02/



Digital "signatures" without timestamping
=========================================

It's important to note that in a conventional
public key system, as described above, your
Certificate Authority can, if it acts maliciously,
sign arbitrary messages in your name:
It simply issues a certificate which binds your
name to one of its own keys, and uses this key
to sign messages in your stead.

In other words, you have to trust your CA
not to misrepresent you.

Based on this, I suggest a system in which you
appoint a *deputy*, an entity somewhat like a CA,
who tells others which messages you have
signed. Let's first examine a simplistic
implementation, similar to the simple timestamping
system above:

     There is a single deputy, a third party trusted
     by everybody in the system. To sign a document,
     the signer authenticates themselves to the TTP
     and submits the document. To verify, the
     verifier submits the document to the TTP and asks
     whether it was earlier submitted by the signer.

Again, clearly, the trust this system places in the
TTP is too high. Therefore, we extend it in a way
similar to the second timestamping system, above,
to ensure that the deputy cannot take back anything
that it has said before.

As with the timestamping service, we let the deputy
operate in rounds. In every round, the deputy 'signs'
statements of the form, "Signer S has signed message M."
The deputy builds a hash tree over these statements,
and publishes the root as its current round value.

A signature consists of all information necessary
to prove that the statement "S signed M" is part
of the hash tree of any round published by the deputy.
Verification consists of retrieving the appropriate
published round value and checking that "S signed M"
is part of that hash tree.

Additionally, every round can include the
hash of the previous round. Verification then
consists of retrieving the current round value;
retrieving the previous round records
(not necessarily from the deputy itself)
and verifying them against the current round value;
and verifying the signature against the relevant
previous round value.

This way, the deputy cannot "undo" a previous round
without also undoing all rounds after it,
because all later rounds include the earlier round
by reference.

While timestamping with catenate certificates
(rounds including the previous round's hash)
is `patented`__, the claims on this patents are
on "method[s] of certifying the temporal sequence
of digital documents in a series of such documents"
or "method[s] of time-stamping a digital document."
Since we don't use this technology to time-stamp
documents or certify their temporal sequence--
we use it to provide digital signatures--, I believe
that the patent does not apply (I'm not a lawyer, though).

__ 
http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1=5136646.WKU.&OS=PN/5136646&RS=PN/5136646

In regular intervals,
the deputy may publish the current round's hash value
in a widely witnessed way. For example, it could
distribute a notarized (non-digital) document
to an international group of libraries, plus anybody
else who is interested and pays a nominal fee.

Then, it becomes truly difficult for the deputy
to deny a signature it has authorized at an
earlier time.

The `literature`__ contains numerous linking schemes
for timestamping certificates that are more
advanced than the simple concept of linearly
linked rounds of Merkle hash trees (`example`__).
Many of these could be trivially applied to
the above "signature" scheme as well.

__ http://www.tcs.hut.fi/~helger/crypto/link/timestamping/
__ http://www.tcs.hut.fi/~helger/cuculus/bula98.html

On the part of the deputy, two types of attack
are obviously possible:

- The deputy can sign arbitrary messages
   in others' names.
- The deputy could neglect to include one round's
   value into the chain of rounds. Then, these
   signatures would be as good as never given.

In the CA/TSS/KAS approach, equivalent attacks
are possible: A signer's CA can give signatures
in the signer's name, and the timestamping service
can neglect to include one round's value into
its chain of rounds, making signatures timestamped
in that round unverifiable after the corresponding
public key has expired.

Of course, the CA/TSS/KAS approach allows there
to be a hierarchy of CAs, instead of having
just a single CA for everybody. Similarly, there
could be a hierarchy of deputies, where every
deputy submits its round values to the parent
deputy for authentication (except the root deputy,
which behaves as described above).



Using Byzantine agreement to construct a trusted root
=====================================================

A problem with the CA/TSS/KAS approach is that
a certain level of trust in the timestamping service
is required; yes, you can verify securely that a
signature is from 1999 by verifying the timestamp
against the hash value published in a 1999 newspaper,
but usually you will not want to dig up old newspapers
before you can visit a web site. But if you rely
on the "current round value" as provided online
by the TSS, the TSS can cheat.

To rectify this situation, a system has been
`proposed`__ in which a group of timestamping
services from different administrative domains
(e.g., different nations) collaborate. In
this system, Prokopius, each participating
TSS publishes their own round values in a
"master" timestamping service, collaboratively
maintained by all the participating TSSes.
This may replace the publication of grounding
values in e.g. a newspaper.

__ http://www.arxiv.org/ps/cs/0106058

In Prokopius, the master timestamping service
operates in rounds which are comparatively long,
in the order of a few days to a week. The
participating nodes use a Byzantine agreement
protocol to agree on the value of each round;
due to the relative long rounds, the high costs
of Byzantine agreement protocols seem justified.

Each participant timestamping service would then
give out timestamps in rounds of a second or so,
but would "ground" its timestamps in the
"master" service maybe once a week.

A very similar system could be employed in the deputy
approach. There would be a hierarchy of
deputies, but the root deputy would be collaboratively
managed by the first-level deputies below the root,
which may come from a number of different
administrative domains.

A signer could then appoint a first-level deputy
that they trust, and be confident that the
first-level deputy will in turn ensure that
the Prokopius-like root deputy acts correctly.



Promises
========

The Prokopius-like root introduces one additional
problem: the long intervals between its rounds,
because until a signature can be verified
against one of the root's rounds, it cannot be
assumed to be trusted by every verifier in the
system. Therefore, it would take days to obtain
a globally verifiable digital signature.

To solve this, we can use conventional key-based
signatures. Before a signature has been
included in one of the root deputy's rounds,
the signer can issue a *promise* that
the signature will be included in the next
root round, and sign this promise with
a private key.

When the next root round is being formed,
the verifier can then ask the signer for
proof that it has really submitted the
signature for inclusion into the root round.
If the signer is unable to provide such proof,
the verifier may submit information to that
effect to the first-level deputies; then,
these deputies will include the signature
into the root round, basically as if it
had been submitted by the original signer.

Thus, a verifier can be sure that the
promised signature will eventually end up
in the next root round, provided that
it "keeps an eye on it."

Of course, the verifier may not be online
during the formation of the next root round,
and thus unable to ascertain the signature's
inclusion into the round. However, they can
easily delegate the task to a trusted
system which *is* "always on" (maybe
the verifier's own deputy). This trusted system
could then, for example, send the whole
signature information to the verifier
by e-mail when the signature has entered
the chain of root values.


Key management
--------------

For the promise system to work, it must be
possible to associate public keys with signers.
To do this, we can let a signer's deputy
double as its CA.

(It should be noted that while we use
public-key cryptography, we only need
key-based signatures for the duration
of a single root round; because we don't
use them in archival storage, we don't
need a timestamping system or Key Archival Service.)

To function as a CA, a deputy must both
be able to publish both certificates and a
Certificate Revocation List.

Both of these functions could well be handled
through the normal signature system, as
already described; the deputy would simply
create certificates and CRLs and sign them
like any other message.

The deputy could try an attack in which it
signs two different CRLs in the same round,
presents one CRL to the verifier in an attempt
to convince them that a certain key is valid,
and later present a second one to the
root deputy to convince it that the key wasn't
valid at all.

If the verifier keeps a copy of the CRL
for every promise it is checking, this isn't
a problem, though. The verifier can show its
version of the CRL to the root deputy, which
will conclude that the deputy made the
verifier believe the signature was valid,
and will therefore include it in the next
root round.

It should be noted that if a key is revoked
in one round, promises given with this key
in the same round should be considered valid.
Otherwise, a signer could simply give a promise
and revoke their key immediately after,
subverting the promise system.



Final remarks
=============

I'd like to repeat that while I believe this system
not to be covered by the Surety patents, I am not
a lawyer. I would like to hear others' opinions
about this matter.

I haven't done a thorough security analysis
on this system, at least not yet, because
I wanted to get a note about it out as soon as
possible in order to establish prior art
in case anybody tries to patent it.

I would be happy to hear about any problems with
my system that I have not considered.




From MAILER-DAEMON Thu Jul 17 18:21:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19dH7x-0004f4-LG
	for mharc-gzz-dev@gnu.org; Thu, 17 Jul 2003 18:21:29 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19dH6q-0004U2-L2
	for gzz-dev@nongnu.org; Thu, 17 Jul 2003 18:20:20 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19dH6Z-0004IU-BM
	for gzz-dev@nongnu.org; Thu, 17 Jul 2003 18:20:03 -0400
Received: from pop.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19dH4f-0003f0-V6
	for gzz-dev@nongnu.org; Thu, 17 Jul 2003 18:18:06 -0400
Received: (qmail 28274 invoked by uid 65534); 17 Jul 2003 22:18:04 -0000
Received: from p5082D860.dip.t-dialin.net (EHLO gmx.de) (80.130.216.96)
	by mail.gmx.net (mp015) with SMTP; 18 Jul 2003 00:18:04 +0200
Message-ID: <3F172043.3010507@gmx.de>
Date: Fri, 18 Jul 2003 00:16:35 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] Dart: Digital archives without patented techology
References: <3F16EC19.3060606@gmx.de>
In-Reply-To: <3F16EC19.3060606@gmx.de>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2003 22:21:27 -0000

Benja Fallenstein wrote:
> ===========================================
> Digital archives without patented techology
> ===========================================

Three additional notes about this dart.

First, we can make it so that you don't need to register with a deputy 
before you can start using the system for yourself.

Instead, you could create an identity simply by creating a file 
containing data identifying you, like--

     name
     address
     e-mail
     current public key

     REQUIRED: the deputy you want to use

The hash of this file is your identity; URIs in your namespace could 
look something like,

     urn:x-foo:<hash>:<localname>

where <hash> is your identity.

You can then start to use the system off-line, and signatures will be 
axiomatic (the hash of 'signed' messages will be stored in a list on 
your harddisk, and anything in that list will be considered signed by you).

Later you can go online, and send the identity file to the deputy you 
picked, and authenticate yourself to the deputy using the information 
from the identity file (most simply, the public key). Then you can 
submit (the hashes of) the messages on your harddisk to the deputy to 
acquire a real, global signature on them.

To resolve x-foo URIs, people would need to have your identity file. 
They'd check the hash of the identity file against the hash in the URI. 
If it matches, they would accept any signature that is given by the 
deputy named in the identity file.

So you could acquire a global, deputy-based id without going online, 
when setting up your Storm system. (You'd need to do this once before 
you could create pointers in Storm.)


Second, I think the system easily extends to documents that can be 
changed by groups of people, e.g. a CVS repository. Simply have the 
deputy authenticate signatures from any member of the group. For each 
member of the group, register that member's public key as one that can 
sign promises for the group.

When a member leaves the group, revoke that member's public key for use 
in that group.


Third, the deputy hierarchy can be used to provide mnemonic, DNS-like 
names for documents. For example,

     urn:x-deputies:foo:fenfire:manifesto

The root deputy would name the first-level deputy (foo); the first-level 
deputy would name the second-level deputy (fenfire) which would name the 
document.

A message would be signed by urn:x-deputies:foo:fenfire:manifesto's 
owner if the root deputy says that 'foo' says that 'fenfire' says that 
'manifesto's owner signed that message.

Of course, in accord with URN policies, a name must never be reassigned.

This would be a way to implement the "URI-on-the-side-of-a-bus" thing in 
our framework, with secure histories provided for these URIs.

- Benja




From MAILER-DAEMON Sat Jul 19 02:49:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19dlXP-0003Yy-Ko
	for mharc-gzz-dev@gnu.org; Sat, 19 Jul 2003 02:49:47 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19dlXN-0003RY-Gs
	for gzz-dev@mail.freesoftware.fsf.org; Sat, 19 Jul 2003 02:49:45 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19dlXK-0003Mi-GM
	for gzz-dev@mail.freesoftware.fsf.org; Sat, 19 Jul 2003 02:49:43 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19dlXJ-0003E1-NR
	for gzz-dev@mail.freesoftware.fsf.org; Sat, 19 Jul 2003 02:49:41 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6J6nbND023941
	for <gzz-dev@mail.freesoftware.fsf.org>; Sat, 19 Jul 2003 09:49:37 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6J6nbrq023937
	for <gzz-dev@mail.freesoftware.fsf.org>; Sat, 19 Jul 2003 09:49:37 +0300
Date: Sat, 19 Jul 2003 09:49:37 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <Pine.LNX.4.44.0307190943570.12090-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: [Gzz] Requirements PEG for controllers events.
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sat, 19 Jul 2003 06:49:46 -0000


==============================================================================
PEG controllers_events--mudyc: Requirements for handling events of controllers
==============================================================================

:Authors:  Matti J. Katila
:Date-Created: 2003-07-15
:Last-Modified: $Date: 2003/07/19 06:29:46 $
:Revision: $Revision: 1.1 $
:Status:   Current
:Scope:    Minor
:Type:     Architecture requirements


.. :Stakeholders:

.. Affect-PEGs:


New user interfaces need custom controllers. Handling the events of these
controllers should be modular, easy and generic from the bottom layer up 
to top layer where the user is main character.


Issues
======

- How this peg affects to Tjl's input framework?

- Should normal mouse controller and custom LEGO controllers 
  fit in the same API at some level?

    RESOLVED:
    Yes, 'cause to user they are just controllers.

- Should custom LEGO controllers be able to control many things
  in different contexts, like fiddling zoom pan in buoyoing view and
  in other view for example change the speed of interpolation?

    RESOLVED:
    This is minor issue since with requirements specified 
    it is doable. The question is: would it be sensible.
  

Requirements
============

For a user the controller interface should be easy, say
-------------------------------------------------------

- Inverting controller.

    - ``This mouse wheel works in wrong direction!``

- Automatic calibrating

    - ``This doesn't work!``

- Bind to any axe or button or modifier from any controller.

    - Bindings should be dynamically changeable while program is running.

        - ``Button 1, why?``
        - ``Why in vertical, why not in horizontal direction?``
        - ``Modifier with this would be nice..``  
        - ``I want that red looking LEGO controller, not that big blue :-)``
  
- (Scale)

    - ``Mouse is too slow!``


For programming, the control framework should support different models
----------------------------------------------------------------------

- Axis model

    - Absolutely 
    - Relative

- Normal mouse model

    - Point model

        - X and y in screen.

    - Dragging model

        - Close to relative axes model

- Modifiers






From MAILER-DAEMON Sun Jul 20 19:08:29 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19eNGv-0003JN-Sq
	for mharc-gzz-dev@gnu.org; Sun, 20 Jul 2003 19:07:17 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19eNGk-0003FJ-AD
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 20 Jul 2003 19:07:06 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19eNGT-00031j-Cn
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 20 Jul 2003 19:06:50 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.20) id 19eNGL-0002hy-5v
	for gzz-dev@mail.freesoftware.fsf.org; Sun, 20 Jul 2003 19:06:41 -0400
Received: (qmail 24631 invoked by uid 65534); 20 Jul 2003 23:06:39 -0000
Received: from pD9E122D7.dip.t-dialin.net (EHLO gmx.de) (217.225.34.215)
	by mail.gmx.net (mp003) with SMTP; 21 Jul 2003 01:06:39 +0200
Message-ID: <3F1B2023.60109@gmx.de>
Date: Mon, 21 Jul 2003 01:05:07 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: URGENT (deadline 23rd): Re: [Gzz] UMLLink paper
References: <20030708072325.GB28929@tarzan.it.jyu.fi> <3F0AC25B.5030003@gmx.de>
	<20030708143149.GF28929@tarzan.it.jyu.fi>
In-Reply-To: <20030708143149.GF28929@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=iso-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Sun, 20 Jul 2003 23:07:16 -0000


Hi Tuomas,

You promised to finish the UMLLink poster & get it to me, so that I 
could address its contents in the accompanying two pages for the website.

Unfortunately, you haven't done so; I haven't received it from you by 
mail and the version that is in CVS is extremely incomplete (basically 
nothing but a layout.)

I'm off starting today until the end of this week, and the deadline is 
the 23rd, i.e. Wednesday. So I cannot take care of this. :-(

Please update the short paper as you see fit and send it + an abstract 
to Lloyd <Lloyd.Rutledge@cwi.nl>.

We'll also get in trouble with printing the poster, since I'm leaving on 
August 2nd. I don't know too much about this, if a print shop can print 
it immediately I can get it done next week (provided I have it by 
then!!), but if this takes longer and I can't get this done before I 
leave we'd have to figure something out-- mail it to Morocco? Might take 
too long. Or to England-- but to whom there?

Argh, argh, argh.
- Benja

Tuomas Lukka wrote:
> On Tue, Jul 08, 2003 at 03:08:43PM +0200, Benja Fallenstein wrote:
>>I can do simple changes and administrative stuff, but I don't feel up to 
>>the more creative stuff. In particular, I can do:
>>
>>- confirm intention to send demo/poster
>>- make abstract
>>- address low-level referee comments (there seem to be none, tho ^.^)
>>- rework paper to address poster/demo, if I know the poster/demo
>>- confirm that I'll give a demo (if we want)
>>
>>I don't feel up to the task of making the poster, though. I also cannot 
>>print it; not sure about the logistics (I'm supposed to bring it to the 
>>conference).
> 
> Ok, I can do the poster text and get it to you as .ps.
> 
> Could you go to a printing shop in Germany and give it to them on a floppy?
> Or do we need to get someone to print it in Jyväskylä and mail it snail-mail
> to you ? 




From MAILER-DAEMON Mon Jul 21 05:06:35 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19eWZ3-0002GO-1s
	for mharc-gzz-dev@gnu.org; Mon, 21 Jul 2003 05:02:37 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19eWWy-00027R-2p
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 05:00:28 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19eWWa-0001rA-CX
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 05:00:05 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19eWPl-0007zv-LQ
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 04:53:01 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6L8qmSL019877;
	Mon, 21 Jul 2003 11:52:48 +0300
Received: from localhost (atsoukka@localhost)
	by silmu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6L8qmRA019873; 
	Mon, 21 Jul 2003 11:52:48 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Mon, 21 Jul 2003 11:52:48 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Subject: Re: URGENT (deadline 23rd): Re: [Gzz] UMLLink paper
In-Reply-To: <3F1B2023.60109@gmx.de>
Message-ID: <Pine.LNX.4.44.0307211147430.19667-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by silmu.st.jyu.fi id
	h6L8qmSL019877
Cc: Tuomas Lukka <lukka@mit.jyu.fi>, Benja Fallenstein <b.fallenstein@gmx.de>,
	Tuukka Hastrup <tuukka.hastrup@iki.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2003 09:02:35 -0000

Hi,

I'm totally out, about what should be done, but I could arrange time for
this tomorrow, and Tuukka is back from Poland.. I understood that he is
ready to make some long days. I suppose, I and Tuukka should start from
learning the poster advice URL
<http://www.swarthmore.edu/NatSci/cpurrin1/posteradvice.htm>.

Mon, 21 Jul 2003, Benja Fallenstein wrote:
> Hi Tuomas,
>=20
> You promised to finish the UMLLink poster & get it to me, so that I=20
> could address its contents in the accompanying two pages for the websit=
e.
>=20
> Unfortunately, you haven't done so; I haven't received it from you by=20
> mail and the version that is in CVS is extremely incomplete (basically=20
> nothing but a layout.)
>=20
> I'm off starting today until the end of this week, and the deadline is=20
> the 23rd, i.e. Wednesday. So I cannot take care of this. :-(
>=20
> Please update the short paper as you see fit and send it + an abstract=20
> to Lloyd <Lloyd.Rutledge@cwi.nl>.
>=20
> We'll also get in trouble with printing the poster, since I'm leaving o=
n=20
> August 2nd. I don't know too much about this, if a print shop can print=
=20
> it immediately I can get it done next week (provided I have it by=20
> then!!), but if this takes longer and I can't get this done before I=20
> leave we'd have to figure something out-- mail it to Morocco? Might tak=
e=20
> too long. Or to England-- but to whom there?
>=20
> Argh, argh, argh.
> - Benja
>=20
> Tuomas Lukka wrote:
> > On Tue, Jul 08, 2003 at 03:08:43PM +0200, Benja Fallenstein wrote:
> >>I can do simple changes and administrative stuff, but I don't feel up=
 to=20
> >>the more creative stuff. In particular, I can do:
> >>
> >>- confirm intention to send demo/poster
> >>- make abstract
> >>- address low-level referee comments (there seem to be none, tho ^.^)
> >>- rework paper to address poster/demo, if I know the poster/demo
> >>- confirm that I'll give a demo (if we want)
> >>
> >>I don't feel up to the task of making the poster, though. I also cann=
ot=20
> >>print it; not sure about the logistics (I'm supposed to bring it to t=
he=20
> >>conference).
> >=20
> > Ok, I can do the poster text and get it to you as .ps.
> >=20
> > Could you go to a printing shop in Germany and give it to them on a f=
loppy?
> > Or do we need to get someone to print it in Jyv=E4skyl=E4 and mail it=
 snail-mail
> > to you ?=20
>=20
>=20
>=20
> _______________________________________________
> Gzz-dev mailing list
> Gzz-dev@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/gzz-dev
>=20

--=20
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>





From MAILER-DAEMON Mon Jul 21 08:32:58 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19eZj1-00012h-VB
	for mharc-gzz-dev@gnu.org; Mon, 21 Jul 2003 08:25:07 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19eZi5-00005O-Np
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 08:24:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19eZhs-0008DI-CC
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 08:23:57 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19eZhr-0008Bl-3g
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 08:23:55 -0400
Received: (qmail 9562 invoked by uid 65534); 21 Jul 2003 12:23:53 -0000
Received: from pD9588280.dip.t-dialin.net (EHLO gmx.de) (217.88.130.128)
	by mail.gmx.net (mp008) with SMTP; 21 Jul 2003 14:23:53 +0200
Message-ID: <3F1BDAFE.3030107@gmx.de>
Date: Mon, 21 Jul 2003 14:22:22 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: URGENT (deadline 23rd): Re: [Gzz] UMLLink paper
References: <Pine.LNX.4.44.0307211147430.19667-100000@silmu.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307211147430.19667-100000@silmu.st.jyu.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Tuomas Lukka <lukka@mit.jyu.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Tuukka Hastrup <tuukka.hastrup@iki.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2003 12:25:06 -0000


Hi,

good to see that you guys can take care of this, thanks! I'm off now.

- Benja

Asko Soukka wrote:
> Hi,
> 
> I'm totally out, about what should be done, but I could arrange time for
> this tomorrow, and Tuukka is back from Poland.. I understood that he is
> ready to make some long days. I suppose, I and Tuukka should start from
> learning the poster advice URL
> <http://www.swarthmore.edu/NatSci/cpurrin1/posteradvice.htm>.
> 
> Mon, 21 Jul 2003, Benja Fallenstein wrote:
> 
>>Hi Tuomas,
>>
>>You promised to finish the UMLLink poster & get it to me, so that I 
>>could address its contents in the accompanying two pages for the website.
>>
>>Unfortunately, you haven't done so; I haven't received it from you by 
>>mail and the version that is in CVS is extremely incomplete (basically 
>>nothing but a layout.)
>>
>>I'm off starting today until the end of this week, and the deadline is 
>>the 23rd, i.e. Wednesday. So I cannot take care of this. :-(
>>
>>Please update the short paper as you see fit and send it + an abstract 
>>to Lloyd <Lloyd.Rutledge@cwi.nl>.
>>
>>We'll also get in trouble with printing the poster, since I'm leaving on 
>>August 2nd. I don't know too much about this, if a print shop can print 
>>it immediately I can get it done next week (provided I have it by 
>>then!!), but if this takes longer and I can't get this done before I 
>>leave we'd have to figure something out-- mail it to Morocco? Might take 
>>too long. Or to England-- but to whom there?
>>
>>Argh, argh, argh.
>>- Benja
>>
>>Tuomas Lukka wrote:
>>
>>>On Tue, Jul 08, 2003 at 03:08:43PM +0200, Benja Fallenstein wrote:
>>>
>>>>I can do simple changes and administrative stuff, but I don't feel up to 
>>>>the more creative stuff. In particular, I can do:
>>>>
>>>>- confirm intention to send demo/poster
>>>>- make abstract
>>>>- address low-level referee comments (there seem to be none, tho ^.^)
>>>>- rework paper to address poster/demo, if I know the poster/demo
>>>>- confirm that I'll give a demo (if we want)
>>>>
>>>>I don't feel up to the task of making the poster, though. I also cannot 
>>>>print it; not sure about the logistics (I'm supposed to bring it to the 
>>>>conference).
>>>
>>>Ok, I can do the poster text and get it to you as .ps.
>>>
>>>Could you go to a printing shop in Germany and give it to them on a floppy?
>>>Or do we need to get someone to print it in Jyväskylä and mail it snail-mail
>>>to you ? 
>>
>>
>>
>>_______________________________________________
>>Gzz-dev mailing list
>>Gzz-dev@nongnu.org
>>http://mail.nongnu.org/mailman/listinfo/gzz-dev
>>
> 
> 





From MAILER-DAEMON Mon Jul 21 08:38:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19eZv1-00060P-DO
	for mharc-gzz-dev@gnu.org; Mon, 21 Jul 2003 08:37:31 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19eZuX-0005aU-VH
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 08:37:01 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19eZu3-0005Gs-PV
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 08:36:34 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19eZq4-0003PO-DF
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 08:32:24 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6LCWHiM018464;
	Mon, 21 Jul 2003 15:32:18 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6LCXNUq022016;
	Mon, 21 Jul 2003 15:33:23 +0300 (EETDST)
Date: Mon, 21 Jul 2003 15:33:23 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: URGENT (deadline 23rd): Re: [Gzz] UMLLink paper
Message-ID: <20030721123323.GA19765@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307211147430.19667-100000@silmu.st.jyu.fi>
	<3F1BDAFE.3030107@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F1BDAFE.3030107@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Tuukka Hastrup <tuukka.hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2003 12:37:24 -0000

On Mon, Jul 21, 2003 at 02:22:22PM +0200, Benja Fallenstein wrote:
> 
> Hi,
> 
> good to see that you guys can take care of this, thanks! I'm off now.
> 
> - Benja
> 
> Asko Soukka wrote:
> >Hi,
> >
> >I'm totally out, about what should be done, but I could arrange time for
> >this tomorrow, and Tuukka is back from Poland.. I understood that he is
> >ready to make some long days. I suppose, I and Tuukka should start from
> >learning the poster advice URL
> ><http://www.swarthmore.edu/NatSci/cpurrin1/posteradvice.htm>.
> >
> >Mon, 21 Jul 2003, Benja Fallenstein wrote:
> >
> >>Hi Tuomas,
> >>
> >>You promised to finish the UMLLink poster & get it to me, so that I 
> >>could address its contents in the accompanying two pages for the website.
> >>
> >>Unfortunately, you haven't done so; I haven't received it from you by 
> >>mail and the version that is in CVS is extremely incomplete (basically 
> >>nothing but a layout.)
> >>
> >>I'm off starting today until the end of this week, and the deadline is 
> >>the 23rd, i.e. Wednesday. So I cannot take care of this. :-(
> >>
> >>Please update the short paper as you see fit and send it + an abstract 
> >>to Lloyd <Lloyd.Rutledge@cwi.nl>.

Hi, I'm working on it right now - got back from London yesterday.

> >>We'll also get in trouble with printing the poster, since I'm leaving on 
> >>August 2nd. I don't know too much about this, if a print shop can print 
> >>it immediately I can get it done next week (provided I have it by 
> >>then!!), but if this takes longer and I can't get this done before I 
> >>leave we'd have to figure something out-- mail it to Morocco? Might take 
> >>too long. Or to England-- but to whom there?

It should be possible immediately - especially if you just ask for it in 
A4 or A3 size chunks.


	Tuomas



From MAILER-DAEMON Mon Jul 21 14:13:31 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19efAA-0005kx-Pp
	for mharc-gzz-dev@gnu.org; Mon, 21 Jul 2003 14:13:30 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19efA8-0005k8-7g
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 14:13:28 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19efA6-0005jF-4l
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 14:13:26 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19efA5-0005ip-MN
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 21 Jul 2003 14:13:25 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6LIDNND003554;
	Mon, 21 Jul 2003 21:13:23 +0300
Received: from localhost (atsoukka@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6LIDN5M003550; 
	Mon, 21 Jul 2003 21:13:23 +0300
X-Authentication-Warning: verso.st.jyu.fi: atsoukka owned process doing -bs
Date: Mon, 21 Jul 2003 21:13:23 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@verso.st.jyu.fi
To: hemppah@cc.jyu.fi
Message-ID: <Pine.LNX.4.44.0307212106280.3236-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Subject: [Gzz] Reformatting (reST) PEG available_overlays--hemppah
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jul 2003 18:13:29 -0000

Hermanni,

There was some fatal formatting errors in your PEG (it made Docutils to 
raise an exception and break compiling process at Himalia) and finally I 
ended up to reformat the whole PEG :)

My solutions might not be the best, so please, check critically out the
new version and adopt only the parts you do like. If there's some reST
syntax you don't understand, ask me.

I didn't touch the content so you may easily also restore the older
version.

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 22 02:36:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19eqky-0002wZ-HN
	for mharc-gzz-dev@gnu.org; Tue, 22 Jul 2003 02:36:16 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19eqkq-0002mv-42
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 02:36:08 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19eqkd-0002D6-My
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 02:35:56 -0400
Received: from posti2.jyu.fi ([130.234.4.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19eqkb-0002B5-KF
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 02:35:53 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti2.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6M6Zhdc008721; 
	Tue, 22 Jul 2003 09:35:43 +0300
Subject: Re: [Gzz] Reformatting (reST) PEG available_overlays--hemppah
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Asko Soukka <asko.soukka@iki.fi>
In-Reply-To: <Pine.LNX.4.44.0307212106280.3236-100000@verso.st.jyu.fi>
References: <Pine.LNX.4.44.0307212106280.3236-100000@verso.st.jyu.fi>
Content-Type: text/plain
Organization: 
Message-Id: <1058855743.5190.15.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 22 Jul 2003 09:35:43 +0300
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2003 06:36:11 -0000

Hi,

Yes, I agree that formatting was not finished yet, I usually write the
text first and then do the formatting :).

Anyway, thank you for your time and for correcting the problems.

Btw, is this case an example of more general issue related to Docutils
(or something else), i.e., even there are draft documents in the CVS
(e.g., PEG drafts as in this particlular case), do we have to format the
text right from the beginning of a writing process, or is it possible
first to focus on a content and only then to formatting of a content in
order to get all documents compiled correctly?

AFAIK, every night all PEGs/design documents/some other documents are
compiled and moved to himalia (or something like that), right? Is it
possible to exclude draft documents from this process?


-Hermanni


On Mon, 2003-07-21 at 21:13, Asko Soukka wrote:
> Hermanni,
> 
> There was some fatal formatting errors in your PEG (it made Docutils to 
> raise an exception and break compiling process at Himalia) and finally I 
> ended up to reformat the whole PEG :)
> 
> My solutions might not be the best, so please, check critically out the
> new version and adopt only the parts you do like. If there's some reST
> syntax you don't understand, ask me.
> 
> I didn't touch the content so you may easily also restore the older
> version.




From MAILER-DAEMON Tue Jul 22 04:22:35 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19esPl-0006Zj-6h
	for mharc-gzz-dev@gnu.org; Tue, 22 Jul 2003 04:22:29 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19esPc-0006Jr-Vu
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 04:22:20 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19esNh-00059h-E1
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 04:20:21 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19esLN-0003lz-3v
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 04:17:57 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6M8HnSL025643;
	Tue, 22 Jul 2003 11:17:49 +0300
Received: from localhost (atsoukka@localhost)
	by silmu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6M8Hmkp025639; 
	Tue, 22 Jul 2003 11:17:49 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Tue, 22 Jul 2003 11:17:48 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
Subject: Re: [Gzz] Reformatting (reST) PEG available_overlays--hemppah
In-Reply-To: <1058855743.5190.15.camel@io.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307221101080.24325-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by silmu.st.jyu.fi id
	h6M8HnSL025643
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2003 08:22:27 -0000

22 Jul 2003, Hermanni Hyyti=E4l=E4 wrote:
> text right from the beginning of a writing process, or is it possible
> first to focus on a content and only then to formatting of a content in
> order to get all documents compiled correctly?

Oh, you've got a point here.

There exist some fatal misformattings, which breaks Docutils process and=20
result no a compiled document (e.g. html). Currently also Navidoc reacts=20
to these with exiting.

Some solutions:

1) Navidoc could be altered to continue processing the compilation queue
   till end, even if there were reST documents, which did not compile.

   Do we want this behavior overally more than the current?

2) Drafts could be saved without without the ".rst" postfix. Their=20
   compilation could still be tested with direct compilation:

   make naviloop RST=3D"doc/pegboard/foo--bar/peg.draft"
 =20
   But they won't be compiled with undirect compilation:

   make naviloop RST=3D"doc/pegboard/foo--bar/"

   Drafts under pegboard directories will also be shown on=20
   the pegboard as files of the pegs.=20

--=20
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 22 07:21:05 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19eutb-0001q7-3C
	for mharc-gzz-dev@gnu.org; Tue, 22 Jul 2003 07:01:27 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19euqm-0001Gg-Mp
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 06:58:32 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19euqD-00016q-I4
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 06:57:58 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19euZG-0007c8-VH
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 06:40:27 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6MAeNiM015909;
	Tue, 22 Jul 2003 13:40:23 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6MAfVFU027873;
	Tue, 22 Jul 2003 13:41:31 +0300 (EETDST)
Date: Tue, 22 Jul 2003 13:41:31 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: [Gzz] Reformatting (reST) PEG available_overlays--hemppah
Message-ID: <20030722104131.GD19765@tarzan.it.jyu.fi>
References: <1058855743.5190.15.camel@io.it.jyu.fi>
	<Pine.LNX.4.44.0307221101080.24325-100000@silmu.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307221101080.24325-100000@silmu.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.it.jyu.fi id
	h6MAeNiM015909
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Hermanni =?iso-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2003 11:01:24 -0000

On Tue, Jul 22, 2003 at 11:17:48AM +0300, Asko Soukka wrote:
> 22 Jul 2003, Hermanni Hyyti=E4l=E4 wrote:
> > text right from the beginning of a writing process, or is it possible
> > first to focus on a content and only then to formatting of a content =
in
> > order to get all documents compiled correctly?
>=20
> Oh, you've got a point here.
>=20
> There exist some fatal misformattings, which breaks Docutils process an=
d=20
> result no a compiled document (e.g. html). Currently also Navidoc react=
s=20
> to these with exiting.
>=20
> Some solutions:
>=20
> 1) Navidoc could be altered to continue processing the compilation queu=
e
>    till end, even if there were reST documents, which did not compile.
>=20
>    Do we want this behavior overally more than the current?

Yes, and a global error report to some log file.

> 2) Drafts could be saved without without the ".rst" postfix. Their=20
>    compilation could still be tested with direct compilation:
>=20
>    make naviloop RST=3D"doc/pegboard/foo--bar/peg.draft"
>  =20
>    But they won't be compiled with undirect compilation:
>=20
>    make naviloop RST=3D"doc/pegboard/foo--bar/"
>=20
>    Drafts under pegboard directories will also be shown on=20
>    the pegboard as files of the pegs.=20

I don't like this - drafts are going to be .rst and we want diffs between
drafts and final versions to work..

	Tuomas



From MAILER-DAEMON Tue Jul 22 08:54:57 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19ewed-0000oW-Ac
	for mharc-gzz-dev@gnu.org; Tue, 22 Jul 2003 08:54:07 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19eweZ-0000nQ-SH
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 08:54:03 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19eweY-0000mk-Ag
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 08:54:02 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19eweX-0000mF-Fb
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 22 Jul 2003 08:54:01 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6MCruiM023591
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 22 Jul 2003 15:53:56 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6MCt31P000221
	for gzz-dev@mail.freesoftware.fsf.org;
	Tue, 22 Jul 2003 15:55:03 +0300 (EETDST)
Date: Tue, 22 Jul 2003 15:55:03 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030722125503.GF19765@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] UMLLink poster paper sent
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2003 12:54:05 -0000

That's now taken care of, now to make the poster.

Hmm, maybe we could send it to Benja's hotel?

	Tuomas



From MAILER-DAEMON Thu Jul 24 19:44:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19fpl6-0002mz-E8
	for mharc-gzz-dev@gnu.org; Thu, 24 Jul 2003 19:44:28 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19fpka-00024N-S6
	for gzz-dev@nongnu.org; Thu, 24 Jul 2003 19:43:56 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19fpkC-00017C-Si
	for gzz-dev@nongnu.org; Thu, 24 Jul 2003 19:43:33 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.20) id 19fpjq-0000J3-Ga
	for gzz-dev@nongnu.org; Thu, 24 Jul 2003 19:43:10 -0400
Received: (qmail 15769 invoked by uid 65534); 24 Jul 2003 23:43:04 -0000
Received: from p5082D34D.dip.t-dialin.net (EHLO gmx.de) (80.130.211.77)
	by mail.gmx.net (mp025) with SMTP; 25 Jul 2003 01:43:04 +0200
Message-ID: <3F206EAC.7020503@gmx.de>
Date: Fri, 25 Jul 2003 01:41:32 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030704 Debian/1.4-1
X-Accept-Language: en
MIME-Version: 1.0
To: hemppah@cc.jyu.fi
References: <E19fcgD-0003Hg-DU@subversions.gnu.org>
In-Reply-To: <E19fcgD-0003Hg-DU@subversions.gnu.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: GZZ developers <gzz-dev@nongnu.org>, gzz-commits@nongnu.org
Subject: [Gzz] Re: [Gzz-commits] journals hemppah
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jul 2003 23:44:26 -0000


Hi,

Hermanni HyytiÃ¤lÃ¤ wrote:
> +    - Identity Based Cryptography
> +      - IBC has had much attention in cryptography domain very recently

I've read a bit about this recently, too.

> +      - a public key can be e.g. person's e-mail, ip-address etc

I.e. the point is: You have an *existing* identifier for a person, and 
want to use this identifier as their public key.

> +      - no more randomly generated keys

I'm not sure what the point is, here? The 'random' key resides with the 
Trusted Third Party.

> +      - no more certificate - key binding problems

I.e., a verifier doesn't need a way to obtain (and verify) a certificate 
for a given public key.

> +      - no more certificate revokations, revokation lists etc

Um, this simply means that you cannot revoke a key. Then, of course, you 
don't need CRLs either. You can also omit CRLs from a classic PKI if you 
don't think you need to revoke keys.

> +      - private keys are provided by a key server

I.e.: There is a single, central, trusted third party (TTP). To obtain a 
private key for <b.fallenstein@gmx.de>, I would authenticate myself to 
the TTP by proving that I'm really the owner of this address; the TTP 
would then generate my private key and send it to me.

The TTP is in the possession of a "master key," a private key that 
enables it to generate everybody else's private key. If this master key 
is exposed, all private keys would have to be invalidated and new 
private keys generated for everybody.

It's noteworthy that IBC has built-in key escrow: The TTP has (or can 
generate) the private key of every participant in the system.

> +      - looks promising w.r.t. Storm's pointer authentication

Why?

What do you intend to use as the public keys? (Email addresses or IPs or 
telephone numbers or domain names would not work, because they can 
change possession over time.)

- Benja




From MAILER-DAEMON Fri Jul 25 02:57:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19fwW1-0005YQ-6Y
	for mharc-gzz-dev@gnu.org; Fri, 25 Jul 2003 02:57:21 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19fwVX-0004zE-Du
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 02:56:51 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19fwVH-0004By-Og
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 02:56:36 -0400
Received: from itu.st.jyu.fi ([130.234.4.65])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19fwUl-0003aW-9e
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 02:56:03 -0400
Received: from itu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by itu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6P6txML023492;
	Fri, 25 Jul 2003 09:55:59 +0300
Received: from localhost (hastrup@localhost)
	by itu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6P6tuXQ023484;
	Fri, 25 Jul 2003 09:55:56 +0300
Date: Fri, 25 Jul 2003 09:55:56 +0300 (EEST)
From: Tuukka Hastrup <hastrup@itu.st.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: IBC (Re: [Gzz] Re: [Gzz-commits] journals hemppah)
In-Reply-To: <3F206EAC.7020503@gmx.de>
Message-ID: <Pine.LNX.4.44.0307250938360.22910-100000@itu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 06:57:19 -0000

On Fri, 25 Jul 2003, Benja Fallenstein wrote:

[on Identity Based Cryptography]

> > +      - no more certificate revokations, revokation lists etc
> 
> Um, this simply means that you cannot revoke a key. Then, of course, you 
> don't need CRLs either. You can also omit CRLs from a classic PKI if you 
> don't think you need to revoke keys.

When you revoke a key, aren't you telling "you're not supposed to use this 
public key anymore"? In IBC, you can include a time perioid in the 
identity. Doesn't that implicitly revoke the key after that time perioid?

> > +      - private keys are provided by a key server
> 
> It's noteworthy that IBC has built-in key escrow: The TTP has (or can 
> generate) the private key of every participant in the system.

You can distribute the trust among several TTP's: I guess the simplest 
would be to always encrypt several times, using different TTP's. It was 
also mentioned that the secret can be distributed so that no single TTP 
ever has the complete secret or any complete private key.

http://crypto.stanford.edu/ibe/

> > +      - looks promising w.r.t. Storm's pointer authentication

> What do you intend to use as the public keys? (Email addresses or IPs or 
> telephone numbers or domain names would not work, because they can 
> change possession over time.)

I don't know if this brainstorming is any use, but I could imagine some 
scheme where the identity and thus the public key is a Storm pointer name. 
Valid pointer blocks could only be issued with the secret key.


-- 
-- Trying to catch me? Just follow up my Electric Fingerprints
-- To help you: Tuukka.Hastrup@iki.fi
                http://www.iki.fi/Tuukka.Hastrup/
                IRCNet: Stugge/tuukkah @#pii,#fenfire,#ynna
                Jabber ID: tuukka@jabber.org, ICQ #11321669





From MAILER-DAEMON Fri Jul 25 03:22:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19fwtg-0007sA-A2
	for mharc-gzz-dev@gnu.org; Fri, 25 Jul 2003 03:21:48 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19fwtb-0007YZ-0b
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 03:21:43 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19fwtY-0007Pm-LS
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 03:21:40 -0400
Received: from posti2.jyu.fi ([130.234.4.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19fwtU-000777-If
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 03:21:36 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti2.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6P7LW0b010551; 
	Fri, 25 Jul 2003 10:21:32 +0300
Subject: Re: [Gzz] Re: [Gzz-commits] journals hemppah
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
In-Reply-To: <3F206EAC.7020503@gmx.de>
References: <E19fcgD-0003Hg-DU@subversions.gnu.org> <3F206EAC.7020503@gmx.de>
Content-Type: text/plain; charset=ISO-8859-1
Organization: 
Message-Id: <1059117691.11060.81.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 25 Jul 2003 10:21:32 +0300
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/)
	at posti2.jyu.fi; Fri, 25 Jul 2003 10:21:32 +0300
X-Spam-Checked: by miltrassassin
	at posti2.jyu.fi; Fri, 25 Jul 2003 10:21:33 +0300
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by posti2.jyu.fi id
	h6P7LW0b010551
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 07:21:46 -0000

On Fri, 2003-07-25 at 02:41, Benja Fallenstein wrote:
> Hi,
>=20
> Hermanni Hyyti=E4l=E4 wrote:
> > +    - Identity Based Cryptography
> > +      - IBC has had much attention in cryptography domain very recen=
tly
>=20
> I've read a bit about this recently, too.


Me too, i.e., couple of papers (however, I omitted proofs :)).


>=20
> > +      - a public key can be e.g. person's e-mail, ip-address etc
>=20
> I.e. the point is: You have an *existing* identifier for a person, and=20
> want to use this identifier as their public key.


True. Because of this requirement, I have a feeling that first
deployments based on IBC are mainly focused on business communications
between companies (as Voltage Security's procucts) because people have
identifiers assigned by a employer, i.e., e-mails.


>=20
> > +      - no more randomly generated keys
>=20
> I'm not sure what the point is, here? The 'random' key resides with the=
=20
> Trusted Third Party.


Ok, I meant random *looking* versus IBC's *less* random looking identier
(e.g., an e-mail).


>=20
> > +      - no more certificate - key binding problems
>=20
> I.e., a verifier doesn't need a way to obtain (and verify) a certificat=
e=20
> for a given public key.


True.


>=20
> > +      - no more certificate revokations, revokation lists etc
>=20
> Um, this simply means that you cannot revoke a key. Then, of course, yo=
u=20
> don't need CRLs either. You can also omit CRLs from a classic PKI if yo=
u=20
> don't think you need to revoke keys.

Ditto.

>=20
> > +      - private keys are provided by a key server
>=20
> I.e.: There is a single, central, trusted third party (TTP). To obtain =
a=20
> private key for <b.fallenstein@gmx.de>, I would authenticate myself to=20
> the TTP by proving that I'm really the owner of this address; the TTP=20
> would then generate my private key and send it to me.
>=20
> The TTP is in the possession of a "master key," a private key that=20
> enables it to generate everybody else's private key. If this master key=
=20
> is exposed, all private keys would have to be invalidated and new=20
> private keys generated for everybody.

> It's noteworthy that IBC has built-in key escrow: The TTP has (or can=20
> generate) the private key of every participant in the system.
>=20


Yes, the one you described is the original scheme my Boneh and Franklin.
However, Gentry and Silverberg
(http://camars.kaist.ac.kr/~ec/id_based/%5B7%5DHierIBE02.pdf) have
extended the original scheme to obtain a fully scalable hierarchical
ID-based encryption scheme: there is a hierarchical tree and upper level
of PKGs (Private Key Generator, as the authors call it) generate private
keys immediately below them in the hierarchy. In their proposal,
entity's ID is a tuple of IDs containing the ID of each of their
ancestors in the hierarchy (and, thus, could be used of signatures). The
two schemes are identical if there is only one level in a system.

Additionally, a paper by Boyen
(http://robotics.stanford.edu/%7Exb/crypto03/crypto03online.pdf)
proposes a practical scheme that combines (current and future) IB-based
signature and encryption algorithms in a practical way. Since the author
works for Voltage Security (at least author's e-mail suggests so;)) we
could imagine that this scheme has influenced somehow to Voltage
Security's products.

I plan to read Boyen's paper today more carefully.



> > +      - looks promising w.r.t. Storm's pointer authentication
>=20
> Why?

As said IBC looks, at first sight, promising: for instance, because of
PKI's lifecycle management/scalability issues (management of identity
binding issues &c) and the lack of offline use (AFAIK). OTOH, IBC can be
used anywhere (even offline) and it's appears to be more simple than
PKI. Thus, IBC seems to suit well in a dynamic systems (e.g. a P2P
network).


>=20
> What do you intend to use as the public keys? (Email addresses or IPs o=
r=20
> telephone numbers or domain names would not work, because they can=20
> change possession over time.)

A tuple of IDs (as described above).



-Hermanni




From MAILER-DAEMON Fri Jul 25 04:12:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19fxgd-0005Qh-KI
	for mharc-gzz-dev@gnu.org; Fri, 25 Jul 2003 04:12:23 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19fxfu-00058D-Oe
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 04:11:38 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19fxfN-00050g-3p
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 04:11:05 -0400
Received: from posti2.jyu.fi ([130.234.4.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19fxPE-0001Tz-Ty
	for gzz-dev@nongnu.org; Fri, 25 Jul 2003 03:54:25 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti2.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6P7s90b017849; 
	Fri, 25 Jul 2003 10:54:09 +0300
Subject: Re: IBC (Re: [Gzz] Re: [Gzz-commits] journals hemppah)
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Tuukka Hastrup <hastrup@cc.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307250938360.22910-100000@itu.st.jyu.fi>
References: <Pine.LNX.4.44.0307250938360.22910-100000@itu.st.jyu.fi>
Content-Type: text/plain
Organization: 
Message-Id: <1059119649.11051.107.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 25 Jul 2003 10:54:09 +0300
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/)
	at posti2.jyu.fi; Fri, 25 Jul 2003 10:54:09 +0300
X-Spam-Checked: by miltrassassin
	at posti2.jyu.fi; Fri, 25 Jul 2003 10:54:10 +0300
Cc: GZZ developers <gzz-dev@nongnu.org>,
	Benja Fallenstein <b.fallenstein@gmx.de>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 08:12:21 -0000

On Fri, 2003-07-25 at 09:55, Tuukka Hastrup wrote:
> On Fri, 25 Jul 2003, Benja Fallenstein wrote:
> 
> [on Identity Based Cryptography]
> 
> > > +      - no more certificate revokations, revokation lists etc
> > 
> > Um, this simply means that you cannot revoke a key. Then, of course, you 
> > don't need CRLs either. You can also omit CRLs from a classic PKI if you 
> > don't think you need to revoke keys.
> 
> When you revoke a key, aren't you telling "you're not supposed to use this 
> public key anymore"? In IBC, you can include a time perioid in the 
> identity. Doesn't that implicitly revoke the key after that time perioid?


Yes. Additional property of IBC is that Alice can send a message to Bob
*before* Bob has ever acquired his private key.


> 
> > > +      - private keys are provided by a key server
> > 
> > It's noteworthy that IBC has built-in key escrow: The TTP has (or can 
> > generate) the private key of every participant in the system.

True: for the original Boneh-Franklin scheme.
Not true: in general case (see my previous mail about hierarchical
IB-based system) ;).

> 
> You can distribute the trust among several TTP's: I guess the simplest 
> would be to always encrypt several times, using different TTP's. It was 
> also mentioned that the secret can be distributed so that no single TTP 
> ever has the complete secret or any complete private key.
> 
> http://crypto.stanford.edu/ibe/

More efficient approach would be the use of erasure code (or similar
approaches): a block (a key) is divided into m identically-sized
fragments, which are then encoded into n fragments (where n > m). Now,
the original block (the key) can be reconstructed from any m fragments,
depending on the quantity r = m/n ( < 1).

Anyhow, I think the hierarchical IBC scheme is still more scalable than
a scheme based on erasure codes.

> 
> > > +      - looks promising w.r.t. Storm's pointer authentication
> 
> > What do you intend to use as the public keys? (Email addresses or IPs or 
> > telephone numbers or domain names would not work, because they can 
> > change possession over time.)
> 
> I don't know if this brainstorming is any use, but I could imagine some 
> scheme where the identity and thus the public key is a Storm pointer name. 
> Valid pointer blocks could only be issued with the secret key.

Hm, I'm not sure this would work right with IBC since the key idea
behind the IBC is that public key is a valid, "real life", identifier
that is directly related to an entity (i.e. a person). With Storm,
anybody (AFAIK) is able to create pointers as much as one wants. Thus,
the possession rate of identifier could be very high and the use of a
pointer for identifying an entity may be flawed.



-Hermanni





From MAILER-DAEMON Fri Jul 25 05:18:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19fyiN-00024b-0L
	for mharc-gzz-dev@gnu.org; Fri, 25 Jul 2003 05:18:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19fyiK-000213-B4
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 05:18:12 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19fyiI-000205-Vj
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 05:18:11 -0400
Received: from itu.st.jyu.fi ([130.234.4.65])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19fyhT-0001h9-UA
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 05:17:20 -0400
Received: from itu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by itu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6P9HCML030416
	for <gzz-dev@mail.freesoftware.fsf.org>; Fri, 25 Jul 2003 12:17:12 +0300
Received: from localhost (hastrup@localhost)
	by itu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6P9HCg6030412
	for <gzz-dev@mail.freesoftware.fsf.org>; Fri, 25 Jul 2003 12:17:12 +0300
X-Authentication-Warning: itu.st.jyu.fi: hastrup owned process doing -bs
Date: Fri, 25 Jul 2003 12:17:11 +0300 (EEST)
From: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>
X-X-Sender: hastrup@itu.st.jyu.fi
To: gzz-dev@mail.freesoftware.fsf.org
Message-ID: <Pine.LNX.4.44.0307251210361.22910-100000@itu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: [Gzz] Not around next week
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 09:18:13 -0000


I worked double days this week (8h/day), so won't be available much next 
week.

I added write permission for group staff-www to ~wiki/wikipasswrds, so you 
should be able to add new accounts with htpasswd on himalia.

-- 
-- Trying to catch me? Just follow up my Electric Fingerprints
-- To help you: Tuukka.Hastrup@iki.fi
                http://www.iki.fi/Tuukka.Hastrup/
                IRCNet: Stugge/tuukkah @#pii,#fenfire,#ynna
                Jabber ID: tuukka@jabber.org, ICQ #11321669




From MAILER-DAEMON Fri Jul 25 13:58:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19g6oC-0004c8-RQ
	for mharc-gzz-dev@gnu.org; Fri, 25 Jul 2003 13:56:48 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19g6nw-0004Vy-0x
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 13:56:32 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19g6my-00042G-Gc
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 13:55:33 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19g6mk-0003Dc-1u
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 13:55:18 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6PHtCJg029134
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Fri, 25 Jul 2003 20:55:12 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6PHuRkp002369
	for gzz-dev@mail.freesoftware.fsf.org;
	Fri, 25 Jul 2003 20:56:27 +0300 (EETDST)
Date: Fri, 25 Jul 2003 20:56:27 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030725175627.GA2359@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] [Lloyd.Rutledge@cwi.nl: More Hypertext 2003 poster and demo
	information]
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 17:56:46 -0000

----- Forwarded message from Lloyd Rutledge <Lloyd.Rutledge@cwi.nl> -----

To: Scarano Vittorio <vitsca@dia.unisa.it>, Tim Wong <thwong@ucdavis.edu>,
	James Ohene-Djan <j.djan@gold.ac.uk>, Cesare Rocchi <rocchi@itc.it>,
	Kumiyo Nakakoji <kumiyo@kid.rcast.u-tokyo.ac.jp>,
	Yasuhiro Yamamoto <yxy@acm.org>, Atsushi Aoki <aoki@sra.co.jp>,
	Jean-Yves.Delort@lip6.fr, Licia Calvi <licalvi@unipv.it>,
	David Gibson <davgib@us.ibm.com>,
	Matthew Gorle <m.gorle@gold.ac.uk>, Roberto.Fresco@isti.cnr.it,
	Oreste.Signore@isti.cnr.it, Luisa.Marucci@isti.cnr.it,
	Mirjana Andric <ma00r@ecs.soton.ac.uk>,
	Wendy Hall <wh@ecs.soton.ac.uk>, Leslie Carr <lac@ecs.soton.ac.uk>,
	mira@computer.org, Mark Truran <mat@cs.nott.ac.uk>,
	Helen Ashman <hla@cs.nott.ac.uk>, Tuomas Lukka <lukka@mit.jyu.fi>,
	Benja Fallenstein <b.fallenstein@gmx.de>,
	Jeffrey A Lasky <jal@it.rit.edu>, Andy Edmonds <andy@uzilla.net>,
	Irene Wong-Bushby <dvsd@mail.ptd.net>, hiltz@njit.edu,
	turoff@njit.edu, Yolaine.Bourda@supelec.fr,
	Cedric.Jacquiot@supelec.fr, liebhart@ict.tuwien.ac.at,
	Juergen Falb <falbj@ict.tuwien.ac.at>,
	Robert Smeikal <smeikal@ict.tuwien.ac.at>,
	"Karl M. Goeschka" <goeschka@ict.tuwien.ac.at>,
	Sasaki Nobuyuki <sasaki@ice.gunma-ct.ac.jp>,
	Andrea Andrenucci <andrea@dsv.su.se>, mehler@uni-trier.de,
	Siegfried Reich <sreich@salzburgresearch.at>,
	Ng S T Chong <ngstc@unu.edu>, jeremy@xanadu.net,
	jeremyalansmith@freeola.com, c0257599@frodo.hud.ac.uk,
	Robert Lisek <robertl@pwn.pl>, Robert Lisek <lisek@lisek.art.pl>,
	Michael Bieber <bieber@oak.njit.edu>
Cc: Lynda.Hardman@cwi.nl
Subject: More Hypertext 2003 poster and demo information
Date: Fri, 25 Jul 2003 19:02:06 +0200
From: Lloyd Rutledge <Lloyd.Rutledge@cwi.nl>
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi


Dear Hypertext 2003 Poster and Demo Presenters,

Below are more details about the posters and demos which hopefully
answer the remaining questions some of you have.

Posters will be up for the duration of the main conference, Wednesday
to Friday inclusive. They should be put up Tuesday evening or
Wednesday morning, and taken down Friday afternoon.  The posters will
always be up during the conference for attendees to see.  They will
browse the posters and demos during the coffee and lunch breaks.  The
conference organizers are currently determining if and when there will
be a special poster session.

The conference will have wireless access.  Therefore, demos can use
this wireless network if access to the Internet is required for them.
There will be no phone lines provided for demos since they are
expensive to arrange, financially risky to leave open, and wireless
performance is much better anyway.

As said, electricity will be provided for the demos.  This is, of
course UK electricity, so you if you don't have UK equipment, you will
need to bring power adapters.  You will be expected to show your demos
running your own computers and monitors, as these are also expensive
to provide.  Typically, demo presenters come with laptops, run the
demos on the laptops, and show them on the laptop screen.  Of course,
the conference's wireless can be accessed from these laptops.  You can
bring a desktop computer and/or a monitor, but you will be responsible
for transporting and securing such equipment, as will any and all
equipment you bring.

After Monday, I leave for a three week vacation, coming back in the
office on Tuesday, August 19th.  If you have any questions during this
time, please send them to General Chair Helen Ashman
<hla@cs.nott.ac.uk> or Program Co-chair Lynda Hardman
<Lynda.Hardman@cwi.nl>, and polease cc them to me so I can catch up
when returning.

Looking forward to a successful and fun poster and demo track,
Lloyd

--
Lloyd Rutledge  vox: +31 20 592 40 93       fax: +31 20 592 43 12
CWI             net: Lloyd.Rutledge@cwi.nl  Web: http://www.cwi.nl/~lloyd
Post:   PO Box 94079    |  NL-1090 GB Amsterdam  |  The Netherlands
Street: Kruislaan 413/C |  NL-1098 SJ Amsterdam  |  The Netherlands

----- End forwarded message -----



From MAILER-DAEMON Fri Jul 25 13:59:48 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19g6r6-0006fr-2w
	for mharc-gzz-dev@gnu.org; Fri, 25 Jul 2003 13:59:48 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19g6qm-0005k9-LK
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 13:59:28 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19g6pt-0005A4-6E
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 13:58:33 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19g6oo-0004jt-W9
	for gzz-dev@mail.freesoftware.fsf.org; Fri, 25 Jul 2003 13:57:27 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6PHvPJg029291
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Fri, 25 Jul 2003 20:57:25 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6PHwfSO002412
	for gzz-dev@mail.freesoftware.fsf.org;
	Fri, 25 Jul 2003 20:58:41 +0300 (EETDST)
Date: Fri, 25 Jul 2003 20:58:41 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030725175841.GB2359@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] [Lloyd.Rutledge@cwi.nl: Re: Your Hypertext Short Paper
	submission invited as Poster]
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Jul 2003 17:59:46 -0000

----- Forwarded message from Lloyd Rutledge <Lloyd.Rutledge@cwi.nl> -----

To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: Your Hypertext Short Paper submission invited as Poster 
In-reply-to: Your message of "Tue, 22 Jul 2003 15:38:59 +0300."
             <20030722123858.GE19765@tarzan.it.jyu.fi> 
Date: Thu, 24 Jul 2003 17:42:25 +0200
From: Lloyd Rutledge <Lloyd.Rutledge@cwi.nl>
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi


Tuomas,

Thank, I have received your materials.

See you at the conference,
Lloyd

On Tue, Jul 22 2003 Tuomas Lukka wrote:

> On Sat, Jul 05, 2003 at 04:12:50PM +0200, Lloyd Rutledge wrote:
> > 2) An abstract for the Website and conference handout (due July 23rd)
> 
> Here:
> 
> 	We present a navigational aid for documentation used in software
> 	development. Based on using human-made UML diagrams as
> 	multi-ended links, we hypertextually connect two distinct areas
> 	of documentation: design documents and
> 	documentation embedded in the program code, such as Javadoc.
> 
> 
> > 3) Two pages for the Website (due July 23rd)
> 
> Attached
> 
> 	Tuomas

--
Lloyd Rutledge  vox: +31 20 592 40 93       fax: +31 20 592 43 12
CWI             net: Lloyd.Rutledge@cwi.nl  Web: http://www.cwi.nl/~lloyd
Post:   PO Box 94079   |  NL-1090 GB Amsterdam  |  The Netherlands
Street: Kruislaan 413  |  NL-1098 SJ Amsterdam  |  The Netherlands

----- End forwarded message -----



From MAILER-DAEMON Mon Jul 28 02:26:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h1T5-0000Fk-3b
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 02:26:47 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h1SW-0007yL-Or
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 02:26:12 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h1SG-0007fM-L6
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 02:25:57 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h1RS-0007Rm-Ly
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 02:25:06 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6S6P0Jg003189
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 28 Jul 2003 09:25:00 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6S6P4Gc018562
	for gzz-dev@mail.freesoftware.fsf.org;
	Mon, 28 Jul 2003 09:25:04 +0300 (EETDST)
Date: Mon, 28 Jul 2003 09:25:04 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030728062504.GA18549@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] [hla@Cs.Nott.AC.UK: JoDI cfp: Future Visions of Common-use
	Hypertext]
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 06:26:44 -0000

----- Forwarded message from hla@Cs.Nott.AC.UK -----

Date:     Sun, 27 Jul 2003 16:03:18 BST
From: hla@Cs.Nott.AC.UK
Subject:  JoDI cfp: Future Visions of Common-use Hypertext
To: lukka@iki.fi
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi

You have received this message as a registered user of the Journal of 
Digital Information.

Call for Papers

Journal of Digital Information announces a Special Issue on
Future Visions of Common-use Hypertext

*linked to a panel session at ACM Hypertext '03
See http://www.ht03.org/panels.html

Special issue Editors: Helen Ashman and Adam Moore, University of Nottingham

Submission deadline: 18 September 2003
Publication: November 2003

Submissions are sought for a special issue for the Hypermedia Systems theme
of JoDI on visions of the future of 'common use' hypertext. This special
issue is linked to a panel session at ACM Hypertext '03, where alternative
digital futures incorporating hypertext as a primary mechanism will be
discussed by a panel of experts.

The Web has been the dominant public perception of hypertext for over 10
years now. There are, of course, many other hypertext systems, that could
augment, live alongside, or even completely replace the Web. The aim of
this special issue, and of the related panel discussion, is to investigate
the viability of these alternative systems, and to consider how their
everyday use can simplify the processes of reading and writing,
understanding and thinking in the working and recreational activities of
large numbers of people.

Submissions to the special issue should firstly describe the system or
concept that the author proposes for everyday hypertext use, and outline
the benefits they will bring to large sections of the population,
discussing where would they be deployed, how would they be used, and by
whom. These systems or concepts could include complete alternative
hypertext management systems, scenarios for using hypermedia in ways that
have a radical effect on some everyday activity (such as reading, writing,
learning, imagining) or could comprise supplementary technologies for the
Web, (such as addressing, searching, retrieving, authoring, or any other
core technology of an everyday hypertext system).

The remainder of the paper should then address the more speculative
questions such as: with virtually unlimited resources, how should the
vision of interconnected information, embodied by the hypertext system or
concept, be realised over the next ten years? What technologies would be
used? Would they be built on any existing infrastructure, and how far back
would there be any useful foundations for a useful point to start again?
What long-term impact on work and recreation could be expected from these
changes?

The primary characteristic of the system or concept in your submission
should be that "one day, everyone will do it this way".

There is no fixed length for submissions. Papers will be reviewed by at
least one member of the conference panel discussion group together with
other selected referees. Authors of accepted papers will be able to modify
their papers, with final versions of papers due by 6th November.

Submission

Authors should submit their papers electronically using the submission form
http://jodi.ecs.soton.ac.uk/form.php3
Selecting the title or editor for this issue from the Theme or Editor
drop-down box will alert the editor to your submission automatically.
Before submitting please take note of the journal's Guidelines for
Submission: Notes for Authors
http://jodi.ecs.soton.ac.uk/sec.php3?content=submit

Authors who wish to submit a paper with unusual features are requested to
contact the Special issue Editor prior to submission. Please send any
queries on the special issue or on the Hypermedia Systems theme to Helen
Ashman, hla@cs.nott.ac.uk.

A copy of this call can be found at
http://jodi.ecs.soton.ac.uk/calls/future-ht.html

The Journal of Digital Information is an electronic journal published only
via the Web. JoDI is currently free to all users thanks to support from the
British Computer Society and Oxford University Press.
http://jodi.ecs.soton.ac.uk/

----- End forwarded message -----



From MAILER-DAEMON Mon Jul 28 02:47:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h1kw-0007Od-Iv
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 02:45:14 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h1ko-00077s-Bn
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 02:45:06 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h1kk-00071P-Ec
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 02:45:02 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h1kf-0006vy-9N
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 02:44:57 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6S6itJg004633
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 28 Jul 2003 09:44:55 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6S6j0gh018793
	for gzz-dev@mail.freesoftware.fsf.org;
	Mon, 28 Jul 2003 09:45:00 +0300 (EETDST)
Date: Mon, 28 Jul 2003 09:45:00 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030728064500.GB18549@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] Back at work
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 06:45:12 -0000

I agreed with Kirsti that I'll take the rest of the holiday
(3 days) on sunny days - today there's too much risk of rain here.

So I'm back at work.

I've decided that my first effort will be to specify FenPDF officially.
This means that I'll PEG a detailed system, including UI and structure,
and all changes to the UI *must* go through the PEG process
for the official FenPDF.

Note that this does not preclude trying out things: the idea would be to make
the system modular and easily assembled from the components in Jython
so that everyone can also have their own version with their own 
functions.

The first draft will be extremely conservative, leaving out some of
the latest proposed ideas (like tool switching &c) just to get a stable
baseline.

The idea is that from now on, we'll always have *the* official version
that *has* to work in a particular way, and then a wealth of testing 
versions that can do anything.

If anyone has any things that I need to take care of, please put them
in my journal.

	Tuomas



From MAILER-DAEMON Mon Jul 28 03:02:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h20r-0000vb-9f
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 03:01:41 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h20j-0000qN-3O
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 03:01:33 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h20Z-0000T3-9l
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 03:01:23 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h20P-0008O2-Vu
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 03:01:14 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6S71BJg005335
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 28 Jul 2003 10:01:11 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6S71GRt018949
	for gzz-dev@mail.freesoftware.fsf.org;
	Mon, 28 Jul 2003 10:01:16 +0300 (EETDST)
Date: Mon, 28 Jul 2003 10:01:16 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030728070116.GC18549@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] Repost PEGs, please
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 07:01:39 -0000

Please repost all PEGs I need to look at - I may well have
deleted some with spam.

In any case, if you don't see a response about a PEG, please 
just go ahead and repost it.

	Tuomas



From MAILER-DAEMON Mon Jul 28 03:17:42 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h2Fx-00014A-2P
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 03:17:17 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h2Fq-0000e7-Li
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 03:17:10 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h2Fg-0000Hr-Gc
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 03:17:00 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h2Fd-00008Y-PW
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 03:16:57 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6S7GsJg006639
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 28 Jul 2003 10:16:54 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6S7Gxe7019038
	for gzz-dev@mail.freesoftware.fsf.org;
	Mon, 28 Jul 2003 10:16:59 +0300 (EETDST)
Date: Mon, 28 Jul 2003 10:16:59 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030728071659.GE18549@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] Lava, coordsyscache
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 07:17:15 -0000

I just noticed an alarming thing:


~/cvs/fenfire$ gj CoordsysCac
./org/fenfire/util/lava/CoordsysCache.java:public class CoordsysCache {
./org/fenfire/util/lava/CoordsysCache.java:    private void p(String s) { System.out.println("CoordsysCache:"+this+": "+s); }
./org/fenfire/view/CanvasView2D.java:    private CoordsysCache coords = new CoordsysCache();
./org/fenfire/view/AreaSelectingView2D.java:    private CoordsysCache coords = new CoordsysCache();

Some lava code implementing an unaccepted PEG is being used in the 
non-lava part; I understand that it's a pretty important thing to have
the fast animation but it also means that we should all do our best
to resolve the situation. Code like that should feel like a stone in your
shoe until it's either officialized or done some other way.

I still don't even understand the need for CoordsysCache, could you please
explain it once again, mudyc? I know it must be annoying to have to explain
it in so much detail but I think it's pretty important that I understand
what it is and why, right?

	Tuomas



From MAILER-DAEMON Mon Jul 28 04:38:32 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h3WG-0008TK-Gx
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 04:38:12 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h3VC-0007Yj-FK
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 04:37:06 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h3Ui-0007LY-FX
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 04:36:37 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h3TB-0006ZI-Ds
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 04:35:01 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6S8YxJg011050
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Mon, 28 Jul 2003 11:34:59 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6S8Z4v4019656
	for gzz-dev@mail.freesoftware.fsf.org;
	Mon, 28 Jul 2003 11:35:04 +0300 (EETDST)
Date: Mon, 28 Jul 2003 11:35:04 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030728083504.GF18549@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] PEG: lava_rules
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 08:38:10 -0000

=============================================================
PEG lava_rules--tjl: Coding rules w.r.t. lava
=============================================================

:Author:   Tuomas J. Lukka
:Last-Modified: $Date: 2003/07/28 08:33:33 $
:Revision: $Revision: 1.2 $
:Status:   Current

There is still some vagueness about lava and its use.
Let's codify the basic rules.

Issues
======

Changes
=======

The rules for lava/ directories in all fenfire subprojects:
These shall be added to the CODING rules.

1) Lava is the place for free experimentation. Anyone may add anything
   to lava/ directories. However, of course it is expected that people
   are polite towards other peoples' lava/ experiments, not deleting code
   without asking on gzz-dev first &c. However, there are no fixed rules
   about what goes into lava, except for the normal license ones.

2) Non-lava code should *never* reference lava code.

3) Non-lava code **MUST NEVER** import lava classes. All references shall
   be fully qualified.

   Exceptions to 2) will sometimes happen to implement / test something,
   and are not absolutely forbidden. However, they are strongly discouraged
   and should stand out in code and be easily greppable.
   This **ABSOLUTE** rule will make it so.

   Instead of ::
   
	import org.nongnu.libvob.lava.placeable.Placeable;
	...
	...
		Placeable p = (Placeable)nodeView.f(fen.constgraph, node);

    or even the more horrible ::

	import org.nongnu.libvob.lava.placeable.*;
	...

    the following code **MUST** be used ::

		org.nongnu.libvob.lava.placeable.Placeable p = 
			(org.nongnu.libvob.lava.placeable.Placeable)nodeView.f(fen.constgraph, node);

    i.e. no imports.

    The same applies to python code, where the appropriate imports would 
    be ::

	from org import fenfire as ff
	import vob

    and then the reference above would be

	vob.lava.placeable.Placeable

    so that the "lava" part of the class name is always included.



From MAILER-DAEMON Mon Jul 28 09:08:14 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h7j3-0001l9-1b
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 09:07:41 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h7in-0001Ze-DF
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:07:25 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h7if-0001Rq-7E
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:07:19 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19h7hI-0000gs-Fy
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:05:52 -0400
Received: (qmail 12660 invoked by uid 65534); 28 Jul 2003 13:05:15 -0000
Received: from pD95886AA.dip.t-dialin.net (EHLO gmx.de) (217.88.134.170)
	by mail.gmx.net (mp016) with SMTP; 28 Jul 2003 15:05:15 +0200
Message-ID: <3F251F21.5080500@gmx.de>
Date: Mon, 28 Jul 2003 15:03:29 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] UMLLink poster paper sent
References: <20030722125503.GF19765@tarzan.it.jyu.fi>
In-Reply-To: <20030722125503.GF19765@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 13:07:39 -0000


Hi,

Tuomas Lukka wrote:
> That's now taken care of, now to make the poster.

I notice it's still not ready so I cannot take it to a print shop.

> Hmm, maybe we could send it to Benja's hotel?

This'll be a busy week because it's the last in Germany and I have to 
prepare my move. So I would appreciate if I didn't have to print the poster.

I don't know how fast post to Morocco is; I'll be living with friends 
there, so it wouldn't be a problem to store it there. I'll be there till 
August 23rd/morning of August 24th at least. I can send you the street 
address if required.

In Nottingham I'll use the on-campus accomodation. I've no idea whether 
we can send something there and have them store it for me, though it 
would certainly be the most convenient and safe option for us.

-b




From MAILER-DAEMON Mon Jul 28 09:10:04 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h7jn-0002UA-G3
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 09:08:27 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h7jX-0002EG-Qn
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:08:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h7j9-0001rW-Bf
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:07:50 -0400
Received: from posti1.jyu.fi ([130.234.4.32])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h7iP-0001DC-Vv
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:07:02 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti1.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6SD6xAD006084
	for <gzz-dev@mail.freesoftware.fsf.org>; Mon, 28 Jul 2003 16:06:59 +0300
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Content-Type: text/plain; charset=ISO-8859-1
Organization: 
Message-Id: <1059397618.15013.9.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 28 Jul 2003 16:06:59 +0300
X-Virus-Scanned: by amavisd-milter (http://amavis.org/)
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by posti1.jyu.fi id
	h6SD6xAD006084
Cc: 
Subject: [Gzz] PEG: Available overlays
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 13:08:19 -0000

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
PEG available_overlays--hemppah: Available overlays
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

:Authors:  Hermanni Hyyti=E4l=E4
:Date-Created: 2003-06-18
:Last-Modified: $Date: 2003/07/28 09:10:55 $
:Revision: $Revision: 1.29 $
:Status:   Incomplete

.. :Stakeholders:
.. :Scope:    Major|Minor|Trivial|Cosmetic
.. :Type:     META|Policy|Architecture|Interface|Implementation

.. Affect-PEGs:

The purpose of this PEG document is to give a short overview of existing
structured
P2P overlays which have an open source implementation.=20

The reason for creating this PEG document is that the current
implementation=20
of GISP [5]_ seems to have (too) many obvious security exploits.
Therefore we need=20
to examine other available structured overlays which have an open source
implementation in hope for finding a more mature P2P platform.=20

The list of implemented overlays is as of July 2003.

Issues
=3D=3D=3D=3D=3D=3D

None.

Terminology
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

This section briefly covers the terminology used in this document.=20

Abstractions
    The following text for the abstraction definitions is taken from=20
    `Towards a Common API for Structured P2P Overlays`_ by Frank Dabek
et al.

.. _DHT:=20

    DHT
        The DHT abstraction provides the same functionality as a=20
        traditional hashtable, by storing the mapping between a
        key and a value. This interface implements a simple store
        and retrieve functionality, where the value is always stored
        at the live overlay node(s) to which the key is mapped by
        the KBR layer. Values can be objects of any type. For ex-ample,
the DHT=20
        implemented as part of the DHash inter-face in CFS stores=20
        and retrieves single disk blocks by their content-hashed keys.

.. _DOLR:

    DOLR
        The DOLR abstraction provides a decentralized direc-tory
        service. Each object replica (or endpoint) has an
        objectID and may be placed anywhere within the system.
        Applications announce the presence of endpoints by pub-lishing
        their locations. A client message addressed with
        a particular objectID will be delivered to a nearby end-point
        with this name. Note that the underlying distributed
        directory can be implemented by annotating trees associ-ated
        with each objectID; other implementations are pos-sible.
        One might ask why DOLR is not implemented on
        top of a DHT, with data pointers stored as values; this is
        not possible because a DOLR routes messages to the near-est
        available endpoint providing a locality property not
        supported by DHTs. An integral part of this process is the
        maintenance of the distributed directory during changes
        to the underlying nodes or links.

Redundancy
    What techniques are used for redundancy    =20

Fault tolerance against hostile nodes
    What techniques are used against hostile nodes   =20

Activity of development
    How actively a software is being developed.

Developer
    Who is developing a software.

Language
    What programming language is used to program a software + additional
    software packages which are required.

License
    Under what license a software is distributed.

Other notes
    Other miscellaneous notes.

Implemented overlays
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D

In this section we list the structured P2P overlays which have an open
source
implementation. Please notice that features described for each
implementation=20
are deliberately kept as short as possible. For more depth information=20
the overlays we suggest reading the original publications.

Chord [1]_
----------

Abstraction
    DHT_/DOLR_

Redundancy
    Replication, backup links.

Fault tolerance against hostile nodes
    (undefined)

Activity of development
    Quite high.

    According to the Chord [1]_ website:

        At this point no official release for=20
        Chord is available, but you are welcome to check out the latest
version=20
        from the CVS repository. This version is experimental, under
active=20
        development, and may frequently be broken.

Developer
    MIT (research community)

Language
    C++ (GCC 2.95, not 2.96, although 3.x should work)

Additional requirements
    * Self-certifying File System (http://sfs.net)
    * autoconf, automake, etc.
    * Berkeley DB 3.X=20

License
    BSD-like

Other notes
    No support for network locality- do not take network latencies into
account
    when building neighbor links.

    Includes a Chord [1]_ simulator.
   =20

Tapestry [2]_
--------------

Abstraction
    DOLR_

Redundancy
    According to `Tapestry: A Resilient Global-scale Overlay for Service
    Deployment`_:

        Tapestry is highly resilient under dynamic conditions,
        providing a near optimal success rate for requests
        under high churn rates, and quicly recovering from
        massive membership events in under a minute.
   =20
    According to the Tapestry [2]_ website:

        Tapestry offers fault-resilient mechanisms for both object=20
        location and point to point message delivery.  For object
location,=20
        Tapestry generates a small number of deterministic and
independent=20
        GUIDs for each object.  An object server publishes an object's=20
        availability on all of its GUIDs, and a client issues Tapestry
locate=20
        requests for all of the object GUIDs in parallel.  This greatly=20
        increases availability under fault conditions, while improving=20
        general performance and reducing performance variability.  For
point=20
        to point message delivery, Tapestry provides pre-calculated
backup=20
        routes at each overlay hop.  UDP soft-state beacons measure
up-to-date=20
        link conditions. Tapestry uses such information and simple
fault-avoidance=20
        protocols to route messages around failures, providing
successful=20
        delivery with high probability if a path between the endpoints
exists.

   =20
Fault tolerance against hostile nodes
    * PKI is used while creating node identifiers
    * MACs are used to maintain integrity of overlay traffic
    * Monitoring system for maintaining neighbor links

Activity of development
    Active.

    Tapestry  1.0 (April 2002)

    According to the Tapestry [2]_ website::

        Tapestry Version 1.0 contains the following functionality:

        * Basic Tapestry Java code running on the SEDA stage-driven
event model
        * Tapestry node insertion
              o Using a static configuration built from configuration
files
              o Using the dynamic iterative insertion of single nodes to
existing=20
                Tapestry networks
        * Support for multiple backup links per route entry
        * Object location
              o Object publication with optional tags
              o Object location with optional tags
              o TapestryFailure messages returned upon the failure of a=20
                TapestryLocateMsg
        * Message routing
              o Routing messages to an exact GUID match
              o Routing messages to the node closest in ID to a given
GUID
        * An initial self-optimizing componentthat monitors link
conditions to=20
          decide when to use backup routes  =20
     =20
     =20
     According to the Tapestry [2]_ website, Tapestry Version 2.0
contains the=20
     following new functionality::

        * Algorithms for adapting to changing network conditions
              o API messages allowing the application to tell the local
node=20
                to enter or leave a Tapestry overlay
              o Recovery algorithms to large scale failures in the
network
              o A resilient parallel insertion algorithm that supported
large flash=20
               crowds adding themselves to the overlay
        * Patchwork: a soft-state network monitoring component that uses
          soft-state beacons to monitor link quality to a node's
neighbors.=20
          As link qualities change, nodes can be replaced by backups in
the=20
          routing table in order to reduce packet loss in overlay
routing.
        * A distributed testing framework: nodes can set themselves to
be=20
          configured as FullTestMember nodes, and await explicit control
          instructions from a central FullTestDriver node. Instructions
are=20
          sent via FullTestMsg messages, and include join, leave,
publish,=20
          routeToObject and routeToNode operations. The results and
resulting=20
          latencies are returned to the FullTestDriver.
        * Interweave: a simple file sharing application
        * Shuttle: a decentralized instant messaging protocol=20

Developer
    University of Berkeley (research community)

Language
    Java (Sun JDK 1.3 or a compatible Java Development and Runtime
environment).
    The Java interface libraries for the BerkeleyDB database=20

Additional requirements
    * The Cryptix JCE library (included with the 2.0 release)
    * UNIX make program
    * The Java interface libraries for the BerkeleyDB database=20
      (included with the 2.0 release)=20
   =20
License
    BSD-like

Other notes
    Support for network locality when building neighbor links.

    Why Oceanstore_ uses Tapestry [2]_?=20
    See http://www.oceanstore.org/info/whytapestry.html=20

Kademlia [3]_
-------------

Abstraction
    DHT_

Redundancy
    No simulation or test results published (not even in the original
publication)
    In *theory*, however, the "free-choice" feature
    gives peers freedom to adapt different conditions. However, the
    author of SharkyPy says:
   =20
        Kademlia has (in my taste, that's why I decided to drop it) a
bad
	hole which makes it's use in remote querying for packets pretty
useless:
	When you have key->value mappings, which have an equal key, in even in
	semi-large networks it gets very unprobable that you get all mappings,
	the more hosts there are, the less probable it is, and the more
mappings
	there are, the less probable it is too. I've tried to remedy this in a
	later implementation, at the cost of lookup speed, but have never
	managed to get all entries when the network had over 100 nodes. (the
	later implementation is based on my own server-framework and uses no
	threads, btw.) This made it unusable for me, as basically I basically
	had to change the lookup-algorithm to query all nodes (back to
gnutella,
	then...), to get all answers. And that's what is important in the
	network I designed it for.


Fault tolerance against hostile nodes
    Nothing said, expect the "free-choice" feature.=20

Activity of development
    Java development discontinued, C++ version
    is under development.

Developer
    New York University (research community).

Language
    Java (Sun JDK 1.3 or a compatible Java Development and Runtime
environment (?))

License
    GPL (Java), "Free for non-commercial use" (C++)

Other notes
    The implementation of the Java version is discontinued.=20

Pastry [4]_
-----------

Abstraction
    DHT_

Redundancy
   Backup links.

Fault tolerance against hostile nodes
   According to the release notes of 1.2, "Security support does not
exist in=20
    this release. Therefore, the  software should only be run in trusted
    environments. Future releases will include security."

Activity of development
    Active
   =20
    Current release is 1.3 (July 23, 2003), no release notes available
for 1.3 yet   =20

Developer
    Microsoft Research and Rice University (research community)

Language
    Java (requires a Java runtime version 1.4), C# (not known)

License
    BSD-like license (Java), MSR-EULA (C#)

Other notes
    Support for network locality - Pastry [4]_ actively replicates the
objects and=20
    places them at random locations in the network. Result: When
locating
    nearby object it might require the client to route to a distant
replica of=20
    the object.
   =20
    According to the Pastry [4]_ website:

        Future releases will address efficiency,=20
        security, interoperability and will provide additional=20
        application components like a generic distributed=20
        hash table implementation, replica management,=20
        caching, etc.

GISP [5]_
---------

Abstraction
    DHT_/DOLR_

Redundancy
    Chord [1]_-like (since GISP uses similar routing tables as Chord)

Fault tolerance against hostile nodes
    Based on our own initial experiments: the fault tolerance
    is relatively weak - no specific techiques used.

Activity of development
    Quite active.

Developer
    Daishi Kato (software engineering community)

Language
    Java (requires a Java runtime version 1.4)

License
    Sun Project JXTA License Version 1.1

Other notes
    Uses 10x more cache as Chord [1]_ for routing table.

    Includes a GISP [5]_ simulator.

Circle [6]_
-----------

Abstraction
    DHT_

Redundancy
    Not-known

Fault tolerance against hostile nodes
    According to Info-Anarchy Wiki:

        Problems are: The DHT implementation is=20
        vulnerable to denial of service attacks.   =20

Activity of development
    Active, the current version is 0.35 (30 May 2003)

Developer
    Paul Harrison (software engineering community)

Language
    Python (version 2.0 or higher, 2.2 preferred, GTK+-2 and PyGTK)=20

License
    GPL

Other notes
    Uses MD5 hashes for generating IDs.
   =20

Khashmir [7]_
-------------

Abstraction
    DHT_ (Kademlia [3]_ algorithm)

Redundancy
    Not known

Fault tolerance against hostile nodes
    According to the authors:

        Note that Khashmir currently isn't very=20
        attack resistant.

Activity of development
    Not active
   =20
    The current version is "3 - Alpha" (2002-09-02)

Developer
    Four developers (software engineering community)

Language
    Python

License
    MIT License

Other notes
    (none)

MLDonkey [8]_
-------------

Abstraction
    DHT_ (Kademlia [3]_ algorithm)

    (MLDonkey [8]_ is compatible with Overnet_, and Overnet claims that
it does=20
    Kademlia [3]_ and multisource downloading)

Redundancy
    Not known (we can imagine that redundancy is relatively high since
MLDonkey
    is widely deplyed)

Fault tolerance against hostile nodes
    Not known (we can imagine that fault tolerance is relatively high
since MLDonkey
    is widely deplyed)

Activity of development
    Very active

    The current version is 2.5-3 (May 26th 2003)=20

Developer
    12 developers (according to Savannah's project page, software
engineering=20
    community)

Language
    Objective-Caml (a compiler, not a interpreter)

License
    GPL

Other notes
    Supported P2P networks include eDonkey, Overnet, Bittorrent,
    Gnutella (Bearshare, Limewire,etc),  Gnutella2  (Shareaza), =20
    Fasttrack  (Kazaa, Imesh, Grobster), Soulseek  (beta), =20
    Direct-Connect  (alpha), and  Opennap  (alpha).
=20
    Networks can be enabled/disabled.

    Widely deployed in real life.

    Overnet is not a free specification ,i.e., change control is in the
Overnet=20
    company's hands.

    According to the `MLDonkey CVS source server`_ (check this_ too),
MLDonkey [8]_=20
    uses MD4 hashes for Overnet/EDonkey2K IDs::
    =20
        peer: an overnet peer in the following format:
        md4: the peer md4
        ip:  the peer ip
        int16: the peer port=20
        int8: the peer kind/uptime/last seen ?
   =20
    Original Overnet uses MD5 (and 2^128 space) for nodeIDs and data
items
    (http://www.overnet.com/documentation/how.html,=20
    http://bitzi.com/help/locallinks)

SharkyPy [9]_
-------------

Abstraction
    DHT_ (Kademlia [3]_ algorithm)

Redundancy
    According to the author:

        "It is being used in real code located at Sprachenzentrum der
Universit=E4t des=20
        Saarlandes (http://www.szsb.uni-saarland.de/tandem), and has
been running for=20
        several months now. Stable."

Fault tolerance against hostile nodes
    No specific techniques used: "it should work as is"

Activity of development
    The current version is 0.2b3 (16th February 2003)

    According to the post_ to the `python-list`_ by the author (posted
04 Feb 2003)::

        SharkyPy 0.2
        ------------

        SharkyPy is a library for creating a distributed hash table
using
        Python. It uses the Kademlia-Protocol
(http://kademlia.scs.cs.nyu.edu/)
        over XMLRPC.

        In constrast to alternatives like khashmir it does not need
twisted or
        any other library, and can even run without a persistence
backend (as
        long as the daemon is kept running). Persistence backends
currently only
        exist for MySQL.

        SharkyPy has been coded to only run with Python 2.3 at the
moment, as it
        uses some new features such as enumerate, etc. But it should
only be a
        matter of time to make it backwards compatible.

        - easily integrated into any program.
        - uses a standard protocol which should also be able to run over
a
          HTTP-proxy (this is still being worked on).
        - loosely based on the Kademlia Java reference implementation,
taking
          features like concurrent node queries into account.
        - completely implemented without external dependencies.

        URL: http://www.heim-d.de/~heikowu/SharkyPy
        License: LGPL (the source doesn't state this yet)
        Categories: Networking

        Heiko Wundram (heikowu@ceosg.de or heikowu@heim-d.de)

        PS: Still looking for co-developers... :)
   =20
    and here's an another message_ (posted 17 Feb 2003)::

        The third public beta of SharkyPy has just now been released.
This beta
        adds new functionality to SharkyPy in the following areas:

        1) Refactoring/Cleaning of most classes, and introduction of
           Borg-patterns to reduce overhead.
        2) Integration of (public-key) signatures into DHT-values, by
using
           Andrew M. Kuchlings PyCrypto package.
        3) Protocol specification is transmitted with every RPC-call, so
that
           future protocols won't break the program.
        4) Several other buxfixes/changes not listed here.

        This version should be considered even more beta than the
previous
        versions, as most of the functionality has only been tested over
a
        limited timespan (half a day). It works for me(tm). And it works
solely
        when using a version of Python 2.3.

        The feature consolidation process will start, when several other
        amendments have been made to the source.

        A stable version 0.2 will be released in about two weeks.
Anybody who is
        interested in trying out SharkyPy so far is encouraged to do so,
and
        should send any bugreports to me.

Developer
    Sprachenzentrum der Universit=E4t des Saarlandes / Heiko Wundram
(research community)

Language
    Python

License
    LGPL

Other notes
    According to the author of SharkyPy:
   =20
        This implementation is heavily based on threads, which makes it
	pretty resource-intensive on the computer it is running on. I never
	intended it to serve more than 30-40 clients, so this didn't matter to
	me. When you use it as a P2P network backend, things will certainly
look
	different.

Changes
=3D=3D=3D=3D=3D=3D=3D

While reviewing the different features of open source implementations of
structured P2P overlays we can conclude that Tapestry seems to be the
most
mature currently available. Specifically, other implementations
lack of features w.r.t. redundancy and fault tolerance that the Tapestry
implementation currently supports. Other reasons for choosing Tapestry
in order of=20
importance:

- The license
- The activity of development
- The implementation language

As a result, we recommend using Tapestry's open source implementation
with Storm.
For detailed changes and information about using Tapestry with Storm,
please
see the `storm_with_tapestry--hemppah` PEG document.
=20

.. [1] http://www.pdos.lcs.mit.edu/chord/
.. [2] http://www.cs.berkeley.edu/~ravenben/tapestry/
.. [3] http://kademlia.scs.cs.nyu.edu
.. [4] http://research.microsoft.com/~antr/Pastry/
.. [5] http://gisp.jxta.org/
.. [6] http://thecircle.org.au/
.. [7] http://khashmir.sourceforge.net/=20
.. [8] http://www.nongnu.org/mldonkey/=20
.. [9] http://www.heim-d.uni-sb.de/~heikowu/SharkyPy/

.. _`Towards a Common API for Structured P2P Overlays`:
http://www.cs.berkeley.edu/~ravenben/publications/pdf/apis.pdf
.. _`Tapestry: A Resilient Global-scale Overlay for Service Deployment`:
http://www.cs.berkeley.edu/~ravenben/publications/pdf/tapestry_jsac.pdf
.. _Overnet: http://www.overnet.com
.. _Oceanstore: http://www.oceanstore.org
.. _`MLDonkey CVS source server`:
http://savannah.nongnu.org/cgi-bin/viewcvs/mldonkey/mldonkey/docs/overnet=
.txt?rev=3D1.1&content-type=3Dtext/vnd.viewcvs-markup
.. _this:
http://savannah.nongnu.org/cgi-bin/viewcvs/mldonkey/mldonkey/src/networks=
/donkey/donkeyOvernet.ml?rev=3D1.4&content-type=3Dtext/vnd.viewcvs-markup
.. _post:
http://mail.python.org/pipermail/python-list/2003-February/143876.html
.. _`python-list`: http://mail.python.org/mailman/listinfo/python-list
.. _message:
http://mail.python.org/pipermail/python-list/2003-February/148394.html




From MAILER-DAEMON Mon Jul 28 09:51:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h8PZ-0006Yp-Ji
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 09:51:37 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h8PJ-0006K4-CV
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:51:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h8OH-0005lT-Jp
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:50:18 -0400
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19h8OG-0005kQ-1n
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:50:16 -0400
Received: (qmail 27271 invoked by uid 65534); 28 Jul 2003 13:50:13 -0000
Received: from pD95886AA.dip.t-dialin.net (EHLO gmx.de) (217.88.134.170)
	by mail.gmx.net (mp010) with SMTP; 28 Jul 2003 15:50:13 +0200
Message-ID: <3F2529B5.2090202@gmx.de>
Date: Mon, 28 Jul 2003 15:48:37 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: =?ISO-8859-1?Q?Hermanni_Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
Subject: Re: [Gzz] PEG: Available overlays
References: <1059397618.15013.9.camel@io.it.jyu.fi>
In-Reply-To: <1059397618.15013.9.camel@io.it.jyu.fi>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 13:51:36 -0000

Hermanni Hyytiälä wrote:
> ==========================================================================
> PEG available_overlays--hemppah: Available overlays
> ==========================================================================
> 
> :Status:   Incomplete

Is this incomplete or current? If incomplete, when do you expect it to 
become current?

-b




From MAILER-DAEMON Mon Jul 28 09:58:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h8V1-00018P-Gg
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 09:57:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h8T6-0000ih-C0
	for gzz-dev@nongnu.org; Mon, 28 Jul 2003 09:55:16 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h8T2-0000eu-Vi
	for gzz-dev@nongnu.org; Mon, 28 Jul 2003 09:55:13 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19h8St-0000G7-N8
	for gzz-dev@nongnu.org; Mon, 28 Jul 2003 09:55:03 -0400
Received: (qmail 11294 invoked by uid 65534); 28 Jul 2003 13:55:02 -0000
Received: from pD95886AA.dip.t-dialin.net (EHLO gmx.de) (217.88.134.170)
	by mail.gmx.net (mp002) with SMTP; 28 Jul 2003 15:55:02 +0200
Message-ID: <3F252AD6.7070007@gmx.de>
Date: Mon, 28 Jul 2003 15:53:26 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: GZZ developers <gzz-dev@nongnu.org>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Gzz] [repost] only_hash_blocks--benja
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 13:57:14 -0000

==========================================================================
Wherever you need a cryptographic hash, use a Storm block
==========================================================================

:Authors:  Benja Fallenstein
:Date-Created: 2003-07-14
:Last-Modified: $Date: 2003/07/28 13:49:36 $
:Revision: $Revision: 1.2 $
:Status:   Current
:Scope:    Major
:Type:     Architecture


When designing cryptographic protocols, you often need to
use cryptographic hashes in one way or another.

Cryptographic hash functions may be broken. As a precaution,
current Storm block URIs include two hashes: a SHA-1 and
a TigerTree hash.

If one but not both of these is broken, we can select
a new, third hash function and `extend the lifetime of
our URIs through timestamping`__. (That's `patented`__,
but maybe we get lucky and the patent will have expired
by the time our first hash function breaks...)

__ http://www.math.columbia.edu/~bayer/papers/Timestamp_BHS93.pdfp
__ 
http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO1&Sect2=HITOFF&d=PALL&p=1&u=/netahtml/srchnum.htm&r=1&f=G&l=50&s1=5373561.WKU.&OS=PN/53735
61&RS=PN/5373561

Now, in such a situation, *all* the (hash, hashed data)
pairs *must* be timestamped in order to remain valid.

If different protocols built on top of Storm store
hashed data in different, application-specific ways
each, all these protocols must be known in order to
reliably do the timestamping. If, however, Storm blocks
are always used then a whole pool can be secured
by simply timestamping each block in the pool through
a simple algorithm.

Therefore, whenever you need a cryptographic hash
to be verified, it is best to put the hashed data
into its own Storm block.

(An additional benefit is that then, Storm will do
the hash checking for you; you don't need to
worry about it.)


Issues
======

None.


Changes
=======

It is best current practice that a protocol which is
part of or based on Storm will, if it needs to verify
the cryptographic hash of some piece of data,

- put that data in its own Storm block;
- refer to it using a Storm URI which contains
   the hash;
- use the Storm interfaces to retrieve the block,
   which ensures that the hash has been checked.

\- Benja




From MAILER-DAEMON Mon Jul 28 09:59:56 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h8XI-0003zb-9v
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 09:59:36 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h8X3-0003aQ-Ks
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:59:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h8Wp-0002sp-8B
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:59:07 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h8WH-00025N-PZ
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 09:58:33 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6SDwJJg000227;
	Mon, 28 Jul 2003 16:58:19 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6SDwOhB022141;
	Mon, 28 Jul 2003 16:58:24 +0300 (EETDST)
Date: Mon, 28 Jul 2003 16:58:24 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] UMLLink poster paper sent
Message-ID: <20030728135824.GA22118@tarzan.it.jyu.fi>
References: <20030722125503.GF19765@tarzan.it.jyu.fi> <3F251F21.5080500@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F251F21.5080500@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 13:59:29 -0000

On Mon, Jul 28, 2003 at 03:03:29PM +0200, Benja Fallenstein wrote:
> 
> Hi,
> 
> Tuomas Lukka wrote:
> >That's now taken care of, now to make the poster.
> 
> I notice it's still not ready so I cannot take it to a print shop.

Ouch, I thought humppake and tuukkah started taking care of so I stopped
looking at it.

> >Hmm, maybe we could send it to Benja's hotel?
> 
> This'll be a busy week because it's the last in Germany and I have to 
> prepare my move. So I would appreciate if I didn't have to print the poster.
> 
> I don't know how fast post to Morocco is; I'll be living with friends 
> there, so it wouldn't be a problem to store it there. I'll be there till 
> August 23rd/morning of August 24th at least. I can send you the street 
> address if required.
> 
> In Nottingham I'll use the on-campus accomodation. I've no idea whether 
> we can send something there and have them store it for me, though it 
> would certainly be the most convenient and safe option for us.

Could you find out?

	Tuomas



From MAILER-DAEMON Mon Jul 28 10:08:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h8g4-00020f-P1
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 10:08:40 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h8aA-0000Kr-5s
	for gzz-dev@nongnu.org; Mon, 28 Jul 2003 10:02:34 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h8a8-0000Fh-4V
	for gzz-dev@nongnu.org; Mon, 28 Jul 2003 10:02:32 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h8a3-0008Qq-7j
	for gzz-dev@nongnu.org; Mon, 28 Jul 2003 10:02:27 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6SE2JJg000447;
	Mon, 28 Jul 2003 17:02:19 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6SE2NFY022168;
	Mon, 28 Jul 2003 17:02:23 +0300 (EETDST)
Date: Mon, 28 Jul 2003 17:02:23 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] [repost] only_hash_blocks--benja
Message-ID: <20030728140223.GB22118@tarzan.it.jyu.fi>
References: <3F252AD6.7070007@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F252AD6.7070007@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: GZZ developers <gzz-dev@nongnu.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 14:08:39 -0000

On Mon, Jul 28, 2003 at 03:53:26PM +0200, Benja Fallenstein wrote:
> ==========================================================================
> Wherever you need a cryptographic hash, use a Storm block
> ==========================================================================
> 
> :Authors:  Benja Fallenstein
> :Date-Created: 2003-07-14
> :Last-Modified: $Date: 2003/07/28 13:49:36 $
> :Revision: $Revision: 1.2 $
> :Status:   Current
> :Scope:    Major
> :Type:     Architecture

Accepted

	Tuomas



From MAILER-DAEMON Mon Jul 28 10:17:21 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19h8o1-0005W3-25
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 10:16:53 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19h8mM-00057Z-5J
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 10:15:10 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19h8l7-0004iZ-9K
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 10:13:53 -0400
Received: from tammi2.cc.jyu.fi ([130.234.4.77])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19h8gV-0002I5-4p
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 10:09:07 -0400
Received: (from apache@localhost)
	by tammi2.cc.jyu.fi (8.11.6/8.11.6) id h6SE8wM14201;
	Mon, 28 Jul 2003 17:08:58 +0300
X-Authentication-Warning: tammi2.cc.jyu.fi: apache set sender to
	hemppah@cc.jyu.fi using -f
Received: from 62.142.77.125 ( [62.142.77.125])
	as user hemppah@imap.cc.jyu.fi by tammi2.cc.jyu.fi with HTTP;
	Mon, 28 Jul 2003 17:08:58 +0300
Message-ID: <1059401338.3f252e7a3b89f@tammi2.cc.jyu.fi>
Date: Mon, 28 Jul 2003 17:08:58 +0300
From: hemppah@cc.jyu.fi
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] PEG: Available overlays
References: <1059397618.15013.9.camel@io.it.jyu.fi> <3F2529B5.2090202@gmx.de>
In-Reply-To: <3F2529B5.2090202@gmx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
User-Agent: Internet Messaging Program (IMP) 3.1
X-Originating-IP: 62.142.77.125
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by tammi2.cc.jyu.fi id
	h6SE8wM14201
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 14:16:51 -0000

Hi,

It should be considered as 'Current' since the storm_with_tapestry--hempp=
ah=20
is 'Current' -- it would be nice if this PEG is accepted *before* the=20
storm_with_tapestry--hemppah ;).

I will change the status of the documents tomorrow.


-Hermanni

Lainaus Benja Fallenstein <b.fallenstein@gmx.de>:

> Hermanni Hyyti=E4l=E4 wrote:
> >
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> > PEG available_overlays--hemppah: Available overlays
> >
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >=20
> > :Status:   Incomplete
>=20
> Is this incomplete or current? If incomplete, when do you expect it to=20
> become current?
>=20
> -b
>=20
>=20
>=20
> _______________________________________________
> Gzz-dev mailing list
> Gzz-dev@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/gzz-dev
>=20




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



From MAILER-DAEMON Mon Jul 28 11:54:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hAFb-0003aN-Ab
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 11:49:27 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hADt-0002tw-7Z
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 11:47:41 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hADU-0002lW-JA
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 11:47:17 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hA9e-0001uH-4M
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 11:43:18 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6SFh8ND007620;
	Mon, 28 Jul 2003 18:43:08 +0300
Received: from localhost (atsoukka@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6SFh8O3007616; 
	Mon, 28 Jul 2003 18:43:08 +0300
X-Authentication-Warning: verso.st.jyu.fi: atsoukka owned process doing -bs
Date: Mon, 28 Jul 2003 18:43:08 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@verso.st.jyu.fi
To: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>
Subject: Re: [Gzz] Not around next week
In-Reply-To: <Pine.LNX.4.44.0307251210361.22910-100000@itu.st.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307281840280.7398-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 15:49:25 -0000

Fri, 25 Jul 2003, Tuukka Hastrup kirjoitti:
> I added write permission for group staff-www to ~wiki/wikipasswrds, so you 
> should be able to add new accounts with htpasswd on himalia.

It would be easy tm make Wiki to use Navidoc (and therefore UML-diagrams, 
which could link Wiki to ffdoc), so /msg when you are online again :) 

ps. there will be problem with sync between ffdoc and wiki, without making 
    changes to Navidoc, it could be solved by running doc-bot at  
    himalia...

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Mon Jul 28 12:19:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hAif-0003Cm-Ff
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 12:19:29 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hAeO-0001rl-HO
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 12:15:04 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hAYM-000803-LY
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 12:08:51 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hAOU-0005gC-0g
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 11:58:38 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6SFwVND008295;
	Mon, 28 Jul 2003 18:58:31 +0300
Received: from localhost (atsoukka@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6SFwVmQ008290; 
	Mon, 28 Jul 2003 18:58:31 +0300
X-Authentication-Warning: verso.st.jyu.fi: atsoukka owned process doing -bs
Date: Mon, 28 Jul 2003 18:58:31 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@verso.st.jyu.fi
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] UMLLink poster paper sent
In-Reply-To: <20030728135824.GA22118@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307281844320.7398-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Benja Fallenstein <b.fallenstein@gmx.de>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 16:19:28 -0000

Mon, 28 Jul 2003, Tuomas Lukka kirjoitti:
> > I notice it's still not ready so I cannot take it to a print shop.
> Ouch, I thought humppake and tuukkah started taking care of so I stopped
> looking at it.

Sorry :( I also thought so, but it seems we didn't. I guess, we lack
motivation, since we have been workin with that paper quite long now.  
Though, still more important to get it ready... I can work for it again
tomorrow, but because I have no idea how poster should look like, I can't
finish it alone.

TODO (at least)
- layout
- text for pictures (the same picters as in short paper?)
- more about experiences?
- conclusions
- further information links?

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Mon Jul 28 12:37:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hB07-00067F-Gw
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 12:37:31 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hAzz-0005qL-Ci
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 12:37:23 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hAzd-0005HW-7a
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 12:37:02 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hAzX-0004z9-Sp
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 12:36:56 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6SGaqJg008490;
	Mon, 28 Jul 2003 19:36:52 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6SGawkQ022843;
	Mon, 28 Jul 2003 19:36:58 +0300 (EETDST)
Date: Mon, 28 Jul 2003 19:36:58 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: [Gzz] UMLLink poster paper sent
Message-ID: <20030728163658.GH18549@tarzan.it.jyu.fi>
References: <20030728135824.GA22118@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307281844320.7398-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307281844320.7398-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Benja Fallenstein <b.fallenstein@gmx.de>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 16:37:29 -0000

On Mon, Jul 28, 2003 at 06:58:31PM +0300, Asko Soukka wrote:
> Mon, 28 Jul 2003, Tuomas Lukka kirjoitti:
> > > I notice it's still not ready so I cannot take it to a print shop.
> > Ouch, I thought humppake and tuukkah started taking care of so I stopped
> > looking at it.
> 
> Sorry :( I also thought so, but it seems we didn't. 

Sigh...

> I guess, we lack
> motivation, since we have been workin with that paper quite long now.  

I can understand - but do realize it's now going to be *published*
and the appearance of the poster is what makes people either look deeper
into navidoc for their documentation needs or turn away.

> Though, still more important to get it ready... I can work for it again
> tomorrow, but because I have no idea how poster should look like, I can't
> finish it alone.
> 
> TODO (at least)
> - layout
> - text for pictures (the same picters as in short paper?)
> - more about experiences?
> - conclusions
> - further information links?

Let's look at these together tomorrow - I'll be online except 
for some hours after 13:30 (music)

	Tuomas



From MAILER-DAEMON Mon Jul 28 14:54:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hD5X-0002Gx-Em
	for mharc-gzz-dev@gnu.org; Mon, 28 Jul 2003 14:51:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hD3t-0001iJ-3Z
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 14:49:33 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hD3X-0001Bx-Mz
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 14:49:12 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hD1u-00006T-Hh
	for gzz-dev@mail.freesoftware.fsf.org; Mon, 28 Jul 2003 14:47:30 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6SIlSND013741;
	Mon, 28 Jul 2003 21:47:28 +0300
Received: from localhost (atsoukka@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6SIlSNJ013737; 
	Mon, 28 Jul 2003 21:47:28 +0300
X-Authentication-Warning: verso.st.jyu.fi: atsoukka owned process doing -bs
Date: Mon, 28 Jul 2003 21:47:28 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@verso.st.jyu.fi
To: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>
Subject: reST/Docutils Wiki and Navidoc (Re: [Gzz] Not around next week)
In-Reply-To: <Pine.LNX.4.44.0307281840280.7398-100000@verso.st.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307282118140.10723-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Jul 2003 18:51:13 -0000

Mon, 28 Jul 2003, Asko Soukka kirjoitti:
> ps. there will be problem with sync between ffdoc and wiki, without making 
>     changes to Navidoc, it could be solved by running doc-bot at  
>     himalia...

Hmm... this is necessary only, if we want to make references from ffdoc to 
Wiki. References only from Wiki to ffdoc won't need compiling 
documentations at Himalia.

Referring from ffdoc to Wiki brings also a yet another syncing problem.  
After modifying and compiling a single Wiki page, all implicit diagrams
added from ffdoc will disappear from that page. I see two solutions:

 - ffdoc is compiled at Himalia; implicit diagrams fron ffdoc to Wiki will
   reappear after next ffdoc run

 - after modifying a Wiki page, every diagram is checked for
   possible references to that particular Wiki-page

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 29 03:00:01 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hOSn-0004te-9r
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:00:01 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hOSk-0004t8-LA
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 02:59:58 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOSj-0004sm-6x
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 02:59:57 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOSi-0004s0-Nf
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 02:59:56 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T6xpJg014482;
	Tue, 29 Jul 2003 09:59:51 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T6xp1b003836;
	Tue, 29 Jul 2003 09:59:51 +0300 (EETDST)
Date: Tue, 29 Jul 2003 09:59:51 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: reST/Docutils Wiki and Navidoc (Re: [Gzz] Not around next week)
Message-ID: <20030729065951.GA3776@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307281840280.7398-100000@verso.st.jyu.fi>
	<Pine.LNX.4.44.0307282118140.10723-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307282118140.10723-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 06:59:59 -0000

On Mon, Jul 28, 2003 at 09:47:28PM +0300, Asko Soukka wrote:
> Mon, 28 Jul 2003, Asko Soukka kirjoitti:
> > ps. there will be problem with sync between ffdoc and wiki, without making 
> >     changes to Navidoc, it could be solved by running doc-bot at  
> >     himalia...
> 
> Hmm... this is necessary only, if we want to make references from ffdoc to 
> Wiki. References only from Wiki to ffdoc won't need compiling 
> documentations at Himalia.
> 
> Referring from ffdoc to Wiki brings also a yet another syncing problem.  
> After modifying and compiling a single Wiki page, all implicit diagrams
> added from ffdoc will disappear from that page. I see two solutions:
> 
>  - ffdoc is compiled at Himalia; implicit diagrams fron ffdoc to Wiki will
>    reappear after next ffdoc run
> 
>  - after modifying a Wiki page, every diagram is checked for
>    possible references to that particular Wiki-page

I see one more solution: *no* references from ffdoc to Wiki.
Ffdoc is supposed to be standalone, right?

	Tuomas



From MAILER-DAEMON Tue Jul 29 03:07:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hOYn-0000Nc-D5
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:06:13 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hOXx-0008VV-LU
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:05:21 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOXo-00089o-MO
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:05:13 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOXk-0007tp-Go
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:05:08 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6T754ND025800;
	Tue, 29 Jul 2003 10:05:04 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6T754BN025796; 
	Tue, 29 Jul 2003 10:05:04 +0300
Date: Tue, 29 Jul 2003 10:05:04 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Lava, coordsyscache
In-Reply-To: <20030728071659.GE18549@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307290903390.15165-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:06:11 -0000

On Mon, 28 Jul 2003, Tuomas Lukka wrote:
> I just noticed an alarming thing:

...
 
> I still don't even understand the need for CoordsysCache, could you please
> explain it once again, mudyc?

Viewports a and b show the same canvas.
Let's say in a we have node a1 focused and in b we have node b1 focused.
If you like to move node a1, you need to know it's coordsys number.
Who has it? No one. So what we have when we would like to do fast 
animation, other than the old vobscene? If the viewport a is main node we 
know a lot of it so we can use this information. As Tuomas recommended, 
I used parent's matching key as a key to save coordsystems in the class
which is under eyes now. By that key the coordsys number can be found from 
others which was the thing to reach for.

> I know it must be annoying to have to explain
> it in so much detail but I think it's pretty important that I understand
> what it is and why, right?

Yes of course. To me this sounds more like normal developement cycle.
I have done things that way, we see it's awful way and do it better.
Now we have some history and we can learn from the mistakes done in there.


   -Matti




From MAILER-DAEMON Tue Jul 29 03:13:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hOes-0006iM-Eg
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:12:30 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hOeI-0005rB-Lk
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:11:54 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOeB-0005ZE-F9
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:11:48 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOdx-000554-2v
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:11:33 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T7BVJg014840;
	Tue, 29 Jul 2003 10:11:31 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T7BVXY003874;
	Tue, 29 Jul 2003 10:11:31 +0300 (EETDST)
Date: Tue, 29 Jul 2003 10:11:31 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] Lava, coordsyscache
Message-ID: <20030729071131.GB3776@tarzan.it.jyu.fi>
References: <20030728071659.GE18549@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307290903390.15165-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307290903390.15165-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:12:29 -0000

On Tue, Jul 29, 2003 at 10:05:04AM +0300, Matti Katila wrote:
> On Mon, 28 Jul 2003, Tuomas Lukka wrote:
> > I just noticed an alarming thing:
> 
> ...
>  
> > I still don't even understand the need for CoordsysCache, could you please
> > explain it once again, mudyc?
> 
> Viewports a and b show the same canvas.
> Let's say in a we have node a1 focused and in b we have node b1 focused.
> If you like to move node a1, you need to know it's coordsys number.

All right so far

> Who has it? No one. 

No, the VobMatcher does! You can find out from it by asking with the
parent and key.

> So what we have when we would like to do fast 
> animation, other than the old vobscene? 

Yes, this is given: fast animation is through reusing the old vobscene.

> If the viewport a is main node we 
> know a lot of it so we can use this information. As Tuomas recommended, 
> I used parent's matching key as a key to save coordsystems in the class
> which is under eyes now. 

Umm, *why*? It sounds as if this is duplicating functionality that's
already in VobMatcher. If not, it *should* be there, right?

> By that key the coordsys number can be found from 
> others which was the thing to reach for.

?

	Tuomas



From MAILER-DAEMON Tue Jul 29 03:32:15 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hOxz-0003xV-Fz
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:32:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hOxx-0003wl-B3
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:32:13 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOxu-0003vE-Ne
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:32:12 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOxA-0003bh-G7
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:31:24 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6T7VKND027231;
	Tue, 29 Jul 2003 10:31:20 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6T7VKEr027225; 
	Tue, 29 Jul 2003 10:31:20 +0300
Date: Tue, 29 Jul 2003 10:31:20 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Lava, coordsyscache
In-Reply-To: <20030729071131.GB3776@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307291026580.15165-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Matti Katila <majukati@cc.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:32:14 -0000

On Tue, 29 Jul 2003, Tuomas Lukka wrote:
>> Viewports a and b show the same canvas.
>> Let's say in a we have node a1 focused and in b we have node b1 focused.
>> If you like to move node a1, you need to know it's coordsys number.
> 
> All right so far
> 
>> Who has it? No one. 
> 
> No, the VobMatcher does! You can find out from it by asking with the
> parent and key.

Uh, I feel like a dumm. Ok, takes some hours to fix this.


   -Matti





From MAILER-DAEMON Tue Jul 29 03:34:38 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hOzv-0005NE-5W
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:34:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hOzT-000558-Pc
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:33:47 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOyO-0004DD-Qd
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:32:42 -0400
Received: from tammi2.cc.jyu.fi ([130.234.4.77])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOxG-0003d3-9T
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:31:30 -0400
Received: (from apache@localhost)
	by tammi2.cc.jyu.fi (8.11.6/8.11.6) id h6T7VP212071;
	Tue, 29 Jul 2003 10:31:25 +0300
X-Authentication-Warning: tammi2.cc.jyu.fi: apache set sender to
	hemppah@cc.jyu.fi using -f
Received: from 62.142.77.125 ( [62.142.77.125])
	as user hemppah@imap.cc.jyu.fi by tammi2.cc.jyu.fi with HTTP;
	Tue, 29 Jul 2003 10:31:25 +0300
Message-ID: <1059463885.3f2622cd2e643@tammi2.cc.jyu.fi>
Date: Tue, 29 Jul 2003 10:31:25 +0300
From: hemppah@cc.jyu.fi
To: Tuomas Lukka <lukka@mit.jyu.fi>
References: <Pine.LNX.4.44.0307281840280.7398-100000@verso.st.jyu.fi>
	<Pine.LNX.4.44.0307282118140.10723-100000@verso.st.jyu.fi>
	<20030729065951.GA3776@tarzan.it.jyu.fi>
In-Reply-To: <20030729065951.GA3776@tarzan.it.jyu.fi>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
User-Agent: Internet Messaging Program (IMP) 3.1
X-Originating-IP: 62.142.77.125
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Subject: [Gzz] What is our Wiki for?  (WAS: reST/Docutils Wiki and Navidoc)
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:34:13 -0000


Ok, perhaps we should discuss more general about:

1) the content we want to store in our wiki
2) what is the function of wiki w.r.t our research group's communucation ways,
software development &c.

Once we have agreed a common "policy" (first discussing, then probably a PEG
document if needed) we can start creating content to wiki.

Currently, my personal opinion is that (as Tuomas cites below) wiki should be a
separate tool that should not be linked to every other tool we have (at least
not for now, maybe later if we found wiki useful).

Any suggestions?


-Hermanni

Quoting Tuomas Lukka <lukka@mit.jyu.fi>:

> On Mon, Jul 28, 2003 at 09:47:28PM +0300, Asko Soukka wrote:
> > Mon, 28 Jul 2003, Asko Soukka kirjoitti:
> > > ps. there will be problem with sync between ffdoc and wiki, without
> making 
> > >     changes to Navidoc, it could be solved by running doc-bot at  
> > >     himalia...
> > 
> > Hmm... this is necessary only, if we want to make references from ffdoc to
> 
> > Wiki. References only from Wiki to ffdoc won't need compiling 
> > documentations at Himalia.
> > 
> > Referring from ffdoc to Wiki brings also a yet another syncing problem.  
> > After modifying and compiling a single Wiki page, all implicit diagrams
> > added from ffdoc will disappear from that page. I see two solutions:
> > 
> >  - ffdoc is compiled at Himalia; implicit diagrams fron ffdoc to Wiki
> will
> >    reappear after next ffdoc run
> > 
> >  - after modifying a Wiki page, every diagram is checked for
> >    possible references to that particular Wiki-page
> 
> I see one more solution: *no* references from ffdoc to Wiki.
> Ffdoc is supposed to be standalone, right?
> 
> 	Tuomas
> 
> 
> _______________________________________________
> Gzz-dev mailing list
> Gzz-dev@nongnu.org
> http://mail.nongnu.org/mailman/listinfo/gzz-dev
> 




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/



From MAILER-DAEMON Tue Jul 29 03:43:41 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hP8l-00084u-RR
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:43:23 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hP3y-0006Yc-5F
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:38:26 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOyn-0004e0-9v
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:33:06 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOyc-0004RY-6U
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:32:54 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T7WqJg016241
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Tue, 29 Jul 2003 10:32:52 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T7Wqi9004118
	for gzz-dev@mail.freesoftware.fsf.org;
	Tue, 29 Jul 2003 10:32:52 +0300 (EETDST)
Date: Tue, 29 Jul 2003 10:32:52 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030729073252.GA4044@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] PEG: creation_history
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:43:22 -0000

==========================================================================
PEG creation_history--tjl: Object creation order RDF schema
==========================================================================

:Authors:  Tuomas Lukka
:Date-Created: 2003-07-28
:Last-Modified: $Date: 2003/07/29 07:21:38 $
:Revision: $Revision: 1.2 $
:Status:   Current
:Stakeholders: benja, mudyc, humppake
:Scope:    Minor
:Type:     Architecture

.. Affect-PEGs:

Time isn't always linear. It can branch. Maybe we should keep track
of the creation of objects as a tree based on versions.

Issues
======

Changes
=======

Create a new namespace, ``http://fenfire.org/rdf-v/2003/07/treetime``.

This namespace shall contain::

    /** An time-like ordering between creation of objects.
     */
    public class TREETIME {
	/** A type that declares a relation to be 
	 * a time-like relation.
	 * This namespace defines one time-like relation,
	 * "follows" for common use, more may be defined
	 * to avoid conflicts, using the TimeRelation class.
	 */
	static public final Object TimeRelation;

	/** (A, follows, B) means that A was created after B.
	 */
	static public final Object follows;

	/** (X, currentOf, follows) means that X is the latest
	 * entity in a "follows" chain. This applies to other
	 * relations, too.
	 */
	static public final Object currentOf;
    }



From MAILER-DAEMON Tue Jul 29 03:46:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hP8j-00082w-GZ
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:43:21 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hP57-0006yn-Q0
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:39:37 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hP3B-0006KJ-Eg
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:37:38 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hP0w-00061c-Kz
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:35:18 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T7ZEJg016503;
	Tue, 29 Jul 2003 10:35:14 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T7ZEYa004149;
	Tue, 29 Jul 2003 10:35:14 +0300 (EETDST)
Date: Tue, 29 Jul 2003 10:35:14 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: hemppah@cc.jyu.fi
Message-ID: <20030729073514.GC4044@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307281840280.7398-100000@verso.st.jyu.fi>
	<Pine.LNX.4.44.0307282118140.10723-100000@verso.st.jyu.fi>
	<20030729065951.GA3776@tarzan.it.jyu.fi>
	<1059463885.3f2622cd2e643@tammi2.cc.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1059463885.3f2622cd2e643@tammi2.cc.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Subject: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:43:19 -0000

On Tue, Jul 29, 2003 at 10:31:25AM +0300, hemppah@cc.jyu.fi wrote:
> 
> Ok, perhaps we should discuss more general about:
> 
> 1) the content we want to store in our wiki
> 2) what is the function of wiki w.r.t our research group's communucation ways,
> software development &c.
> 
> Once we have agreed a common "policy" (first discussing, then probably a PEG
> document if needed) we can start creating content to wiki.
> 
> Currently, my personal opinion is that (as Tuomas cites below) wiki should be a
> separate tool that should not be linked to every other tool we have (at least
> not for now, maybe later if we found wiki useful).
> 
> Any suggestions?

My suggestion would be that wiki would be primarily for people
with no access to CVS... Or is there a need to use it in some other way?

BTW: *how* are the home pages handled at the moment?

	Tuomas



From MAILER-DAEMON Tue Jul 29 03:49:09 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hPEL-0001Gj-GB
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 03:49:09 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hP9o-0008WC-7G
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:44:28 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hOzh-0005H7-Vk
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:34:03 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hOza-0005AL-Ar
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 03:33:54 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T7XnJg016410;
	Tue, 29 Jul 2003 10:33:49 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T7XoPP004132;
	Tue, 29 Jul 2003 10:33:50 +0300 (EETDST)
Date: Tue, 29 Jul 2003 10:33:50 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] Lava, coordsyscache
Message-ID: <20030729073350.GB4044@tarzan.it.jyu.fi>
References: <20030729071131.GB3776@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291026580.15165-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307291026580.15165-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Matti Katila <majukati@cc.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 07:49:07 -0000

On Tue, Jul 29, 2003 at 10:31:20AM +0300, Matti Katila wrote:
> On Tue, 29 Jul 2003, Tuomas Lukka wrote:
> >> Viewports a and b show the same canvas.
> >> Let's say in a we have node a1 focused and in b we have node b1 focused.
> >> If you like to move node a1, you need to know it's coordsys number.
> > 
> > All right so far
> > 
> >> Who has it? No one. 
> > 
> > No, the VobMatcher does! You can find out from it by asking with the
> > parent and key.
> 
> Uh, I feel like a dumm. Ok, takes some hours to fix this.

;) Nevermind, it happens - libvob is a complex system with lots
of features.

At the same time, could you think what we need to do to fix the docs
so that this wouldn't have happened?

	Tuomas



From MAILER-DAEMON Tue Jul 29 04:25:12 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hPkY-0003fF-Lg
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 04:22:26 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hPiw-0003C6-R8
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 04:20:46 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hPh4-00027Y-28
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 04:18:51 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hPdk-0000r4-4u
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 04:15:24 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6T8FJSL023778;
	Tue, 29 Jul 2003 11:15:19 +0300
Received: from localhost (atsoukka@localhost)
	by silmu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6T8FJU3023774; 
	Tue, 29 Jul 2003 11:15:19 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Tue, 29 Jul 2003 11:15:18 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: Tuomas Lukka <lukka@mit.jyu.fi>
In-Reply-To: <20030729073514.GC4044@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307291057110.21376-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>, hemppah@cc.jyu.fi
Subject: [Gzz] Handling homepages (WAS: Re: What is our Wiki for?)
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 08:22:24 -0000

> BTW: *how* are the home pages handled at the moment?

Using Navidoc.

Modify the current *.rst files or create new ones under 
non-gnu/fenfire. Add necessary extra files (e.g. images), run
make and commit.

Some notes about 'make' of homepages:

- if new pages are created, at first it creates new background textures
  for them using libvob (which is excepted to be located at 
  ../../libvob from non-gnu/fenfire)

- possible new background textures created should be added to cvs
  manually (non-gnu/fenfire/papers)

- Navidoc adds Benja's navigation bar to every page. 

A problem with Navidoc and home pages is that it compiles every page every 
time and thus every "Generated on:" timestamp changes.

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 29 05:03:22 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hQMT-0006qZ-41
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 05:01:37 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hQJM-0005zj-5F
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 04:58:24 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hQDe-0004TH-Cw
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 04:52:31 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hQD9-0004HL-Ey
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 04:51:59 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6T8prSL025315;
	Tue, 29 Jul 2003 11:51:54 +0300
Received: from localhost (atsoukka@localhost)
	by silmu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6T8pruM025311; 
	Tue, 29 Jul 2003 11:51:53 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Tue, 29 Jul 2003 11:51:53 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
In-Reply-To: <20030729073514.GC4044@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>, hemppah@cc.jyu.fi
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 09:01:35 -0000

Tue, 29 Jul 2003, Tuomas Lukka kirjoitti:
> > Currently, my personal opinion is that (as Tuomas cites below) wiki should be a
> > separate tool that should not be linked to every other tool we have (at least
> > not for now, maybe later if we found wiki useful).
> My suggestion would be that wiki would be primarily for people
> with no access to CVS... Or is there a need to use it in some other way?

So, I guess I'm still allowed to make Wiki diagrams to link ffdoc, but
it's only for good that diagrams embedded from Wiki to ffdoc vanish after
ffdoc update.

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 29 05:08:54 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hQSg-0000Oe-Rn
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 05:08:02 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hQSX-0000Ia-KB
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:07:53 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hQSE-0000AK-Ob
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:07:35 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hQQp-00088m-C5
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:06:07 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T964Jg021807;
	Tue, 29 Jul 2003 12:06:04 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T964B5004911;
	Tue, 29 Jul 2003 12:06:04 +0300 (EETDST)
Date: Tue, 29 Jul 2003 12:06:04 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Asko Soukka <asko.soukka@iki.fi>
Message-ID: <20030729090604.GE4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291057110.21376-100000@silmu.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307291057110.21376-100000@silmu.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>, hemppah@cc.jyu.fi
Subject: [Gzz] Re: Handling homepages (WAS: Re: What is our Wiki for?)
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 09:08:00 -0000

On Tue, Jul 29, 2003 at 11:15:18AM +0300, Asko Soukka wrote:
> > BTW: *how* are the home pages handled at the moment?
> 
> Using Navidoc.
> 
> Modify the current *.rst files or create new ones under 
> non-gnu/fenfire. Add necessary extra files (e.g. images), run
> make and commit.

So in which file is the actual homepage? Which cvs?
Make what?

Having this process explained somewhere might help ;)

> Some notes about 'make' of homepages:
> 
> - if new pages are created, at first it creates new background textures
>   for them using libvob (which is excepted to be located at 
>   ../../libvob from non-gnu/fenfire)
> 
> - possible new background textures created should be added to cvs
>   manually (non-gnu/fenfire/papers)

Umm, what's non-gnu/fenfire?

My directory structure is flat: 

cvs/fenfire
cvs/fenfire-depends
cvs/libvob
...

	Tuomas



From MAILER-DAEMON Tue Jul 29 05:17:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hQbP-00034q-Jr
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 05:17:03 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hQTm-000172-QC
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:09:10 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hQPo-0007uD-UY
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:05:06 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hQOZ-0007TZ-UT
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:03:48 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6T93iJg021724;
	Tue, 29 Jul 2003 12:03:44 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6T93jkV004862;
	Tue, 29 Jul 2003 12:03:45 +0300 (EETDST)
Date: Tue, 29 Jul 2003 12:03:45 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
Message-ID: <20030729090345.GD4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>, hemppah@cc.jyu.fi
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 09:17:02 -0000

On Tue, Jul 29, 2003 at 11:51:53AM +0300, Asko Soukka wrote:
> Tue, 29 Jul 2003, Tuomas Lukka kirjoitti:
> > > Currently, my personal opinion is that (as Tuomas cites below) wiki should be a
> > > separate tool that should not be linked to every other tool we have (at least
> > > not for now, maybe later if we found wiki useful).
> > My suggestion would be that wiki would be primarily for people
> > with no access to CVS... Or is there a need to use it in some other way?
> 
> So, I guess I'm still allowed to make Wiki diagrams to link ffdoc, but
> it's only for good that diagrams embedded from Wiki to ffdoc vanish after
> ffdoc update.

Ahh, that's a good point... Do we want to allow wiki diagrams
refer to ffdoc?

	Tuomas



From MAILER-DAEMON Tue Jul 29 05:22:11 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hQgA-00051q-Lh
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 05:21:58 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hQg7-0004yu-E0
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:21:55 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hQf9-0004Yu-Dm
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:20:55 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hQef-0004QV-NS
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:20:26 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6T9KKSL026789;
	Tue, 29 Jul 2003 12:20:20 +0300
Received: from localhost (atsoukka@localhost)
	by silmu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6T9KKRL026784; 
	Tue, 29 Jul 2003 12:20:20 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Tue, 29 Jul 2003 12:20:19 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: b.fallenstein@gmx.de,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <Pine.LNX.4.44.0307291218180.26652-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: [Gzz] UMLLink poster
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 09:21:56 -0000

Hi Benja,

Do you feel the UMLLink poster ready now?
(I hope you still have time to look at it.)

What would be the next step for it?

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 29 05:32:28 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hQmu-0007R4-Fs
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 05:28:56 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hQfK-0004e0-8h
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:21:06 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hQdJ-0003sK-JB
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:19:01 -0400
Received: from silmu.st.jyu.fi ([130.234.4.64])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hQZH-0002bl-GW
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 05:14:51 -0400
Received: from silmu.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by silmu.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6T9EkSL026582;
	Tue, 29 Jul 2003 12:14:46 +0300
Received: from localhost (atsoukka@localhost)
	by silmu.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6T9EkBr026578; 
	Tue, 29 Jul 2003 12:14:46 +0300
X-Authentication-Warning: silmu.st.jyu.fi: atsoukka owned process doing -bs
Date: Tue, 29 Jul 2003 12:14:46 +0300 (EEST)
From: Asko Soukka <asko.soukka@iki.fi>
X-X-Sender: atsoukka@silmu.st.jyu.fi
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Re: Handling homepages (WAS: Re: What is our Wiki for?)
In-Reply-To: <20030729090604.GE4044@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307291211200.26444-100000@silmu.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>, hemppah@cc.jyu.fi
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
Reply-To: Asko Soukka <asko.soukka@iki.fi>
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 09:28:54 -0000

Tue, 29 Jul 2003, Tuomas Lukka kirjoitti:
> Umm, what's non-gnu/fenfire?

Oh, it's Savannah WWW-repository.

cvs -d <membername>@subversions.gnu.org:/webcvs co non-gnu/fenfire

How we should balance between http://www.nongnu.org/fenfire/ (that CVS) 
and http://himalia.it.jyu.fi/wiki/ I have hopes that Wiki pages would be 
updated more frequently.

-- 
Asko Soukka <asko.soukka@iki.fi>
<http://www.iki.fi/asko.soukka/>




From MAILER-DAEMON Tue Jul 29 06:26:47 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hRgc-0005yY-Rn
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 06:26:30 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hRer-0005II-FM
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:24:41 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hRdr-0004V6-Dj
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:23:41 -0400
Received: from posti4.jyu.fi ([130.234.5.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hRdC-00046Z-1x
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:22:58 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti4.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6TAMlbR013826; 
	Tue, 29 Jul 2003 13:22:47 +0300
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
In-Reply-To: <20030729090345.GD4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
Content-Type: text/plain
Organization: 
Message-Id: <1059474167.17462.13.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 29 Jul 2003 13:22:47 +0300
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/)
	at posti4.jyu.fi; Tue, 29 Jul 2003 13:22:48 +0300
X-Spam-Checked: by miltrassassin
	at posti4.jyu.fi; Tue, 29 Jul 2003 13:22:50 +0300
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 10:26:29 -0000

On Tue, 2003-07-29 at 12:03, Tuomas Lukka wrote:
> On Tue, Jul 29, 2003 at 11:51:53AM +0300, Asko Soukka wrote:
> > Tue, 29 Jul 2003, Tuomas Lukka kirjoitti:
> > > > Currently, my personal opinion is that (as Tuomas cites below) wiki should be a
> > > > separate tool that should not be linked to every other tool we have (at least
> > > > not for now, maybe later if we found wiki useful).
> > > My suggestion would be that wiki would be primarily for people
> > > with no access to CVS... Or is there a need to use it in some other way?
> > 
> > So, I guess I'm still allowed to make Wiki diagrams to link ffdoc, but
> > it's only for good that diagrams embedded from Wiki to ffdoc vanish after
> > ffdoc update.
> 
> Ahh, that's a good point... Do we want to allow wiki diagrams
> refer to ffdoc?

Ditto (i.e., humppake's point partially obsoletes my previous
stametement ;).

It would be nice, for instance,  that if we have a brief description of
a term (or similar) in wiki, then there would be a link(s) to ffdoc and
by following that/those link(s) a user would get more detailed/technical
explanation of the term (e.g. a design document, Javadoc...).

In addition to other possible uses, I suggest that wiki would act as a
"starting point" for looking information related to our project. When I
joined to project last October, it would has been *very* nice if there
has been a "starting point" where to start look more information.


-Hermanni


-Hermanni




From MAILER-DAEMON Tue Jul 29 06:38:00 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hRqZ-0001nm-WB
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 06:36:47 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hRpz-0001UJ-3x
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:36:11 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hRkK-0007bA-RX
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:30:21 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hRgV-0005uy-I6
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:26:23 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6TAP1Jg026553;
	Tue, 29 Jul 2003 13:25:01 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6TAP2Fi005311;
	Tue, 29 Jul 2003 13:25:02 +0300 (EETDST)
Date: Tue, 29 Jul 2003 13:25:02 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Hermanni =?iso-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
Message-ID: <20030729102502.GF4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
	<1059474167.17462.13.camel@io.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <1059474167.17462.13.camel@io.it.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.it.jyu.fi id
	h6TAP1Jg026553
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 10:36:46 -0000

On Tue, Jul 29, 2003 at 01:22:47PM +0300, Hermanni Hyyti=E4l=E4 wrote:
> On Tue, 2003-07-29 at 12:03, Tuomas Lukka wrote:
> > On Tue, Jul 29, 2003 at 11:51:53AM +0300, Asko Soukka wrote:
> > > Tue, 29 Jul 2003, Tuomas Lukka kirjoitti:
> > > > > Currently, my personal opinion is that (as Tuomas cites below) =
wiki should be a
> > > > > separate tool that should not be linked to every other tool we =
have (at least
> > > > > not for now, maybe later if we found wiki useful).
> > > > My suggestion would be that wiki would be primarily for people
> > > > with no access to CVS... Or is there a need to use it in some oth=
er way?
> > >=20
> > > So, I guess I'm still allowed to make Wiki diagrams to link ffdoc, =
but
> > > it's only for good that diagrams embedded from Wiki to ffdoc vanish=
 after
> > > ffdoc update.
> >=20
> > Ahh, that's a good point... Do we want to allow wiki diagrams
> > refer to ffdoc?
>=20
> Ditto (i.e., humppake's point partially obsoletes my previous
> stametement ;).
>=20
> It would be nice, for instance,  that if we have a brief description of
> a term (or similar) in wiki, then there would be a link(s) to ffdoc and
> by following that/those link(s) a user would get more detailed/technica=
l
> explanation of the term (e.g. a design document, Javadoc...).
>=20
> In addition to other possible uses, I suggest that wiki would act as a
> "starting point" for looking information related to our project. When I
> joined to project last October, it would has been *very* nice if there
> has been a "starting point" where to start look more information.

Why would wiki make a good starting point?

I'd think we should use .rst for those things.

For Wiki, the main use I see is "running commentary", i.e.
"X is broken, you need to do Y right now to accomplish it" &c

Anything permanent should probably be on the rst side.

	Tuomas



From MAILER-DAEMON Tue Jul 29 07:28:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hSdu-00015Y-Uz
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 07:27:46 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hSPh-00027U-BO
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 07:13:05 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hSL2-0000pU-NK
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 07:08:17 -0400
Received: from posti4.jyu.fi ([130.234.5.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hRwR-0004KW-TV
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 06:42:52 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti4.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6TAgibR016694; 
	Tue, 29 Jul 2003 13:42:44 +0300
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
In-Reply-To: <20030729102502.GF4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
	<1059474167.17462.13.camel@io.it.jyu.fi>
	<20030729102502.GF4044@tarzan.it.jyu.fi>
Content-Type: text/plain
Organization: 
Message-Id: <1059475364.17462.29.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 29 Jul 2003 13:42:44 +0300
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/)
	at posti4.jyu.fi; Tue, 29 Jul 2003 13:42:45 +0300
X-Spam-Checked: by miltrassassin
	at posti4.jyu.fi; Tue, 29 Jul 2003 13:42:46 +0300
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 11:27:45 -0000

On Tue, 2003-07-29 at 13:25, Tuomas Lukka wrote:
> > > > 
> > > > So, I guess I'm still allowed to make Wiki diagrams to link ffdoc, but
> > > > it's only for good that diagrams embedded from Wiki to ffdoc vanish after
> > > > ffdoc update.
> > > 
> > > Ahh, that's a good point... Do we want to allow wiki diagrams
> > > refer to ffdoc?
> > 
> > Ditto (i.e., humppake's point partially obsoletes my previous
> > stametement ;).
> > 
> > It would be nice, for instance,  that if we have a brief description of
> > a term (or similar) in wiki, then there would be a link(s) to ffdoc and
> > by following that/those link(s) a user would get more detailed/technical
> > explanation of the term (e.g. a design document, Javadoc...).
> > 
> > In addition to other possible uses, I suggest that wiki would act as a
> > "starting point" for looking information related to our project. When I
> > joined to project last October, it would has been *very* nice if there
> > has been a "starting point" where to start look more information.
> 
> Why would wiki make a good starting point?

1) Information categorization
We could categorize things under different categories with links (e.g.,
"Tutorials", "Terms", "Best practices", "Documentation",
"Tutorials/Fenfire project", "Tutorials/Subprojects", "Best
Practices/LibVob", "Best Practices/Design Patterns" "Best
Practices/Avoid these things", "Terms/Xanalogical model", "Terms/3D
programming" &c).

2) Familiar interface
People are able to use familiar interface for viewing information, i.e.,
their favourite web browser.


> I'd think we should use .rst for those things.

If .rst files can do categorization then it should be fine ;).

> 
> For Wiki, the main use I see is "running commentary", i.e.
> "X is broken, you need to do Y right now to accomplish it" &c
> Anything permanent should probably be on the rst side.

Indeed. Wiki should *not* store anything permanent (i.e. official)
documents. As said, wiki would only act a starting point/quick ref place
where information is categorized with links to official documents for
more detailed (official information) information.



-Hermanni






From MAILER-DAEMON Tue Jul 29 08:18:18 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hTQk-0007ha-CI
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 08:18:14 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hTQT-0007Rq-QO
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:17:57 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hTQ3-0007Ct-BV
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:17:32 -0400
Received: from pop.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19hTPm-00074p-9H
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:17:14 -0400
Received: (qmail 19716 invoked by uid 65534); 29 Jul 2003 12:17:13 -0000
Received: from pD9588B0E.dip.t-dialin.net (EHLO gmx.de) (217.88.139.14)
	by mail.gmx.net (mp005) with SMTP; 29 Jul 2003 14:17:13 +0200
Message-ID: <3F266564.70704@gmx.de>
Date: Tue, 29 Jul 2003 14:15:32 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: =?UTF-8?B?SGVybWFubmkgSHl5dGnDpGzDpA==?= <hemppah@cc.jyu.fi>
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
References: <20030729073514.GC4044@tarzan.it.jyu.fi>	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>	<20030729090345.GD4044@tarzan.it.jyu.fi>	<1059474167.17462.13.camel@io.it.jyu.fi>	<20030729102502.GF4044@tarzan.it.jyu.fi>
	<1059475364.17462.29.camel@io.it.jyu.fi>
In-Reply-To: <1059475364.17462.29.camel@io.it.jyu.fi>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Tuomas Lukka <lukka@mit.jyu.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Tuukka Hastrup <Tuukka.Hastrup@iki.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 12:18:12 -0000

Hermanni HyytiÃ¤lÃ¤ wrote:
>>Why would wiki make a good starting point?
> 
> 1) Information categorization
> We could categorize things under different categories with links (e.g.,
> "Tutorials", "Terms", "Best practices", "Documentation",
> "Tutorials/Fenfire project", "Tutorials/Subprojects", "Best
> Practices/LibVob", "Best Practices/Design Patterns" "Best
> Practices/Avoid these things", "Terms/Xanalogical model", "Terms/3D
> programming" &c).
...
>>I'd think we should use .rst for those things.
> 
> If .rst files can do categorization then it should be fine ;).

Of course we can already use hierarchy, but we could also extend rst a 
little to make categorization more flexible. Suggestion: Add a header to 
rst pages::

     =====
     Title
     =====

     :Author: ...
     :Created: ...
     :Categories: Tutorials -> Fenfire project; Terms -> RDF

Then, in the output the categories would be hyperlinked, and there would 
be auto-generated summary pages; a bit like in Tim Bray's ongoing_, 
where articles can also be in multiple categories (example_).

.. _ongoing: http://www.tbray.org/ongoing/
.. _example: http://www.tbray.org/ongoing/When/200x/2003/07/28/SummerPix

I think it would be cool if it were possible to categorize everything 
that way, including PEGs, darts, and design documents...

- Benja




From MAILER-DAEMON Tue Jul 29 08:34:02 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hTfs-0003mv-Uq
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 08:33:52 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hTeZ-0003Cv-UL
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:32:31 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hTdg-0002sy-Fh
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:31:38 -0400
Received: from imap.gmx.net ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19hTUR-0008UW-5p
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:22:03 -0400
Received: (qmail 22010 invoked by uid 65534); 29 Jul 2003 12:22:02 -0000
Received: from pD9588B0E.dip.t-dialin.net (EHLO gmx.de) (217.88.139.14)
	by mail.gmx.net (mp010) with SMTP; 29 Jul 2003 14:22:02 +0200
Message-ID: <3F266688.6070603@gmx.de>
Date: Tue, 29 Jul 2003 14:20:24 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] PEG: creation_history
References: <20030729073252.GA4044@tarzan.it.jyu.fi>
In-Reply-To: <20030729073252.GA4044@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 12:33:51 -0000

Tuomas Lukka wrote:
> Time isn't always linear. It can branch. Maybe we should keep track
> of the creation of objects as a tree based on versions.

I don't quite understand exactly. What is linked? "Objects?" "Versions?" 
How are these represented in RDF?

Thanks,
- Benja




From MAILER-DAEMON Tue Jul 29 09:03:40 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hU8B-00006E-Vh
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 09:03:07 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hU7j-0007nW-JS
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 09:02:39 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hU4p-0006QL-Q5
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:59:41 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19hU0X-0004t0-Ol
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 08:55:13 -0400
Received: (qmail 20939 invoked by uid 65534); 29 Jul 2003 12:55:12 -0000
Received: from pD9588B0E.dip.t-dialin.net (EHLO gmx.de) (217.88.139.14)
	by mail.gmx.net (mp003) with SMTP; 29 Jul 2003 14:55:12 +0200
Message-ID: <3F266E4E.8050701@gmx.de>
Date: Tue, 29 Jul 2003 14:53:34 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: Asko Soukka <asko.soukka@iki.fi>
Subject: Re: [Gzz] UMLLink poster
References: <Pine.LNX.4.44.0307291218180.26652-100000@silmu.st.jyu.fi>
In-Reply-To: <Pine.LNX.4.44.0307291218180.26652-100000@silmu.st.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 13:03:05 -0000


Hi Asko,

Asko Soukka wrote:
> Do you feel the UMLLink poster ready now?
> (I hope you still have time to look at it.)

One thing is the size. Lloyd wrote--

 > The board for displaying your poster at the conference will be
 > 140cm wide and 180 cm high.

The sxw is 70cm wide and 90cm high. Is it intended that it is so much 
smaller? (I've never made a poster so I don't know.)

- Benja




From MAILER-DAEMON Tue Jul 29 10:06:19 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hV78-0004Z2-C2
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 10:06:06 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hV6p-0004LV-RP
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:05:47 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hV6X-0004B2-GS
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:05:30 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hV5k-0003xO-HN
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:04:40 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6TE4ZJg006175;
	Tue, 29 Jul 2003 17:04:35 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6TE4aPo006453;
	Tue, 29 Jul 2003 17:04:36 +0300 (EETDST)
Date: Tue, 29 Jul 2003 17:04:36 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Hermanni =?iso-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
Message-ID: <20030729140436.GG4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
	<1059474167.17462.13.camel@io.it.jyu.fi>
	<20030729102502.GF4044@tarzan.it.jyu.fi>
	<1059475364.17462.29.camel@io.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
In-Reply-To: <1059475364.17462.29.camel@io.it.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by mailhost.it.jyu.fi id
	h6TE4ZJg006175
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 14:06:05 -0000

On Tue, Jul 29, 2003 at 01:42:44PM +0300, Hermanni Hyyti=E4l=E4 wrote:
> On Tue, 2003-07-29 at 13:25, Tuomas Lukka wrote:
> > > > >=20
> > > > > So, I guess I'm still allowed to make Wiki diagrams to link ffd=
oc, but
> > > > > it's only for good that diagrams embedded from Wiki to ffdoc va=
nish after
> > > > > ffdoc update.
> > > >=20
> > > > Ahh, that's a good point... Do we want to allow wiki diagrams
> > > > refer to ffdoc?
> > >=20
> > > Ditto (i.e., humppake's point partially obsoletes my previous
> > > stametement ;).
> > >=20
> > > It would be nice, for instance,  that if we have a brief descriptio=
n of
> > > a term (or similar) in wiki, then there would be a link(s) to ffdoc=
 and
> > > by following that/those link(s) a user would get more detailed/tech=
nical
> > > explanation of the term (e.g. a design document, Javadoc...).
> > >=20
> > > In addition to other possible uses, I suggest that wiki would act a=
s a
> > > "starting point" for looking information related to our project. Wh=
en I
> > > joined to project last October, it would has been *very* nice if th=
ere
> > > has been a "starting point" where to start look more information.
> >=20
> > Why would wiki make a good starting point?
>=20
> 1) Information categorization
> We could categorize things under different categories with links (e.g.,
> "Tutorials", "Terms", "Best practices", "Documentation",
> "Tutorials/Fenfire project", "Tutorials/Subprojects", "Best
> Practices/LibVob", "Best Practices/Design Patterns" "Best
> Practices/Avoid these things", "Terms/Xanalogical model", "Terms/3D
> programming" &c).
>=20
> 2) Familiar interface
> People are able to use familiar interface for viewing information, i.e.=
,
> their favourite web browser.

What advantages does wiki have w.r.t. rst for either of those?

1) This is about structuring information, not about wiki vs rst.

2) .rst goes into html

> > I'd think we should use .rst for those things.
>=20
> If .rst files can do categorization then it should be fine ;).
>=20
> >=20
> > For Wiki, the main use I see is "running commentary", i.e.
> > "X is broken, you need to do Y right now to accomplish it" &c
> > Anything permanent should probably be on the rst side.
>=20
> Indeed. Wiki should *not* store anything permanent (i.e. official)
> documents. As said, wiki would only act a starting point/quick ref plac=
e
> where information is categorized with links to official documents for
> more detailed (official information) information.

Why?

	Tuomas



From MAILER-DAEMON Tue Jul 29 10:12:13 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hVD1-0006fv-GX
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 10:12:11 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hVCJ-0006TY-2J
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:11:27 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hV8O-0005cc-S1
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:07:25 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hV6q-0004MO-OM
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:05:48 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6TE5iJg006232;
	Tue, 29 Jul 2003 17:05:44 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6TE5jGp006460;
	Tue, 29 Jul 2003 17:05:45 +0300 (EETDST)
Date: Tue, 29 Jul 2003 17:05:45 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
Message-ID: <20030729140545.GH4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
	<1059474167.17462.13.camel@io.it.jyu.fi>
	<20030729102502.GF4044@tarzan.it.jyu.fi>
	<1059475364.17462.29.camel@io.it.jyu.fi> <3F266564.70704@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F266564.70704@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Hermanni =?iso-8859-1?B?SHl5dGnDpGzDpA==?= <hemppah@cc.jyu.fi>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 14:12:07 -0000

On Tue, Jul 29, 2003 at 02:15:32PM +0200, Benja Fallenstein wrote:
> Of course we can already use hierarchy, but we could also extend rst a 
> little to make categorization more flexible. Suggestion: Add a header to 
> rst pages::
> 
>     =====
>     Title
>     =====
> 
>     :Author: ...
>     :Created: ...
>     :Categories: Tutorials -> Fenfire project; Terms -> RDF
> 
> Then, in the output the categories would be hyperlinked, and there would 
> be auto-generated summary pages; a bit like in Tim Bray's ongoing_, 
> where articles can also be in multiple categories (example_).
> 
> .. _ongoing: http://www.tbray.org/ongoing/
> .. _example: http://www.tbray.org/ongoing/When/200x/2003/07/28/SummerPix
> 
> I think it would be cool if it were possible to categorize everything 
> that way, including PEGs, darts, and design documents...

I like this idea.

	Tuomas



From MAILER-DAEMON Tue Jul 29 10:17:23 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hVFH-0007mW-Ir
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 10:14:31 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hVEg-0007TH-Ey
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:13:54 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hVDD-0006l2-T2
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:12:24 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hV8j-0005oS-6O
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:07:45 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6TE7gJg006360;
	Tue, 29 Jul 2003 17:07:42 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6TE7hRu006472;
	Tue, 29 Jul 2003 17:07:43 +0300 (EETDST)
Date: Tue, 29 Jul 2003 17:07:43 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] PEG: creation_history
Message-ID: <20030729140743.GI4044@tarzan.it.jyu.fi>
References: <20030729073252.GA4044@tarzan.it.jyu.fi> <3F266688.6070603@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F266688.6070603@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 14:14:30 -0000

On Tue, Jul 29, 2003 at 02:20:24PM +0200, Benja Fallenstein wrote:
> Tuomas Lukka wrote:
> >Time isn't always linear. It can branch. Maybe we should keep track
> >of the creation of objects as a tree based on versions.
> 
> I don't quite understand exactly. What is linked? "Objects?" "Versions?" 
> How are these represented in RDF?

Ouch... what I meant is, e.g., canvases and imported pdf files
in FenPDF. Fixed in CVS

	Tuomas



From MAILER-DAEMON Tue Jul 29 10:18:39 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hVHA-0008R3-K9
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 10:16:28 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hVE8-0007AB-5y
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:13:20 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hVB3-0006HO-4p
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:10:09 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hVB0-0006GV-0e
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:10:06 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6TEA0Jg006412;
	Tue, 29 Jul 2003 17:10:01 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6TEA1qI006488;
	Tue, 29 Jul 2003 17:10:01 +0300 (EETDST)
Date: Tue, 29 Jul 2003 17:10:01 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Benja Fallenstein <b.fallenstein@gmx.de>
Subject: Re: [Gzz] UMLLink poster
Message-ID: <20030729141001.GJ4044@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307291218180.26652-100000@silmu.st.jyu.fi>
	<3F266E4E.8050701@gmx.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3F266E4E.8050701@gmx.de>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 14:16:27 -0000

On Tue, Jul 29, 2003 at 02:53:34PM +0200, Benja Fallenstein wrote:
> 
> Hi Asko,
> 
> Asko Soukka wrote:
> >Do you feel the UMLLink poster ready now?
> >(I hope you still have time to look at it.)
> 
> One thing is the size. Lloyd wrote--
> 
> > The board for displaying your poster at the conference will be
> > 140cm wide and 180 cm high.
> 
> The sxw is 70cm wide and 90cm high. Is it intended that it is so much 
> smaller? (I've never made a poster so I don't know.)

Openoffice didn't allow 140x180 so I divided by two.

	Tuomas



From MAILER-DAEMON Tue Jul 29 10:32:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hVWR-0005h5-7B
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 10:32:15 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hVWO-0005gJ-CC
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:32:12 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hVWM-0005g5-5Z
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:32:11 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hVWL-0005fq-Iq
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 10:32:09 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6TEW5ND023430
	for <gzz-dev@mail.freesoftware.fsf.org>; Tue, 29 Jul 2003 17:32:05 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6TEW5k4023426
	for <gzz-dev@mail.freesoftware.fsf.org>; Tue, 29 Jul 2003 17:32:05 +0300
Date: Tue, 29 Jul 2003 17:32:05 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <Pine.LNX.4.44.0307291723530.15165-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: 
Subject: [Gzz] Libvob: nadirCS hasn't parent.
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 14:32:13 -0000



Well, I noticed this last year but perhaps forgot to mention it.

When asking parent of nadir coordinate system it returns -1 rather than 
the one which has been rotated.

Anyone want to fix this?


   -Matti




From MAILER-DAEMON Tue Jul 29 12:25:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hXI4-0002Ut-Em
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 12:25:32 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hXHy-0002HX-Ga
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 12:25:26 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hXGb-00014w-4u
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 12:24:02 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hX87-00065V-2l
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 12:15:15 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6TGFAND026346;
	Tue, 29 Jul 2003 19:15:10 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6TGFAgW026342; 
	Tue, 29 Jul 2003 19:15:10 +0300
Date: Tue, 29 Jul 2003 19:15:10 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Lava, coordsyscache
In-Reply-To: <20030729073350.GB4044@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307291836360.15165-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 16:25:30 -0000

On Tue, 29 Jul 2003, Tuomas Lukka wrote:
> On Tue, Jul 29, 2003 at 10:31:20AM +0300, Matti Katila wrote:
> > 
> > Uh, I feel like a dumm. Ok, takes some hours to fix this.

Now enough hours later I can say, phhh...
 
> ;) Nevermind, it happens - libvob is a complex system with lots
> of features.
> 
> At the same time, could you think what we need to do to fix the docs
> so that this wouldn't have happened?

First someone should document how this makes sense?

    public void chgFast(VobScene oldVS, int parent) {
        p("parent: "+parent+" to make chgFast: "+oldVS.matcher.getKey(parent)
          + ", foo: "+ oldVS.matcher.getCS(oldVS.matcher.getKey(parent)));

 ...

AreaSelectingView2D:: parent: 199 to make chgFast: Norg.fenfire.util.Pair@3188c9d9, foo: -1

So, 199 == -1?


Should I have guess that this works only if parent is cs number 0?

    public int getCS(Object key) {
        if(key == null) key = NULL;
        return getCSByKeyObject(new Key(key, 0));
    }

    public int getCS(int parent, Object key) {
        if(key == null) key = NULL;
        return getCSByKeyObject(new Key(key, parent));
    }

I understand, after some thinking, why it's so, because of recursive 
coordsystems, but it for example can be written in javadoc - thank you.

So, coorsys number <=> matching key is not true.


   -Matti




From MAILER-DAEMON Tue Jul 29 13:27:52 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hYFa-0003Ol-Ba
	for mharc-gzz-dev@gnu.org; Tue, 29 Jul 2003 13:27:02 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hYFU-00039o-UF
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 13:26:56 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hYFO-0002vz-JN
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 13:26:53 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hYFE-0002aR-GR
	for gzz-dev@mail.freesoftware.fsf.org; Tue, 29 Jul 2003 13:26:40 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6THQcJg021951;
	Tue, 29 Jul 2003 20:26:38 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6THQdAn007239;
	Tue, 29 Jul 2003 20:26:39 +0300 (EETDST)
Date: Tue, 29 Jul 2003 20:26:39 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: Matti Katila <majukati@verso.st.jyu.fi>
Subject: Re: [Gzz] Libvob: nadirCS hasn't parent.
Message-ID: <20030729172639.GK4044@tarzan.it.jyu.fi>
References: <Pine.LNX.4.44.0307291723530.15165-100000@verso.st.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0307291723530.15165-100000@verso.st.jyu.fi>
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: gzz-dev <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jul 2003 17:27:01 -0000

On Tue, Jul 29, 2003 at 05:32:05PM +0300, Matti Katila wrote:
> 
> 
> Well, I noticed this last year but perhaps forgot to mention it.
> 
> When asking parent of nadir coordinate system it returns -1 rather than 
> the one which has been rotated.
> 
> Anyone want to fix this?

Please make a failing test, I'll fix it.

	Tuomas



From MAILER-DAEMON Wed Jul 30 03:05:25 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hl0a-0008Ly-KN
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 03:04:24 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hkza-0007v3-Ed
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 03:03:22 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hkzM-0007ko-Gs
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 03:03:09 -0400
Received: from posti4.jyu.fi ([130.234.5.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hkxv-0007Ud-BK
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 03:01:39 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti4.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6U71ObR000898; 
	Wed, 30 Jul 2003 10:01:24 +0300
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
In-Reply-To: <20030729140545.GH4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
	<1059474167.17462.13.camel@io.it.jyu.fi>
	<20030729102502.GF4044@tarzan.it.jyu.fi>
	<1059475364.17462.29.camel@io.it.jyu.fi> <3F266564.70704@gmx.de>
	<20030729140545.GH4044@tarzan.it.jyu.fi>
Content-Type: text/plain
Organization: 
Message-Id: <1059548484.19008.0.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 30 Jul 2003 10:01:24 +0300
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/)
	at posti4.jyu.fi; Wed, 30 Jul 2003 10:01:26 +0300
X-Spam-Checked: by miltrassassin
	at posti4.jyu.fi; Wed, 30 Jul 2003 10:01:27 +0300
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>,
	Benja Fallenstein <b.fallenstein@gmx.de>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 07:04:22 -0000

On Tue, 2003-07-29 at 17:05, Tuomas Lukka wrote:
> On Tue, Jul 29, 2003 at 02:15:32PM +0200, Benja Fallenstein wrote:
> > Of course we can already use hierarchy, but we could also extend rst a 
> > little to make categorization more flexible. Suggestion: Add a header to 
> > rst pages::
> > 
> >     =====
> >     Title
> >     =====
> > 
> >     :Author: ...
> >     :Created: ...
> >     :Categories: Tutorials -> Fenfire project; Terms -> RDF
> > 
> > Then, in the output the categories would be hyperlinked, and there would 
> > be auto-generated summary pages; a bit like in Tim Bray's ongoing_, 
> > where articles can also be in multiple categories (example_).
> > 
> > .. _ongoing: http://www.tbray.org/ongoing/
> > .. _example: http://www.tbray.org/ongoing/When/200x/2003/07/28/SummerPix
> > 
> > I think it would be cool if it were possible to categorize everything 
> > that way, including PEGs, darts, and design documents...
> 
> I like this idea.


Me too :).



-Hermanni




From MAILER-DAEMON Wed Jul 30 03:58:24 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hlpp-00032s-EI
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 03:57:21 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hlpZ-0002PL-1c
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 03:57:05 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hloV-0001Yg-Ad
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 03:55:59 -0400
Received: from posti2.jyu.fi ([130.234.4.33])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hloU-0001V3-31
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 03:55:58 -0400
Received: from io.it.jyu.fi (hemppah@io.it.jyu.fi [130.234.160.112])
	by posti2.jyu.fi (8.12.8/8.12.8/antispam) with ESMTP id h6U7tnXB001769; 
	Wed, 30 Jul 2003 10:55:49 +0300
Subject: Re: [Gzz] Re: What is our Wiki for? (WAS: reST/Docutils Wiki and
	Navidoc)
From: Hermanni =?ISO-8859-1?Q?Hyyti=E4l=E4?= <hemppah@cc.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
In-Reply-To: <20030729140436.GG4044@tarzan.it.jyu.fi>
References: <20030729073514.GC4044@tarzan.it.jyu.fi>
	<Pine.LNX.4.44.0307291146540.25173-100000@silmu.st.jyu.fi>
	<20030729090345.GD4044@tarzan.it.jyu.fi>
	<1059474167.17462.13.camel@io.it.jyu.fi>
	<20030729102502.GF4044@tarzan.it.jyu.fi>
	<1059475364.17462.29.camel@io.it.jyu.fi>
	<20030729140436.GG4044@tarzan.it.jyu.fi>
Content-Type: text/plain
Organization: 
Message-Id: <1059551749.18999.56.camel@io.it.jyu.fi>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.2.3 
Date: 30 Jul 2003 10:55:49 +0300
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-milter (http://www.amavis.org/)
	at posti2.jyu.fi; Wed, 30 Jul 2003 10:55:50 +0300
X-Spam-Checked: by miltrassassin
	at posti2.jyu.fi; Wed, 30 Jul 2003 10:55:51 +0300
Cc: Tuukka Hastrup <Tuukka.Hastrup@iki.fi>, Asko Soukka <asko.soukka@iki.fi>,
	gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 07:57:20 -0000

On Tue, 2003-07-29 at 17:04, Tuomas Lukka wrote:
> > > 
> > > Why would wiki make a good starting point?
> > 
> > 1) Information categorization
> > We could categorize things under different categories with links (e.g.,
> > "Tutorials", "Terms", "Best practices", "Documentation",
> > "Tutorials/Fenfire project", "Tutorials/Subprojects", "Best
> > Practices/LibVob", "Best Practices/Design Patterns" "Best
> > Practices/Avoid these things", "Terms/Xanalogical model", "Terms/3D
> > programming" &c).
> > 
> > 2) Familiar interface
> > People are able to use familiar interface for viewing information, i.e.,
> > their favourite web browser.
> 
> What advantages does wiki have w.r.t. rst for either of those?
> 
> 1) This is about structuring information, not about wiki vs rst.
> 
> 2) .rst goes into html


Using different programs (i.e. interfaces) for structuring information
(editor <-> rst) and for viewing information (browser <-> html); with
wiki there's only one program for these tasks.


> 
> > > I'd think we should use .rst for those things.
> > 
> > If .rst files can do categorization then it should be fine ;).
> > 
> > > 
> > > For Wiki, the main use I see is "running commentary", i.e.
> > > "X is broken, you need to do Y right now to accomplish it" &c
> > > Anything permanent should probably be on the rst side.
> > 
> > Indeed. Wiki should *not* store anything permanent (i.e. official)
> > documents. As said, wiki would only act a starting point/quick ref place
> > where information is categorized with links to official documents for
> > more detailed (official information) information.
> 
> Why?

Starting point:
For people who join to our research group, or our own people how move
from one subproject to an another: people get started with their tasks
more quicly since there is more "mandatory" information what they should
know before doing anything.


-Hermanni




From MAILER-DAEMON Wed Jul 30 05:14:16 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hn2C-0003Hc-0b
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 05:14:12 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hn29-0003Au-IV
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 05:14:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hn27-00035c-9r
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 05:14:08 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hn26-0002mq-Cs
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 05:14:06 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6U9DxJg000886
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Wed, 30 Jul 2003 12:13:59 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6U9E0ai011471
	for gzz-dev@mail.freesoftware.fsf.org;
	Wed, 30 Jul 2003 12:14:01 +0300 (EETDST)
Date: Wed, 30 Jul 2003 12:14:00 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030730091400.GA11460@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] Incomplete PEG: fenpdf spec 1
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 09:14:10 -0000

==========================================================================
PEG fenpdf_v1_spec_1--tjl: FenPDF v1 first specification
==========================================================================

:Authors:  Tuomas J. Lukka
:Date-Created: 2003-07-28
:Last-Modified: $Date: 2003/07/30 09:11:45 $
:Revision: $Revision: 1.4 $
:Status:   Incomplete
:Stakeholders: benja, mudyc, humppake
:Scope:    Major
:Type:     Policy

.. Affect-PEGs:


We need a common vision for what FenPDF 1.0 will look like. 
Currently there are lots of good ideas, but several people
pulling in slightly different directions.

Everything in this PEG is very much under discussion - if you see
something you don't like, say it


Issues
======

- Should ``CONTENTLINK`` RDF vocabulary be included?
  We should be as conservative as possible; we shall have
  transclusions anyway.

  OTOH, clinks have their uses.

  Hmm, for v1.0 maybe we should have *either* clinks *or*
  pdf transclusions but not both?

- RDF for cursors / bookmarks? Is just two views good enough
  for browsing? Accidental severing of contacts. Need some way to get anywhere.

  PROPOSED RESOLUTION: TREETIME for now.

- "overall view" of the whole space? -- embed to 2D somehow for a map?

  RESOLVED: Later. Needs experiments first

- ``rmb_action_switch--humppake``?
  Gives more actions for the mouse, but may be confusing; the UI is definitely
  not self-explanatory then.

  RESOLVED: Later.

- Should left-button click+drag select or move?

  PROPOSED RESOLUTION: move. Shift for select. Clicking and dragging
  for moving *feels* right.

- Do we need bookmarks and overall views - would simply connecting the previous
  and next canvas and pageimagescrolls in time order?

  PROPOSED RESOLUTION: Use TREETIME and provide interface for it.

- Should the elements in the system contain their insertion time?
  As wallclock time or a tree (when merging)?

  PROPOSED RESOLUTION: Use TREETIME and provide interface for it.

- What were benja's suggestions - couldn't find a PEG

Introduction
============

This is a PEG that's different from most - it changes the whole perspective.
Instead of looking outwards and pushing the envelope, this PEG tries
for the first time to actually contain a complete working system.

This PEG will select what goes in and what does not for FenPDF 1.0.

Not having something in this feature set does certainly not mean that
it's abandoned or that it's a bad idea: it just means that we will
not include that functionality into FenPDF 1.0 even if it is implemented,
in order to keep things simple or for some other reason.

FenPDF 1.0 is kind of a "director's cut" (a term Ted sometimes used), 
and it's expected that there will be parallel versions, with different
names and identities that do almost the same thing but differently.
These are good for experiments and competition is healthy -- the same
components can be assembled differently by different people.

This spec is **extremely** conservative as to which features are taken 
in. We need a working baseline 1.0 that remains the same and functional.
We need to get *using* is asap. The policy is that we take in exactly what
*has* to be there for a working FenPDF. Including TREETIME or something like
it is because all points of the system must remain reachable.

This is the first spec PEG - once accepted, the specification here will be moved 
to the main docs/ directory and be amended only through future PEGs.

Note that evolution of the FenPDF PEG is not the only way to add new features
and e.g. canvas / document types. FenPDF is only the first applitude 
we will try to settle. There will be others (fencode, fenwrite, ... ?) which
will operate within the same graph.

Structure
=========

In a sense, this the most important part of this PEG: this part specifies
the structure that will be used within our research group when test-using
fenpdf. No other RDF nodes will be allowed in the common data base, until
the next version of FenPDF (1.1?), or v1.0 of some other applitude is defined.

Everyone may use their own user interfaces, but the shared structure is
set in stone here.

RDF
---

The structure behind FenPDF consists 
of the RDF structure in ``CANVAS2D``, ``FF``, ``RDF`` (type), and ``STRUCTLINK``.

As long as FenPDF is the only applitude used,
all other RDF words are either randomly generated ``urn-5`` words or literals.

This means that the structure is: 

- Canvases containing nodes at specific locations

- directional links between nodes

- contents for the nodes

Xanalogical
-----------

As this is FenPDF, version 1.0 will support only text and page spans.
Content links will not be supported, only transclusions.
For text spans, URN5 text spans will be used - storing the keystrokes
in their own blocks is an extra complication for now.

User interface
==============

While the Structure was an important part, the user interface is the most *difficult* one.
There are several possible directions and we need to select one for FenPDF 1.0.

One that we will provide as a backwards-compatibility option in later versions of FenPDF
if it is seen to be good.

Requirements
------------

- Need to be able to easily get whole PDF zoomed, without bg, easily movable

- Easily get 2-view mode for linking 

- Attach custom controllers easily

- should be possible to figure out without manual

- easy to insert new PDFs - error handling?

    - pool control

- history path accessible

- buoys carefully tuned: no clutter, easy to understand and control

    - debug mode: show where buoy locations come from!

- easy switch between fullscreen and windowed mode - window size taken 
  into account naturally

Overall visuals
---------------

Whatever is under the cursor *shall* show it somehow, e.g. main view by slightly changing color 
of irregu edges, text nodes by lightening, etc. *EVERYTHING* must do this.

Foci
----

Two foci, shown on top 

Buoy placement
--------------

There are several different kinds of buoys in this system:

Canvas-Canvas
    These are directed and can occur on either side.
    The buoy should show some context but not too much
    to avoid going to too small zoom.

Canvas-PDF Transclusion
    Always to the right.
    Max. 20 pages of the whole document are shown.
    

PDF-Canvas Transclusion
    Always to the left
    Here, enough context needs to be shown since the transclusion 
    is just the same as the anchor.



Bindings
--------

Left mouse button:
    
    click
	go to

    click + drag on main view
	pan

    shift + click + drag on main view
	select

    click + drag on a selection in main view
	drag into other view for creating transclusion


Right mouse button:
    
    click + drag on main view
	adjust zoom. Up = zoom out, down = zoom in.

    click
	context menu

middle mouse button:

    click + drag anywhere
	move view separator up / down

    click on main view
	X11 paste to insertion cursor

Context Menus
-------------

On struct-connected buoys: "Unlink this buoy"

For any object, "Delete this X" where X is "Text", "Paper", "PDF file", "transclusion"


Visible buttons
---------------

Action buttons everywhere:

    Import PS/PDF

    New paper

    Save

    Quit

Toggles everywhere:

    Fancy papers

Toggles in pdf mode:

    Reading zoom

These buttons shall have the ubiquitous 3D look, with the toggles having
the old Tk look, with a square in them that is lit or unlit based on the state
(need to distinguish between buttons and toggles somehow).

They shall react to mouseovers and mouse clicks instantly with visual feedback.

The buttons shall be placed to the upper left corner, stacked vertically, and shall
be relatively small (10-15pixels high)

Some space between action buttons and toggles.

Versioning / Merging
====================






From MAILER-DAEMON Wed Jul 30 07:57:37 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hpaL-0003SY-BD
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 07:57:37 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hpaJ-0003Py-27
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 07:57:35 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hpa6-00032F-ST
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 07:57:23 -0400
Received: from posti.it.jyu.fi ([130.234.160.33] helo=mailhost.it.jyu.fi)
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hpZz-0002gT-7y
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 07:57:15 -0400
Received: from tarzan.mit.jyu.fi (tarzan.private [172.16.160.40])
	by mailhost.it.jyu.fi (8.12.9/8.12.9) with ESMTP id h6UBvDJg009702
	for <gzz-dev@mail.freesoftware.fsf.org>;
	Wed, 30 Jul 2003 14:57:13 +0300 (EETDST)
Received: (from lukka@localhost)
	by tarzan.mit.jyu.fi (8.12.9/8.12.9/Submit) id h6UBvGXf012226
	for gzz-dev@mail.freesoftware.fsf.org;
	Wed, 30 Jul 2003 14:57:16 +0300 (EETDST)
Date: Wed, 30 Jul 2003 14:57:16 +0300
From: Tuomas Lukka <lukka@mit.jyu.fi>
To: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <20030730115716.GB11460@tarzan.it.jyu.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.4i
X-Virus-Scanned-By: amavisd-milter at it.jyu.fi
Cc: 
Subject: [Gzz] Why Pair keys?!?
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 11:57:35 -0000

CVS says that benja or mudyc is the author of the following code in CanvasView2D
(I'm not sure)

	while (iter.hasNext()) {
	    Object n = iter.next();
	    if (dbg) p("placeable object: "+n);
	    org.nongnu.libvob.lava.placeable.Placeable p = 
		    (org.nongnu.libvob.lava.placeable.Placeable)nodeView.f(fen.constgraph, n);

	    int cs = vs.coords.orthoBox(paper2screen, 0,1,2,3,4,5,6);
	    vs.matcher.add(matchingParent, cs, new Pair(container, n));
	    vs.activate(cs);

	    if(cull) {
		cs = vs.cullCS(cs, "CULL", box2screen);
	    }
	    p.place(vs, cs);
        }


Generating new Pair objects
in the innermost loop for all nodes is *not* acceptable.
It makes view generation much less efficient and gives a lot more work
to the GC, which is especially an issue on kaffe.

Could the author please explain why this is necessary?
I'm sure we can find a way around this, such as going to 
a hierarchical structure with the matchingParent, i.e. first
one dummy coordsys after matchingParent with the container as the key
and after that, the node..

	Tuomas



From MAILER-DAEMON Wed Jul 30 12:48:17 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hu0q-000309-N9
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 12:41:16 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hu0j-0002uW-0R
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 12:41:09 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19htsZ-0008ES-Fp
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 12:32:45 -0400
Received: from verso.st.jyu.fi ([130.234.4.66])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19htq1-0007Yv-5d
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 12:30:05 -0400
Received: from verso.st.jyu.fi (localhost.localdomain [127.0.0.1])
	by verso.st.jyu.fi (8.12.8/8.12.8) with ESMTP id h6UGTsND010099;
	Wed, 30 Jul 2003 19:29:54 +0300
Received: from localhost (majukati@localhost)
	by verso.st.jyu.fi (8.12.8/8.12.8/Submit) with ESMTP id h6UGTs16010095; 
	Wed, 30 Jul 2003 19:29:54 +0300
Date: Wed, 30 Jul 2003 19:29:53 +0300 (EEST)
From: Matti Katila <majukati@verso.st.jyu.fi>
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Why Pair keys?!?
In-Reply-To: <20030730115716.GB11460@tarzan.it.jyu.fi>
Message-ID: <Pine.LNX.4.44.0307301916120.15165-100000@verso.st.jyu.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 16:41:15 -0000

On Wed, 30 Jul 2003, Tuomas Lukka wrote:
> CVS says that benja or mudyc is the author of the following code in CanvasView2D
> (I'm not sure)
> 
> 	while (iter.hasNext()) {
> 	    Object n = iter.next();
> 	    if (dbg) p("placeable object: "+n);
> 	    org.nongnu.libvob.lava.placeable.Placeable p = 
> 		    (org.nongnu.libvob.lava.placeable.Placeable)nodeView.f(fen.constgraph, n);
> 
> 	    int cs = vs.coords.orthoBox(paper2screen, 0,1,2,3,4,5,6);
> 	    vs.matcher.add(matchingParent, cs, new Pair(container, n));
> 	    vs.activate(cs);
> 
> 	    if(cull) {
> 		cs = vs.cullCS(cs, "CULL", box2screen);
> 	    }
> 	    p.place(vs, cs);
>         }
> 
> 
> Generating new Pair objects
> in the innermost loop for all nodes is *not* acceptable.
> It makes view generation much less efficient and gives a lot more work
> to the GC, which is especially an issue on kaffe.
> 
> Could the author please explain why this is necessary?

Tested it and using:
   vs.matcher.add(matchingParent, cs, n);
didn't work, perhaps the key is already used in somewhere.
It can be that  
   vs.matcher.add(matchingParent, foo, container);
doesn't either work..

> I'm sure we can find a way around this, such as going to 
> a hierarchical structure with the matchingParent, i.e. first
> one dummy coordsys after matchingParent with the container as the key
> and after that, the node..

Please be handy and fix it. It would be a good lesson for me to understand 
the VobMatcher.


   -Matti




From MAILER-DAEMON Wed Jul 30 14:01:44 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hvEa-0004s9-0G
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 13:59:32 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hvDo-0004J2-Np
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 13:58:44 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hvDT-0003SC-Ju
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 13:58:26 -0400
Received: from siaag1ad.compuserve.com ([149.174.40.6])
	by monty-python.gnu.org with esmtp (Exim 4.20) id 19hvBD-0001lR-1z
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 13:56:03 -0400
Received: (from mailgate@localhost)
	by siaag1ad.compuserve.com (8.12.9/8.12.7/SUN-2.7) id h6UHtxhL026493
	for gzz-dev@mail.freesoftware.fsf.org;
	Wed, 30 Jul 2003 13:55:59 -0400 (EDT)
Date: Wed, 30 Jul 2003 13:55:50 -0400
From: Marlene Mallicoat <MarleneM@compuserve.com>
Sender: Marlene Mallicoat <MarleneM@compuserve.com>
To: GZZ developers <gzz-dev@mail.freesoftware.fsf.org>
Message-ID: <200307301355_MC3-1-4523-7557@compuserve.com>
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	 charset=ISO-8859-1
Content-Disposition: inline
Cc: 
Subject: [Gzz] Hyperstructure workshop at HyperText '03 Conference
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 17:59:29 -0000

Hi, All --

Please check out =


http://www.ht03.org/workshops.html#zigzag

Hope to see some of you there!
Marlene



From MAILER-DAEMON Wed Jul 30 14:07:36 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19hvMI-00019E-8D
	for mharc-gzz-dev@gnu.org; Wed, 30 Jul 2003 14:07:30 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19hvMB-0000jr-7Q
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 14:07:23 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19hvM4-0000Mm-9r
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 14:07:17 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19hvLm-0007yN-Ed
	for gzz-dev@mail.freesoftware.fsf.org; Wed, 30 Jul 2003 14:06:58 -0400
Received: (qmail 27762 invoked by uid 65534); 30 Jul 2003 18:06:56 -0000
Received: from pD9E12FCB.dip.t-dialin.net (EHLO gmx.de) (217.225.47.203)
	by mail.gmx.net (mp023) with SMTP; 30 Jul 2003 20:06:56 +0200
Message-ID: <3F2808D8.9020803@gmx.de>
Date: Wed, 30 Jul 2003 20:05:12 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: Marlene Mallicoat <MarleneM@compuserve.com>
Subject: Re: [Gzz] Hyperstructure workshop at HyperText '03 Conference
References: <200307301355_MC3-1-4523-7557@compuserve.com>
In-Reply-To: <200307301355_MC3-1-4523-7557@compuserve.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: GZZ developers <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Jul 2003 18:07:29 -0000

Marlene Mallicoat wrote:
> Hi, All --
> 
> Please check out 
> 
> http://www.ht03.org/workshops.html#zigzag

Ouch, I wasn't aware of the CFP / deadline (today)...

Anyway, I'm looking forward to the workshop.
- Benja




From MAILER-DAEMON Thu Jul 31 11:03:46 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19iEy2-00006C-2y
	for mharc-gzz-dev@gnu.org; Thu, 31 Jul 2003 11:03:46 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19iEy0-00005d-7l
	for gzz-dev@mail.freesoftware.fsf.org; Thu, 31 Jul 2003 11:03:44 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19iExx-0008WP-Vy
	for gzz-dev@mail.freesoftware.fsf.org; Thu, 31 Jul 2003 11:03:43 -0400
Received: from mail.gmx.de ([213.165.64.20] helo=mail.gmx.net)
	by monty-python.gnu.org with smtp (Exim 4.20) id 19iExx-0008WF-Cx
	for gzz-dev@mail.freesoftware.fsf.org; Thu, 31 Jul 2003 11:03:41 -0400
Received: (qmail 31593 invoked by uid 65534); 31 Jul 2003 15:03:39 -0000
Received: from p5082D1B6.dip.t-dialin.net (EHLO gmx.de) (80.130.209.182)
	by mail.gmx.net (mp022) with SMTP; 31 Jul 2003 17:03:39 +0200
Message-ID: <3F292F64.80807@gmx.de>
Date: Thu, 31 Jul 2003 17:01:56 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: Tuomas Lukka <lukka@mit.jyu.fi>
Subject: Re: [Gzz] Incomplete PEG: fenpdf spec 1
References: <20030730091400.GA11460@tarzan.it.jyu.fi>
In-Reply-To: <20030730091400.GA11460@tarzan.it.jyu.fi>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: gzz developers list <gzz-dev@mail.freesoftware.fsf.org>
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2003 15:03:44 -0000

Tuomas Lukka wrote:
> This spec is **extremely** conservative as to which features are taken 
> in. We need a working baseline 1.0 that remains the same and functional.
> We need to get *using* is asap.

Ok.

> The policy is that we take in exactly what
> *has* to be there for a working FenPDF. Including TREETIME or something like
> it is because all points of the system must remain reachable.

ISSUE: How is TREETIME supposed to be *shown*?

> Note that evolution of the FenPDF PEG is not the only way to add new features
> and e.g. canvas / document types. FenPDF is only the first applitude 
> we will try to settle. There will be others (fencode, fenwrite, ... ?) which
> will operate within the same graph.

I don't think 'applitude' is a good word because FenPDF will (at least 
initially) be a separate application and even released separately.

In German, we have "Auskopplung" for a single from a music album that 
was released separately. I don't know what the corresponding English 
word is.

> In a sense, this the most important part of this PEG: this part specifies
> the structure that will be used within our research group when test-using
> fenpdf. No other RDF nodes will be allowed in the common data base, until
> the next version of FenPDF (1.1?), or v1.0 of some other applitude is defined.

Why?!? This makes no sense. We picked RDF because having extra 
connections aren't a problem for interpreting the connections you do 
understand.

I think that this should more sensibly read, FenPDF may not create other 
stuctures besides those specified here.

> RDF
> ---
> 
> The structure behind FenPDF consists 
> of the RDF structure in ``CANVAS2D``, ``FF``, ``RDF`` (type), and ``STRUCTLINK``.

The clone issue must be resolved before we can set this in stone.

> As long as FenPDF is the only applitude used,
> all other RDF words are either randomly generated ``urn-5`` words or literals.

Why? I can see no reason for specifying this.

> This means that the structure is: 
> 
> - Canvases containing nodes at specific locations
> - directional links between nodes
> - contents for the nodes

Yes.

> Xanalogical
> -----------
> 
> As this is FenPDF, version 1.0 will support only text and page spans.
> Content links will not be supported, only transclusions.

Will transclusions of *text* be supported, and if so, how?

> For text spans, URN5 text spans will be used - storing the keystrokes
> in their own blocks is an extra complication for now.

Good.

> While the Structure was an important part,

s/was/is/
s/part/issue/

> the user interface is the most *difficult* one.
> There are several possible directions and we need to select one for FenPDF 1.0.
> 
> One that we will provide as a backwards-compatibility option in later versions of FenPDF
> if it is seen to be good.

Verb missing. Do you mean "We will provide..."? (Or is this a 
continuation of the last sentence? Then you should only put a comma 
between them and not start a new para, that's confusing...)

> - easy to insert new PDFs - error handling?
> 
>     - pool control

Pool control? What? How?

>     - debug mode: show where buoy locations come from!

? explain

> Whatever is under the cursor *shall* show it somehow, e.g. main view by slightly changing color 
> of irregu edges, text nodes by lightening, etc. *EVERYTHING* must do this.

Nice idea. Probably everything should show it in the same way though: by 
lightening up.

> Foci
> ----
> 
> Two foci, shown on top 

Which layout? I'd like it to be like currently, so that the lower one is 
wider and "panel-like," and the lower one cannot show PDFs.

The "Home" key and a "Home" button usable with mouse should move the 
lower focus to a starting-point-canvas, which would normally also be the 
root of the TREETIME time tree, making it a good starting place to get 
to every canvas and PDF out there.

> There are several different kinds of buoys in this system:
> 
> Canvas-Canvas
>     These are directed and can occur on either side.
>     The buoy should show some context but not too much
>     to avoid going to too small zoom.

Should mention that this is created for STRUCTLINKs and nothing else.

> Bindings
> --------
> 
> Left mouse button:
>     
>     click
> 	go to
> 
>     click + drag on main view
> 	pan

"On main view?" What is "main view"? It seems unnatural that this 
wouldn't work on *all* views.

>     shift + click + drag on main view
> 	select

On a PDF, this is clear. On a canvas, what does it mean? Does it select 
a piece of the canvas, or a group of spans on the canvas? If I start 
selecting inside a text node, do I select a rectangle or a span of text?

>     click + drag on a selection in main view
> 	drag into other view for creating transclusion

Why only in other view? Why not be able to transclude to same view?

Or, oh, do you assume that only page spans can be cloned, and they can 
only be cloned from the PDF onto a canvas? That would make perfect sense 
and invalidate all three points above. If you mean that, please make it 
clear, then the above issues should have been taken care of.


ISSUE, though: I don't like the overloading of click+drag. Isn't there a 
  better way? Maybe Shift+drag to create the transclusion after 
selecting? Hm.

ISSUE: What actions *destroy* the current selection (unselect it)? 
Should every click destroy the selection? (Even panning?) If so, maybe 
the click+drag to create transclusion could be tolerable.

Also, ISSUE: Shift+click+drag is certainly not something you can figure 
you can just figure out (see requirements). What to do about that?

> Right mouse button:
>     
>     click + drag on main view
> 	adjust zoom. Up = zoom out, down = zoom in.

ISSUE: How to adjust pan? (Key binding?)

> middle mouse button:
> 
>     click + drag anywhere
> 	move view separator up / down

How do do this without middle button?

>     click on main view
> 	X11 paste to insertion cursor

ISSUE: You don't discuss how to create structlinks!

ISSUE: This describes only mouse bindings. How does the keyboard work? 
How is a new node created? How do I edit an existing node? Is a text 
cursor shown, and when, and how does it work? These need to be specified.

ISSUE: How to move nodes on a canvas? Rearrangement seems quite 
important, so it would be bad to leave it to a later version.

ISSUE: Can I enter text in both foci, or only in one?

(Actually it would be better to say "focus" everywhere and to say "view" 
nowhere, except to distinguish between "PDF reading" and "structure 
browsing/editing" view.)

> Context Menus
> -------------
> 
> On struct-connected buoys: "Unlink this buoy"

ISSUE: How to unlink two nodes on same paper?

> For any object, "Delete this X" where X is "Text", "Paper", "PDF file", "transclusion"

Shouldn't it also be "Delete this link," then?

> Visible buttons
> ---------------
> 
> Action buttons everywhere:
> 
>     Import PS/PDF
> 
>     New paper
> 
>     Save
> 
>     Quit

Make that "Save & Quit"

Add "Home" or "Go home" button.

> Toggles everywhere:
> 
>     Fancy papers

s/Fancy papers/Show backgrounds

> Toggles in pdf mode:
> 
>     Reading zoom

What is "PDF mode"? I think the toggle should be shown whenever a PDF is 
focused.

> These buttons shall have the ubiquitous 3D look, with the toggles having
> the old Tk look, with a square in them that is lit or unlit based on the state
> (need to distinguish between buttons and toggles somehow).

I don't understand your description of the toggle look. How about using 
the universal checkbox look?

> They shall react to mouseovers and mouse clicks instantly with visual feedback.

Mouseovers: lighting up.

> The buttons shall be placed to the upper left corner, stacked vertically, and shall
> be relatively small (10-15pixels high)

Hm, not sure whether this is big enough to be easily readable...

> Issues
> ======
> 
> - Should ``CONTENTLINK`` RDF vocabulary be included?
>   We should be as conservative as possible; we shall have
>   transclusions anyway.

I think it would be ok not to have content links.

>   OTOH, clinks have their uses.
> 
>   Hmm, for v1.0 maybe we should have *either* clinks *or*
>   pdf transclusions but not both?

If we have content links but not PDF transclusions, we need content 
links to text -> bit difficult to show.

Or, a way to make a link between a node and an enfilade. That could 
actually be good... hm. To the user, it would be functionally very 
similar to a structlink.

Transclusion is probably better if we have only one of the two, but 
having both would also be good.

If we have clinks, when the user has selected a piece of PDF, it would 
be good to have a "Create link" button which creates a new paper with an 
empty node that's linked to the PDF. Actually, would also be good to 
have this when the user is on a canvas and has selected a text node. 
Then this would be a simple, universal way of creating a new annotation 
to something.

Or maybe "make paper" should always work like this if there's a selected 
node? When making a new paper, you almost always want it to be linked to 
the current paper?

For text nodes it could also be in the context menu (if we don't have a 
way to select them in the interface)...

> - RDF for cursors / bookmarks?

Don't! The panel focus with a "home" canvas takes care of this.

>   Is just two views good enough
>   for browsing? Accidental severing of contacts. Need some way to get anywhere.
> 
>   PROPOSED RESOLUTION: TREETIME for now.

Fine.

> - Should left-button click+drag select or move?
> 
>   PROPOSED RESOLUTION: move. Shift for select. Clicking and dragging
>   for moving *feels* right.

Although that's definitely true, click+drag for select is easy to figure 
out (clashes with one of the requirements), and click and drag for 
moving isn't *necessary*: you can archieve the same goal with just 
clicking where you want to go...

Strawperson alternative proposal: Left drag selects. Right drag pans. 
Middle drag or Shift+drag zooms. Ctrl+drag changes size of foci (or 
alternatively, changing focus size isn't possible in FenPDF 1). In this 
proposal, it would be much easier to figure out enough of the whole 
system to do full editing.

> - What were benja's suggestions - couldn't find a PEG

Which ones?

- Benja




From MAILER-DAEMON Thu Jul 31 12:12:30 2003
Received: from list by monty-python.gnu.org with archive (Exim 4.20)
	id 19iG21-0005UC-Sx
	for mharc-gzz-dev@gnu.org; Thu, 31 Jul 2003 12:11:57 -0400
Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.20)
	id 19iG0Y-0005B5-Hr
	for gzz-dev@nongnu.org; Thu, 31 Jul 2003 12:10:26 -0400
Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.20)
	id 19iFzr-0004dp-0i
	for gzz-dev@nongnu.org; Thu, 31 Jul 2003 12:09:44 -0400
Received: from mail.gmx.net ([213.165.64.20])
	by monty-python.gnu.org with smtp (Exim 4.20) id 19iFzo-0004Zf-JX
	for gzz-dev@nongnu.org; Thu, 31 Jul 2003 12:09:40 -0400
Received: (qmail 9162 invoked by uid 65534); 31 Jul 2003 16:09:38 -0000
Received: from p5082D1B6.dip.t-dialin.net (EHLO gmx.de) (80.130.209.182)
	by mail.gmx.net (mp012) with SMTP; 31 Jul 2003 18:09:38 +0200
Message-ID: <3F293EDD.8070405@gmx.de>
Date: Thu, 31 Jul 2003 18:07:57 +0200
From: Benja Fallenstein <b.fallenstein@gmx.de>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US;
	rv:1.4) Gecko/20030714 Debian/1.4-2
X-Accept-Language: en
MIME-Version: 1.0
To: =?UTF-8?B?SGVybWFubmkgSHl5dGnDpGzDpA==?= <hemppah@cc.jyu.fi>, 
	GZZ developers <gzz-dev@nongnu.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: 
Subject: [Gzz] Available overlays PEG
X-BeenThere: gzz-dev@nongnu.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: Gzz developers  <gzz-dev.nongnu.org>
List-Unsubscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://mail.gnu.org/pipermail/gzz-dev>
List-Post: <mailto:gzz-dev@nongnu.org>
List-Help: <mailto:gzz-dev-request@nongnu.org?subject=help>
List-Subscribe: <http://mail.nongnu.org/mailman/listinfo/gzz-dev>,
	<mailto:gzz-dev-request@nongnu.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Jul 2003 16:11:56 -0000

> ==========================================================================
> PEG available_overlays--hemppah: Available overlays
> ==========================================================================
> 
> :Authors:  Hermanni HyytiÃ¤lÃ¤
> :Date-Created: 2003-06-18
> :Last-Modified: $Date: 2003/07/31 12:56:11 $
> :Revision: $Revision: 1.39 $
> :Status:   Current
> :Scope:    Major

(I agree that the scope of this PEG is major, but it doesn't actually 
fit the definition of "Major:" it's not true that "most code needs a 
touchup." ``pegboard_format--tjl`` should probably be changed to say 
something like, "A fundamental change" or something.)

> :Type:     Architecture

I don't agree with this: While changing the used overlay would be a big 
change, it's still an implementation change, not an architectural change.

> :Stakeholders: tjl, benja
> .. Affect-PEGs:

Please fix the syntax here (line missing, see the compiled version for 
error msg). Actually, I think "current" PEGs shouldn't have any 
commented out fields like this-- the ".. Affect-PEGs" field should 
simply be removed.

> The purpose of this PEG document is to give a short overview of existing structured
> P2P overlays which have an open source implementation. 

Not true: At the end, you specify that we shall change to Tapestry. You 
should say so at this point, already.

If you intend this PEG to make a no decision, only a recommendation, 
then you could e.g. say,

     This PEG gives an overview of existing P2P overlays which have
     an open source implementation. Based on the overview, it
     recommends the Tapestry_ overlay to be used in Storm.

(link to review of Tapestry)

> The reason for creating this PEG document is that the current implementation 
> of GISP [5]_ seems to have (too) many obvious security exploits. Therefore we need 
> to examine other available structured overlays which have an open source 
> implementation in hope for finding a more mature P2P platform. 

s/ in hope for finding/in the hope to find/

> The list of implemented overlays is as of July 2003.
> 
> Issues
> ======
> 
> None.
> 
> Terminology
> ===========
> 
> This section briefly covers the terminology used in this document. 
> 
> Abstractions
>     The following text for the abstraction definitions is taken from 
>     `Towards a Common API for Structured P2P Overlays`_ by Frank Dabek et al.
> 
> .. _DHT: 
> 
>     DHT
>         The DHT abstraction provides the same functionality as a 
>         traditional hashtable, by storing the mapping between a
>         key and a value. This interface implements a simple store
>         and retrieve functionality, where the value is always stored
>         at the live overlay node(s) to which the key is mapped by
>         the KBR layer. Values can be objects of any type. For ex-ample, the DHT 
>         implemented as part of the DHash inter-face in CFS stores 
>         and retrieves single disk blocks by their content-hashed keys.

s/ex-ample/example/
s/inter-face/interface/

> .. _DOLR:
> 
>     DOLR
>         The DOLR abstraction provides a decentralized direc-tory

s/direc-tory/directory/

>         service. Each object replica (or endpoint) has an
>         objectID and may be placed anywhere within the system.
>         Applications announce the presence of endpoints by pub-lishing

s/pub-lishing/publishing/

>         their locations. A client message addressed with
>         a particular objectID will be delivered to a nearby end-point

s/end-point/endpoint/, I think.

>         with this name. Note that the underlying distributed
>         directory can be implemented by annotating trees associ-ated
>         with each objectID; other implementations are pos-sible.

assoc-iated, pos-sible.

>         One might ask why DOLR is not implemented on
>         top of a DHT, with data pointers stored as values; this is
>         not possible because a DOLR routes messages to the near-est
>         available endpoint providing a locality property not
>         supported by DHTs. An integral part of this process is the
>         maintenance of the distributed directory during changes
>         to the underlying nodes or links.

near-est

It's not clear to me from the above if and how a DHT can be implemented 
on top of a DOLR. Since we need a DHT for indexing, this is important. 
(For downloading blocks, we can use DOLR.)

> Redundancy
>     What techniques are used for redundancy     
> 
> Fault tolerance against hostile nodes
>     What techniques are used against hostile nodes    

These aren't useful definitions. Either provide a definition that's not 
only the words reordered, or don't provide any definition at all :-)

As a reader, I don't like to read lots of definitions before the actual 
content of the document starts, so define only what you really think has 
to be defined :-)

What do you *mean* by "redundancy," though? Maybe you should use "Fault 
tolerance against node failures?"

> Implemented overlays
> ====================
> 
> In this section we list the structured P2P overlays which have an open source
> implementation. Please notice

s/notice/note/

> that features described for each implementation 
> are deliberately kept as short as possible.

"that the description of each implementation's features is"

> For more depth information about the 
> overlays we suggest reading the original publications.

s/depth/in-depth/

> Chord [1]_
> ----------

I'd prefer if, instead of using a footnote, you simply gave the homepage 
of a project as one point below, i.e., "Abstraction, home page, 
redundancy..."

> Abstraction
>     DHT_/DOLR_
> 
> Redundancy
>     Replication, backup links.

What is "backup links?"

> Fault tolerance against hostile nodes
>     (undefined)

What do you mean by "undefined"???

> Activity of development

It would be good if you put language and license before this, because 
they're most important in evaluating the applicability of an overlay.

> Developer
>     MIT (research community)

What do you mean by "(research community)"? You use this again, below, 
but you never explain what you mean by it.

> License
>     BSD-like

`Advertisement clause`__ or not?

__ http://www.gnu.org/licenses/license-list.html#OriginalBSD

> Other notes
>     No support for network locality- do not take network latencies into account
>     when building neighbor links.

s/-/--/
s/do not/does not/

How does it implement DOLR if it doesn't support locality?

> Tapestry [2]_
> --------------
> 
> Abstraction
>     DOLR_
> 
> Redundancy
>     According to `Tapestry: A Resilient Global-scale Overlay for Service
>     Deployment`_:
> 
>         Tapestry is highly resilient under dynamic conditions,
>         providing a near optimal success rate for requests
>         under high churn rates, and quicly recovering from
>         massive membership events in under a minute.

This doesn't list *techniques* (as per your defn above), it says how 
useful the developers believe their techniques to be. You should 
probably change the defn (or leave it out).

s/quicly/quickly/, or add "[sic]"
>     
>     According to the Tapestry [2]_ website:
> 
>         Tapestry offers fault-resilient mechanisms for both object 
>         location and point to point message delivery.  For object location, 
>         Tapestry generates a small number of deterministic and independent 
>         GUIDs for each object.  An object server publishes an object's 
>         availability on all of its GUIDs, and a client issues Tapestry locate 
>         requests for all of the object GUIDs in parallel.  This greatly 
>         increases availability under fault conditions, while improving 
>         general performance and reducing performance variability.  For point 
>         to point message delivery, Tapestry provides pre-calculated backup 
>         routes at each overlay hop.  UDP soft-state beacons measure up-to-date 
>         link conditions. Tapestry uses such information and simple fault-avoidance 
>         protocols to route messages around failures, providing successful 
>         delivery with high probability if a path between the endpoints exists.

I think the stuff about message delivery doesn't apply to us, so you 
could edit that out.

> Fault tolerance against hostile nodes
>     * PKI is used while creating node identifiers
>     * MACs are used to maintain integrity of overlay traffic
>     * Monitoring system for maintaining neighbor links

Explain how this helps against hostile nodes, which is the most 
important part of this PEG after all.

> Activity of development
...
>      According to the Tapestry [2]_ website, Tapestry Version 2.0 contains the 
>      following new functionality::

How is this relevant for "Activity of development"?

> Language
>     Java (Sun JDK 1.3 or a compatible Java Development and Runtime environment).
>     The Java interface libraries for the BerkeleyDB database 

How about Kaffe?

Can Tapestry run without JNI?

> Other notes
>     Support for network locality when building neighbor links.
> 
>     Why Oceanstore_ uses Tapestry [2]_? 

Don't pose rethorical questions like this-- it doesn't look good. Say 
"Reasons why Oceanstorage uses Tapestry:" instead.

>     See http://www.oceanstore.org/info/whytapestry.html 

This page is entitled, "Why Do We Need Locality?", though, not "Why do 
we use Tapestry."

> Kademlia [3]_
> -------------
> 
> Abstraction
>     DHT_
> 
> Redundancy
>     No simulation or test results published (not even in the original publication)

Replace ")" by ")."

>     In *theory*, however, the "free-choice" feature
>     gives peers freedom to adapt different conditions. However, the
>     author of SharkyPy says:

Link "SharkyPy" to the product, and if possible, link "says" to the 
source of the quote.

>         Kademlia has (in my taste, that's why I decided to drop it) a bad
> 	hole which makes it's use in remote querying for packets pretty useless:

Don't  indent first line of blockquote.

> 	When you have key->value mappings, which have an equal key, in even in
> 	semi-large networks it gets very unprobable that you get all mappings,
> 	the more hosts there are, the less probable it is, and the more mappings
> 	there are, the less probable it is too. I've tried to remedy this in a
> 	later implementation, at the cost of lookup speed, but have never
> 	managed to get all entries when the network had over 100 nodes. (the
> 	later implementation is based on my own server-framework and uses no
> 	threads, btw.) This made it unusable for me, as basically I basically
> 	had to change the lookup-algorithm to query all nodes (back to gnutella,
> 	then...), to get all answers. And that's what is important in the
> 	network I designed it for.

Wow. That's pretty much a killer for us.

Any response from the authors?

> Activity of development
>     Java development discontinued, C++ version
>     is under development.

Not released, right?

> GISP [5]_
> ---------
> 
> Abstraction
>     DHT_/DOLR_
> 
> Redundancy
>     Chord [1]_-like (since GISP uses similar routing tables as Chord)

If that only boils down to saying, "Replication, backup links," then I 
think replicating that here is shorter than saying it's Chord-like ;-)

> Fault tolerance against hostile nodes
>     Based on our own initial experiments: the fault tolerance
>     is relatively weak - no specific techiques used.

Uh, which experiments?

> Other notes
>     Uses 10x more cache as Chord [1]_ for routing table.

Why does it? Source?

> MLDonkey [8]_
> -------------
> 
> Abstraction
>     DHT_ (Kademlia [3]_ algorithm)
> 
>     (MLDonkey [8]_ is compatible with Overnet_, and Overnet claims that it does 
>     Kademlia [3]_ and multisource downloading)

As you discuss the two Pastry impls together, you should probably do the 
same with Overnet.

> Redundancy
>     Not known (we can imagine that redundancy is relatively high since MLDonkey
>     is widely deplyed)
> 
> Fault tolerance against hostile nodes
>     Not known (we can imagine that fault tolerance is relatively high since MLDonkey
>     is widely deplyed)

I don't think that we can just assume that...

BTW, the author of Overnet was very unhappy about MLDonkey deploying the 
protocol because they thought it slowed down the network or something, 
and they called MLDonkey machines "rogue peers." So such "rogue peers" 
can apparently cause problems, even if they are programmed by a benign 
(but ignorant) programmer.


> Language
>     Objective-Caml (a compiler, not a interpreter)

s/a compiler, not a interpreter/compiled, not interpreted/

Objectiv-Caml is a language, not a compiler.

Other notes: It would be good to know how hard it would be to use 
MLDonkey's DHT routing mechanism separately (ask programmers?).

> SharkyPy [9]_
> -------------
>         This implementation is heavily based on threads, which makes it
> 	pretty resource-intensive on the computer it is running on. I never

Don't indent first line, please.

> Changes
> =======
> 
> While reviewing the different features of open source implementations of 
> structured P2P overlays we can conclude that Tapestry seems to be the most
> mature currently available. Specifically, other implementations
> lack of features w.r.t. redundancy and fault tolerance that the Tapestry
> implementation currently supports. Other reasons for choosing Tapestry in order of 
> importance:
> 
> - The license
> - The activity of development
> - The implementation language
> 
> As a result, we recommend using Tapestry's open source implementation with Storm.
> For detailed changes and information about using Tapestry with Storm, please
> see the `storm_with_tapestry--hemppah` PEG document.

s/with Storm/for use in Storm/. Use double backticks for the PEG name.

The meaning of "For detailed changes please see" isn't clear to me. Does 
acceptance of this PEG mean that storm_with_tapestry--hemppah is also 
accepted? Maybe say, "For a detailed list of changes necessary to use 
Tapestry in Storm, see..."

``storm_with_tapestry--hemppah`` isn't an accepted PEG; maybe should 
refer to it as "pending PEG" or something...

Link the PEG, don't just give its name.

> .. _`Towards a Common API for Structured P2P Overlays`: http://www.cs.berkeley.edu/~ravenben/publications/pdf/apis.pdf
> .. _`Tapestry: A Resilient Global-scale Overlay for Service Deployment`: http://www.cs.berkeley.edu/~ravenben/publications/pdf/tapestry_jsac.pdf

You don't need the back-ticks here.

For reading as text, it would be good to have the link URIs closer to 
the actual links in the document.

- Benja




