← Back to catalogue
Published

Meeting / Session

vr.wm-act-025 · wm-act-025-meeting-session

Provide the context an agent needs to convene, run, observe and hand off a single meeting or session occurrence — identity, convening basis, timing, setting, participation, agenda, conduct, outcomes and record obligations — without owning the durable records, the convening body or the parties it references.

World Models Activities and processes ACT.MTG
Bundle → Layer → Finding → QuestionsClassifiersWhat it isWhy it existsDistinguishing featuresWhat robots and AI may and may not doMoral aspectsOwnersLinks to other meta-modelsIdentity and identifiersDirect propertiesRecognitionCapabilities and actionsHazards and failure modesStandards and interfacesContext of useSources

Bundle → Layer → Finding → Questions Filled

6 bundles · 12 layers · 25 findings · 103 questions

Session constitution and convening basis What this occurrence is, how it is identified and classified, and the authority and notice under which it exists.

Identity and classification

Stable identification of the occurrence across systems and revisions, and the classification axes that select the applicable obligations.

Occurrence identity and revision resolution

How one meeting occurrence is distinguished from its series, from its own earlier revisions, and from copies of it held in other systems.

  1. Which authoritative master-system identifier designates this occurrence, and which governed global identifier is published for it? identity
  2. How is a single occurrence distinguished from its recurring series when both carry the same identifier? identity
  3. Which revision counter and timestamp determine which copy of the meeting definition prevails when two differ? provenance
  4. Which external system identifiers are bound to this occurrence, and which of them may be treated as authoritative? interoperability

Session classification

The classification axes — meeting type, formality, attendance mode and openness class — that select which procedural, disclosure and record obligations bind this occurrence.

  1. What meeting type and formality class does this session belong to under the convening body's rules? classification
  2. Is the session conducted in person, online or in a mixed mode, and which mode applies to each participant? classification
  3. Which openness class applies to the session as a whole, and may individual portions carry a different class? access
  4. Which classification changes are permitted after the notice has been issued, and what re-notification does each trigger? constraint

Convening authority and notice

The binding to the party entitled to call the session, and the convocation act that makes it effective.

Convening authority binding

Reference to the body, office or instrument under whose authority the session is called, and the presiding arrangement for this occurrence only.

  1. Which governance body or office convened this session, and under which rule or instrument was it entitled to do so? authority
  2. Who requested the session, and was a minimum requisition threshold required and satisfied? requirement
  3. Which chair or acting officer presided over this occurrence, and how was that determined? ownership
  4. Which standing terms of reference constrain this session, and from where are they resolved at read time? relationship

Notice and convocation

The act of announcing the session to those entitled to attend or observe, and the sufficiency tests that attach to that announcement.

  1. What notice was issued, to whom, through which channel, and how long before the session? process
  2. Does the applicable regime require public announcement, and which content must that announcement carry? requirement
  3. What is the consequence for the validity of business transacted if the notice period or content requirement was not met? exception
  4. Which post-issuance changes require an amended or re-issued notice? constraint
Time, series position and setting When the occurrence is scheduled and observed, where it sits in a series, and the physical, virtual and accessibility conditions under which it takes place.

Timing, series position and schedule change

Planned and observed temporal extent, recurrence position, and the transitions that move or end the occurrence.

Planned and observed timing

The scheduled temporal extent of the occurrence and the times actually observed for opening, suspension, resumption and close.

  1. What are the planned start and end of the session, and in which named time zone were they expressed? temporal
  2. What actual opening, suspension, resumption and closing times were observed, and by which observer? measurement
  3. Which time value governs a procedural deadline when the planned and observed times diverge? constraint
  4. How are all-day, open-ended and multi-day sessions bounded in this model? definition

Series membership and recurrence position

Whether the occurrence was generated by a recurrence rule, what it inherits from the series, and how it relates to the sessions before and after it.

  1. Was this occurrence generated by a recurrence rule, and what rule expression produced it? composition
  2. Which properties of this occurrence override the series definition and which remain inherited? relationship
  3. How is an occurrence detached from its series, and what identity does it carry afterwards? lifecycle
  4. Which sessions immediately precede and follow this one for the purpose of carrying business over? relationship

Schedule change, postponement and cancellation

The scheduling status of the occurrence and the authorised transitions that move, postpone, replace or cancel it.

  1. What is the current scheduling status of the occurrence, and which statuses are terminal? state
  2. Who may postpone, reschedule or cancel this occurrence, and what confirmation does each action require? authority
  3. How is a counter-proposal of a different time recorded, and how is it resolved? process
  4. Which obligations survive a cancellation and which are extinguished by it? requirement

Setting, access channel and accessibility

The physical venue and resources, the virtual conferencing endpoints, and the accessibility conditions for equivalent participation.

Physical setting and reserved resources

Where the occurrence physically takes place, what capacity the setting has, and which rooms, equipment and support services are reserved for it.

  1. Where does the session physically take place, and which place record is authoritative for that location? spatial
  2. Which rooms, equipment and support resources are reserved for the session, and by whom were they reserved? composition
  3. What is the capacity of the setting, and how is over-subscription handled? constraint
  4. How is the physical setting recorded when the session has no physical venue at all? exception

Virtual access channel and mixed-mode equivalence

The conferencing endpoints published for the session, the admission control applied to them, and what guarantees equivalent participation across modes.

  1. Which conferencing endpoints are published for this session, and what features does each provide? interoperability
  2. Which credential or access code distinguishes moderator entry from ordinary participant entry? security
  3. How is admission to the virtual room controlled before and during the session? access
  4. In a mixed-mode session, what guarantees that remote and in-room participants have equivalent standing? quality

Accessibility provision and accommodation

The accessibility services provided for the occurrence, how participant accommodation needs are captured, and how provision quality is assessed.

  1. Which accessibility services are provided for this session, and who requested each one? requirement
  2. By when must agenda and materials be circulated so that participants using assistive technology can prepare? temporal
  3. How are accommodation requests captured, and what fallback applies when a request cannot be met? exception
  4. How is the quality of live captioning or interpretation assessed for this occurrence? quality
Participation, presence and quorum Who was invited, in what capacity, who actually took part, and whether the occurrence was competent to transact business.

Roles, invitation state and substitution

The invited population, the capacity each party holds, and the mechanisms by which participation can be transferred or withdrawn.

Participant roles and invitation state

The capacity in which each invited party is expected to take part, and the current state of their response to the invitation.

  1. Which role does each invited party hold in this occurrence, and which roles must be filled for it to proceed? classification
  2. What invitation response has each invited party given, and when was that response last updated? state
  3. Which invited entries denote individuals, which denote groups, and which denote rooms or other resources? definition
  4. Is a response expected from each invitee, and what is assumed when none is given by the session start? constraint

Delegation, proxy and recusal

Transfer of participation to another party, the rights that transfer with it, and the withdrawal of a participant from part of the proceedings.

  1. May an invitee delegate participation, and to whom was participation delegated for this occurrence? relationship
  2. Does a delegate or alternate inherit the delegator's speaking and voting rights in full? authority
  3. How is a proxy or voting instruction recorded, and when does it lapse? lifecycle
  4. Which declared interests require a participant to withdraw from part of the proceedings, and over which items? exception

Presence observation and quorum determination

What was actually observed about presence, and the competence determination derived from it against an externally owned threshold.

Presence observation

Observed presence of parties during the occurrence, the source and reliability of each observation, and reconciliation between competing sources.

  1. Who was actually present, and for which intervals of the occurrence was each party present? measurement
  2. Which observation source produced each presence record, and how reliable is that source? provenance
  3. How is presence reconciled when in-room and platform-derived observations disagree? validation
  4. For how long does platform-derived presence data remain retrievable before it expires at source? retention

Quorum determination

The determination, at this occurrence, of whether the number and composition of those present met the threshold required to transact business.

  1. Which quorum rule applies to this occurrence, and which instrument defines the threshold? requirement
  2. Was the quorum satisfied at the opening and at each point where business was decided? validation
  3. What is the effect on business transacted if the quorum is lost part-way through the occurrence? exception
  4. Who verifies the quorum, and on whose request must a verification be carried out? authority
Agenda and conduct of proceedings The business set down for the occurrence, the procedural acts by which it was handled, and the deliberative outcomes reached.

Agenda composition and control

How the business is structured before the session and how it is altered once the session has opened.

Agenda item structure

The items of business set down for the occurrence, their ordering, purpose, sponsorship, supporting papers and time allocation.

  1. Which items make up the agenda, in what order, and what purpose does each item serve? composition
  2. Who sponsors each item, and what outcome is expected from it? ownership
  3. Which supporting papers are tabled for each item, and from where do they resolve? relationship
  4. How much time is allocated to each item, and what happens when the allocation is exceeded? constraint

Agenda adoption and amendment

The procedural act of adopting the agenda and the in-session changes that add, withdraw, reorder, defer or carry over business.

  1. Was the agenda formally adopted, and what distinguishes the provisional version from the adopted one? decision
  2. How are items added, withdrawn or taken out of order once the session has opened? process
  3. Which items were deferred, and to which future occurrence were they carried? temporal
  4. Which items may be disposed of without debate, and under what condition? constraint

Procedural acts and floor management

The sequence of procedural acts during the occurrence and the allocation of the right to speak.

Procedural acts

The ordered procedural acts of the occurrence — call to order, suspension, resumption, points of order, closure of portions and adjournment — with their declaring officer and rule basis.

  1. Which procedural acts occurred during the occurrence, and in what order? event
  2. Who declared each procedural act, and under which rule was the declaration made? authority
  3. Which procedural objections were raised, and how was each disposed of? exception
  4. How is the sequence of proceedings reconstructed if the occurrence is interrupted or the capture fails? process

Floor and speaking management

How the right to speak is allocated, how contributions are attributed, and who may restrict a participant's channel during the occurrence.

  1. How is the right to speak allocated, and in which order are speakers taken? process
  2. Which contributions are attributed to which speaker, and in what capacity did that speaker contribute? provenance
  3. What speaking-time limits apply, and how is an overrun handled? constraint
  4. Who may mute, remove or otherwise restrict a participant's channel, and on what ground? authority

Motions, voting and outcomes

Questions put to the occurrence, the method by which they were decided, and the follow-up that flows from them.

Motion and vote conduct

How a question is put, by which method it is decided, what tally results and who declares the outcome — the conduct of deciding, not the durable decision itself.

  1. What question was put to the meeting, who moved it, and was a seconder required? process
  2. By which voting method was the question decided, and what threshold applied? decision
  3. What was the tally, including abstentions, and who declared the result? measurement
  4. Which participants were excluded from the vote, and on what basis? exception
  5. How is a tied or failed vote resolved at this occurrence? constraint

Outcomes and follow-up assignment

What the occurrence concluded, which conclusions require a separate durable decision record, and what follow-up work was assigned or referred.

  1. Which conclusions did the occurrence reach, and which of them require a separate durable decision record? decision
  2. Which follow-up actions were assigned, to whom, and by when? ownership
  3. Which matters were referred to another body or to a later occurrence? relationship
  4. What evidence shows that an outcome was actually reached rather than merely discussed? evidence
In-session capture and record obligation What was captured while the occurrence ran, on what basis, and which durable records the occurrence owes to whom.

Capture and record hand-off

Recording and live transcription performed during the occurrence, and the obligation to produce durable records from it.

Recording and transcription capture

Whether and how the occurrence was recorded or live-transcribed, the notification and consent basis for doing so, and where the captured media are held pending disposition.

  1. Was the occurrence recorded or live-transcribed, and which portions were captured in which modality? event
  2. How were participants notified before capture began, and where consent was required, how was it obtained and recorded? privacy
  3. Which capture media were produced, and where are they held pending disposition? provenance
  4. What happens to captured media if a participant withdraws consent after the occurrence? exception

Record production obligation and linkage

Which durable records the occurrence owes, under which rule, who must produce and certify them, and how they anchor back to items and acts of this occurrence.

  1. Which durable records must this occurrence produce, and under which rule is each one required? requirement
  2. Which minimum content must the required record carry for this meeting type? constraint
  3. Who is responsible for producing the record, and who must certify its accuracy? ownership
  4. How is the produced record linked back to this occurrence and to individual agenda items and procedural acts? relationship
Confidentiality, admission and interchange How open the occurrence is, what personal data it holds, and how it is projected into external vocabularies and platforms.

Openness, admission and personal data

The openness determination and its procedure, who may be admitted to observe, and the personal data the occurrence holds about participants.

Openness, closure and admission

Whether the occurrence or parts of it are closed, on what ground and by what procedure, and who may be admitted to observe what remains open.

  1. Is the occurrence open to observers, and which portions of it are closed? access
  2. On which stated ground is each closed portion justified, and who certified that the ground applies? authority
  3. What procedural step is required before a portion may be closed? process
  4. Who is entitled to observe without participating, and which registration or accreditation conditions apply? constraint
  5. On what ground may an attendee be excluded during the occurrence, and what embargo applies to what they learned? security

Personal data held by the occurrence

The inventory of personal data the session context holds about participants, why each element is necessary, and when it becomes due for disposition.

  1. Which personal data about participants does the session context hold, and why is each element necessary? privacy
  2. What is the stated basis for processing attendance, contribution and capture data at this occurrence? authority
  3. Which sensitive or special-category disclosures may arise during the occurrence, and how are they contained? security
  4. When does session-held personal data become due for disposition, and which policy owner executes that disposition? retention

Interchange and platform binding

Declarative mapping of the occurrence into external calendar, event and conferencing vocabularies, with the lossy points and reconciliation rules recorded.

Interchange and platform binding

Which external vocabularies and platforms the occurrence is projected into or bound to, which mappings are lossy, and which system holds authority for which field.

  1. Which external calendar or event vocabularies is this occurrence projected into, and which fields map without loss? interoperability
  2. Which local concepts have no equivalent in a target vocabulary, and how are they carried across? constraint
  3. How are conflicting copies of the same occurrence reconciled across systems? validation
  4. Which conferencing platform hosts the occurrence, which object identifier does it assign, and which of its data is authoritative here? provenance
  5. What must be exported and retained if the hosting platform is decommissioned or the tenancy ends? retention

Classifiers Filled

Family
World Models
Category
Activities and processes
Entry kind
event
Navigation path
NAV.ACT.MTG
Domain
ACT.MTG
Industry
Cross-industry
Tags
meetingsessionact.mtg

What it is Filled

WM-ACT-025 models one bounded occurrence in which two or more parties are convened, synchronously or in mixed mode, to transact business under a shared agenda. It covers the occurrence from convocation to close: how it is identified and classified, on whose authority it was called, when and where it takes place, who was invited and who was actually present, what was on the agenda, what procedural acts and votes occurred, what outcomes were reached, what was captured during the session, how open the session was, and which durable records it owes. It deliberately stops at the boundary of the artefacts it produces and the actors it references: minutes and transcripts (WM-REC-012), decision records (WM-REC-010), the convening body (WM-ORG-018), parties, places, tasks and documents are referenced with subject-specific binding parameters only. The model is storage- and interface-neutral; iCalendar, JSCalendar, schema.org, XCON and vendor conferencing objects are alignments and projections, not the semantics.

In scope

  • Identity, classification and revision of a single meeting or session occurrence, including its position in a recurring series.
  • Binding to the convening authority and the convocation notice, with the sufficiency tests attached to that notice.
  • Planned and observed timing, suspension and resumption, rescheduling, postponement and cancellation of the occurrence.
  • Physical setting, virtual conferencing endpoints, mixed-mode equivalence, reserved resources and accessibility provision.
  • Invited and actual participation: roles, invitation response state, delegation and proxy, presence observation and recusal.
  • Quorum determination at this occurrence, measured against a threshold rule owned by the convening body.
  • Agenda composition, adoption, amendment, deferral and carry-over, with references to tabled papers.
  • Conduct of proceedings: procedural acts, speaking-turn management, motions, voting method, tally and declared result.
  • Outcomes reached and follow-up assignments, expressed as references to the records and tasks that carry them.
  • In-session capture (recording, live transcription) with notification and consent basis, and the obligation to produce durable records.
  • Openness and closure of the session or its portions, observer admission, and the inventory of session-held personal data.
  • Declarative alignment to calendar, event and conferencing vocabularies.

Out of scope

  • Drafting, approval, authenticity, publication and disposition of the minutes or transcript — owned by WM-REC-012; 'approval of the minutes' appears here only as an agenda item of a later session.
  • Content, status, rationale, supersession and implementation tracking of decision records — owned by WM-REC-010.
  • Composition, mandate, terms of reference, standing membership, chair designation rules and delegated powers of the convening body — owned by WM-ORG-018.
  • Master identity, contact data and affiliation of persons and organisations — owned by the adopting Dimension's party models.
  • Master data for places, buildings and rooms — only the reference and a local room designation are held here.
  • Generic occurrence semantics shared by all activities — owned by the parent model WM-ACT-018.
  • Execution and completion lifecycle of assigned actions — owned by the task model.
  • Version and custody management of tabled papers — owned by the document model.
  • Runtime evaluation and enforcement of access decisions, and storage of audit trails; this model carries classifications and references to audit events only.
  • Operation of calendaring transport (iTIP, CalDAV) and conferencing media transport, floor-control protocol mechanics and codec negotiation.
  • Decisions taken without a meeting (written resolutions, silence or written procedure) where no session occurrence exists.
  • Meeting-effectiveness analytics, sentiment scoring and engagement metrics.

Why it exists Filled

Provide the context an agent needs to convene, run, observe and hand off a single meeting or session occurrence — identity, convening basis, timing, setting, participation, agenda, conduct, outcomes and record obligations — without owning the durable records, the convening body or the parties it references.

Distinguishing features Filled

  • A meeting is a convened occurrence with participants, an agenda and a procedure; minutes (WM-REC-012) and decisions (WM-REC-010) are separate records.
  • It differs from a calendar entry, which only schedules, and from a conferencing platform, which only carries the session.
  • Its openness is classified before it opens, and closing a portion needs a recorded procedural basis.
  • It references decisions and tasks without mirroring their state.

What robots and AI may and may not do Filled

Must not

  • Record, transcribe or analyse a session without a declared purpose and notice to participants.
  • Close a public session or portion without the required procedure.
  • Declare a vote result that was not counted under the meeting's rules.
  • Keep presence or contribution data beyond the procedural or record need.

Only with a human decision

  • Closing a session or portion to the public.
  • Declaring a vote result with formal effect.
  • Cancelling or postponing a session with statutory notice requirements.

May

  • Compile and circulate an agenda with supporting papers.
  • Send invitations and collect responses.
  • Determine quorum from recorded presence.
  • Emit a calendar projection of the session.

Moral aspects Filled

  • Recording and transcription affect participants' privacy and freedom to speak openly.
  • Open meetings of public bodies serve transparency and accountability.
  • Remote formats must not exclude participants with disabilities or weak connections.

Who is affected

  • Participants and members
  • The public with a right to attend
  • People discussed in the meeting

Owners Filled

Steward

Name one accountable owner for the Meeting / Session package who can decide classification code lists, approve alignment mappings and sign off breaking changes; the registry entry currently carries only a placeholder owner and must be resolved before the model leaves candidate status.

Roles

Model owner
Decide and publish the local code lists, the identity priority and the authoritative master system for meeting identifiers; Approve alignment mappings and record conflicts rather than resolving them silently; Sign off breaking changes and their migration path
Session secretariat or clerk
Create the occurrence, issue notice within the required lead time and circulate accessible agenda materials; Maintain the attendance register, quorum determinations, procedural act sequence and division records during the occurrence; Commission the durable records owed and bind the returned references and anchor maps
Presiding officer
Declare procedural acts, rule on objections and declare voting results; Determine and certify the closure of portions on a stated ground where the regime permits it; Confirm the accuracy of the attendance and division records for which the applicable regime requires certification
Interoperability steward
Maintain and test the field mappings to calendaring, event and conferencing vocabularies and record every lossy point; Maintain the bound external identifier map and the field authority flags between platform and local copies; Trigger export obligations before a platform's source retention window closes
Data protection and records liaison
Maintain the personal data inventory, necessity statements and processing bases for occurrence-held data; Resolve the applicable retention floors and record disposition due instants and returned outcome references; Route erasure, restriction and disposal requests to the owning policy and record models rather than executing them here

Links to other meta-models Filled

extends

  • WM-ACT-018 — parent activity or occurrence model - Specialise the generic occurrence with the deliberative surface only: agenda, quorum determination, procedural acts, motions, capture and record obligation. Generic occurrence identity, scheduling status and cancellation semantics remain defined by the parent and are not redefined here.

child

  • WM-REC-012 — minutes or transcript record - Carry the obligation to produce a durable record, its required content, producer and certifier references, and the anchor map from items and acts to record passages. The record's draft, approval, correction, authenticity, publication and disposition lifecycle stays with the target. Mandatory where an open-meeting or company-law regime applies; absent otherwise.
  • WM-REC-010 — decision record - Route a declared outcome to a durable decision record and hold the returned reference. Decision rationale, status, supersession and implementation tracking belong to the target; only the conduct of putting and deciding the question is modelled here.

references

  • WM-ORG-018 — governance body - Bind the occurrence to the body that convened it and resolve the quorum threshold, voting entitlement and presiding rules from it at read time. Membership, mandate and delegated powers are not copied into the occurrence.
  • Party model for persons and organisations (identifier assigned by the adopting Dimension) - Resolve every invitee, presiding officer, speaker, voter and assignee to a mastered party. Role, invitation status, presence intervals and recusal are occurrence-scoped and held locally; identity attributes are not.
  • Place and facility model (identifier assigned by the adopting Dimension) - Resolve the venue and reserved rooms. The occurrence holds the reference, a local room designation and capacity only.
  • Document model for tabled papers (identifier assigned by the adopting Dimension) - Bind agenda items to the versions of the papers tabled for them. Document versioning and custody remain with the target.
  • Task or action model (identifier assigned by the adopting Dimension) - Hand off assigned follow-up actions with assignee and due date. Execution, progress and completion lifecycle belong to the target.
  • Access-policy evaluation and audit-event services of the adopting Dimension - Carry openness classifications, closed-portion markers and references to audit event identifiers. Authorisation evaluation, enforcement and audit-trail storage are performed and owned by the target services.
  • Records retention schedule and data-protection policy of the adopting Dimension - Resolve retention floors and disposition rules for occurrence-held data. The model records due dates and outcome references; the target owns and executes disposition.

aligned

  • IETF RFC 5545 iCalendar and RFC 5546 iTIP - Align occurrence identity, recurrence, participant roles and statuses, status values and revision semantics to the normative calendaring vocabulary; mapping is declarative and recorded conflicts are not silently resolved.
  • IETF RFC 8984 JSCalendar and RFC 9073 event publishing extensions - Align participant, virtual location, structured participant type and resource semantics; note that JSCalendar excludes participant-only changes from the sequence counter, which the local revision rule mirrors.
  • schema.org Event - Align attendance mode, event status, organiser and attendee roles, superordinate and subordinate event links, and the recordedIn relation used for the durable record link. The postponed and rescheduled statuses have no lossless calendaring equivalent and are recorded as a conflict.
  • OASIS Akoma Ntoso Version 1.0 debate vocabulary - Align procedural act kinds, roll call, quorum, voting and speech attribution vocabulary. Akoma Ntoso models the debate document rather than the occurrence, so its document-level structures belong to WM-REC-012.
  • IETF RFC 6501 XCON conference information data model - Align the conference object identifier, admission policy and platform role vocabulary. Conference state, floor control mechanics and media handling remain the platform's runtime concern.
  • IANA iCalendar Element Registries - Source governed code lists for participation statuses, participation roles, calendar user types, methods, classifications, participant types, resource types and feature types instead of minting local equivalents.

neighbor

  • WM-REC-012 — minutes or transcript record - This model records that a record is owed, which content the applicable regime requires, who must produce and certify it, and which agenda item each passage anchors to. The record's own draft, approval, correction, authenticity and disposition lifecycle belongs to WM-REC-012.
  • WM-REC-010 — decision record - Putting a question, the voting method, the tally and the declaration of the result are session conduct and are modelled here. The durable decision with its rationale, status, supersession and implementation is carried by WM-REC-010 and referenced by identifier.
  • WM-ORG-018 — governance body - Quorum thresholds, membership, voting entitlement and delegated powers are properties of the body's constitution. This model records only the determination made at this occurrence and the officer who presided over it.
  • WM-ACT-018 — parent activity model - Generic occurrence identity, scheduling status and cancellation semantics common to all activities are inherited from the parent. This model specialises only the deliberative surface: agenda, quorum, motions, capture and record obligation.
  • Party models for persons and organisations - Participants are references. Role, invitation response, presence intervals and recusal are occurrence-scoped facts held here; names, addresses and affiliations are not mastered here.
  • Access-policy evaluation and audit services - The model classifies openness, marks closed portions and stores references to audit events raised elsewhere. It does not evaluate authorisation, enforce it, or hold the audit trail.
  • Conferencing platform (XCON model or vendor service) - Conference object state, admission policy enforcement, floor control and media handling are the platform's runtime concern. This model binds the conference object identifier, the published endpoints and the exported attendance observations.
  • Calendar interchange formats - iCalendar, JSCalendar and schema.org Event are alignments. Mappings are recorded with their lossy points; no conformance is claimed and no format is required by the semantics.

parent

  • WM-ACT-018

contains

  • WM-REC-012
  • WM-REC-010

What else AI and robots need to interact with it Filled

Identity and identifiers required Filled

  • Authoritative master-system identifier issued by the system of record for meetings in the adopting Dimension — for example the governance secretariat's meeting register identifier or the docket number of the convening body — which always takes precedence when it exists.
  • Governed global identifier or IRI published for the occurrence, such as a domain-qualified calendaring UID or a Dimension-controlled URI, used when no master-system identifier has been issued.
  • UUID or ULID assigned by the adopting Dimension as a last resort, retained as an alias once a master-system identifier is later issued so that existing references continue to resolve.
  • A meeting date, a room booking reference, a position in a series, a conferencing join code or an agenda title is never an identifier; each may be an attribute or a bound external identifier, but none may be promoted to primary identity.

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Filled

  • A meeting has a convenor, a time, a place or channel, an agenda and invited participants.
  • Confused with a calendar event, an informal call, a conference platform session and the minutes.

Capabilities and actions required Filled

  • Convene session: Create an occurrence entry bound to a convening authority, assign its identifier and fix its classification before any notice is issued.
  • Compile and circulate agenda: Assemble items with order, purpose, sponsor, tabled-paper references and time allocation, and circulate them in accessible formats within the required lead time.
  • Dispatch invitations and collect responses: Issue the invitation to each invited party with its role, and record returned participation statuses, delegations and counter-proposals without altering the occurrence's revision for response-only changes.
  • Determine quorum: Compare the observed present population against the threshold rule resolved from the convening body and record the determination with its instant and counted base.
  • Sequence proceedings: Record the ordered procedural acts of the occurrence and the speaking turns allocated under them, each with a declaring or presiding officer reference and an event instant.
  • Conduct vote and declare result: Put a question, apply the chosen voting method and threshold, record the tally and any exclusions, and record the declaration of the result as conduct of the occurrence.
  • Revise or cancel schedule: Change the time, setting or status of the occurrence, increment the revision sequence, and issue the corresponding scheduling messages and re-notice where required.
  • Determine openness and close a portion: Record the openness determination for the occurrence or a named portion, the ground relied on, the procedural step taken and the certification obtained.
  • Commission durable records: Emit the record obligations owed by the occurrence to the owning record models, with content requirements, producer and certifier references and anchor points, and record the returned identifiers.
  • Emit interchange projection: Produce a projection of the occurrence into a named external vocabulary, recording the field mapping actually applied and every lossy point rather than silently dropping data.

Hazards and failure modes required Filled

  • Invalid decisions due to quorum or notice errors.
  • Unauthorized recording or sharing of the session.
  • Leak of content from a closed portion.

Standards and interfaces required Filled

  • W3C WebRTC for real-time media.
  • RFC 6501 XCON conference information data model.
  • RFC 5546 iCalendar Transport-Independent Interoperability Protocol (iTIP).

Context of use required Filled

  • Recording legality varies by jurisdiction, including between all-party and one-party consent regimes. The model records a consent basis and notification facts but makes no legality determination.
  • The open-meeting obligations, closure exemptions and minute-content requirements cited are United States federal; equivalent regimes in other jurisdictions differ in the closure grounds, the certification role and the retention floor.
  • The ten-year retention floor for meeting records is drawn from UK company law and applies to companies constituted under it, not to public bodies or to other jurisdictions.
  • Quorum, proxy, casting-vote and written-resolution rules are entity-type and jurisdiction specific and are always resolved from the convening body's instrument rather than defaulted here.
  • Time handling assumes proleptic Gregorian dates and IANA time zone identifiers; non-Gregorian recurrence and jurisdictions with irregular daylight-saving changes need the named zone retained, which is why an offset alone is not accepted.
  • Platform retention windows and export behaviour are vendor and tenancy specific; the one-year attendance report window cited is one vendor's documented policy, not a general rule.

Sources Filled

  1. RFC 5545: Internet Calendaring and Scheduling Core Object Specification (iCalendar) - Internet Engineering Task Force (IETF)
  2. RFC 8984: JSCalendar: A JSON Representation of Calendar Data - Internet Engineering Task Force (IETF)
  3. RFC 9073: Event Publishing Extensions to iCalendar - Internet Engineering Task Force (IETF)
  4. RFC 5546: iCalendar Transport-Independent Interoperability Protocol (iTIP) - Internet Engineering Task Force (IETF)
  5. RFC 7986: New Properties for iCalendar - Internet Engineering Task Force (IETF)
  6. RFC 6501: Conference Information Data Model for Centralized Conferencing (XCON) - Internet Engineering Task Force (IETF)
  7. RFC 3339: Date and Time on the Internet: Timestamps - Internet Engineering Task Force (IETF)
  8. iCalendar Element Registries - Internet Assigned Numbers Authority (IANA)
  9. Event — Schema.org Type - Schema.org Community Group (W3C)
  10. Akoma Ntoso Version 1.0 Part 1: XML Vocabulary, OASIS Standard - OASIS LegalDocML Technical Committee
  11. Companies Act 2006, Part 13, Chapter 6: Records of resolutions etc. - UK Government (legislation.gov.uk, The National Archives)
  12. 5 U.S.C. § 552b — Open meetings (Government in the Sunshine Act) - Legal Information Institute, Cornell Law School (reproducing the United States Code)
  13. 5 U.S.C. § 1009 — Advisory committee procedures (Federal Advisory Committee Act) - Legal Information Institute, Cornell Law School (reproducing the United States Code)
  14. Accessibility of Remote Meetings (W3C Group Note) - World Wide Web Consortium (W3C), Accessible Platform Architectures Working Group
  15. meetingAttendanceReport resource type — Microsoft Graph v1.0 - Microsoft

Open questions

  • Locate a primary procedural-rules authority (standing orders, parliamentary procedure or a legislative rules-of-order source) to support motions, seconders, points of order, casting votes and tied-vote resolution; Akoma Ntoso is a debate-document vocabulary by the model's own concession and cannot carry the conduct surface alone.
  • Establish which model owns the recurring series definition. The structure asserts it belongs to WM-ACT-018, but the frozen relationship contract records WM-ACT-018 only as a parent and contains no series relation, leaving the inheritance and override rules uncontracted.
  • Search for a governed vocabulary of meeting-level security controls — lobby and admission policy, watermarking, exfiltration limits, moderator credential handling — to close the dimension currently and correctly marked as a gap rather than fabricated.
  • Re-check IANA registries, RFC 9073 and any newer conferencing work for a normative crosswalk between iCalendar ROLE, JSCalendar roles and XCON roles; the absence of one is currently recorded as a conflict and should be re-tested rather than left permanently open.
  • Test the retention and closure claims against at least one non-Anglo-American regime (EU or other civil-law open-meeting and corporate record rules) so that the two-jurisdiction basis of the strictest-floor reasoning is not mistaken for a general rule.
  • Add an accessibility authority with normative force (EN 301 549, WCAG or an equivalent statutory baseline) alongside the W3C Group Note, which the model itself treats as guidance rather than a requirement.
  • Scope the declared sibling model for decisions taken without a meeting (written resolutions and silence procedure), which is excluded by definition here and currently has no home in the registry.
  • Re-verify the vendor attendance-report retention window and export behaviour against current vendor documentation, and confirm whether the platform-exit-obligation question is satisfiable within that window.
  • Multilingual regimes beyond the fact that interpretation was provided: language coverage per speaker, booth assignment and relay chains are not modelled.
  • Floor control protocol mechanics, media negotiation and codec selection; only the floor control policy code and the resulting speaking turns are held.
  • Cost, travel, catering and logistics of convening a meeting.
  • Hearing and tribunal specifics — oath administration, witness examination sequence, exhibits and evidentiary rulings — are only partially reachable through the generic procedural act vocabulary.
  • Machine-evaluable encoding of standing orders, so that a rule such as a casting-vote entitlement can be checked automatically rather than recorded as text.
  • Decisions taken without a meeting (written resolutions, silence procedure) are excluded by definition and need a sibling model if the adopting Dimension transacts business that way.
  • Anonymous or unregistered public attendance at large open meetings, where a per-party presence record cannot be produced.
  • Meeting-effectiveness analytics and engagement scoring.

Machine files

Card as JSON Specification AGENTS.md Source Card backlog vercy.card/1

Provenance

world-models research · reviewable-draft

Built from: models/wm-act-025-meeting-session/spec.yaml, ver-cy/world-models/card-supplements/wm-act-025-meeting-session.json