Skip to content
This repository has been archived by the owner on Jun 11, 2020. It is now read-only.
/ popolo-ori Public archive

Extention of the Popolo ontology for municipality council meetings.

Notifications You must be signed in to change notification settings

argu-co/popolo-ori

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

24 Commits
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Popolo-ORI

Usage is not recommended, repo is no longer maintained.

Popolo-ORI is an extension of the Popolo specification, or more specifically, the Popolo Ontology. It is designed to standardize data that stems from the meeting software used by Dutch municipalities. It is part of the Open-Raadsinformatie project (github).

Here is the owl file

New classes

The amount of classes in an ontology should be kept as low as possible. For each added class, a reason is stated for including it here.

AgendaItem

An item in a list of topics to be discussed at an event.

Vanilla Popolo knows only Events, which can have child Events. This could be used to describe items in an agenda, but this causes a few issues. Firstly, if some front-end application were to list all Events, it would show both meetings and their agenda items. Secondly, Agenda Items have a position (index) in their parent Event.

Attachment

A file that is attached to something.

Most meeting software used by (Dutch) municipalities use a lot of attachments. These are mostly linked to Agenda Items. Popolo does not have a Model for these kind of items.

Amendment

A proposal to modify another proposal.

This sub-class of the Motion item has the added 'amends' property.

Using JSON-LD @context

If your API needs to comply with Popolo-ORI, you will need to include the @context JSON object in your API responses. You can do this in the body of the JSON response or as a link in the HTTP header. Read more about applying this in the W3C spec of JSON-LD.