Goal(Choose one we like the best):
- To provide a data format like "Atom" for reputation data.
- To provide a data format in order to open up existing reputation data and to share it across domains.
1. It only defines "framework". (relationship among elements. Also see Principle #3 for the defined elements.)
- The users define the context and how to use.
- It is a markup language(XML) to write reputation data.
- No score format, normalization and representation. (Users should define those.)
2. Transport is out of scope.
- However, it assumes REST API(HTTP GET) to be used for retrieving this document(data).
3. It keeps the structure simple.
No more than 2 layers in hierarchy. (3 layers with <ReputationBundle>)
- Only 7 elements are defined. (excluding ds:Signature)
<Reputation>, <Context>, <Subject>, <Assertion>, <Score>, <ReputationBundle>, <Date>
- It avoids defining a group element if possible.
- It avoids defining unnecessary schema(elements, attributes).
- It avoids defining unnecessary data types. (e.g. id values since URI is identifier.)
4. It supports and covers 80% of use cases.
- It avoids adding function for specific usage. (Can the usage apply to other use cases?)
- It avoids supporting all needs out there.
5. People intuit how to use it.
- The semantics of elements and attributes make sense to everyone.
Open Reputation Management Systems (ORMS) TC Wiki