Changes between Version 3 and Version 4 of GROUP_PERSISTENCE_R0


Ignore:
Timestamp:
04/13/09 14:12:33 (16 years ago)
Author:
gogov
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • GROUP_PERSISTENCE_R0

    v3 v4  
    1616The R3 format replaces the R2 format. These are the goals of these task: 
    1717 * The R2 format is a file format for saving a given Book. Compared to it, the R3 format is a Resource format - it should be capable of saving any given Resource. 
    18  
    19  * This Resource-oriented format gives features that should be taken in mind when implementing it 
    20 : 
     18 * This Resource-oriented format gives features that should be taken in mind when implementing it: 
    2119  * In future it should allow saving/loading any Resource - Frame, Page, Annotation. This will be very useful if we consider Frame/Page editor for example. It would be also useful for saving templates. 
    22  
    23  * Improve machine and human readability of the format 
    24 : 
    25   * XML aspect - redesign the used XML tags to be both human and machine readable 
    26 . 
    27   * File structure - create a good and consistent structure inside the archive 
    28 . 
    29   * Data standards - what goes where 
    30 : 
     20 * Improve machine and human readability of the format: 
     21  * XML aspect - redesign the used XML tags to be both human and machine readable. 
     22  * File structure - create a good and consistent structure inside the archive. 
     23  * Data standards - what goes where: 
    3124   * XML aspect - XML should contain Immutables and metinfo. Define where does it belong in the structure 
    32  
    33    * Binary data - define location of the binary data for each ProObject (Resources in particular) 
    34 . 
     25   * Binary data - define location of the binary data for each ProObject (Resources in particular). 
    3526   * Text data - define how to handle text contents; where to store them and in what form. 
    36  * Define how a Resource is located and accessed (ID, local path, URL) 
    37 . 
     27 * Define how a Resource is located and accessed (ID, local path, URL). 
    3828 * Support caching and offline content - currently cache mechanism doesn't exust. The file format needs to support cache and ability to save online resources. 
    39  
    4029  * Caching however should be limited. In future releases we may consider GUI input for the limit, for example "100MB" 
    41  
    42  * Make the R3 format backward compatible with R2 
    43 : 
    44   * The application should be able to load a book in R2 format and save it to R3 format 
    45 . 
     30 * Make the R3 format backward compatible with R2: 
     31  * The application should be able to load a book in R2 format and save it to R3 format. 
    4632  * Optional - achieve saving a book in R2 format. This doesn't need to have GUI for saving in R2 but there may be a mechanism for converting R3 to R2.  
    47  
    4833 * Support of saving online content. This may not be implemented now, but in future we may have to support downloading online Resources and saving them into the book. 
    49  
    5034 * Also in the future, we need to refactor the Storage in order to implement lazy loading of Resources (and Resource preview, respectively). 
    51   
    5235 
    5336== Task result ==