Platform Release 6 Notes
From n² wiki
Nearby: Platform Releases
These are notes on new features and bug fixes that are planned for release 6, released to internal staging on 9th October 2007 and due to go to live on 18th October
[edit] Creating Snapshots of Stores
This release introduces a new feature for creating snapshots of a store's content and metadata. Store owners can now submit a scheduled job which will initiate the snapshotting procedure at any determined time. A list of snapshots made for a store can be found by accessing the store's snapshot collection (at a URI like http://api.talis.com/stores/mystore/snapshots). Each snapshot made is linked from here and can be downloaded over HTTP. The snapshot is a tar file containing three things: a copy of the contentbox, a copy of the metabox and other private graphs in NTriples format, plus a system file which contains platform specific information that will allow automatic restoration of snapshots in a future release. The system file is encrypted, but the other files are fully accessible. As mentioned in the notes for the previous release stores are placed into a read-only mode while a snapshot is being taken, so applications will need to be able to handle the 503 response code returned from certain services during this time. (Related Jira issues: jira:CAL-163)
[edit] Controlling Blank Node Replacement
When RDF is submitted to the platform, blank nodes are automatically replaced by URIs. Up until this release store owners had no control over the types of URIs created. Release 6 allows a template to be specified to control the syntax of the generated URIs. This is specified by using a URI template in the store's configuration which allows much more flexibility for creating non-http or application-specific URIs. See the section on Store Configuration for full details. At the moment this template can only be updated by platform administrators, so please contact us if you would like it changed for your store. In the future store owners will have full control over setting this template and we're looking at additonal substitution tokens that could be useful. (Related Jira issues: jira:CAL-270)
