User Tools

Site Tools


content:tech:rhizome_manifest

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
content:tech:rhizome_manifest [02/05/2014 01:04]
Andrew Bettison created, much taken from [[Rhizome]] page
content:tech:rhizome_manifest [27/09/2015 19:40] (current)
Andrew Bettison Fix BID link
Line 2: Line 2:
  
 Every [[Rhizome bundle]] consists of a single manifest and an optional payload.  The manifest carries [[http://en.wikipedia.org/wiki/Metadata|meta-data]] about the bundle: Every [[Rhizome bundle]] consists of a single manifest and an optional payload.  The manifest carries [[http://en.wikipedia.org/wiki/Metadata|meta-data]] about the bundle:
-  * Essential ("core") information needed for bundle integrity, prioritisation ([[Rhizome rank]]), and de-duplication+  * Essential ("core") information needed for bundle integrity (anti forgery and tampering)transport (de-duplication) and prioritisation ([[Rhizome rank]]): 
-    * Bundle ID +    * [[BID]] 
-    * version+    * bundle version
     * payload size     * payload size
-    * payload hash+    * payload hash (only if size is not zero) 
 +    * tail (only for a [[Rhizome journal]])
     * signature     * signature
-    * tail ([[Rhizome journal]]) 
   * Optional information to assist prioritisation and delivery:   * Optional information to assist prioritisation and delivery:
-    * sender +    * sender [[SID|SID]] 
-    * recipient+    * recipient [[SID|SID]]
     * expiry ([[Rhizome Use-By]])     * expiry ([[Rhizome Use-By]])
     * [[Rhizome bounding circle]]     * [[Rhizome bounding circle]]
Line 18: Line 18:
     * content type     * content type
   * Other optional, application-specific meta-data:   * Other optional, application-specific meta-data:
-    * format (eg, character encoding, image dimensions)+    * file name
     * creation date     * creation date
 +    * format (eg, character encoding, image dimensions)
  
 The last two categories of meta-data could be encrypted without affecting Rhizome transport and storage, since they are only needed on the recipient's device, and so will be encrypted in future. The last two categories of meta-data could be encrypted without affecting Rhizome transport and storage, since they are only needed on the recipient's device, and so will be encrypted in future.
Line 64: Line 65:
   * For a while, software upgrades create manifests containing the deprecated field and the newer field   * For a while, software upgrades create manifests containing the deprecated field and the newer field
   * Eventually a software release and all following releases cease to insert the deprecated field   * Eventually a software release and all following releases cease to insert the deprecated field
-  * This provides a time window during which the [[automatic upgrade]] has a chance to upgrade all the Rhizome software in the field+  * This provides a time window during which [[Auto upgrade]] has a chance to upgrade all the Rhizome software in the field
  
  
content/tech/rhizome_manifest.1399017889.txt.gz · Last modified: 02/05/2014 01:04 by Andrew Bettison