- ...Gateway
-
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">

-
Development of the APIB and the APIB gateway 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.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...applications
-
SGML is defined in the international standard ISO
8879.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...scripts
-
World Wide Web gateways often use HTML forms in this way
as a means of obtaining input for CGI programs.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...HREF="node4.html#FIGENTITY">6)
-
Note that the references to Figure 7 and clause
6.3.3 in the NOTES are currently hard coded in
the raw SGML used to generate this web page (see Figure 10). Although the IR DTD supports cross
references, the IRs in the APIB do not currently take advantage of
this support. These IRs will be re-tagged in the near future to use
the DTD's constructs for cross referencing.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...node
-
If the web browser caches previously viewed web pages,
users can achieve the same effect by using their web browser's
backtracking mechanism. They will achieve a faster response because
the APIB will not be queried. However, if the APIB has recently been
modified, the previously viewed web pages will be out of date. Also,
if the user obtained the current web page by choosing a name from a
list of IR Query results, then there are no cached pages to backtrack
to, and the user has no choice but to use the backtracking push
buttons.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...command
-
This would be improved if users could review the
SGML, leave a pointer to it, and invoke a copy at AP publication time.
This would require maintaining a table of pointers on the APIB server
for each user. These tables could be maintained in a manner similar
to the method the NIST EXPRESS Server[LIBES94] (see Section 6) uses to
maintain users' private directories.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...invoked
-
Actually, there are four CGI script names who share the
same Tcl file by means of symbolic linking. Tcl code at the beginning
of the file derives expitem from the value of
argv[0]. Also, there are some additional
implementation details that have been omitted from this
discussion.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...mail
-
Although standards bodies such as ISO and ANSI
may have elaborate publishing systems, they are often unavailable to
those who actually write the standards.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...semantics
-
This involves using natural language understanding
techniques from artificial intelligence to semantically analyze the
texts in the digital library and to analyze queries.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...DTD
-
The legacy IRs and APs were written using either
commercial word processing tools or LaTeX[LAMP]. An auto-tagging software tool has been implemented
to help convert the LaTeX IRs into SGML, but this tool assumes that
the IR document uses a particular set of LaTeX style files developed
for STEP[WILSON]. Unfortunately, some of
the legacy LaTeX IRs use LaTeX customizations that are incompatible
with the auto-tagger.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
- ...STEP
-
Also appeared in SGML '94
Proceedings, Graphic Communications Association, Vienna VA,
November 1994.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.