Reference to 'latest version' not properly specified
Description
relates to
Activity
Heath Frankel October 27, 2015 at 10:29 AM
So you want to specify how the VERSIONED_OBJECT.latest_version function should be implemented?
It has been decided that EHR URIs will not have an parameter indicating symbolically which version to return. It will only support identified objects which assumes LATEST_TRUNK_VERSION when a VERSIONED_OBJECT.uid is provided otherwise the specific VERSION.uid. There is nothing for LATEST_VERSION as we could not see any use case within the context of LINKs.
Thomas Beale October 27, 2015 at 10:18 AM
The original problem was how to create a technical reference that always refers to the 'latest' version of the target. I think we can only do this in a URI string, then it must get resolved to whatever the latest is, when it gets used to create any identifier objects.
Heath Frankel October 27, 2015 at 10:01 AM
Still not sure I understand the problem
Thomas Beale October 22, 2015 at 8:18 AM
Probably resolution of this CR takes care of this PR.
Thomas Beale October 22, 2015 at 8:18 AM
Probably the OBJECT_VERSION_ID should always refer to a proper technical version - therefore the need to refer to 'latest version' is taken care of by https://openehr.atlassian.net/browse/SPECRM-33#icft=SPECRM-33
Details
Details
Reporter
Components
Affects versions
Priority
Major
Currently the Support IM definitions for VERSION_TREE_ID and OBJECT_VERSION_ID don't support a 'latest version' reference, even though the latter is defined in the Architecture Overview. The VERSIONED_OBJECT class does have a latest_version function, but there appears no programatic way to generate the equivalent reference to such an object.