John,
No problem, this really can be blamed on FrameMaker too. Whenever it is working with XML and related files, FM uses a third-party Xerces XML validator to do lots of the XML work. This is great when everything works, but when there are errors, apparently FM simply reports the error text verbatim that it receives back from Xerces. In many cases, it can be cryptic to decode, especially as there is no documentation for it with FM. So, when you get these errors, sometimes it can be real tricky to figure out where the actual problem is. It seems that only experience is adequate for being able to recognize and solve these kinds of problems quickly. You see in this case, though, nobody here really knew the answer, presumably because nobody here had followed your particular sequence before and therefore didn't have the error registered in their "mental" FM reference.
Russ