anchor.diff:  		    "event" : "The event type here",
   		    "data" : "The data here",
   		    "timestamp" : "The event timestamp",
  -		    "id" : "The event ID"
  +		    "id" : "The event ID",
  +		    "tag" : "A random value that looks like an UID"
       }
   	
   === version
  
positive.code: 
  `timestamp` and `id` are not defined by the producer but are assigned by the streaming platform.
  They allow to identify the message inside `Reactivity` system and to know when it has been published by the consumer.
  
  === Extensions
  
  
negative.code: * `organization`: the topic where events related to `Organization` are published  
  * `artifact`: the topic where events related to `Artifacts` are published
  
  This statement is true only when the client produce and consumes data directly from/to the topic (through `Kafka`).
  However, there is the particular case of a WEB application subscribing to a source of events comming from a suspended `SSE` connection from the server.
  
           +--------------+-------------+
  +------->|     Topic    |             |
  |        +--------------+             |       +-----------------+
  |        |     user     | Broadcaster |  SSE  |                 |
  |        | organization |             |------>| Web Application |
  |        |   artifact   |             |       |                 |
  |        +--------------+-------------+       +-----------------+
  |
  |        +---------------------------+
  |        |                           |
  +--------+           KAFKA           |
           |                           |
           +---------------------------+
  
  In this simple diagram we can see that the `Broadcaster` is consuming different topics from `Kafka`.
  When a message is received, it's pushed to the web application that established a `SSE` connection.
  The only chance for the web application to understand the type of data represented by a received message is to find `topic` attribute in the `JSON`.
  
      {
  		    "topic" : "organization|user|artifact"
  		    "version" : "...",
  		    "event" : "...",
  		    "data" : "...",
  		    "timestamp" : "...",
  		    "id" : "...",
  		    "tag" : "..."
      }
  		 
  === data
  
  The `data` contains the payload of the event provided by the producer.
  