Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

tm::psi(3pm) [debian man page]

TM::PSI(3pm)						User Contributed Perl Documentation					      TM::PSI(3pm)

NAME

       TM::PSI - Topic Maps, PSI (published subject identifiers)

DESCRIPTION

       This package provides predefined subjects, all of which will be preloaded in every map which is instantiated with the TM 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.

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

       The subjects are sorted:

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

       TMDM-related (XTM things)
	   These are the additional concepts which are mandated by TMDM.

       AsTMa-related
	   Here are more concepts which are needed by the AsTMa= language(s), such as "template" or "ontology".

       TMQL-related
	   Here are more concepts which are needed by TMQL.

       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): "is-subclass-of" and "isa".  Together with these roles are defined "subclass",
       "superclass" and "instance", "class", 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 CANNOT be subclassed themselves. This means that no map is allowed to use, say, "is-specialization-of" as a subclass of
       "is-subclass-of".  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 "name", "occurrence" 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}});

SEE ALSO

       TM

AUTHOR INFORMATION

       Copyright 200[1-68], Robert Barta <drrho@cpan.org>, 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

perl v5.10.1							    2010-07-18							      TM::PSI(3pm)

Check Out this Related Man Page

TM::Synchronizable::MapSphere(3pm)			User Contributed Perl Documentation			TM::Synchronizable::MapSphere(3pm)

NAME

       TM::Synchronizable::MapSphere - Topic Maps, trait for a syncing a hierarchical TM repository

SYNOPSIS

	  use TM;
	  use base qw(TM);
	  use Class::Trait ('TM::MapSphere',
			    'TM::Synchronizable::MLDBM' => {
				exclude => [ "sync_in", "sync_out" ]
			    },
			    'TM::Synchronizable::MapSphere');

DESCRIPTION

       This trait adds "sync_in" and "sync_out" functionality to a map sphere. The point here is that embedded child maps are also synced out or
       in.

   Map Meta Data
INTERFACE

   Methods
       sync_in
	   $ms->sync_in ($path)

	   A whole subtree of the map repository can be sync'ed in, i.e. synchronized with contents in an associated resource. If this method is
	   triggered with a particular path, then the map there will be (a) synced in, (b) queried for sub-maps and (c) these sub-maps will be
	   instantiated.  Recursively, these submaps will be sync'ed in, etc. All these sub maps will be mounted under this branch of the tree.

	   When a map is instantiated, its implementation package will be extracted from the parent map using a "implementation" characteristic.
	   The resource URL will be determined from one of the subject indicators, the base URI will be determined from the subject address of the
	   map topic. If any of these are missing, this particular sub-map is ignored.

	   Example: Let us assume that a map has a "baseuri" "http://whatever/" and a resource URL "http://example.org/here.xtm". It is a
	   materialized map using the XTM driver. If this map is mounted into a root map under "/foo/", then the entry will take the form (using
	   AsTMa= 2.0 as notation):

	      foo isa topicmap
	      ~ http://example.org/here.xtm
	      = http://whatever/
	      implementation: TM::Materialized::XTM

	   @@@ TODO: no path @@@@?

       sync_out
	   $ms->sync_out ([ $path ], [ $depth ])

	   This method syncs out not only the root map sphere object (at least if the resource "mtime" is earlier that any change on the map
	   sphere). The method also consults the mount tab to find child maps and will sync them out as well.

	   The optional "path" parameter controls which subtree should be synced out. It defaults to "/".

	   The optional $depth controls how deep the subtree should be followed downwards. Default is "MAX_DEPTH" (see the source).

AUTHOR

       Robert Barta, <drrho@cpan.org>

COPYRIGHT AND LICENSE

       Copyright (C) 200[67] by Robert Barta

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself, either Perl version 5.8.4 or,
       at your option, any later version of Perl 5 you may have available.

perl v5.10.1							    2008-04-10					TM::Synchronizable::MapSphere(3pm)
Man Page