As interaction traces are coming from personal activities, it is mandatory to manage properly the way these traces are accessed. The general idea is to consider any M-trace (managed through a TBMS : Trace Base Management System) as an atomic resource which is available if a valid token is provided by the “consumer program” (i.e. the program which could make a get, a put, a post or a delete on a trace depending on the rights given by the token). This section aims to document this process and to describe the corresponding protocols for programs aiming to access M-Traces managed through such a process.

The following figure illustrates the secured access to a M-Trace.