We develop a self-contained web app that provides a simplified, real-time view
onto the Democratic Commons data in Wikidata, and which exposes the data in
easy-to-use APIs and formats. Others can use this tool as integration middleware
between data in Wikidata and their own tools and services.
We run two instances publicly, one which is faithful to the upstream, and
another that has a degree of moderation and oversight. There'd be a lot of
detail in how that moderation is done, to be discussed.
The tool itself is made available under an OSS licence for others to run
locally, and to ease uptake we make it ready for e.g. Docker and Kubernetes.
Benefits
We provide a tool anyone can use to make use of Wikidata data, without having
to understand SPARQL, the Wikidata data model, etc.
mySociety has a data staging post it can deploy internally for e.g.
TWFY, WTT.
We develop a realtime pipeline which could underpin realtime reporting of
election results across a wide stakeholder group (e.g. other civic tech
organisations, press agencies, individuals)
Potential features
REST APIs
Search
Bulk data downloads
Outbound events/notifications on changes
Simple human-readable HTML interface (c.f. Legislative Explorer)
Optional moderation interface
Discussion points
I'm very woolly as to how the moderation could/should happen. I suspect you'd
want community groups to "own" moderation for countries, and for them to
self-organise.
There's still the issue of how boundaries are maintained.
Architecture and implementation
In Python world, I'd use:
Django (web framework)
django-rest-framework (APIs)
celery + RabbitMQ (asynchronous tasks, data fetching)
Democratic Commons Lens proposal
Background
Outline
We develop a self-contained web app that provides a simplified, real-time view onto the Democratic Commons data in Wikidata, and which exposes the data in easy-to-use APIs and formats. Others can use this tool as integration middleware between data in Wikidata and their own tools and services.
We run two instances publicly, one which is faithful to the upstream, and another that has a degree of moderation and oversight. There'd be a lot of detail in how that moderation is done, to be discussed.
The tool itself is made available under an OSS licence for others to run locally, and to ease uptake we make it ready for e.g. Docker and Kubernetes.
Benefits
Potential features
Discussion points
I'm very woolly as to how the moderation could/should happen. I suspect you'd want community groups to "own" moderation for countries, and for them to self-organise.
There's still the issue of how boundaries are maintained.
Architecture and implementation
In Python world, I'd use: