CVS update: openprivacy/htdocs/notes/reputations

From: cvs@openprivacy.org
Date: Tue Dec 12 2000 - 19:06:06 PST

Date: Tuesday December 12, 19100 @ 19:06
Author: fen
CVSWEB Options: -------------------

Main CVSWeb: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi

View this module: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations

-----------------------------------

Update of /usr/local/cvsroot/openprivacy/htdocs/notes/reputations
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes/reputations

Modified Files:
        requirements.txt
Log Message:
cleaned up the rest - first cut complete!

*****************************************************************
File: openprivacy/htdocs/notes/reputations/requirements.txt

CVSWEB Options: -------------------

CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?annotate=1.23

CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.23&content-type=text/x-cvsweb-markup

CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt.diff?r1=1.23&r2=1.22

-----------------------------------

Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.22 openprivacy/htdocs/notes/reputations/requirements.txt:1.23
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.22 Tue Dec 12 18:58:32 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Tue Dec 12 19:06:06 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.22 2000/12/13 02:58:32 fen Exp $
+$Id: requirements.txt,v 1.23 2000/12/13 03:06:06 fen Exp $
 
 Reputation Server Requirements: top level feature list
 
@@ -150,30 +150,32 @@
 3. works with any message-based asynchronous data transport mechanism
     a. e.g. UDP, SMTP, ICQ, Carrier Pigeon, etc.
 
-F. === ontology / meaning ===
+F. === Phase II ===
 
-Support reputation by ontology/semantics. Systems can define their own
-vocabulary which can be used to markup reputations. (Ontologies will try to
-become standardized). The goal here will be to have ontology space with
-keywords so that certain 'meme' spaces will have words with different
-definitions( Java: SUN Microsystems vs Starbucks).
-
-G. === Optional ===
-
-Support a reputation:// URI namespace based on pet names (or another appropriate
-facility):
- http://www.erights.org/elib/capability/pnml.html. This could provide a
- facility to specify a way to lookup a reputation based on a human name and
- include this URI in another facility (XML, e-mail, etc). A client
- application could then use this URI namespace as a pointer to determine a
- reputation for an object which is not currently part of the Sierra
- reputation system.
+1. Support reputation by ontology/semantics
 
-H. === Wish list ===
+Note: Systems can define their own vocabulary which can be used to markup
+reputations. (Ontologies will try to become standardized). The goal here
+will be to have ontology space with keywords so that certain 'meme' spaces
+will have words with different definitions.
+e.g., 'Java'[ontology='programming']=>"SUN Microsystems"
+ vs. 'Java'[ontology='food']=>"Starbucks"
+
+2. Support a reputation:// URI namespace based on pet names
+ (or another appropriate facility):
+ ref: <http://www.erights.org/elib/capability/pnml.html>
+ a. specify reputation lookup based on human-readable name and
+ include this URI in another facility (XML, e-mail, etc).
+
+Note: A client application could then use this URI namespace as a pointer to
+ determine a reputation for an object which is not currently part of the
+ Sierra reputation system.
 
-Ability to verify calculated results by requesting the 'opinions' which were
+G. === Wish list ===
+
+1. Ability to verify calculated results by requesting the 'opinions' which were
 used to determine a calculation and then compare the results of the calculation
 with the opinion. (Note that this is unreliable, in that the returned set
 of 'opinions' is defined by the local reputation server(s).
 
-Desirable to be censorship-resistant (e.g., Freenet, MojoNation, Publius)
+2. Desirable to be censorship-resistant (e.g., Freenet, MojoNation, Publius)

This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST