Hi,
So, an indexer receives a composite, derives the models and when requested starts indexing. Info on the models is stored in postgres. Its the user(dapp)'s responsibility to store the composite that is required to interact with the data. The composite is most often hardcoded as there is most often a fixed relationship between dapp and indexer.
There may however be use cases in which this relationship is more dynamic, for example in a distributed database as a service, where a dapp/user can re-create, and augment composites from models on offer ( by a cluster of indexers).
Where then do we store a users composites? There is an obvious candidate called ComposeDB. You may have heard about it
So, should we have a standard model to store composite information? Might this be something you are already working on? If so, would there be something i could use already?
Thanks, Joera