Figure 5: DTD-diagram for CATALOG

Child elements
<metadata> <aref> <ablock>
parent elements
none

Attributes for CATALOG
Name
Type
Class
Value
Remark
[CATALOG-CLASS]
name
implied
 
This specifies the particular use case for the catalog.
[CREATOR]
cdata
implied
 
This denotes the tool (incl. version) which created the actual catalog.
[MODIFICATION-DATE]
cdata
implied
 
This denotes the date, the catalog was last modified. If the catalog is generated from scratch it is the creation date.
If the catalog is the primary database, the date of the last modification is given.
The value must follow the patterns given in 2.2.7.1. REVISION
[NAME]
cdata
required
 
This is the name of the catalog. It can be used for reference purposes.
[PUBID]
cdata
fixed
-//MSR//DTD container catalog 2.0 CNTCTL0200.DTD//EN
This gives the public identifier of the catalog.
A creator must place it according to the DTD.
[STATE]
cdata
implied
 
This denotes the state of the contents of the catalog if the catalog is the only database.
[VERSION]
name
implied
 
This denotes the version of the catalog structure. If omitted, it is 2.0
This is the root of the catalog. It comprises of metadata and assertion blocks. The metadata are related to the catalog itself.
If an entire system is transferrred, the root of the configuration can be denoted in the <aref> of <catalog>.
The use case of the catalog is denoted in [catalog-class] as:

program-kit
used to exchange entire program kits.
tool-kit
used to exchange tool kits
History-overview
used to exchange an history overview of one particular work item.

The [pubid] attribute must have the value:
-//MSR//DTD container catalog 2.0 CNTCTL0200.DTD//EN