gzz-commits
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gzz-commits] manuscripts/FutureVision review-answers-benja.txt


From: Benja Fallenstein
Subject: [Gzz-commits] manuscripts/FutureVision review-answers-benja.txt
Date: Sat, 08 Nov 2003 08:58:12 -0500

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Branch:         
Changes by:     Benja Fallenstein <address@hidden>      03/11/08 08:58:12

Modified files:
        FutureVision   : review-answers-benja.txt 

Log message:
        more

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/FutureVision/review-answers-benja.txt.diff?tr1=1.1&tr2=1.2&r1=text&r2=text

Patches:
Index: manuscripts/FutureVision/review-answers-benja.txt
diff -u manuscripts/FutureVision/review-answers-benja.txt:1.1 
manuscripts/FutureVision/review-answers-benja.txt:1.2
--- manuscripts/FutureVision/review-answers-benja.txt:1.1       Sat Nov  8 
08:43:54 2003
+++ manuscripts/FutureVision/review-answers-benja.txt   Sat Nov  8 08:58:11 2003
@@ -176,22 +176,32 @@
     I wrote something about this in my Journal. We've adopted so much of Ted's
     viewpoint that we've become contrarians, but technophobes? ;)
 
-
         In particular, I believe that there is the basis of some really
         interesting Semantic Web work here, where item-based editing and 
display
         is just one application of in terms of application-neutral, 
semantically
         modelled data.
 
-
     Do you get the point of this?
 
+RDF is a structured data format. The stuff that the SemWeb people
+are interested in is to program things that process this data
+automatically. We're doing editing and displaying of a network of items,
+which is data. So this reviewer is saying that we could operate
+on the same data as the Semantic Web people, have their tools
+operate on data entered through our system and have their data
+displayed by us.
+
+    --
 
         The presentation of the paper though is currently too bitty - too many
         unelaborated claims interspersed with irrelevant technical details.
 
-
     Ok, how will we address this.
 
+Go through the paper, keep an eye open for these, decide in each case
+whether to a) cut b) elaborate c) insert "in our opinion."
+
+    --
 
         Specific Comments--
         Abstract: if we build systems structured around things we care about,




reply via email to

[Prev in Thread] Current Thread [Next in Thread]