Overview
A service assigns work to a person or agent. The recipient can respond to the assignment and report its state. The proposal examines which existing task semantics can be reused.
This is a reuse assessment. Its operations and representation are still under discussion.
Proposed operations
Target: A task identifier, its assignment and the applicable update version.
- Accept or decline
- Respond to the assignment.
- Report progress
- Update the task’s recorded state.
- Report completion
- Provide a completion report. The service may still need to verify the work.
Inputs and results
Inputs. The assignment reference, response or progress information, and any completion evidence required by the service.
Results. A recorded assignment response or task update. Acceptance of an assignment and verification of its completion are separate states.
Permissions. Accepting a task does not grant access to the resources needed to carry it out. The service and client retain their existing permissions.
Human participation. The service’s task interface.
The behaviour is described here. A machine-readable representation has not yet been selected.
Check links in a documentation release
- A service assigns an agent to check links in a specified documentation release.
- The agent accepts the assignment and performs the permitted checks.
- It submits a report and the service records the update.
A cancelled or changed assignment needs to be reconciled before a completion report is accepted. Acceptance does not permit editing or publishing the release.
Existing standards
- iCalendar · RFC 5545
Defines task data through VTODO.
- iTIP · RFC 5546, section 3.4
Defines task responses and completion updates. A proposed MAP binding must identify any remaining gap.
Versions and open questions
Reuse assessment
The existing task protocols are being evaluated. No MAP binding or compatibility claim is established.
- The mapping to existing task semantics and whether a MAP binding is needed.
- Completion evidence, cancellation and changes to an accepted assignment.
Contribute to this definition →
Implementations
No implementation evidence has been published for this proposal.
Support declarations and test reports are supplied by their contributors. Listing them does not certify compatibility. Each targets a type version, execution profile and exact record.