Communication and collaborative meeting
Meeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Research draft, second pass
A second pass drafted this model: the structure a model of this thing needs, and what is known about it in the world. The line under this one says how the second half was obtained - researched against sources, or recalled without web access, in which case nothing here was read anywhere and every claim is a lead to verify. Unreviewed either way.
Bundle → Layer → Finding → Questions Missing, in the backlog
Not described yet. This gap is in the card backlog.
Note: Research contour: bundles not designed yet; questions are listed as open questions.
Classifiers Filled
- Family
- Enterprise profiles
- Category
- Enterprise subject
- Entry kind
- subject
- Domain
- EnterpriseKNW
- Industry
- Cross-industry
- Tags
- EM-KNW-03W2subjectMeetingMeetingParticipationCommunicationChannelDiscussionThreadMessageReference
What it is Filled
Meeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Why it exists Filled
Meeting, participants, agenda, channel, discussion and outcomes. An assignment and a decision are created as separate objects with provenance.
Distinguishing features Derived, awaiting review
- Minutes do not prove everyone's consent
- A decision has an authority
- A quote preserves its source and access scope
What robots and AI may and may not do Derived, awaiting review
Must not
- Negative case: A phrase in a chat is automatically treated as an approved policy.
Note: Negative case of the research brief, not yet a rule for agents.
Moral aspects Missing, in the backlog
Not described yet. This gap is in the card backlog.
Owners Filled
Steward
Владелец базы знаний / корпоративных записей
Master systems
- DMS
- wiki
- журнал решений
Links to other meta-models Filled
references
- WM-ACT-025 - conceptual-candidate
- WM-REC-012 - conceptual-candidate
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Derived, awaiting review
- Meeting
- MeetingParticipation
- CommunicationChannel
- DiscussionThread
- MessageReference
Direct properties not applicable Not applicable
Not applicable
Enterprise record contour: physical properties belong to referenced world models.
Recognition required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Hazards and failure modes required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Context of use required Missing, in the backlog
Not described yet. This gap is in the card backlog.
Sources Filled
- W3C PROV: claims, sources and actions
- SKOS: concepts, definitions and mapping
- DMS/wiki/ADR practice: document, version, carrier and decision
Open questions
- How to distinguish presence from consent?
- What is carried over from a discussion into an official fact?
- How to observe access rules for the original communication?
- Установить границу и решение reuse/extend/new по действующим спецификациям.
- Подтвердить semantic crosswalk, права и source mastership.
- Выбрать immutable refs; провести проверки fixtures до заявления о публикационной готовности.
Machine files
Provenance
enterprise research programme · published-partial
Built from: enterprise/models/em-knw-03/brief.json
Still in Russian: suggested owner, blocking decisions, vercy candidates. Translate in research/enterprise/i18n/units.en.json.