[DATAGOV Core] Trying to recall a concept from Rocco Bellanova’s presentation

[Sruthi Vanguri]

Yes, mutable mobiles is what I had in mind too. Wondered if there was a different term.
Thanks Matteo :)

From: Mattéo Bard <m.bard at uva.nl>
Date: Wednesday, 11 March 2026 at 14:12
To: Sruthi Vanguri <s.vanguri at uva.nl>, Core Datagov <core at lists.datagovlab.net>
Subject: Re: Trying to recall a concept from Rocco Bellanova’s presentation

Hi Sruthi,

Could it potentially be mutable mobiles? It basically says that at every stage of a journey the data is not just stably transmitted but reconstructed. So every single transformation procedure creates a slightly different object which then creates this multiple relational layered structured that the interoperability database of eu-LISA is. Aka, data is not moved from one database to another, but copied and transformed to fit a new layer of databases that function for a different purpose.

All the best,
Matteo

From: Core <core-bounces at lists.datagovlab.net> on behalf of Sruthi Vanguri via Core <core at lists.datagovlab.net>
Date: Tuesday, 10 March 2026 at 19:56
To: Core Datagov <core at lists.datagovlab.net>
Subject: [DATAGOV Core] Trying to recall a concept from Rocco Bellanova’s presentation

Hi Team,

I’m working on my pilot and remembered a concept from Rocco Bellanova’s presentation in our office a few months ago that seems relevant to my work. Unfortunately, I can’t recall the exact term!

>From what I remember, he was discussing data journeys and the idea that a datapoint becomes a new entity at each step of its trajectory. In other words, it’s not strictly reproducible. The original entity itself does not pass through all stages; rather, each copy moves forward and becomes something slightly different. The data therefore does not remain stable across the journey. Basically, the opposite of Latour’s “immutable mobiles.”

This is a bit of a long shot, but does this ring a bell for anyone?

Thank you!!

Best,
Sruthi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ghserv.net/pipermail/core/attachments/20260311/8102c92b/attachment.htm>