https://w3id.org/jeswr/task#⚠️ Experimental — AI-agent-generated (Claude Opus 4.8, @jeswr PSS agent); under active development, not production-hardened.
Other representations: Turtle · JSON-LD context · index
| Term | Label | Comment |
|---|---|---|
http://purl.org/dc/terms/created | created | Creation timestamp (xsd:dateTime) of the task (dct: relation). |
http://purl.org/dc/terms/creator | creator | WebID of the task creator (dct: relation). |
http://purl.org/dc/terms/description | description | Task body / description (dct: relation). |
http://purl.org/dc/terms/title | title | Task title (the dct: relation used for the human-readable summary). |
assignee | assignee | The WebID of the agent a task is assigned to. Drives the cross-app 'tasks assigned to me' federation query. |
Closed | Closed | Lifecycle state class: the task is closed. Asserted as rdf:type on the task subject (never a literal). |
Open | Open | Lifecycle state class: the task is open. Asserted as rdf:type on the task subject (never a literal). |
State | Workflow State | The shared workflow-state / board-column class — re-used from the W3C workflow ontology. solid-issues persists each tracker column as a per-tracker #status-<slug> rdfs:Class typed wf:State (subclass of wf:Open or wf:Closed), declares the entry column via wf:initialState, and the per-state reachable columns via wf:allowedTransitions. It is restated here because it is the domain of the tm: WIP-limit properties below. |
Task | Task | The shared task/issue class — one wf:Task per item, the SolidOS issue-pane model. |
Tracker | Tracker | The W3C workflow ontology issue tracker — the container of issues (wf:Task) and, here, the subject that carries its automation rules via tm:rule. Re-used, restated because it is the domain of tm:rule. |
http://www.w3.org/ns/odrl/2/Constraint | Constraint | ODRL 2.2 Constraint — a boolean condition `leftOperand operator rightOperand`. Re-used as a tm:Rule's tm:condition guard so the suite's existing @jeswr/solid-odrl constraint evaluator applies unchanged. Defined by the W3C ODRL vocabulary. |
http://www.w3.org/ns/odrl/2/leftOperand | left operand | ODRL 2.2 leftOperand — the subject of a condition (what about the issue/event is being tested, e.g. the new status, the priority). Re-used in a tm:condition odrl:Constraint. |
http://www.w3.org/ns/odrl/2/operator | operator | ODRL 2.2 operator — the relational operator of a condition (odrl:eq, odrl:neq, odrl:gt, …). Re-used in a tm:condition odrl:Constraint. |
http://www.w3.org/ns/odrl/2/rightOperand | right operand | ODRL 2.2 rightOperand — the value a condition's left-operand is compared against. Re-used in a tm:condition odrl:Constraint. |
action | action | An effect a tm:Rule performs when it fires and its conditions hold (the 'THEN'). Its value is a tm:Action — one of the coded actions (tm:SetStatus, tm:SetPriority, tm:Assign, tm:AddComment, tm:CloseIssue). A rule may carry several actions, all applied client-side. |
Action | Automation Action | The effect a tm:Rule performs when it fires and its conditions hold — the 'THEN' of an ECA rule. The suite's coded-value actions are instances of this class: tm:SetStatus, tm:SetPriority, tm:Assign, tm:AddComment, tm:CloseIssue. An action carries its parameter via tm:actionValue (e.g. the priority to set, the status slug, the assignee WebID, the comment body). The mutation is applied client-side. |
actionValue | action value | The parameter of a tm:Action — e.g. the priority literal for tm:SetPriority, the status slug for tm:SetStatus, the assignee WebID (an IRI) for tm:Assign, or the comment body literal for tm:AddComment. Its datatype / whether it is an IRI or a literal depends on the action; carries no fixed rdfs:range so it can hold either. Some actions (e.g. tm:CloseIssue) need no value. |
AddComment | add comment | Action: add a comment to the issue. The comment body literal is carried on tm:actionValue. |
Assign | assign | Action: set the issue's wf:assignee. The assignee WebID (an IRI) is carried on tm:actionValue. |
CloseIssue | close issue | Action: close the issue (move it to the workflow's terminal status). Needs no tm:actionValue. |
condition | condition | An optional guard on a tm:Rule (the 'IF') — its value is an odrl:Constraint (odrl:leftOperand / odrl:operator / odrl:rightOperand), the SAME constraint shape @jeswr/solid-odrl already evaluates, deliberately reused rather than minting a parallel condition vocabulary. A rule may carry several; the rule fires only when ALL its conditions are satisfied (a rule with no condition fires whenever its trigger fires). |
OnAllSubtasksDone | on all sub-tasks done | Trigger: every sub-task of a parent issue has reached a terminal (closed) state. The basis for the built-in 'complete parents automatically' automation. |
OnAssigned | on assigned | Trigger: an issue was (re)assigned (its wf:assignee changed). |
OnCreated | on created | Trigger: a new issue was created in the tracker. |
OnDueDatePassed | on due date passed | Trigger: an open issue's due date has passed (it is overdue). The basis for the built-in 'escalate overdue issues' automation. |
OnStatusChange | on status change | Trigger: an issue's workflow status changed. Pair with a tm:condition over the new status (an odrl:Constraint whose left-operand is the issue's status) to fire only on a specific transition. |
rule | rule | Links a wf:Tracker to one of its tm:Rule automation rules. The set of rules a tracker's collaborators evaluate client-side. |
Rule | Automation Rule | A tracker automation rule: an event-condition-action ('when X then Y') rule attached to a wf:Tracker. It bundles exactly one tm:trigger (the event that fires it), zero or more tm:condition guards (each an odrl:Constraint that must hold), and one or more tm:action effects to apply. Rules are persisted in the pod and evaluated CLIENT-side whenever fresh issue state is observed (pods have no server-side compute). The Jira/Monday automation model expressed in RDF. |
SetPriority | set priority | Action: set the issue's priority. The target priority is carried on tm:actionValue (e.g. "high"). |
SetStatus | set status | Action: move the issue to a workflow status. The target status slug is carried on tm:actionValue. |
trigger | trigger | The event that fires a tm:Rule (the 'WHEN'). Its value is a tm:Trigger — one of the coded triggers (tm:OnStatusChange, tm:OnDueDatePassed, tm:OnAllSubtasksDone, tm:OnAssigned, tm:OnCreated). Exactly one per rule. |
Trigger | Automation Trigger | The event that fires a tm:Rule — the 'WHEN' of an ECA rule. The suite's coded-value triggers are instances of this class: tm:OnStatusChange, tm:OnDueDatePassed, tm:OnAllSubtasksDone, tm:OnAssigned, tm:OnCreated. A trigger may carry refining data (e.g. the target status of a status-change) on app-defined properties; the coded value identifies the event class. |
wipMax | WIP maximum | The maximum number of work items (cards) allowed in a workflow state / board column — the upper bound of a kanban WIP (work in progress) limit (Jira's column 'Max', Trello/Monday's per-list cap). A client warns (or blocks the move client-side) when adding a card would push the column OVER this count, the core kanban mechanism for limiting work in progress so bottlenecks surface. Optional; absent means no upper bound. A non-negative integer. |
wipMin | WIP minimum | The minimum number of work items (cards) that should be in a workflow state / board column — the lower bound of a kanban WIP (work in progress) limit. A client warns when the column holds FEWER than this many open items (an under-filled column starves the flow). Optional; absent means no lower bound. A non-negative integer. |
Announce | Announce | ActivityStreams 2.0 Announce — the activity an app POSTs to a peer's inbox to notify of a task event (assignment, state change). The cross-app notification verb. |