Activities

This page is not normative

This page is not considered a core part of the Vultron Protocol as proposed in the main documentation. Although within the page we might provide guidance in terms of SHOULD, MUST, etc., the content here is not normative.

Activities are the core of the ActivityPub protocol. They are used to represent actions that are performed by actors. The ActivityStreams vocabulary defines a number of activities, and we extend these with specific activities that are used in the Vultron AS vocabulary. So far, we have found the ActivityStreams vocabulary to be sufficient for our needs, so our extensions are limited to specifying the types of activities, actors, and objects that are used in the Vultron protocol.

A full mapping of Vultron to ActivityStreams is available in the Vultron ActivityStreams Ontology.

Design Goals

Our goal in each of these activity definitions is to

• Avoid creating new activity types when an existing activity type can be used.
• Avoid creating defined activity types with the same objects and targets to avoid confusion. Each activity type / object / target combination should have a single meaning within the protocol.

For documentation purposes, we have divided the Vultron AS activities by user flow. Each of these user flows shows the activities that are used to perform a specific task. The user flows are:

• Reporting a Vulnerability
• Acknowledging a Report
• Initializing a Case
• Managing a Case
• Suggest Actor for Case
• Inviting an Actor to a Case
• Initializing a Participant
• Managing Participants
• Establishing an Embargo
• Managing an Embargo
• Status Updates
• Transferring Case Ownership
• Error Handling