...Choices

Trade names and company products are mentioned in the text in order to adequately specify experimental procedures and equipment used. In no case does this identification imply recommendations or endorsements by the National Institute of Standards and Technology, nor does it imply that the products are necessarily the best available for the purpose.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...HREF="footnode.html#16">

This work is funded by the National Institute of Standards and Technology's Systems Integration for Manufacturing Applications (SIMA) program, a part of the US government's High Performance Computing and Communications initiative.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...development

Collaboratory development is a team effort, accomplished using a ``virtual'' research center where developers can communicate with colleagues, share data and resources, and obtain digital information from repositories, without regard to geographical location[KOUZ].

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...declaration

The SGML declaration provides information about the dialect of SGML being used such as the character set, delimiter characters, identifier lengths, etc.[TEI]

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...(ESIS)

See Attachment 1 of Appendix B of [GOLD].

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...Corrigendum

Although the HyTime Technical Corrigendum's primary purpose is to correct the HyTime[HYTIME] standard, it also extends the facilities of SGML.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...possible

An in-depth discussion of property sets and groves is beyond the scope of this document. The reader is encouraged to consult the HyTime Technical Corrigendum[TC] for additional information.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...HREF="node14.html#SECPUBLISH">3.6

We have not yet implemented the filter, although we plan to do so in the near future. The STEP AP developers currently using our SGML environment have existing documentation for most of their AP in a word processor format and, therefore, chose to work directly with the AP-publishing DTD.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...AP

It is not necessary for the reader to know what Units of Functionality are in order to follow this example. Also, the actual declarations in the DTDs were simplified for this example in order make it easier to follow.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...UoF.SubC.Intro.Text

Its element declaration is not shown in the example because of space limitations.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...preferable

Another reason for providing a user interface that is as straightforward as possible is that STEP document authors are a geographically distributed group, making them expensive to train in person.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...documents

If SGML document producers need to maintain revision histories, then access is important for them too.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...DTDs

We are considering using ISO's exchange DTD to represent the STEP documents describing representation and implementation methods.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...scripts

World Wide Web gateways often use HTML forms in this way as a means of obtaining input for CGI programs.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...public

The STEP DTDs are available for download. The APIB gateway discussed in Section 3.5 is also available. However, because the STEP documents in the APIB are copyrighted by ISO, access to these documents is restricted. Requests for further information should be directed to the authors.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

...STEP

Also appeared in SGML '94 Proceedings, Graphic Communications Association, Vienna VA, November 1994.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.