[Gzz-commits] manuscripts/SemFen article.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/02 01:11:15

Modified files:
        SemFen         : article.rst 

Log message:
        comment

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/SemFen/article.rst.diff?tr1=1.21&tr2=1.22&r1=text&r2=text

Patches:
Index: manuscripts/SemFen/article.rst
diff -u manuscripts/SemFen/article.rst:1.21 manuscripts/SemFen/article.rst:1.22
--- manuscripts/SemFen/article.rst:1.21 Thu May  1 13:52:53 2003
+++ manuscripts/SemFen/article.rst      Fri May  2 01:11:15 2003
@@ -3,7 +3,7 @@
 ==========================================================================
 
 
-.. :Stamp: $Id: article.rst,v 1.21 2003/05/01 17:52:53 benja Exp $
+.. :Stamp: $Id: article.rst,v 1.22 2003/05/02 05:11:15 tjl Exp $
 
 .. Authors: Benja Fallenstein, Tuukka Hastrup, Tuomas J. Lukka
 
@@ -46,13 +46,18 @@
 Introduction
 ============
 
+[tjl] XXX: the idea that the global graph can be constructed
+using semantic interoperability is not apparent here! *NEEDS*
+to be. Otherwise, referee: "Yes, great, but what does it have
+to do with SemWeb?"
+
 Assume that a user needs to coordinate the activities of her
 workgroup. She has at her disposal applications for email,
 project planning, scheduling appointments with her colleagues, 
 keeping track of unresolved issues, creating presentations,
 text documents, and spreadsheets.
 
-In a traitional desktop system, she will keep track of the
+In a conventional desktop system, she will keep track of the
 project's goals in one application, write them up as a
 presentation in another, schedule the presentation in a
 third application, and write the agenda in a fourth. If the
@@ -63,7 +68,7 @@
 her computer, it will be scattered across different files.
 
 In this article, we describe the design of Fenfire,
-a desktop environment allowing applications like these
+a desktop environment and framework allowing applications like these
 to be integrated into a seamless whole. 
 
 In Fenfire, all of the above applications would store
@@ -91,13 +96,14 @@
 email application (XXX figure of simplified graph).
 
 The desktop environment would make these connections visible.
-Whenever an email raising a comment is shown
+Whenever an email raising an issue is shown
 by the email application, Fenfire would show
 issues raised by it floating in a margin (XXX figure n-a)),
 rendered by the issue tracking application.
 When clicking on an issue, it would become
 the main view, as when following an HTML link
-(XXX figure n-c)). The email would become a marginal note
+(XXX figure n-c XXX *except* non-disruptively)). 
+The email would become a marginal note
 or *buoy* connected to the issue.
 
 .. The figure above should have three parts: