A motion is “a formal step to introduce a matter for consideration by a group.”1
The Motion class should have properties for:
the organization in which the motion is proposed
House of Commons
the legislative session in which the motion is proposed
2nd Session of the 41st Parliament
the person who proposed the motion
the transcript or text of the motion
That the House do now proceed to the Orders of the Day.
Bob distinguishes routine from non-routine motions.
the date on which the motion was proposed
January 1, 2013
the requirement for the motion to be agreed to
the result of the motion
The motion was agreed to.
Few specifications exist for motions, and few legislatures publish motions in a machine-readable format. In many, the only specified or recorded motions are those with a single vote event. However, a single motion may have multiple vote events; for example, a voice vote followed by a recorded vote. Dublin Core, Schema.org, and Parliamentary Metadata Language terms are retained from the inventory of terms.
Either a person or an organization can create a CreativeWork. A Motion is a subclass of CreativeWork, and only a person can create a Motion.
||A formal step to introduce a matter for consideration by an organization|
||The organization in which the motion is proposed|
||The legislative session in which the motion is proposed|
||The person who proposed the motion|
||The transcript or text of the motion|
||An issued identifier|
||A motion category, e.g. adjournment|
||The date on which the motion was proposed|
||The requirement for the motion to be adopted|
||The result of the motion|
||An event at which people vote on the motion|
JSON differences from other RDF serializations:
organizationis used instead of
publisher, to be consistent with the Membership class.
classificationis used instead of
additionalType, to be consistent with the Organization class.
classificationproperty is a string, instead of a
dateis used instead of
dateSubmitted, for clarity.
Implementations may use values from outside this list.