this runs parallel to a lot of my thoughts. one thing that you don't quite address, and which i believe has derailed all efforts to do stuff like this, is the c

this runs parallel to a lot of my thoughts. one thing that you don't quite address, and which i believe has derailed all efforts to do stuff like this, is the challenge of getting a large group of developers to agree on a single set of data formats. it is only once you nail that, that doing many of the composition/copy/paste things become possible. some of these formats are easy: jpeg, png, utf-8. when it comes to something like: the meta data schema for a song? a recipe? that's a can of worms and flamewars. to some extent you've got the DBFS thing that everything shares but that's only of use for sharing so far as you can get easy agreement about what fieldnames should he available for a kind of thing. you've also got security concerns. if everything shares the same database, any random bit of code can ship that data off to a russian data mining op. or corrupt your song database. or encrypt everything and ransom it. you kind of address this by puttin a layer of indirection here, and having security and access managed via the message bus, but this needs a UI, and i don't think apple, android, or facebook has really mastered the ui for permissions.