Adjust advice on merging persistent compositions

Description

See for details.

Activity

Show:
Sebastian Garde
March 23, 2020, 8:51 AM

At https://specifications.openehr.org/releases/RM/latest/common.html#_version_merging

The last part of the first sendence reads a bit weird, suggest thsi could reworded e.g. like this:

One of the most common operations in distributed versioned environments, particularly in healthcare, is that content created in one system is imported into another system, and modifications are created locally there which are then sent back the first system. modified in the receiving system and subsequently sent back to the first system.

 

A bit later, other_input_version_ids is named as an attribute, but I think it needs to be other_input_version_uids:

…new Version is an instance of ORIGINAL_VERSION<T>, and the other_input_version_uids attribute is updated

 

Thomas Beale
March 23, 2020, 11:22 AM

Both fixed, thanks
Don't know why, but the second commit is not showing properly on this CR; see here for direct link: https://github.com/openEHR/specifications-RM/commit/4a3d87e6ed6e0a1bc24b30330c4027eddd67ab03

Sebastian Garde
March 23, 2020, 11:47 AM

maybe the “:” directly after the issue id (without any whitespace) in the log message causes the commit link to fail?

Thomas Beale
March 23, 2020, 11:54 AM

I normally avoid doing that (because I never trust Atlassian to do anything properly), but thought I had remembered that that particular thing did actually work. Seems not…

Reporter

Thomas Beale

Raised By

Ian McNicoll

Components

Affects versions

Configure