You make a very good point here. Solid is obviously a considerably more advanced version of what I tried to do here. The main motivation for my project was to ease transactions like registrations, logins and any other forms of identification or information sharing. Like in the case of Solid, my idea was to try and standardize data by organizing it by topics & keys.

The main differences compared to Solid, would be the non-decentralized data storage (smartphone) and the active user involvement in each data sharing transaction, meaning the user has to actively scan a QR code (later other forms can be added like NFC, etc.) for the data sharing to take place (as opposed to Solid, where data can be read indefinitely by an app until access is revoked). An extra thing that Qodebeam provides is (user-supervised) write access, meaning a service can also request to save something in the user data store.

Overall, I'd say it's just a (slightly) different approach to the problem of personal data ownership and sharing. Maybe something that would work well as an intermediate step towards something more advanced like the Solid offering. I hope it makes sense.