From Dave Burke on March 21:

o Section 11.5.6 / 11.5.7: Seems like <device>, <gender> is duplicated
across <voiceprint>s for  identification / multi-verification? Is this
redundancy a known issue?

From Dan Burnett on March 24:

We have wrangled over which values belong in the first voiceprint only for 
years now, and similarly for which values belong in incremental vs. 
cumulative.  Additionally, the text and the schema are not in alignment 
today.  Originally the goal was to have each element only contain elements 
that were relevant, without redundancy, but because different intended users 
of this specification have had different ways in which they intended to fill 
in this info, we have removed some options and added others.  To accommodate 
all of the use cases presented over the past few years, I have the following 
proposal:

We permit <adapted> under only the first <voiceprint>, and make it optional.  
As in -09, it is only returned for a verification (and not
training) result.
We permit <incremental> and require <cumulative> under all <voiceprint> 
elements.
Both <incremental> and <cumulative> can contain the same set of elements under 
the first <voiceprint> (which I'll temporarily name "Set A"), and both 
<incremental> and <cumulative> can contain the same set of elements under all 
but the first <voiceprint> (which I'll temporarily name "Set B").

Set A:
- may contain <decision>, <utterance-length>, <device>, <gender>, and 
<verification-score>.  <verification-score> is required.  <decision> is 
required under one or the other of <incremental> and <cumulative>, but not 
both.  It is only returned for a verification (and not training) result.  All 
other elements are optional under both <incremental> and <cumulative>.

Set B:
- may contain <utterance-length>, <device>, <gender>, and <verification-
score>.  <verification-score> is required.  All other elements are optional.

Consequences of the proposal:
- the content model is more permissive than what both the text and schema 
permit in -09, except
1) it limits <decision> to only occur once in the entire result, and that only 
in a verification result (as opposed to training), and
2) it requires <verification-score> under all <incremental> and <cumulative> 
elements anywhere in the result.