Chapter 7. Class-3 TAN Files, Varia

Table of Contents

Keyword Vocabulary (TAN-key)
Root Element and Head
Data (<body>)
Morphological Concepts and Patterns (TAN-mor)
Principles and Assumptions
Root Element and Header
Data (<body>)
TAN Catalog Files (collection)

This chapter provides general background to the elements and attributes that are unique to all class 3 TAN files, which are devoted to formats that do not fit the other two classes. For detailed discussion of specific elements and attributes, see Chapter 8, TAN patterns, elements, and attributes defined.

All too often, a project has a set of vocabulary it draws from time and again. To repeat the the section called “IRI + name Pattern” can be both tedious and treacherous. If a project with hundreds of TAN files sdecides to change or augment its vocabulary it could take a long time to find and make all the changes.

The TAN-key format is intended to allow a project to define the IRI + name patterns for things that it regularly names, to be applied to any element that takes @which. For example, it is a suitable way to gather the IRI + name patterns for the people who worked on a project, or to define special kinds of div types.

TAN-key files are a core part of the TAN schema, defining commonly used concepts in <token-definition>, <div-type>s, and so forth. For a complete list of predefined TAN keywords, see Chapter 9, Official TAN keywords

For more details on how this format relates to other TAN formats, see the section called “Keys and Inclusions”.

A TAN-key file has <TAN-key> as the root element.

The <definitions> of a TAN-key file will be empty, or have <group-type>s.

The <body> of a TAN-key file consists simply of <item>s, perhaps gathered into groups via <group> or @group. These groups have, at present, no effect upon other TAN files that import them. They have been useful, however, in more advanced uses of the format, particularly in the case of the standard TAN-key file for <div-type> (../TAN-key/div-types.TAN-key.xml), where common types of divisions have been given a rudimentary typology suitable for transformations into other formats.

Most frequently, a TAN-key file will contain items that have the IRI + name pattern. The only exception is when it contains <token-definition>s.