Thanks you all so much for all the suggestions and engagement!!
@byarielm.fyi, an audit of existing overlap would be super helpful.
@mfzx.net , I think your suggestion is great, but also tangential to what I’m looking for? If I understand correctly, MASL is the actual rich metadata that would describe an image. I’m interested in something more like standard.site, which is simply a distribution shell - so an arbitrary number of different apps can publish images to the lexicon, which can then be read by an equally arbitrary number of apps. think a MASL body could live inside this distribution, but it’s not top priority. Lmk if I’m understanding this wrong, as it’s entirely new to me!
@bmann.ca I don’t understand how Atmosphere blob storage works to be able to speak intelligently to your questions. That said, a concrete example is - here’s a Luminframe record: PDSls , which references the image in blog storage. I’m thinking that a future state publish workflow on Luminframe would create both its bespoke lexicon record and this new proposed record. the Luminframe could either continue referencing the blob image directly, or instead create the global image version first and then the luminframe.image would reference the community.image record. I prefer the reference idea.
@al9000.com I agree with Boris that it makes sense to keep it small and grow organically, especially because I’m interested in distribution and not in describing an image in full detail. That said, I can forsee this evolving closer and closer to your more robust version as adoption picks up and more use cases are needed.
Thanks y’all. Let me know if I missed anything!!