Batch Annotation creation use case

I have read what documentation and examples I could find for Web Annotation and HTTP and there is a space in which I remain without an answer. Is there a protocol for unContained Annotations to be saved (updated/created) in a batch? With one Annotation, it is clear to return a `Location` header with the URL and similarly when creating a new Container.

In my case an interface creates n new Annotations that may share some relationship but do not belong in a Container together, I have a Web Annotation repository that would like to allow some `POST /batch` scenario with an array of JSON-LD Annotations for creating. The existing behavior returns 201 and a comma separated list of URLs in the `Location` header. Errors break the batch and the first error is returned. Is this unusual? It gets expensive to make 40 calls for a new set, so some batch option feels normal, but I cannot find any examples or guidelines.

In this case, we are building the interface(s) and the Annotation Store, but the Annotation Store is open to the public, so we want to put forth an API that is as congruent as possible with existing standards.

Thanks for your thoughts,

Patrick Cuba, Lead Developer
Walter J. Ong S.J. Center for Digital Humanities
Saint Louis University
+1.314.977.4249