annotation.id is a MUST #8
Description
But common/id.json only has a warning if the test fails.
If the thinking is to use common/id.json to test for ids on any resource, then the bug is actually in the title, description and errorMessage fields.
That said ... it is valid to send an annotation without an ID in a POST via the protocol to create a new annotation. Then there isn't any existing URI for it, as the server must assign one anyway. Worth flagging such cases in the test json?