TM::PSI (3pm)

This package provides predefined subjects, all of which will be preloaded in every map which is instantiated with the \s-1TM\s0 package hierarchy. When the subjects are defined also their relationship are kept here (example: isa is an instance of an assertion).

Every such subject is defined by its

item identifier

The internal identifier, which does not really mean much.

subject identifier

The subject indicator(s), which is ultimately the one which identifies any of the subjects here.

\s-1NOTE\s0: For none of the subjects declared here a subject address exists. All concepts are TM-related concepts.

The subjects are sorted:

\s-1TMRM\s0-related

These are the minimal subjects which make a map what it is. Examples are \*(C`isa\*(C' and its related role (type) \*(C`class\*(C' and \*(C`instance\*(C', and \*(C`is-subclass-of\*(C' and its related roles.

\s-1TMDM\s0-related (\s-1XTM\s0 things)

These are the additional concepts which are mandated by \s-1TMDM\s0.

AsTMa-related

Here are more concepts which are needed by the AsTMa= language(s), such as \*(C`template\*(C' or \*(C`ontology\*(C'.

\s-1TMQL\s0-related

Here are more concepts which are needed by \s-1TMQL\s0.

To learn about these predefined concepts, you can do one of the following

   use TM::PSI;
   warn Dumper ($TM::PSI::core, $TM::PSI::topicmaps_inc, $TM::PSI::astma_inc, $TM::PSI::tmql_inc);

Taxonometry

Two association types are predefined by the standard(s): \*(C`is-subclass-of\*(C' and \*(C`isa\*(C'. Together with these roles are defined \*(C`subclass\*(C', \*(C`superclass\*(C' and \*(C`instance\*(C', \*(C`class\*(C', respectively.

The TM::* suite of packages has these not only built in, but also works under the assumption that these association types and also the roles \s-1CANNOT\s0 be subclassed themselves. This means that no map is allowed to use, say, \*(C`is-specialization-of\*(C' as a subclass of \*(C`is-subclass-of\*(C'. The costs of this constraint is quite small compared to the performance benefits.

Infrastructure Concepts

To make the whole machinery work, every topic map must contain infrastructure topics such as \*(C`name\*(C', \*(C`occurrence\*(C' etc. They are topics like the topics a user may put into the map. While this is the right thing to do, in practical situation you often will want to filter out these infrastructure topics. You can always get a list of these via

@@@ fix docu @@@@@

$tm->mids (keys %{$TM::PSI::topicmaps->{mid2iid}});

\s-1TM\s0

Copyright 200[1-68], Robert Barta <[email protected]>, All rights reserved.

This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

http://www.perl.com/perl/misc/Artistic.html