Cite the Record
Menu

Shard schema

Person shard · 0.2.0

A person entity — current MP, peer, committee witness, former member. Carries identity, current roles, registered interests, recent written questions asked or answered, recent votes, and provenance back to the Members API and Register of Interests source.

This page is the field reference for developers and AI clients. If you came here looking for a person, browse the person index instead.

Draft field reference. Canonical .json file not published.

Verified example pending /schemas/person@0.2.0.json (pending) Authoritative source Use with AI

Required fields

6

Optional fields

7

Dialect

JSON Schema draft 2020-12

Version

0.2.0

Required fields

Every shard validating against person@0.2.0 ships these fields. Provenance lines show where each value comes from — the load-bearing column for the structured-evidence promise.

  • stableId string<slug>

    CTR-stable person identifier.

    Provenance: Generated at intake from name + constituency or peerage; survives constituency boundary review.

    e.g. person:sarah-owens-mid-devon

  • officialId string

    Members API memberId.

    Provenance: Members API memberId verbatim.

  • displayName string

    Display form of the name.

    Provenance: Members API nameDisplayAs field.

  • entityType enum (4 values)

    Person sub-type.

    • mp
    • peer
    • committee_witness
    • former_member

    Provenance: Members API memberType.

  • canonicalUrl string<URL>

    Live profile URL on members.parliament.uk.

    Provenance: Constructed from the Members API memberId via the documented URL template at intake.

  • provenance object

    Provenance for the underlying Members-API snapshot.

    Provenance: Emitted by intake at the weekly members-snapshot run.

Optional fields

Present where the source carries the value or the derivation succeeds. Code consuming this schema should treat them as nullable.

  • party string · optional

    Current party affiliation.

    Provenance: Members API latestParty; never inferred.

  • constituency string · optional

    Current constituency for MPs.

    Provenance: Members API latestHouseMembership; never inferred.

  • enteredParliament string<ISO 8601> · optional

    First election date in current run.

    Provenance: Members API representedConstituencyEntry.start.

  • currentRoles array<object> · optional

    Current government / opposition / committee roles.

    Provenance: Members API representations endpoint.

  • registeredInterests array<object> · optional

    Registered financial interests.

    Provenance: House of Commons Register of Members' Financial Interests; refreshed at the publish cadence of the official register.

  • writtenQuestions array<object> · optional

    Recent written questions asked or answered.

    Provenance: Records of recordType = written_question where this person appears as asker or answerer in the per-record entity links.

  • recentVotes array<object> · optional

    Recent division votes.

    Provenance: Division-vote records linked to this member from the Hansard divisions feed.

Source families for planned person data

The following real source-family taxonomy is associated with person@0.2.0. Click through for metadata and publication status.

Related schemas

Entities referenced by this shard kind. A person shard's entities[] / nested references resolve to shards of these kinds.

Versioning + dialect
Schema id
person@0.2.0
Dialect
https://json-schema.org/draft/2020-12/schema
Canonical .json
/schemas/person@0.2.0.json (pending)
Verified example
Not linked until a verified live example is available.

Each planned schema follows semver. Patch bumps are additive and backwards-compatible. Minor bumps may add required fields or change validation rules. Major bumps will use a new URL path once canonical files are published.

Published structured data will declare its version in a $schema field. AI clients should respect that version when files become available.