cross-posted on nexml-discuss first...
The example is the ID Tl241048 in
http://treebase.org/treebase-web/search/downloadAStudy.html?id=10000&format=nexml
The nexus output has multiple taxa blocks and the taxon name
Cardamine_alpina_DAE2_R325 (which is associated with the offending otu
elements in the nexml form) occurs in multiple taxa blocks. In the
(mesquitized) form of NEXUS that allows multiple TAXA blocks, the
block TITLE acts like a namespace. So identical taxa labels are not a
problem in NEXUS. But in nexml spec ids are supposed to be unique
throughout the file.
I suspect this difference in approaches to dealing with disambiguation
may be the source of the bug.