Let me make note of my random thougts before I forget.
- Reputation needs to have an identifier of somebody being scored.
- The same for who is scoring.
- For what criteria, this reputation score was made.
- For the reputation to be aggregatable, it has to have a distribution that we know about the aggregated distribution (such as normal distribution).
- The information about the distribution, including what distribution, mean, and standard diviation must be published together with the score.
- Display score must be intuitive for an average person.
- Date that score was made
- Signature by the score maker
So, the reputation score file should contain:
| item | type | e.g. |
|---|---|---|
| SubjectID | XRI/URI | =nat |
| ReputationServiceID | XRI/URI | @myRS |
| Criteria | Text | Operation quality of this RP |
| Display Score (Cumulative Percentage) | float | 74.2 |
| Score | Float | 56.8 |
| Distribution | enum | normal |
| Mean | float | 50 |
| Standard Deviation | float | 10 |
| Subject Public Key | String | 2fdlafodnewoldfjkaslf … |
| Date | XMLDATE | 2008-02-01T14:34:00Z |
| Signature | string | af8afsld92dfjdsla…blah…blah… |
In the above table, I am proposing to use cumulative distribution P(X<x) as the display score, so that the meaning of the score is clear for anybody. If the score is 95.5, the subject is among the top 5% of most trusted in that criteria.
Also, public key of the subject being rated is included as par OpenID TX proposal.
Using this, parties who are trying to talk to the subject can be sure that the party really is the party that has been rated by the above rating agency.
This data can be serialized in XML format, or JSON, or tag=value format etc.
OK. This is another input to forthcoming ORMS TC at OASIS Open.