Is this a clone of the Google AIPs? Like https://aep.dev/160/ seems to just copy https://google.aip.dev/160.
This looks like a useful set of guidelines. I see the most value in reducing the bikeshedding which invariably happens when designing an API. I wonder if anyone is using AEP and can comment on downsides or problems they've encountered.
One thing I've noticed is that the section on batch endpoints is missing batch create/update. Also batch get seems a little strange - in the JSON variant it returns an object with a link for missing entities.
I don't know if I just don't get it, but this feels like it's describing... an API?
"Identify standard operations
Section titled “Identify standard operations” Once the resources are defined, identify one or more standard methods for each of those resources. Standard methods operate on the lifecycle of a resource lifecycle: namely, they create, read, update, delete, and list resources."
I mean... yes?
I miss the days when "API" meant any programming interface - not just web/rpc - and good API design was about providing the right level of abstraction and making doing the right thing easy and the wrong thing hard, not just CRUD.
On the landing page one can find:
- a list of AEPs (explore the AEPs)
- a link to the AEP ecosystem
- a description of how AEPs are built
- a list of AEP clients
- something to do with open standards and versioning
- a blog
and
- a single sentence suggesting the project has something to do with APIs
If any maintainers stop by this comment section, I suggest offering some explanation about what this project _does_.