From: cvs@openprivacy.orgCVS update: openprivacy/htdocs/notes
Date: Tuesday December 12, 19100 @ 18:30
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:
TODO
Log Message:
added namespace, website notes; spell-checked & cleaned up
added some notes/questions/clarifications
*****************************************************************
File: openprivacy/htdocs/notes/TODO
CVSWEB Options: -------------------
CVSWeb: Annotate this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/TODO?annotate=1.9
CVSWeb: View this file: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/TODO?rev=1.9&content-type=text/x-cvsweb-markup
CVSWeb: Diff to previous version: http://openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/htdocs/notes/TODO.diff?r1=1.9&r2=1.8
-----------------------------------
Index: openprivacy/htdocs/notes/TODO
diff -u openprivacy/htdocs/notes/TODO:1.8 openprivacy/htdocs/notes/TODO:1.9
--- openprivacy/htdocs/notes/TODO:1.8 Fri Dec 8 19:53:55 2000
+++ openprivacy/htdocs/notes/TODO Tue Dec 12 18:30:00 2000
@@ -1,69 +1,84 @@
-s********************************************************************************
-Last-Modified: $Date: 2000/12/09 03:53:55 $
-Version: $Id: TODO,v 1.8 2000/12/09 03:53:55 burton Exp $
********************************************************************************
+Version: $Id: TODO,v 1.9 2000/12/13 02:30:00 fen Exp $
+********************************************************************************
List of areas we need to define within OpenPrivacy... generally organized by
priority.
********************************************************************************
-Fri Dec 8 18:49:00 2000 (burton): Document mechanism for returning the prefered
-set of reputation servers ... this should be a filter (see UML documentation)..
+2000.12.12 fen: update website (assigned to: Fen)
-Tue Dec 5 19:26:38 2000 (burton): Define XML (or just a mechanism) for
-manipulating a profile. Grafting on more info, deleteing nodes, query, etc.
+2000.12.12 fen: namespace definitions (assigned to: Kevin)
+ reputation:xmlns="http://www.openprivacy.org/2000/12/reputation-metainfo"
+ payload:xmlns="http://www.openprivacy.org/2000/12/reputation-opinion"
+
+Fri Dec 8 18:49:00 2000 (burton): Document mechanism for returning the preferred
+ set of reputation servers ... this should be a filter (see UML
+ documentation)
+ [2000.12.12 fen: does this mean that a set (array) of server URI's needs
+ to be a filter? Or does this mean that we need to document what a filter
+ is - and how it is used - to define the set that is returned?]
-Tue Dec 5 15:17:42 2000 (burton): Ontological Vocabulary. When expressing an
- opinion of an Internet resource, try and define a vocabulary based on an
- Ontological URI. Basically words are defined by how they are used and when
- someone expresses an opinion we should make sure that the words they use to
- describe themselves are standardized.
+Tue Dec 5 19:26:38 2000 (burton): Define XML (or just a mechanism) for
+ manipulating a profile. Grafting on more info, deleting nodes, query, etc.
+Tue Dec 5 15:17:42 2000 (burton): Ontological Vocabulary.
+ Define a minimum default vocabulary for ratings and reputations. This
+ will support a standardized usage. Note that reputation accrual can affect
+ the way a word may be interpreted locally.
Wed Dec 6 18:44:05 2000 (burton): Need to go over reverse communications
protocol.
http://pix.comedia.com/OpenPrivacy/20000929/DSCN4685.JPG
- The goal of this was so that a portal/remote agent could communicate back with
- the initiating agent (sometimes the user) but only if there is an explicit
- communications channel provided by the user.
+ A remote agent (in this case, the JetsPeek portal) must be able to
+ communicate with the initiating agent (sometimes the user) but only if
+ there is an explicit communications channel provided by the user.
This has to do with Agent communication. If a Primary Agent (Broker)
communicates with a Secondary Agent, the SA can potentially allow packets to
return back to the user as a payload.
- - We need to use something like the Mojonation (referal) service.
- - not really. If we use a referal but with an event based TCP alert this
+ - We need to use something like the MojoNation (referral) service.
+ - not really. If we use a referral but with an event based TCP alert this
can talk back to the client.
-Wed Dec 6 18:41:49 2000 (burton): We need to have a mechanism to query/modify
-a set of static profiles. - set a profile (add/remove) - graft on profile info
-(add/remove) - we need a way to build up reputations... - need a way to query
-the profile (XQL based on a profile markup???) - need a way to report
-results... this may not be on a virtual circuit... should we use a messaging
-mechanism for this?
+Wed Dec 6 18:41:49 2000 (burton): mechanism to query/modify static profiles.
+ - set a profile (add/remove)
+ - graft on profile info (add/remove)
+ - we need a way to build up reputations...
+ - need a way to query the profile (XQL based on a profile markup???)
+ - need a way to report results... this may not be on a virtual
+ circuit... should we use a messaging mechanism for this?
Wed Dec 6 18:52:28 2000 (burton): Need to come up with an example of a real
- XMLDsig... at the very minimum for documentation purpsoses.
+ XMLDsig... at the very minimum for documentation purposes.
+ [2000.12.12 fen: see
+ http://www.openprivacy.org/cgi-bin/cvsweb/cvsweb.cgi/openprivacy/src/xml/reputations/reputation-opinion-example.xml
+ Still TBD: creation of namespace definitions and validating parser]
+Wed Dec 6 23:50:21 2000 (burton): Agent query protocol: Given a URL to an
+ agent... determine what capabilities/facilities it can support.
+Wed Dec 6 23:58:30 2000 (burton): PRObE interaction: select, update, delete,
+ etc.
-
+Wed Dec 6 23:59:39 2000 (burton): [JetsPeek] SCDS interaction: specify
+ keywords, query, reputation, etc in order to get a list or RSS channels
+ you might be interested in. (result should be OCS).
+Wed Dec 6 23:59:55 2000 (burton): Reputation Manager Facility. Given an URI,
+ and my bias... compute a reputation
-
-Wed Dec 6 23:50:21 2000 (burton): Agent query protocol: Given a URL to an
-agent... determine what capabilities/facilities it can support.
-Wed Dec 6 23:58:30 2000 (burton): PRObE interaction: select, update, delete,
-etc.
+
+
+
+
+
+
-Wed Dec 6 23:59:39 2000 (burton): SCDS interaction: specify keywords, query,
-reputation, etc in order to get a list or RSS channels you might be interested
-in. (result should be OCS).
-Wed Dec 6 23:59:55 2000 (burton): Reputation Manager Facility( given an URI,
-and my bias... compute a reputation )
This archive was generated by hypermail 2b30 : Mon Jan 22 2001 - 15:52:14 PST
