|
Technical reports reflect statements and studies to various topics. These can be DTD related as well as generic.
|
(SP) Structural principles
|
This is the document which is maintained during the development of the DTD. It reflects the actual results of data modeling, semantics and application hints, and SGML elements. The level of detail and maturity increases during the process of DTD development. This document is most likely available when the DTD is released.
As this document is accompanying the development process, its final version is neither an ideal user guide nor an ideal reference manual. Nevertheless it is useful for implementors as well as for users.
|
|
This document is mostly the specification for formatting (paper as well as online) engines.
This document is written when the DTD is finished. It may receive some information available already the structural principles. Its scope is to specify the processing of instances.
|
(EA) Elements and attributes
|
This document is the reference description for elements and attributes. It contains all elements and attributes of the specific DTD.
This document is used by implementors as well as by users.
|
|
This document is (authoring environment independent) description how to generate a new document. Its information is already there in the other documents. The user guide is presented in a tutorial style.
|
|
This instance is intended as a sample to illustrate the general usage of the DTD. It is simple enough to illustrate how the DTD works.
|
|
This instance is intended to be used as a test case for implementations. It should use all elements and cases. Furthermore it should give an impression how real project instances should look like (size, amount of element etc.).
It is possible to have multiple reference instances:
(RIP) performance
|
useful for performance tests
|
(RIV) volume
|
useful for resource tests
|
(RIC) content
|
as an example for a complex instance to show all the features of a DTD
|
(RIA1) alternatives
|
in some cases, there are alternative content models which prohibit full path coverage. In this case it is necessary to provide an instance for each alternative.
|
|