A language for describing resource-oriented APIs & turning them into Swagger or resource diagrams. Oriented around the concepts we want to expose in the APIs.
With numerous interactions among teams, we should have a way to coordinate definitions (structures, enumerations, ...) that are "owned" by one team and used by another. Here's a simple example. The Activations-BE team's Segment Delivery API needs an "identity mapping" that uses identifier types and precision levels. Those values typically would be defined by a reslang enumeration, but the "official" enumeration should be owned by the Identity team, not Activation.
As a suggestion, I imagine something like C's #include or Java's import. Simple textual inclusion seems sufficient for what we need. A search path would be a bonus.
With numerous interactions among teams, we should have a way to coordinate definitions (structures, enumerations, ...) that are "owned" by one team and used by another. Here's a simple example. The Activations-BE team's Segment Delivery API needs an "identity mapping" that uses identifier types and precision levels. Those values typically would be defined by a reslang enumeration, but the "official" enumeration should be owned by the Identity team, not Activation.
As a suggestion, I imagine something like C's
#include
or Java'simport
. Simple textual inclusion seems sufficient for what we need. A search path would be a bonus.