Hi Rodolfo, all, >> a) We remove because it is not a match to the new s1 anymore. > > Can be removed or left there. It's a tool/user choice > >> b) We keep it attached to the new s1 but we change its >> similarity/score attributes to some arbitrary value to >> indicate the match is not the same. > > The tool could recalculate the similarity score. Updating it > would be optional. It seems to me that we have to have a specified behavior. The candidates can always be removed obviously (although the preference should be to keep things whenever possible). But if the tool keeps the matches then something should indicate that they are not matching the content anymore. And because not all tools can re-calculate similarity/score maybe something else, a 'scopeChanged' flag of some sort? Re-segmenting will affect any information attached to the segments, so we probably want some generic mechanism that can be applied to all things like the candidates (e.g. notes, QA results, etc.) -ys