A vote event is an event at which people’s votes are recorded.
The Vote Event class should have properties for:
the organization whose members are voting
House of Commons
the legislative session in which the vote event occurs
2nd Session of the 41st Parliament
Vote No. 42
the motion on which people are voting
That the House do now proceed to the Orders of the Day.
the time at which the event begins
January 1, 2013 at 12:30pm
the time at which the event ends
January 1, 2013 at 12:45pm
the result of the vote event
The ayes have it.
Within the Legislative Council of Hong Kong, the motion was passed by the functional constituencies but negatived by the geographical constituencies.
the vote totals
Yeas: 128, Nays: 145
the individual votes
John Doe cast a vote in favor of the motion.
Few specifications exist for vote events, and few legislatures publish vote data in a machine-readable format. Dublin Core, Schema.org, and Parliamentary Metadata Language terms are retained from the inventory of terms.
||An event at which people's votes are recorded|
||The organization whose members are voting1|
||The legislative session in which the vote event occurs1|
||An issued identifier, e.g. a sequential number|
||The motion being decided|
||The vote event's category|
||The time at which the event begins|
||The time at which the event ends|
||The result of the vote event2|
||The result of the vote event within groups of voters|
||The number of votes for an option|
||A voter's vote|
VoteEvent class is a subclass of the
The vote totals should agree with the individual votes. The vote totals may not include all options from individual votes, and the individual votes may not include all present voters, in particular if the options chosen that have no effect on the result, e.g. abstentions.
1. If an implementation uses the Motion class, it is not necessary to repeat the
legislative_session properties on the motion's vote events, unless they differ; for example, a committee may consider a legislature's motion, such as in the Riksdag.
2. If a motion has multiple vote events, it is relevant to communicate the result of each event.
JSON differences from other RDF serializations:
organizationis used instead of
organizer, to be consistent with the Membership class.
legislative_sessionis used instead of
superEvent, for clarity.
Implementations may use values from outside this list.