CVS update: openprivacy/htdocs/notes/reputations

From: cvs@openprivacy.org
Date: Wed Dec 13 2000 - 16:31:27 PST

Date: Wednesday December 13, 19100 @ 16:31
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-serv24067

Modified Files:
        requirements.txt
Log Message:
added protocol versioning...

*****************************************************************
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.34

CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/reputations/requirements.txt?rev=1.34&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.34&r2=1.33

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

Index: openprivacy/htdocs/notes/reputations/requirements.txt
diff -u openprivacy/htdocs/notes/reputations/requirements.txt:1.33 openprivacy/htdocs/notes/reputations/requirements.txt:1.34
--- openprivacy/htdocs/notes/reputations/requirements.txt:1.33 Wed Dec 13 14:00:02 2000
+++ openprivacy/htdocs/notes/reputations/requirements.txt Wed Dec 13 16:31:27 2000
@@ -1,6 +1,6 @@
 -*- indented-text -*-
 
-$Id: requirements.txt,v 1.33 2000/12/13 22:00:02 burton Exp $
+$Id: requirements.txt,v 1.34 2000/12/14 00:31:27 burton Exp $
 
 Reputation Server Requirements: top level feature list
 
@@ -110,14 +110,16 @@
         v. if signed object but no reputation, return reputation of signer
         vi. define retrieval set formats (set of grafts or merged value)
     c. removeReputation(URI=object, XML=reputation) // delete
- d. define exceptions
+ d. defined exceptions
         i. reputation_does_not_exist
         ii. insufficient_permissions_for_operation
         iii. timeout
         iv. (what else?)
- e. should uses a standardized interface.
+ e. a standardized interface.
         i. SOAP, XQL, etc. (TBD: this technical area is very limited to-date)
-
+ f. Protocol versioning. We get this for 'free' with XML namespaces. If the
+ namespace isn't known then the protocol does not work.
+
 Note: database admininstration features such as database.size and
       database.numberOfObjects are outside the scope of these requirements
       and are left to the implementation
@@ -193,7 +195,6 @@
    don't support peer-to-peer network communication. This is basically any host
    behind a firewall, NAT, etc.
 
-FIXME: need to define Phase I first.. :)
 G. === Phase II ===
 
 1. Support reputation by ontology/semantics

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