While a permanode can have any arbitrary attributes and values (and each value can be single-valued or multi-valued), the following are the conventional attributes and values used by the various tools, search, FUSE, and web UI.
a set of zero or more keywords (or phrases) indexed completely, for searching by tag. No HTML.
A name given to the permanode. No HTML.
An account of the permanode. It may include but is not limited to: an abstract, a table of contents, or a free-text account of the resource. No HTML. As of 2013-12-28, not very defined yet.
when a permanode is a file, the camliContent is set to the fileref (the blobref of the "file" schema blob)
when a permanode has camliContent set, but the camliContent is of a non-image, the camliContentImage points to a "file" schema's blobref of an image representation of the content. For instance, this might be the cover art of an MP3 file or a thumbnail of a spreadsheet.
when the permanode represents a set (unordered, unkeyed), the parent permanode (the container set) has a camliMember set to the permanode of each child element.
when the permanode represents an associative container, each keyed child permanode blobref is pointed to by the "camliPath:$key" attribute on the parent. This is used by the FUSE client, and respected in the UI (browser, publishing code), etc.
when the application needs to note the type of a permanode before any other attributes (like those above) are added which would otherwise imply its type, the camliNodeType lets applications be specific. This should only be used if another attribute can't imply it. Currently only used by FUSE to indicate the difference between a new file and a new directory permanode. Known values include: * "directory". this permanode will have "camliPath:$key" attributes later. * "file". this permanode will have a "camliContent" later. for now, it should be treated as if it's an empty, 0-byte file.
Can be "hide". Experimental. Affects default visibility in web UI.
when a permanode represents a file or directory visible to FUSE, "xattr:$x" is used to store the value for extended attribute "x". Extended attribute data may contain any arbitrary bytes, so values are base64 encoded.