Not if the data is siloed away in some app’s container that you don’t know to check.
That’s the crux of this proposal. It’s not removing the ability to have folder structures. But more enabling such data localisation and modification by any apps targeting that data label.
Currently (well… previously as we don’t have this implemented.), you’d do something like:
// this is all pseudo API let myPhoto = <data> let app = new Safe(<my app id>); // saved in apps own container app.save('/profile_pic', myPhoto); // and to retrieve let myPhoto = <data> let app = new Safe(<my app id>); // retrieved from apps own container let photo = app.get('/profile_pic')
Only this app knows about this data. No other app can access this photo.
With this proposal for apps to manage their own data
// more pseudocode let myPhoto = <data> let app = new Safe(<my app id>); // automatically labelled with `appId`, and saved in that index // ALSO has 'photo' label applied automatically app.save(myPhoto) // and to retrieve let myPhoto = <data> let app = new Safe(<my app id>); //retrieved from apps own index let photo = app.get('/profile_pic') // BUT ALSO let someOtherApp = new Safe(<another app id>); // if another app has 'photo' permissions let photo = someOtherApp.getFromIndex('photos', '/profile_pic');
It is the semantic in web, in that each index could be an RDF struct explaining what’s within, and referencing the data via URL. Just accessible across apps.
Indeed, it could / would be great to have these labels applied from a data’s RDF automatically. In which case, each index is simply a quick reference of all data of a particular type. Though as we don’t have RDF baked in yet, label’s is perhaps a shortcut.