github.com/olivere/camlistore@v0.0.0-20140121221811-1b7ac2da0199/doc/schema/claims/attributes.txt (about)

     1  Permanode Attributes
     2  
     3  While a permanode can have any arbitrary attributes and values (and
     4  each value can be single-valued or multi-valued), the following are
     5  the conventional attributes and values used by the various tools,
     6  search, FUSE, and web UI.
     7  
     8  "tag": (multi-valued)
     9  
    10      a set of zero or more keywords (or phrases) indexed completely, for
    11      searching by tag. No HTML.
    12  
    13  "title": (single-valued)
    14  
    15      A name given to the permanode. No HTML.
    16  
    17  "description": (single-valued)
    18  
    19      An account of the permanode. It may include but is not limited to:
    20      an abstract, a table of contents, or a free-text account of the
    21      resource. No HTML.  As of 2013-12-28, not very defined yet.
    22  
    23  "camliContent": (single-valued)
    24  
    25      when a permanode is a file, the camliContent is set to the fileref
    26      (the blobref of the "file" schema blob)
    27  
    28  "camliMember": (multi-valued)
    29  
    30      when the permanode represents a set (unordered, unkeyed), the
    31      parent permanode (the container set) has a camliMember set to the
    32      permanode of each child element.
    33  
    34  "camliPath:$dirent_name" (single-valued)
    35  
    36      when the permanode represents an associative container, each keyed
    37      child permanode blobref is pointed to by the "camliPath:$key"
    38      attribute on the parent.  This is used by the FUSE client, and
    39      respected in the UI (browser, publishing code), etc.
    40  
    41  "camliNodeType" (single-valued)
    42  
    43      when the application needs to note the type of a permanode before
    44      any other attributes (like those above) are added which would otherwise
    45      imply its type, the camliNodeType lets applications be specific.
    46      This should only be used if another attribute can't imply it.
    47      Currently only used by FUSE to indicate the difference between a new
    48      file and a new directory permanode.  Known values include:
    49  
    50          * "directory". this permanode will have "camliPath:$key"
    51            attributes later.
    52          * "file". this permanode will have a "camliContent" later. for
    53            now, it should be treated as if it's an empty, 0-byte file.
    54  
    55  "camliDefVis" (single-valued)
    56  
    57      Can be "hide". Experimental. Affects default visibility in web UI.
    58  
    59  "xattr:$attr_name" (single-valued)
    60  
    61      when a permanode represents a file or directory visible to FUSE,
    62      "xattr:$x" is used to store the value for extended attribute "x".
    63      Extended attribute data may contain any arbitrary bytes, so values
    64      are base64 encoded.
    65  
    66  "camliRoot" (single-valued)
    67  
    68      TODO: doc
    69  
    70  "camliImportRoot" (single-valued)
    71  
    72      TODO: doc