= TUC - The Understanding Computer =

= TUC USER MANUAL =

== Version 22.1 Date 140910 ==

Revised for Confluence by Rune Sætre
Based on Version 21.4 Date 060515,
From From www.idi.ntnu.no/~tagore

==

...

VERSION MANAGEMENT ==

The TUC system is developed by the University of Trondheim, NTNU.

It may be distributed under software license agreements, but may not be handed to third parties or used for
commercial purposes without written permission by the developer.

The TUC system may be used free of charge provided that it is not used in commercial applications and
that the copyright notice remains unchanged.

...

To ensure a disciplined distribution of the latest versions, the system should not be redistributed to third parties.
For a description of the [[#Version Management Policy]], see the end of this manual.

== MAIN DESCRIPTION ==

TUC is an acronym for The Understanding Computer.

TUC is a prototypical Natural Language Processor written in Prolog.
It is designed to be a general purpose easily adaptable natural language processor.

I consists of a general grammar for a subset of the language, a semantic knowledge base, and modules for interfaces to other systems like UNIX, SQL-databases and Traffic Information Systems.

There is at

Rune Sætre
Information Systems Group
Department of Computer and Information Science
University of Trondheim (NTNU)
N-7491 Norway

E-MAIL:
busstuc@idi.ntnu.no

...

This program is provided as research software, on an "as is" basis without warranty of any kind, either expressed or implied.

== VERSION MANAGEMENT ==

To ensure a disciplined distribution of the latest versions, the system should not be redistributed to third parties.
For a description of the [[#Version Management Policy]], see the end of this manual.

Table of Contents

...

== MAIN DESCRIPTION ==

TUC is an acronym for The Understanding Computer.

TUC is a prototypical Natural Language Processor written in Prolog.
It is designed to be a general purpose easily adaptable natural language processor.

I consists of a general grammar for a subset of the language, a semantic knowledge base, and modules for interfaces to other systems like UNIX, SQL-databases and Traffic Information Systems.

There is at the moment two versions, one for English and one for Norwegian. We will let the English version be used for a generic description. (A suffix _e distinguishes the English version from the Norwegian version _n).

...

Noun complements are modifiers of the noun.

n_compl(<subject>,<preposition>,<object>)

Example:

n_compl(person,with,telescope).
n_compl(park,with,statue).

==== Adjective complements ====

Adjective complements are complements to the adjectives.

an_compl(<adjective>,<subject>,<preposition>,<object>)

Example:

na_compl(personresponsible,agent,withfor,telescopething). n_compl(park,with,statue).

==== Adjective complements ====

Adjective complements are complements to the adjectives.

a_compl(<adjective>,<subject>,<preposition>,<object>)

Example:

==== Part-Of hierarchy ====

A relation apo (a part of) is used to define
the constituent structure of the nouns.

Example:

month apo year.
week apo month.
day apo week.

This is used to lexically allow some expressions like

"week in a year"

without explicitly defining it as noun compliance.

NB. The relation apo must NOT be confused with the ako relationa_compl(responsible,agent,for,thing).

====

...

Attributes ====

A relation apo (a part of) is used to define
the constituent structure of the nouns.

...

The attributes of a class is declared by a
predicate 'has_a'.

Example:

country has_a capital.
dog has_a owner.

==== Comparisons ====

Comparisons are polymorphic relations between objects.

comp_templ(<generic>,<class>,<class>,<specific>).

Example:

comp_templ(gt,person,person,height/gt).

=== User Defined Facts ===

A file 'facts.pl' contains a set of definitions of
object names. The main relation is 'is a' :

richard isa employee.
january isa month.

=== Script files ===

TUC may be directed to read NL text from file.

The command is in dialogue mode

E: \r <file> .

The file <file> must have extension .e (English) or .n (Norwegian),

e.g. twm.e whose content is shown above.

=== Version Management Policy ===

The program system has a Version X.Y and a Date YYMMDD.
The Date is the date of the last modification.

The documentation also has a Version X.Y and a
Date YYMMDD, which is the date of the last correction.

The Version of the documentation and the program system
must correspond. The Date however may deviate.

Two files, documents or programs with the same
Version and Date are identical.

The documentation can be changed (improved ) without
changing the Version number. If the program is unaffected,
only the Date is changed.

Similarly, programs can be changed (improved) with only
a change in the Date when the documentation is not affected

Each file has a similar field for the last revision date.
Changes in the files will normally be added a signature
and a date of the modification ( e.g. TA-960702).

The date of the system release is the date of the
last revision of any of its files.
This date is written in the file version.pl.

== COPYRIGHT NOTICE ==

The TUC system is developed by the University of Trondheim, NTNU.

It may be distributed under software license agreements, but may not be handed to third parties or used for
commercial purposes without written permission by the developer.

The TUC system may be used free of charge provided that it is not used in commercial applications and
that the copyright notice remains unchanged.

COPYRIGHT (C) 2001-2012

Tore Amble
Knowledge Systems Group
LINGIT A/S, Trondheim.
and the Department of Computer and Information Science
University of Trondheim (NTNU)
N-7491 Norway

Rune Sætre
Information Systems Group
Department of Computer and Information Science
University of Trondheim (NTNU)
N-7491 Norway

E-MAIL:
busstuc@idi.ntnu.no

== SOFTWARE DISCLAIMER ==

This program is provided as research software, on an "as is" basis without warranty of any kind, either expressed or implied

"week in a year"

without explicitly defining it as noun compliance.

NB. The relation apo must NOT be confused with the ako relation.