FireBrick FB6602, Руководство пользователя

Страница: 32 / 152

Configuration
17
<?xml version="1.0" encoding="UTF-8"?>
This defines the version of XML that the file complies with and the character encoding in use. UTF-8 is used
everywhere by the FireBrick.
The XML file contains one or more elements, which may be nested into a hiearchy.
Note
In XML, the configuration objects are represented by elements, so the terms object and element are
used interchangeably in this manual.
Each element consists of some optional content, bounded by two tags - a start tag AND an end tag.
A start tag consists of the following sequence of characters:-
• a < character
• the element name
• optionally, a number of attributes
• a > character
An end tag consists of the following sequence of characters:-
• a < character
• a / character
• the element name
• a > character
If an element needs no content, it can be represented with a more compact self closing tag. A self closing tag
is the same as a start tag but ends with /> and then has no content or end tag.
Since the
<
,
>
and
"
characters have special meaning, there are special ('escape') character sequences starting
with the ampersand character that are used to represent these characters. They are :-
Table 3.1. Special character sequences
Sequence Character represented
&lt; <
&gt; >
&quot; "
&amp; &
Note that since the ampersand character has special meaning, it too has an escape character sequence.
Attributes are written in the form :
name="value"
or
name='value'
. Multiple attributes are separated
by white-space (spaces and line breaks).
Generally, the content of an element can be other child elements or text. However, the FB6000 doesn't use text
content in elements - all configuration data is specified via attributes. Therefore you will see that elements only
contain one or more child elements, or no content at all. Whilst there is generally not any text between the tags,
white space is normally used to make the layout clear.