I've been following the work and discussions that have been happening on the V2 API and have been wondering what the community thinks about the idea of also having some prescriptive, consumer-friendly services (prescriptive, yet extensible) and models around how to store metadata in the Atlas repository for particular types. These APIs would not replace, but supplement the more generic V2 API.
One example of a metadata 'domain' that might commonly be stored is that metadata that describing a data resource and how to connect to it. I think we can come up with a prescriptive model of how to store information about how to connect to common resources (e.g., relational dbs, files, etc.) so that users who want to store this kind of information in Atlas don't have to reinvent the wheel. I could also envision this facilitating cases where there are multiple Atlas repository deployments - having a similar model and services for accessing information of a similar type would be helpful. There are a number of other domains that could also be considered (e.g., discovery metadata such as profile data, classifications, quality etc.) - just wanted to open the discussion and get your thoughts on this. Has there been any discussion/thought on this topic to date? Best regards, Stephanie
