[topicmapmail] Thoughts about (the evolution of) topic maps

[Tobias Redmann]

Hello everybody,

until now, I thought a topic map is a abstract model (for knowledge  
structures for example), but the standard says:

"... a standardized notation for interchangeably representing  
information
about the structure of information resources used to define topics,  
and the
relationships between topics. A set of one or more documents that  
employes
the notation defined by this International Standard is called topic  
map."
(ISO 13250:2002)

Let me summarize:
A topic map is one or more DOCUMENT

So, what about:
- a thing (formally known as topic map) hold in a data base
- things in mind ..


Ok, lets have a look on the data model standard:
"Topic Maps is a technology for encoding knowledge and connecting  
this encoded knowledge to relevant
information resources. Topic maps are organized around topics, which  
represent subjects of discourse;
associations, representing relationships between the subjects; and  
occurrences, which connect the subjects to
pertinent information resources."

Let me summarize:
Topic Maps is a TECHNOLOGY for encoding knowledge

(But what is a technology?)

Have one more look at the data model document:
Topic maps may be represented in many ways: using Topic Maps syntaxes  
in files, inside databases, as internal
data structures in running programs, and even mentally in the minds  
of humans. All these forms are different ways
of representing the same abstract structure

Let me summarize again:
[Topic Map is a] abstract structure


So, what us a topic map:
- Document?
- Technology for encoding knowledge?
- Abstract Structure?


It is very confusing to define, what a topic map is. I would say:

A topic map is a abstract model that describes knowledge structures.  
This model may be represented in many ways (xtm, HyTM, files db etc).


Best regards,

Tobias (Berlin/Germany)


Tobias Redmann
E-Mail: tobias at meshed.de