How does a merge agent handle communicating findings?
Some findings will entail issues such as receiving a topic with a particular locator (topic identifier) which is the same as the locator of an existing topic in the database, with different content
An inherent behavior in a topic maps agent space is that of
keeping humans in the loop. A merge agent needs to communicate with:
- Topic Map administrators in the case of detected failures of hardware or software
- Topic Map users, curators, etc, in the case (not limited to)
- Topics with same topic locators but different content (possibly imported from a foreign source)
- Topics in which ambiguity hints either:
- a merge appears to be indicated
- an existing merge appear incorrect in light of, e.g. new information