Relationship with a actual outcome of an action

When applying the RRMV to real world information, there is need for relating an Action(Result) to a (digital) materialisation of it. Without this connection the effort to express the legislation in terms of RRMV stays abstract.

We can distinguish 3 different kinds of real world information that carry important elements.

• The System: The technological infrastructure used to execute the Requirement’s actions. It typically has the capability to store the action results.
• The Data Flow: The pathway through which data is transmitted within the system for a specific action conducted by concrete agents at known temporal moments.
• The Individual submission: The actual delivery of the mandated result by a single, unique agent.

To illustrate the above aspects: for the reporting in the context of the Regulation (EU) 2018/1999 on the Governance of the Energy Union and Climate Action, reportNet is the system via which MSs are providing the information. Since this is a regular, yearly process that must be performed the policy officer creates a data flow to collect all submissions of all MS for a given year. (aka Reporting article 26 in 2024, 2025, ...) In such a data flow, each year may have additional guidelines or methodes that apply to all MSs for that year. The existence of a data flow is natural because the assessment of the individual submissions is often a relative comparision to the other submissions in the same data flow.
Within that data flow, an individual submission is being recorded.

The request is to provided properties for capturing the above information. Suggestion is to associate these properties with the class ActionResult. As these properties are very closely related to the provisioning of the result of an Action.