perkeep/website/content/docs/schema

<h1>Schema</h1>

<p>At the lowest layer Camlistore doesn't care what you put in it
(everything is just dumb bytes) and you're free to adopt your own data
model.  However, the upper layers of Camlistore standardize on a <a href="/gw/doc/schema">common
schema</a> to represent various classes of data.</p>

<p>Here are some of the models we've started to formalize a <a href="http://json.org/">JSON</a> schema for:</p>

<ul>
  <li><a href="/gw/doc/schema/files">Files</a>: traditional filesystems.  Files, directories, inodes, symlinks, etc.</li>

  <li><a href="/gw/doc/schema/objects/permanode.txt">Permanodes</a>: the immutable root "anchor" of mutable Camli objects (see <a href="terms">terminology</a>).  Must be <a href="/docs/json-signing">signed</a>.</li>

  <li><a href="/docs/json-signing">Signing</a></li>

  <li><a href="/gw/doc/schema/objects/static-set.txt">Static Sets</a></li>

  <li><b>Dynamic Sets</b>, a Camli Object representing a mutable set of items (e.g. blog, photo collection / gallery, mutable filesystem, etc).  TODO: docs sprinkled in various places.  Consolidate.</li>

  <li><a href="/gw/doc/schema/objects/keep.txt">Keep claims</a></li>


</ul>