- 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_.
This. It's a pretty awful way to present anything. The reader is still clueless and unsure about what they are reading even after navigating through 3 or so links. At each click I was hoping to read anything related to APIs but all I was reading is bureaucrat noise.
Perhaps it's a good idea. I can't tell. I wonder if anyone can.
The CRUD methods are great examples where we deviate from the AIPs.
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.
"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?