Developer’s Guide

Table Of Contents
Use one of these grammars in your document or web page to display
and work with FileMaker data in XML format.
Note XML data generated by the Web Companion is encoded using
UTF-8 format (Unicode Transformation Format 8). For information,
see
“About UTF-8 encoded data” on page 10-8.
About XML namespaces
To avoid name collisions, unique XML namespaces help distinguish
XML tags by the application they were designed for. For example, if
your XML document contains two DATABASE elements, one for
FileMaker Pro XML data and another for Oracle XML data, the
namespaces will identify the DATABASE element for each.
The FileMaker Pro Web Companion generates a default namespace
for each grammar. For example, for the FMPDSORESULT
grammar, the following namespace is generated:
xmlns=“http://www.lemaker.com/fmpdsoresult”
About FileMaker Pro database error codes
The FileMaker Pro Web Companion generates an error code at the
beginning of each grammar based on the current error status of the
database. A value of zero (0) is returned for no error.
<ERRORCODE>0</ERRORCODE>
See appendix C, “FileMaker Pro values for error codes.”for
information.
Using FileMaker Pro XML to deliver your data on the Web 10-3
Using the FMPDSORESULT grammar
When you specify “–dso_xml” as the format for a FileMaker Pro
CGI request, the Web Companion will generate XML data based on
a database-specific grammar that uses field names as element names.
The FMPDSORESULT grammar is useful for publishing databases
on web pages that are formatted with cascading style sheets or
XSLT. (See
“Comparing CSS, XSLT, and JavaScript” on
page 10-11 for information.) The FMPDSORESULT grammar is
compatible with the Microsoft XML Data Source Object (DSO) used
by Internet Explorer, and is available on the FileMaker Developer
CD (Developer Extra\ileMaker, Inc\External FileMaker
APIs\XML\Documentation\fmpxmlresult_dtd.htm).
The Web Companion will also generate the document type definition
for the grammar if you specify “–dso_xml_dtd” as the format. This
is useful if you want an XML parser to validate the XML before your
document goes to production.
Note Beginning with Internet Explorer 4.0, Internet Explorer has
directly supported XML without the requirement of additional
software. The XML can be displayed using dynamic data binding
features available in the browser. This is accomplished with a Java
applet that ships with Internet Explorer, which presents the XML as
a DSO to the browser. With the DSO, the Internet Explorer browser
exposes XML data to scripting languages such as JavaScript or
VBScript via the Microsoft Document Object Model (DOM). Keep
in mind that the Microsoft XML DSO applet does not provide a
mechanism for updating the data, nor does it know anything about
FileMaker Pro database layouts or value lists. In addition, future
browser updates could change, limit, or remove the functionality
described above.