曝光臺 注意防騙 網曝天貓店富美金盛家居專營店坑蒙拐騙欺詐消費者

objects and generation of HTML documents from the SGML
11 Objects 11 Actions 11 logic 11
Object (Done) (T)(Show)
1 cruise speed I
Short name
@ 1 Cruise Mach
Abbreviation
0 [CR’ MACH
Definition
1 the speed selected for the cruise phese of u
the flight.
I I 1 tq
[Show Revisions)
Figure 3. Domain-object definition
source files. The HTML documents represented editions of the
target manual, and supported interaction via Web browsers.
The author’s main focus of activity with the system would be
through the text-entry window, where free text and objects were
combined. The functional prototype focused on the engineering
problems of creating and entering the objects, producing true,
Proposed text
completion L 1 navigation
The CD-OBJ N=17 (descent) F=as> CDOBJ
N=18 (mode) F=fs> is CD-OBJ
N=19 (disengage) F=p> by one of the
following CD-OBJ N=20 (condition)
F=fp>: <BR>
-loss of the nal
\ Entry Window
The DES mode is disengaged by one
of the following conditions:
- loss of the na
\ Generated Window
Figure 4. Schematic overview offunctional prototype
55
dynamic hypertext, and generating both SGML and HTML
representations. Consequently, some ideas developed in the
conceptual prototype, such as text structures and types, were
not explored in the functional prototype.
In the text-entry window, entities were represented as SGMLtagged
instances. When text was being entered in the editing
window, the prototype would dynamically suggest textcompletion
of known objects, actions and relations in a text
field in the window’s upper border. Pressing the “control” key
caused the system to replace the currently typed prefix with the
SGML-tagged instance proposed as a completion, with the user
selecting characteristics for the instance (such as number and
abbreviation) from a pop-up dialogue box. In this way, for
example, a reference to the object <AIRPORT> could generate
“airport,” “airports, ” “APT” or “APTs.” Along similar lines,
the prototype provided different syntactic forms for actions that
could be specified by the user. The prototype had
complementary representations for all entities in both English
and French.
In the generated-text window, entities were represented by
referring expressions generated by the instance. These
expressions appeared as colored, clickable text. Clicking on
one of these links caused the prototype to display the instance
definition in a pop-up window. The scan of the source SGML
was rather slow, so the generated-text window was re&shed on
explicit command of the user rather than automatically, which
would have caused annoying delays.
When the author wished to enter a new reference for which an
object was not already defined, he or she could create new
objects. For each object, the prototype provided a dialogue box
with appropriate buttons and text fields to enable the user to
enter slot values; among the slots were parallel fields for entry
of English and French versions of the same entities, so that a
single common object could be used to create documents in
more than one language and so that translation of the FCOM
between English and French (in either direction) could be
partially automated. This was not as sophisticated as the
support provided by DRAFTER [7, 81 but neither was it as
restrictive.
When a document was complete, the author could export the
underlying SGML as an HTML file that represented the
“finished” manual page. The HTML file contained the author’s
ffee text plus, embedded where specified, textual referen=
generated by the objects that were marked as hyperliuks to the
reference’s definition in an auxiliary HTML file.
The prototype had several limitations. These included lack of
handlers for graphics and lack of formatting. Despite these
limitations, however, the prototype did demonstrate the
creation and editing of hypertext documents using a common
store of objects to deride consistent referring expressions.
SGML files were automatically created via authoring actions in
the text-entry window, HTML files were automatically created
from the SGML files, and the auxiliary HTML files were
created that contained the definitions of the objects that were
linked from the HTML manual pages.
4. DISCUSSION
The work presented here led to the development of a functional
specification of the COHERE system. In creating the
specification, we learned a number of lessons in postimplementation
　
中國航空網 www.k6050.com
航空翻譯 www.aviation.cn
本文鏈接地址：航空資料8(14)