![background image](http://html1.mh-extra.com/html/campbell/loggernet/loggernet_instruction-manual_3781887501.webp)
Appendix B. Campbell Scientific File Formats
XML documents possess a tree structure that consists of elements and element
attributes. The document is expected to have a single root element which can
contain any number of sub-elements which in turn can contain any number of
sub-elements and/or other content. Every element must have a name and can
optionally have a set of attributes which are a collection of name/value pairs
where the name is unique.
Most XML files will begin with a sequence that identifies the file as XML and
can also specify the character encoding of the file (if no character encoding is
specified, the file is assumed to use the UTF-8 unicode character encoding).
The following example shows this sequence as it will appear in CSIXML data
files:
<?xml version=“1.0” standalone=“yes”?>
XML is derived from SGML (Standard Generalized Markup Language) and
shares much of the same syntax rules as SGML. HTML (HyperText Markup
Language) is also derived from SGML and, as a result, also has a significant
resemblance to XML. XML elements are represented using tags. A tag begins
with the less than character (<) followed by the name of the element. If that
element has attributes, these will be expected to follow the element name with
a name=“value” syntax. At least one white space character is expected to
separate the attributes and the element name. Other than this rule, XML parsers
ignore the presence of whitespace within the tag. If an element is empty
(contains no child elements), the tag can end with a slash character (/) and the
greater than character (>). If the element is not empty (the element does have
child elements), the tag is expected to end with a greater than character (>) and
the child elements or element content will be expected to follow. In this case,
the end of the element is marked by another less-than character (<) followed by
a slash character (/), the element name, and a greater than character (>).
The following example shows how an element with content may appear:
<v n=“pi”>3.14159</v>
The following example shows how an empty element may appear:
<v n=“emptyString”/>
Because XML reserves special characters for its mark-up language, pre-defined
entities are recognized by all XML parsers. These entities include the
following:
TABLE B-2. Pre-Defined XML Entities
<
less than sign (<)
>
greater than sign (>)
& ampersand
(&)
"
double quote (“)
'
apostrophe or single quote (‘)
B-7
Summary of Contents for LoggerNet
Page 2: ......
Page 30: ...Preface What s New in LoggerNet 4 xxvi...
Page 32: ...Section 1 System Requirements 1 2...
Page 44: ...Section 2 Installation Operation and Backup Procedures 2 12...
Page 136: ...Section 4 Setting up Datalogger Networks 4 80...
Page 227: ...Section 7 Creating and Editing Datalogger Programs 7 9...
Page 298: ...Section 7 Creating and Editing Datalogger Programs 7 80...
Page 402: ...Section 9 Automating Tasks with Task Master 9 12...
Page 406: ...Section 9 Automating Tasks with Task Master 9 16...
Page 450: ...Section 11 Utilities Installed with LoggerNet Admin and LoggerNet Remote 11 22...
Page 454: ...Section 12 Optional Client Applications Available for LoggerNet 12 4...
Page 462: ...Section 13 Implementing Advanced Communications Links 13 8...
Page 482: ...Section 14 Troubleshooting Guide 14 20...
Page 570: ...Appendix F Calibration and Zeroing F 16...
Page 578: ...Appendix G Importing Files into Excel G 8...
Page 579: ......