Discussion

Label Discussion

Description

Discussions are arguments made by the MPs about matters relating to the Parliament (e.g. bills). Sometimes multiple Debates are discussed in the same discussion, which means that at some point in the discussion the debates/bills are switched. In that case the node will also take the MultiDebate label.

Co-labels:Not Bill Related | MultiDebate

Attributes

• identifier uid: integer

  Unique identifier of this object.

• order_stamp_in_meeting: integer

  A number indicating the placement of the discussion node along a chain of discussions that take place in a meeting.

• (optional) notes: string

  Short comments on the discussion.

• (optional) order_stamp_in_debate: integer

  A number indicating the placement of the discussion node along a chain of discussions that are part of a debate.

Connected relations

Outgoing

• DIVIDED_IN to Partition

• NEXT_IN_DEBATE to Discussion

• NEXT_IN_MEETING to Discussion

• PUBLISHED_IN to Source

Incoming

• CONTAINS from Meeting

• DISCUSSED_IN from Debate

• NEXT_IN_DEBATE from Discussion

• NEXT_IN_MEETING from Discussion

Constraints

• A Discussion must contain the attributes ‘order_stamp_in_meeting’, ‘order_stamp_in_debate’. If the Discussion contains the label “Not Bill Related” or the label “MultiDebate” it must contain just the attribute ‘order_stamp_in_meeting’.
• All partitions in a discussion must have the correct order_stamp and must be correctly connected by a NEXT relation. A partition uid must match the order_stamp. If the order and the time missmatch, the node must be labeled as a “Inconsistent Timestamp”.
• All transcripts must have the correct order_stamp in a discussion and must be correctly connected by a NEXT relation. If the order and the time missmatch, the node must be labeled as a “Inconsistent Timestamp”.
• A discussion must follow a defined structure:
  • It must be connected to at least one Debate with a DISCUSSED_IN relation. The only exception is if the debate is labeled as ‘Not Bill Related’”.
  • It must be connected to one and only one Meeting with exactly one CONTAINS relation
  • It must be connected to one and only one Source with exactly one PUBLISHED_IN relation

Visual Representation