RE: [TM4J-users] exporting subject indicators

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

Thanks for the prompt reply Kal! I'm really grateful for your help.

I'll bet that's it. No I don't have <subjectIndicatorRef> elements in my
source.

I'm not using TMHarvest at present ... I'm using Cocoon pipelines with XSLT
to harvest the topics. On the bright side, this makes it easy to add a
subjectIndicator as a separate pipeline stage. If I understand you
correctly, I would just need to add a <subjectIdentity> to my topics,
pointing at themselves? It sounds a bit weird ... maybe I've misunderstood.

<topic id="foo"/>

would become

<topic id="foo">
	<subjectIdentity>
		<subjectIndicatorRef xlink:href="#foo"/>
	</subjectIdentity>
</topic>

or maybe <topicRef> is better

<topic id="foo">
	<subjectIdentity>
		<topicRef xlink:href="#foo"/>
	</subjectIdentity>
</topic>

Is that it?

Cheers

Con

> Do your input topic maps have <subjectIndicator> elements in
> them ? (or
> if you are harvesting them using TMHarvest, do you set the
> subjectIndicator property) ? My guess is that you are only setting the
> sourceLocator property. So your topic with the id pdf-file
> gets a source
> locator
> http://www.nztec.org/tm/harvest/xtm/nztec-ontology.xtm#pdf-file,
> but does not get a subjectIndicator. By default, the XTM
> exporter tries
> to be "clever" and if you export a TM with a base locator
> http://foo.xtm
> then all source locators of the format http://foo.xtm#bar get exported
> as an ID attribute with the value bar.
>
> The merging works in memory because if topic A has
> sourceLocator foo and
> topic B has a subjectIndicator foo, then the topics must be
> merged. When
> you round trip to external files, however you will lose that
> sourceLocator.
>
> My advice is to explicitly set the subject indicators in your ontology
> topic map.