Skip to content
This repository was archived by the owner on Jan 10, 2021. It is now read-only.
Michiel@unhosted edited this page Oct 3, 2013 · 6 revisions

How cases work

When giving a score to each point in a topic, you (as a reviewer/curator) will obviously want to give the same score to "comparable" data points. Say you gave MySpace a 'good (20)' score for the data point that states they give users 24 hours notice before actioning a take-down request, and Facebook also gives the same 24 hours notice in the same situation, then you would want to give that the same 'good (20)' valuation, and not suddenly a different one. That's exactly what a case does.

In this example, the topic maybe 'take-down requests', and the 'case' that would apply here to both the MySpace and the Facebook point in this topic would be something like "yes, but with 24 hours notice" -> "good (20)".

List of cases per (category/)topic:

  • business-transfer
    • may sell your data in merger → bad (20)
    • will notify before merger → good (20)
  • changes-involvement
    • little → bad (35)
    • feedback invited → good (20)
  • changes-notice
    • user needs to rely on tosback.org → bad (70)
    • user is notified on the day → neutral (0)
    • user is notified a week or more in advance → good (30)
    • user is notified a month or more in advance → good (40)
Clone this wiki locally