RemoteStorage
From Unhosted Web Community Group
Contents |
remoteStorage specification
Introduction
This document describes when storage providers as well as hosted and unhosted web apps may call themselves 'remoteStorage-compatible', and may use this logo. The logo is licensed under Creative Commons, so anybody may freely use it as an image, but the if the logo or the term are used in a way that implies a claim to be remoteStorage-compatible, then that claim would simply not be true.
Requirements on storage providers
Until 9 September 2012, a storage provider should do one of the following:
- adhere to one of the 'stable' APIs described in http://www.w3.org/community/unhosted/wiki/RemoteStorage-2011.10
- [experimental] announce a read-write-web-00#simple service as a personal data service
Between now and 9 September 2012, a CouchDB-based option as well as a WebDAV-based option will be added. The first option will be removed on 9 September 2012, and only the other options will then remain.
Requirements on applications
In order to call itself remoteStorage-compatible, an application should allow users to store all their per-user data on any remoteStorage-compatible storage server. This means that it should implement a client for each possible type of server. We recommend using (and contributing to) remoteStorage.js for this whenever possible.
