% run this through LaTeX with the appropriate wrapper

\chapter {User Naming Architecture}

\section {Overview}

The original work in INCA defined a naming architecture.
Some of this work has been overtaken by
standardisation activity, and other components are not relevant here.
A few pieces are retained, as they may be of general use.
The entire naming architecture is shown in Appendix~\ref{naming} on
page~\pageref{naming}.

\section {THORN}
\label{thorn:na}
The THORN\index{thorn} project is a significant ESPRIT project, which is implementing
Directory services\cite{thorn}.
THORN has defined a Naming Architecture, which includes a number of
non-standard, but useful attributes
\cite{thorn-na}.
This architecture has been adopted for use in QUIPU at UCL, and for this
reason, information in this architecture is  not duplicated here.
The latest version of the THORN Naming Architecture (also known as the RARE
Naming Architecture) in available 
via FTAM from UCL (the address is given in the {\bf Preface\/} of this Manual)
in the files
\file{thorn/thorn-na.txt},
\file{thorn/thorn-na.ps} or
\file{thorn/thorn-na.ms} depending whether you want a ``plain text'',
``postscript'' or ``nroff -ms'' version.
Alternatively you could Mail \verb"quipu-support" asking for the 
relevant document (see Section~\ref{quipu:support}).

\section {Common Name Forms}

The use of ISO 3166 codes is abhorrent, as it makes the DUA perform
things which the DSA should do.
Therefore a more general country attribute is introduced 
(see Figure~\ref{country-na}).
The intention is to use this attribute to
permit users to search for countries based on familiar
strings.

QUIPU supports multiple inheritance,
so there is a need to define an QUIPU Object class, which will permit
all of the standard QUIPU attributes to be associated with all
objects in the QUIPU Directory, the definition can be found in
Figure~\ref{na-summary}, in Appendix~\ref{naming}.

\tagrind {country}{Country}{country-na}

\section {DSA Naming Architecture }

The following Naming Architecture components are needed in order to support
the QUIPU Mechanism for distributed operations.
These are defined here, as a convenient location.
Numbers are assigned elsewhere in this manual.

\tagrindfile {na}{Naming Architecture}{na}

