In such cases, the name variant applies only to the URI in the ref attribute on the persName element that is the immediate child of the person or personGrp element.
I think the app is considering any name variant factoid to be a name variant of any URI appearing inside the persName element. Instead, it should consider the name variant factoid to be a name variant only for the immediate child of the person or personGrp element.
@wsalesky SPEAR aggregation pages are currently incorrectly grabbing some name variants. See here: http://wwwb.library.vanderbilt.edu/exist/apps/srophe/spear/aggregate.html?id=http://syriaca.org/person/2201. The third name variant is actually a name for an anonymous group that happens to include the URI for person/2201.
In such cases, the name variant applies only to the URI in the ref attribute on the persName element that is the immediate child of the person or personGrp element.
`
That code didn't render very well in the issue. See here: http://wwwb.library.vanderbilt.edu/exist/apps/srophe/spear/119-29/tei
So which names do you expect to see here?
The third example, "The nobles of Abgar....", appearing here: http://wwwb.library.vanderbilt.edu/exist/apps/srophe/spear/aggregate.html?id=http://syriaca.org/person/2201 should not appear as a name variant for Abgar VIII.
Rather, this name variant should only appear as a name variant here: http://wwwb.library.vanderbilt.edu/exist/apps/srophe/spear/aggregate.html?id=http://syriaca.org/person/2233
I think the app is considering any name variant factoid to be a name variant of any URI appearing inside the persName element. Instead, it should consider the name variant factoid to be a name variant only for the immediate child of the person or personGrp element.
Does that help?