Upgrading to Rhizome version 0.6.0

To upgrade an existing Rhizome store to this version you will need to make these modifications to the store:

• Add the pages found in rhizome-config.py after the comment "#added in 0.6.0:"
• Replace the signup page with the new one
• Update any RxPath expressions that used the rdf:ID to use get-statement-uris() instead.
• Replace any usages of save-metadata and get-rdf-as-xml XPath functions with save-rdf and serialize-rdf, respectively.
• Add these statements:
• auth:GroupAccessToken rdfs:subClassOf: auth:AccessToken
• auth:AccountGroup rdfs:subClassOf: auth:Role

Upgrading to Rhizome version 0.5.1

• Add the skin CSS pages found in rhizome-config.py (after the comment "#css skins")
• Add the statement base:site-template: wiki:uses-skin: base:skin-lightblue.css

Upgrading to Rhizome version 0.5

The following changes may require changes to your application.

The find-unauthorized XPath function has been replaced with authorize-statements.

The following config settings have changed:

• The defaultPageName setting has been moved from server.cfg to the application config.
• initModel is replaced with domStoreFactory
• unAuthorizedExpr is no longer used, modify rhizome-config.py directly.
• authorizeAdditions and authorizeRemovals have been replaced by before-add and before-remove triggers.
• authorizeXPathFuncs signature and usage has changed

To upgrade an existing Rhizome store to this version you will need to make these modifications to the store:

• Add the pages found in rhizome-config.py after the comment "#added in 0.5.0:"
• Add the RxML defined by the authStructure variable in rhizome-config.py

Upgrading to Rhizome version 0.4.3

Any rdf:li psuedo-predicates that appeared in a RxPath expression should be replaced with rdfs:member. Alternatively, you could add the statement "rdfs:member: rdfs:subPropertyOf: rdf:li" to any model that uses such expressions (but this is an ugly hack).

Any references to the request metadata variable __user should be replaced with __account.

To upgrade an existing Rhizome store to this version you will need to make these modifications to the store:

• Changes for RDF schema support:
• replace references to wiki:Any with rdfs:Resource
• add the following statements:

 rdfs:member: rdfs:subPropertyOf: auth:requires-authorization-for
 rdf:first: rdfs:subPropertyOf: auth:requires-authorization-for
 wiki:revisions: rdfs:subPropertyOf: auth:requires-authorization-for
 a:contents: rdfs:subPropertyOf: auth:requires-authorization-for

If you have set the authPredicates config variable, replace the above statements with the properties you listed there.

• Changes for refactoring foaf:OnlineAccount out of foaf:Person:
• replace references to foaf:Person with foaf:OnlineAccount.
• replace references to wiki:login-name with foaf:accountName (or declare wiki:login-name a subproperty of foaf:accountName).
• If you wish to enable comments, add comments.xsl (see rhizome-config.py for page attributes)

Upgrading to Rhizome version 0.4.2

To upgrade an existing store to this version you will need to add the theme resources to your store.

Alternatively, if you don't want to use themes, do not replace your current site-template.xsl.

Upgrading to Rhizome version 0.4

Migrating an existing instance of Rhizome to the latest version involves exporting and re-importing the site as described in the Rhizome manual. If you have non-page resources you want to keep, you need to manually re-add them. The easiest way to do that is search for them using the "Edit" view, save the resulting RxML to a file and re-add them using either the generic-new-template page or by including it in your application's config script using the __addRxML__ directive. Alternatively, you can copy the statements from the old wikistore.nt or the transaction log and include them using the __addTriples__ directive in your config file.

The following list details changes between 0.4 and 0.3 that may require changes to existing sites:

• RxML now uses "bnode:" instead of "http://4suite.org/anonymous" as the URI prefix to represent anonymous (blank) nodes. Any existing RxML files should be updated to reflect this.
• The ZML syntax has changed: "#" is now the comment character instead of ";" and numbered lists are now created using "1." instead of "#". You can upgrade existing ZML (and RxML) files using the -u (or --upgrade) option of the ZML command line tool. It will make a copy of the specified file with the latest ZML syntax. (The file spec can contain wild cards.)
• The default PATH created by Rhizome has changed: Instead of putting the current directory that the Rhizome instance was launched from on the path, it uses the ALT_SAVE directory (by default "content"). Thus any files that relied on being on the PATH (e.g. external static files) should be moved to the ALT_SAVE directory.
• The "index" and "sidebar" pages now reference "index.zml" and "sidebar.zml" respectively, instead of "index.txt" and "sidebar.txt". If you placed your own version of those files on the PATH, you will need to rename them.
• Rhizome now uses the FOAF schema for representing users. To migrate existing users requires a few resources to be changed to the FOAF equivalent:
  wiki:User => foaf:Person
  wiki:fullname => foaf:name
  wiki:email => foaf:mbox (and turn the email literal into a <mailto:> URI)
  This script does this:
  sed 's/rx4rdf.sf.net/ns/wiki#User/xmlns.com/foaf/0.1/Person/g' wikistore.nt
  sed 's/rx4rdf.sf.net/ns/wiki#fullname/xmlns.com/foaf/0.1/name/g' wikistore.nt
  sed 's/rx4rdf.sf.net/ns/wiki#email> "(.*)"/xmlns.com/foaf/0.1/mbox> <mailto:1>/g' wikistore.nt