popolo-project / popolo-spec

International legislative data specifications
http://www.popoloproject.com/
99 stars 18 forks source link

AgendaItem to deal with sub-events #121

Open joepio opened 7 years ago

joepio commented 7 years ago

While we were importing parliamentary data from local governments (municipalities from the Netherlands) and national governments (e.g. the Dutch parliament), we found that governments tend to structure their meetings with agenda items. The meeting software that they use also structures the various themes and issues in this way.

Currently, the popolo specification lets events have child events. Therefore, we should store these items as 'events'.

However, this poses a problem. Say, for example, that a web application wants to render a calendar that displays all meetings for some government. It fetches all events, but this also includes the children of events. This creates multiple events for a single point in time (one parent + all sub-events), where people are present at both.

I suggest that we introduce a new schema for these sub-event children: Agenda Items. I suggest that its schema inherits schema:CreativeWork consists of the following attributes:

What are your thoughts on this?

jpmckinney commented 7 years ago

Indeed - there's some prior work we can reuse for agenda items, including:

wfdd commented 7 years ago

It seems slightly odd to me to conflate the items on the agenda with the act of discussing those items.

jpmckinney commented 7 years ago

I think the suggestion is just to have a class for items on the agenda.

I don't think the suggestion is for one object to do the work of both agenda items and the event itself.