Extension:Jade

The JADE (Judgement And Dialog Engine) extension provides two new namespaces,  and , used for collecting and discussing judgments. Judgments are an opinion about a wiki revision, diff, or page.

Configuration
The  setting determines what types of judgments can be made about each wiki entity. Wikis may have slightly different models, for example on Wikidata, we don't make "wp10" quality judgments but instead will specify "itemquality". The default values are as follows: $wgJadeAllowedScoringSchemas = [ "diff" => [ "damaging" => "damaging/v1.json", "goodfaith" => "goodfaith/v1.json", ],   "revision" => [ "wp10" => "wp10/v1.json", ],   "page" => [ "drafttopic" => "drafttopic/v1.json", ], ];

Jade namespace: Judgments
For the official schema of JSON stored in the  namespace, see the top-level schema and the subschemas for each judgment's score. Page titles must correspond to what is being judged, somewhat like Talk pages corresponding to exactly one title. The various wiki entity types that might be judged and example URLs are,
 * Revision - Snapshot of a page at a specific revision ID, for example https://en.wikipedia.org/wiki/Jade:Revision/12345678 judges https://en.wikipedia.org/w/index.php?title=Sinharaja_Forest_Reserve&oldid=12345678
 * Diff - Change made at a specific revision ID, for example https://en.wikipedia.org/wiki/Jade:Diff/12345678 judges https://en.wikipedia.org/w/index.php?diff=12345678
 * Page - Things that will always be true about a specific page ID. For example, https://en.wikipedia.org/wiki/Jade:Page/531458 judges https://en.wikipedia.org/wiki/Washburn_Observatory

Schema validation is extremely strict. A revision may be rejected simply because its title doesn't match the entity being judged, or for structural errors in the JSON. See the schema for more details. Currently, there's no easy way to get information about why judgment content is failing validation.

Usage
Pages in the  namespace are difficult to edit by hand, and are intended to be edited through a third-party tool. Currently, no such integrations exist, so please check back again in the future.

We've decided to not include a UI, at least in the initial versions of this project, for the same reasons that ORES didn't include a UI at first. We're cutting development costs by focusing on the service itself, and the UI can be a separate effort.