MSRREP.DTD is derived from MSRDOC.DTD. Only a few elements are added. Therefore it is possible to derive most of the processing also.
The DTD mainly consists of three parts:
<report-head>(see 2.1. report-head)  carries all the document metadata as well as project related information

<report-body> (see 2.3. report-body)  carries the main part of the document as well as the change management support (see 2.4.1. change objects)

<report-rear> (see 2.5. report rear)  taking all appendices

Figure 1: MSRREP.DTD and administrative data
In the top level element <report-head> there is also <admin-data> (see 2.2. admin-data), providing means to describe the document versions, revisions etc. It is not treated as a document part since it is mainly metadata. This element is included also on a chapter level if the document is fragments into entities.
All three sections contain a generic structure which allows to define an unlimited chapter hierarchy (<chapter>). It is up to the user to take sure, that the number of chapter nesting does not exceed the capability of the SGML processing systems.
Cross-referencing is done in a non semantical way using <xref>. A subset of the MSRDOC.DTD id classes are supported in MSRREP.DTD also. These are mainly the organizational ones but not the technical ones of MSRDOC.DTD. MSRREP.DTD adds some id classes with the change management support. Some semantic references are also provided
MSRREP.DTD provides paragraph level markup as

paragraphs
an ordinary paragraph
tables
implemented as CALS tables
lists
provided as numbered, unnumbered and labelled lists. Each Item can mainly contain all paragraph level markup
figures
Allowing to include sizeable graphics
verbatim
for preformatted text
topic
which allows to insert bridge titles

There are some elements providing character level markup. Most of them represent a certain semantics as it is the case in MSRDOC.DTD.
Elements taken from MSRDOC.DTD are not changed except <xref> which supports only the id classes in MSRREP.DTD. This leads to some structures which could be considered as overdesigned, mainly in the metadata where <company> still has all the project oriented elements of MSRDOC.DTD.
All elements have an attribute [signature] which is targeted to be filled by a check routine. It can be used to find out changes in the document.