I have talked about a lot of software and techniques since starting this blog but I don’t have an easy way to organize them by topic map task. That is, when do you need which tool? And how would you evaluate one tool against another?
The second question, comparing tools, probably isn’t something I will get to in the coming year. Might but don’t get your hopes up. I do think I can start to outline one view of when you need which tool.
To talk about tools for topic maps, I need to have an outline of the process of creating a topic map.
My first cut at that process looks like this:
I already see some places that need repair/expansion so don’t take this as anything but a rough draft.
It can become better but only with your comments.
For example, I like the cloud metaphor, mostly because it is popular and people think they know what it means. 😉 But, here is leaves the false impression that “clouds” are the only source of data for a topic map.
What about people and their experiences? Or museums, art, books (those hard rectangular things), sensors, etc. Public vs. private clouds.
Maybe what I should do is keep the cloud and remove data/text and let the cloud be a hyperlink to another image that has more detail? Something like “universes of knowledge – enter here” or something like that. What do you think?
Question: For purposes of just blocking the process, should indexing point to “processing?” I know it can occur later or earlier but just curious how others feel.
The double ended arrows are to show that interaction is possible between stages. Such as authoring and the topic map instance. That the act of authoring a topic map can make the author of the topic map create different paths than originally intended. That happens so constantly that I thought it important to capture.
Question: And similarity measures. Where do I put them? Personally I think they fall under mining/analysis because that will be the basis for creation of the topic map but I can see an argument for merging/processing of the topic map also needing such rules in case another topic map ventures within merging distance.
Comments/suggestions?
PS: I would like to keep the diagram fairly uncluttered, even if I have to use the images or arrows to lead to other information or expand in someway. Diagrams that can’t be interpreted in a glance seem to defeat the purpose of having a diagram. (Not claiming that quality for this diagram, one of the reasons I am asking for you help.)
[…] the draft Topic Map Tool Chain, I would put this under mining/analysis, but as was pointed out in comments, the mining/analysis […]
Pingback by Zorba: The Most Complete XQuery Processor « Another Word For It — January 1, 2012 @ 5:58 pm