What did you notice? :-) ... I would say they are kept and shown across revision changes. Up or down, as restoring a revision is actually an Up revision, so new revision anyway.

-Dave

Thanks Dave. We're actually not sure, because we hadn't been paying attention to the particular topic's comment state when looking at it in Review Space (we were focused on another problem entirely). Upon restoring the earlier version to throw away our troubleshooting changes, we suddenly realized there *might* have been a comment. There *was* a comment for sure according to a screen capture I took last Friday (yellow underlines on the interesting text), but there is no evidence of a comment now (yellow lines or an obvious actual comment).

So the Annotations (comments) are stored in the CMS repository and are available over the Annotations API endpoints.

If you were here before, then my way of making the Annotations API easily usable is through ISHRemote, see https://github.com/sdl/ISHRemote/ where Annotation cmdlets are available since v0.11

On a small repository, the below might still work, but at some point exporting everything over one call is not a good idea... 

New-IshSession -WsBaseUrl https://ish.example.com/ISHWS/ -PSCredential admin
Find-IshAnnotation | Out-GridView

Note that ISHRemote allows exporting per content object (DocumentObj) or Publication even. The Annotations are softly linked by logical/version/language identifier (not by card id)
New-IshSession -WsBaseUrl https://ish.example.com/ISHWS/ -PSCredential admin
Get-IshDocumentObj -LogicalId GUID-C7BE64D8-7543-44FE-B748-3DDA93CF29B3 | Get-IshAnnotation

-Dave

Awesome. I'll have to take some time and figure this out. What do you consider a small repository?