From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Friday December 8, 19100 @ 16:41
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
-----------------------------------
Update of /usr/local/cvsroot/openprivacy/htdocs/notes
In directory openprivacy.org:/home/fen/projects/openprivacy/htdocs/notes
Modified Files:
soc-reputation.txt
Log Message:
cleared out old ideas - replace xml markup with reference to more complete version
*****************************************************************
File: openprivacy/htdocs/notes/soc-reputation.txt
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/soc-reputation.txt?annotate=1.6
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/soc-reputation.txt?rev=1.6&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/soc-reputation.txt.diff?r1=1.6&r2=1.5
-----------------------------------
Index: openprivacy/htdocs/notes/soc-reputation.txt
diff -u openprivacy/htdocs/notes/soc-reputation.txt:1.5 openprivacy/htdocs/notes/soc-reputation.txt:1.6
--- openprivacy/htdocs/notes/soc-reputation.txt:1.5 Fri Dec 8 13:57:45 2000
+++ openprivacy/htdocs/notes/soc-reputation.txt Fri Dec 8 16:41:09 2000
@@ -1,9 +1,9 @@
-$Id: soc-reputation.txt,v 1.5 2000/12/08 21:57:45 fen Exp $
+$Id: soc-reputation.txt,v 1.6 2000/12/09 00:41:09 fen Exp $
-some more SOC on reputations - in temporal order.
-I have left older ideas that are superseded by newer ideas below
-in order to give as much overview as possible...
+Ref:
+http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/src/xml/reputations/reputation-opinion-example.xml
+a stream-of-consciousness on reputations...
Every object in an OpenPrivacy system
extends a class Reputation
@@ -14,39 +14,6 @@
Every OpenPrivacy Agent is a ReputationServer
or at least can pass reputation requests on to another server
-
-<!-- example simple reputation -->
-<reputation>
- <pubkey>aSignature</pubkey>
-</reputation>
-
-<!-- example reputation with semantic link and time stamp -->
-<reputation>
- <semantic-link>
- <descriptor="privacy"/>
- <ontology="URI='Websters Collegiate Dictionary, Third Edition'"\>
- </semantic-link>
- <date-time>2000.12.06 10:21:31 PDT</date-time>
- <pubkey>aSignatureSigningTheSemanticLinkAndDateTimeStamp</pubkey>
-</reputation>
-
-
-The Semantic Link is intended to describe a concept
-Generally, it is a word or phrase and a pointer to an ontology or use case
-
-<!-- the word 'privacy' as defined by Webster's -->
-<semantic-link>
- <descriptor="privacy"/>
- <ontology="URI='Websters Collegiate Dictionary, Third Edition'"\>
-</semantic-link>
-
-<!-- here we mean the word 'privacy' in the same way John Gilmore used it -->
-<semantic-link>
- <descriptor="privacy"/>
- <use-case="http://www.eff.org/pub/Privacy/privacy_gilmore.speech"\>
-</semantic-link>
-
-
When a Reputation is attached to an object
the Assigner grafts an element that has three parts:
1) A Semantic Link
@@ -54,106 +21,6 @@
3) A signed SHA-1 hash of these two elements and the object
The object must have a static component for this to be reliable
-<!-- this is a reputation attached to an object -->
-<openprivacy-object>
- <immutable-reputable-section>
- <comment>this object contains only a comment</comment>
- </immutable-reputable-section>
- <grafts>
- <reputation>
- <semantic-link>
- <descriptor="lame"/>
- <ontology="URI='Websters Collegiate Dictionary, Third Edition'"\>
- </semantic-link>
- <object-hash>
- <hash-type>SHA-1</hash-type>
- <hash>aHashOfTheImmutableReputableSection</hash>
- </object-hash>
- <pubkey>aSignatureSigningTheSemanticLinkAndTheHash</pubkey>
- </reputation>
- </grafts>
-</openprivacy-object>
-
-
-Note that the only things that can have a reputation are immutable objects
-Or we could say: the only things that can be reputed are signed objects
-This changes the above example to:
-
-<openprivacy-object>
- <reputation>
- <comment>this object contains only a comment</comment>
- <pubkey>signatureOfCreator</pubkey>
- </reputation>
- <grafts>
- <reputation>
- <semantic-link>
- <descriptor="lame"/>
- <ontology="URI='Websters Collegiate Dictionary, Third Edition'"\>
- </semantic-link>
- <object-hash>
- <hash-type>SHA-1</hash-type>
- <hash>aHashOfTheReputationSignature</hash>
- </object-hash>
- <pubkey>aSignatureSigningTheSemanticLinkAndTheHash</pubkey>
- </reputation>
- </grafts>
-</openprivacy-object>
-
-
-Perhaps openprivacy-objects are reputation objects
- linked by address and hash values:
-
-<!-- this object has the URI="http://jewel.openprivacy.org/lamedoc1.opr" -->
-<reputation>
- <object>
- <comment>this object contains only a comment</comment>
- </object>
- <object-hash>
- <hash-type>SHA-1</hash-type>
- <hash>aHashOfTheLocalObject</hash> <!-- the comment above -->
- </object-hash>
- <pubkey>signatureOfCreator</pubkey> <!-- signing the hash -->
-</reputation>
-
-<reputation>
- <object>
- <refer-URI>http://openprivacy.org/objects/lame1.rep>
- <semantic-link>
- <descriptor="lame"/>
- <ontology="URI='Websters Collegiate Dictionary, Third Edition'"\>
- </semantic-link>
- <dsig>SignatureOf
- </object>
- <object-hash>
- <hash-type>SHA-1</hash-type>
- <hash>aHashOfTheReputationSignature</hash>
- </object-hash>
- <pubkey>signatureOfCreator</pubkey>
-</reputation>
-
-
-OK, Time to get a bit more real and use some real XML...
-
-<!--
- signing an object at location http://jewel.openprivacy.org/lamedoc1.opr
- we create a new object at http://jewel.openprivacy.org/lamedoc1-signauture.opr
--->
-<Signature Id="ObjectOne" xmlns="http://www.w3.org/2000/09/xmldsig#">
- <SignedInfo>
- <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2000/CR-xml-c14n-20001026"/>
- <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
- <Reference URI="http://jewel.openprivacy.org/lamedoc1.opr">
- <Transforms>
- <Transform Algorithm="http://www.w3.org/TR/2000/CR-xml-c14n-20001026"/>
- </Transforms>
- <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
- <DigestValue>j6lwx3rvEPO0vKtMup4NbeVu8nk=</DigestValue>
- </Reference>
- </SignedInfo>
- <SignatureValue>MC0CFFrVLtRlk=...</SignatureValue>
-</Signature>
-
-
Local garbage collection, editing, enhancement and censorship
A reputation server can sweep its objects and, based on local criteria:
remove the object if:
@@ -169,63 +36,15 @@
Reputation Server Requirements - top level feature list
basic database features (insert, select, delete)
define selection criteria constraints
- define retreival set format
+ define retrieval set format
define exceptions
define admin features, such as size, number of objects, etc.
object validation
does the object that was grafted to still exist / has it changed?
are signatures valid/reputable?
sorting, ranking
- results may be returned ranked accirding to local server rules
- reputaion calculation (may require peer communications)
+ results may be returned ranked according to local server rules
+ reputation calculation (may require peer communications)
given an object, return its full reputation
as a set of object grafts
as a merged value
-
-<!--
- A Reputation is a URI-addressable DSig with optional additional features (elements)
--->
-<Signature>
- <!--
- we base on XML-DSig to ensure that reputations cannot be forged
- -->
- <SignedInfo>
- <CanonicalizationMethod Algorithm="http://www.w3.org/TR/2000/CR-xml-c14n-20001026"/>
- <SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#dsa-sha1"/>
- <!--
- the home URL is used to poin to self for reputation grafts
- -->
- <home URL="...">
- <!--
- The Reference URI points to the object to which we are attaching
- this Reputation
- There could be more than one Reference section
- -->
- <Reference URI="...">
- <DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/>
- <DigestValue>...</DigestValue>
- </Reference>
- <reputation-opinion ontology="...">
- <!--
- the ontology provides a context and/or meaning
- the entry-descriptor is a word or phrase defined in the ontology
- -->
- <entry descriptor="lame"/>
- </reputation-opinion>
- <reputation-opinion ontology="http://ontology.reputation.org/simple.xml">
- <!--
- here the entry elements have both a key word and a value
- -->
- <entry type="*" value="5">
- <entry type="speed" value="4"/>
- <entry type="satisfaction" value="5"/>
- </reputation-opinion>
- </SignedInfo>
- <SignatureValue>MC0CFFrVLtRlk=...</SignatureValue>
-</Signature>
-
-
-A Reputation can be attached to a Bias, or Rating of an object, e.g.,
-
-A Bias or Rating is a multi-valued Reputation
-
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST