function(arg1, arg2, arg3) -> result

Predicates, however, are in a sense bidirectional, because of the way the pattern matching works

predicate(topic : role1, $VAR : role2)

predicate($VAR : role1, topic : role2)

The order of the roles are, on the other hand, insignificant

predicate(topic : role1, $VAR : role2)

instance-of (instance,class)

NOTE: the order of the arguments is significant

Like players, instance and class may be specified in two ways:

using a variable ($name)

using a topic reference

e.g. instance-of ( $A, city )

instance-of makes use of the superclass-subclass associations in the topic map

the API lets you write code without worrying about that, however

the processor returns a ParsedQueryIF object, which can be executed

parameters can be passed to the query on each execution

makes up nearly the entire framework

used to extract information from topic maps

lets you execute tolog queries to extract information from the topic map

looping and control flow structures

template

used to create template pages

separates layout and structure from content

not Topic Maps-aware

collected from the tm-sources.xml configuration file

each topic map has its own id (usually the file name)

Each page also holds a set of variable bindings

each variable holds a collection of objects

objects can be topics, base names, locators, strings, ...

Tags access variables

Tells the page which tag library to include and binds it to a prefix

Prefixes are used to qualify the tags (and avoid name collisions)

Use the <tolog:context> tag around the entire page

The "topicmap" attribute specifies the ID of the current topic map

The first time you access the page in your browser the page gets compiled

where to find the other files, plus plug-ins

tm-sources.xml

tells the navigator where to find topic maps

log4j.properties

configuration of the log4j logging

events in the location