From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes/reputations
Date: Tuesday December 12, 19100 @ 23:40
Author: burton
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:/tmp/cvs-serv21474
Modified Files:
goals.txt requirements.txt
Log Message:
...
*****************************************************************
File: openprivacy/htdocs/notes/reputations/goals.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/goals.txt?annotate=1.13
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/goals.txt?rev=1.13&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/goals.txt.diff?r1=1.13&r2=1.12
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/goals.txt
diff -u openprivacy/htdocs/notes/reputations/goals.txt:1.12 openprivacy/htdocs/notes/reputations/goals.txt:1.13
--- openprivacy/htdocs/notes/reputations/goals.txt:1.12 Mon Dec 11 13:54:42 2000
+++ openprivacy/htdocs/notes/reputations/goals.txt Tue Dec 12 23:40:22 2000
@@ -1,4 +1,4 @@
-$Id: goals.txt,v 1.12 2000/12/11 21:54:42 burton Exp $
+$Id: goals.txt,v 1.13 2000/12/13 07:40:22 burton Exp $
NOTE: Sierra is a code name for a Reputation server. The name may change.
@@ -7,14 +7,12 @@
=== high level goals ===
Sierra is an attempt to build a 'Reptation' server which can store, serve, and
-calculate Reputations based on Opinions.
-
-Provide an XML object server which can serve/manage 'reputations'. Reputations
-are signed objects (DSig) which have a payload XML namespace.
-
-System should be infrastructure agnostic. You should be able to develop with
-any programming language on any Operating System.
-
+calculate Reputations based on Opinions. It will provide an XML object server
+which can serve/manage 'reputations'. Reputations are signed objects (DSig)
+which have a payload XML namespace. Opinions are expressed on URIs which can be
+calculated into a Reputation (this also means that reputation servers can have
+reputations).
+
Reputation servers are just a communications 'daemon' which any Internet
technology can support (HTTP servers, db servers, etc).
@@ -27,3 +25,5 @@
+The final system should be infrastructure agnostic. You should be able to
+develop with any programming language on any Operating System.
*****************************************************************
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.27
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.27&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.27&r2=1.26
-----------------------------------
Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.26 openprivacy/htdocs/notes/reputations/requirements.txt:1.27
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.26 Tue Dec 12 23:10:38 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Tue Dec 12 23:40:22 2000
@@ -1,4 +1,4 @@
-$Id: requirements.txt,v 1.26 2000/12/13 07:10:38 fen Exp $
+$Id: requirements.txt,v 1.27 2000/12/13 07:40:22 burton Exp $
Reputation Server Requirements: top level feature list
@@ -76,7 +76,6 @@
Note: Getting data in and out of the system securely is not part of this spec
D. === Data store facility ===
-
1. Data store features to support:
a. putReputation(URI=object, XML=reputation) // insert
b. reputationCollection = getReputation(querySet=???) // select
@@ -97,17 +96,26 @@
i. size of database (Kb)
ii. number of objects
iii. (what else?)
-
+ iv. generally this is out-of-scope for a reputations system.. it should
+ be provided by an underlying databased facility.
+ f. should uses a standardized interface. SOAP, XQL, etc. This needs to be
+ defined as this technical area is very limited to-date.
+
2. Standardized data format specification
a. based on the xmldsig namespace (xmlns="http://www.w3.org/2000/09/xmldsig#")
b. extended by:
i. reputation:xmlns="http://www.openprivacy.org/2000/12/reputation-metainfo"
ii. payload:xmlns="http://www.openprivacy.org/2000/12/reputation-opinion"
+ iii. Any additional data payload format is allowed. Only requirement is
+ that it is XML.
+ iv. RDF is a recommended reference as its use will be highly
+ desirable for providing meta-info for additional payloads.
+ c. technically any XML data could be stored in an 'reputations' based XML
+ repository. XML Signature will probably be used more often.
+
3. Standardized data store API
a. (XML...)
-
-E. === sorting, ranking, calculating ===
1. Sorting, ranking
a. results may be returned ranked according to local server rules
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST