[Tm4j-developers] RE: [TM4J-users] differently-scoped names causing a merge?

[Conal T. <co...@pa...>]

I think I've found what was going wrong with my topicmaps (in which the name
scopes were being ignored).

I debugged org.tm4j.topicmap.utils.XTMBuilder and found that for a baseName
to be scoped, the scope element has to appear before the baseNameString
element. Looking at the DTD, this is of course perfectly correct - the
optional <scope> child of a <baseName> must be the first child element. So
it was my mistake. D'oh! :-(

But it seems to me that it'd be nice for XTMBuilder to flag a <scope>
appearing after a <baseNameString> as an error, rather than ignoring it. The
scoping of <occurrence> and <association> elements is handled differently,
and for these elements XTMBuilder seems to accept <scope> elements which
appear (invalidly) after a <resourceData>, <member>, etc,

Cheers

Con