Give the client the possibility to to define which reference version to use

[ykoer]

Since we reference the most recent version of the document, it would make sense to give the client the possibility to pass a key/value list of document names and versions to use for the given client transaction.

[bserdar]

what is the exact need for this? Do you want to use the latest, or a particular one? how does the calling app know which one is the latest? Would it make more sense if we let you define association versions like 1.2.LATEST?

…

On Mon, Feb 27, 2017 at 10:43 AM, Yusuf Kör ***@***.***> wrote: Since we reference the most recent version of the document, it would make sense to give the client the possibility to pass a key/value list of document names and versions to use for the given client transaction. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#29>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADgDDZMHneVoqZozZLYYdH3dWTyj6XCDks5rgwsngaJpZM4MNaUI> .

[ykoer]

If he user can decide which metadata version to query, why not giving him also the power to decide which metadata versions should be used for referenced documents.
I think this is more consistent.
Or we we force to version references again.