For example, the Radius declaration in 5-3 defines an integer
type named Radius. Likewise, Images defines a set of image
files. Showing an increased complexity, Part describes
a factory part data record comprised of six attribute fields, five string
fields (Name, Color, Temperature, Weight, and Currency) and the real Cost
field. Finally, to demonstrate some simple data nesting, the Route
declaration describes a data structure used to store a hypothetical terrain
traversal route. It includes the fields RouteCost, a real number
representing route length and difficulty, RouteLength, an integer
noting the number of route points saved, RoutePoints, actually
an array of position point records comprised of integer X and Y coordinates,
and RouteScript, the file path of a system shell script which
the user may call to display the route information.
5.5
-- Hermes constants: Hermes constants include logical,
numeric, character, array, record and set constants. Logical constants
include booleans. Numeric constants include integers and reals. Character
constants include names, files and strings, which are surrounded by 0,
1, or 2 quotes, respectively. When character constants are compared for
equality, the comparison is not case sensitive. For example, = ('CASE",
"case") evaluates to true. Arrays, records and sets can be arbitrarily
nested. 
5.9
-- Hermes name values: A name is any sequence of letters, digits
and underscores beginning with a lower-case letter. Names are used for
keywords, domain names, functionnames, predicate names, and name constants.
For example: select, query1, minimumCost, supplier_part.
5.11
-- Hermes file names: Hermes uses single quotes to enclose
file names such as 'parts.rel'. By including an '@' character
followed by a host-machine name, as in 'parts.rel@tanagra.cs.umd.edu',
or the URL style double-slash '//' followed a host-machine name , as in '//tanagra.cs.umd.edu/parts.rel',
a Hermes file name can address data from specific, perhaps remote,
host machines. Additionally, use of embedded spaces, which the search engine
removes during parsing, further eases Hermes rule writing as lengthy
file names may span several lines (see Fig. 5-12). NOTE: In cases where
the search engine runs on the same named host machine, Hermes will
automatically shorten the file name to that of the local path. That is
to say that, should we process the Fig. 5-12 rule from a Hermes
search engine running on the spectrum.eg.bucknell.edu host, then
Hermes would modify the rule to read as that in Fig. 5-13.
5.12
-- Hermes strings consist of any keyboard character sequence
-- letters, digits, punctuation and spaces -- inclosed by double quotes.
Two double quotes together, within a string, form an embedded double quote
as in "the animal ""Zebra"" will appear quoted within the rendered
string".
Hermes allows strings to span lines (via embedded white spaces) for
rule writing clarity; The search engine converts these multi-space (white
space) gaps to single spaces during parsing -- The string in Fig. 5-15,
for instance, will read "Find the temperature of a part, resolving qualitative
and quantitative measures." after parsing.
5.15
-- Hermes sets consist of unordered like type elements lists
surrounded by left and right braces '{}' -- Empty braces represent
an empty set. Hermes commonly uses its set notation to represent
unordered lists of data records such as those found in relational or object-oriented
databases. Fig. 5-21 lists several database record sets; the last of which
illustrates a hypothetical parts database in which each record contains
a part name, quantity, color, and list of sub-parts.