Mandatory policy of server-generated IDs
Issue
JSON:API is open to the possibility of client-generated IDs in the creation of resources.
However, if we understand that every DestinationDate implementation is responsible for its own namespace (that is, its URL), the server should also have control of the IDs generation policies. This aligns nicely with the REST architectural style we adopt where a resource's URL acts as an identifier for users of the API. Also following modern standard for data interoperability, such as the FAIR principles, we should have resources' URLs acting as persistent URIs.
Proposal
Add to the standard that servers MUST generate their resources' IDs. These resources' IDs combined with their endpoints must serve as persistent URIs.