<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="/lib/exe/css.php?s=feed" type="text/css"?>
<rdf:RDF
    xmlns="http://purl.org/rss/1.0/"
    xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
    xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
    xmlns:dc="http://purl.org/dc/elements/1.1/">
    <channel rdf:about="/feed.php">
        <title>Documentation Center public:dson_spec:format_description:syntax</title>
        <description></description>
        <link>/</link>
        <image rdf:resource="/lib/tpl/dazdoccenter/images/favicon.ico" />
       <dc:date>2026-04-14T11:28:24+00:00</dc:date>
        <items>
            <rdf:Seq>
                <rdf:li rdf:resource="/public/dson_spec/format_description/syntax/start"/>
            </rdf:Seq>
        </items>
    </channel>
    <image rdf:about="/lib/tpl/dazdoccenter/images/favicon.ico">
        <title>Documentation Center</title>
        <link>/</link>
        <url>/lib/tpl/dazdoccenter/images/favicon.ico</url>
    </image>
    <item rdf:about="/public/dson_spec/format_description/syntax/start">
        <dc:format>text/html</dc:format>
        <dc:date>2012-05-30T17:31:38+00:00</dc:date>
        <title>Syntax</title>
        <link>/public/dson_spec/format_description/syntax/start</link>
        <description>
&lt;h1 id=&quot;syntax&quot;&gt;Syntax&lt;/h1&gt;
&lt;div class=&quot;level1&quot;&gt;

&lt;p&gt;
The &lt;abbr title=&quot;DAZ Scene Object Notation&quot;&gt;DSON&lt;/abbr&gt; file format has a text and a binary form.  Text formats are generally easier to debug during development and content crafting, and binary is generally more efficient to transmit.  The binary format is merely a zlib compressed (aka “zipped”) version of the text format.
&lt;/p&gt;

&lt;p&gt;
&lt;a href=&quot;http://www.json.org/&quot; class=&quot;urlextern&quot; target=&quot;_blank&quot; title=&quot;http://www.json.org/&quot; rel=&quot;nofollow noopener&quot;&gt;JSON&lt;/a&gt; is used as the file format syntax.  JSON was chosen as it is lighter weight than XML, and a standard used throughout the web for data transmission.  There exist parsers for it in JavaScript, C++, C#, as well as many other languages.  It is also a very simple language to write a new parser for should existing ones not fit a given need. 
&lt;/p&gt;

&lt;p&gt;
For the rest of the document, elements of the scene file will be presented in JSON notation, which can be found at the JSON website: &lt;a href=&quot;http://www.json.org/&quot; class=&quot;urlextern&quot; target=&quot;_blank&quot; title=&quot;http://www.json.org/&quot; rel=&quot;nofollow noopener&quot;&gt;http://www.json.org&lt;/a&gt;.
&lt;/p&gt;

&lt;p&gt;
As a quick summary, an &lt;em&gt;object&lt;/em&gt; is written as:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;{
    &amp;quot;key&amp;quot; : value,
    &amp;quot;key2&amp;quot; : value
}&lt;/pre&gt;

&lt;p&gt;
An &lt;em&gt;array&lt;/em&gt; is written as:
&lt;/p&gt;
&lt;pre class=&quot;code&quot;&gt;[ value, value, value ]&lt;/pre&gt;

&lt;p&gt;
A value can be a &lt;em&gt;string&lt;/em&gt;, &lt;em&gt;float&lt;/em&gt;, &lt;em&gt;object&lt;/em&gt;, &lt;em&gt;array&lt;/em&gt;, &lt;em&gt;null&lt;/em&gt;, &lt;em&gt;true&lt;/em&gt;, or &lt;em&gt;false&lt;/em&gt;.
&lt;/p&gt;

&lt;p&gt;
Unless otherwise noted, all child elements of an element must appear in the order specified, if they are present.
&lt;/p&gt;

&lt;p&gt;
Within the root file object (the &lt;a href=&quot;/public/dson_spec/object_definitions/daz/start&quot; class=&quot;wikilink1&quot; title=&quot;public:dson_spec:object_definitions:daz:start&quot;&gt;DAZ&lt;/a&gt; object) there are several properties named &lt;em&gt;*_library&lt;/em&gt;.  These are simply arrays of asset definitions of a given type.
&lt;/p&gt;

&lt;/div&gt;
</description>
    </item>
</rdf:RDF>
