Splitting of Static and Dynamic Data

[Buried-In-Code]

Problem

A problem I've had with the various formats that have existed so far, as well as this project is the storing of dynamic data. The problem with storing dynamic data is that it is constantly changing and unless I'm constantly checking all of a sudden my data is out of date.

Example:

• Series status
• Total issue count in a series
• User Ratings

Proposition

I don't have an idea as to how to manage the dynamic data as current, but I would state that the file/s created from this RFC should only contain static data

[gotson]

At the moment the discussion is mostly about the data model, not its location.

To me there should be 2 location for the data :

• a centralized server, like comicvine, but open source and open for its data. This would contain e static and dynamic data.
• a local export, like a comicinfo.xml (but probably another format, to be defined), which would contain some information exported.

Your point is interesting though, dynamic data could probably have a timestamp when exported, so it can be compared when retrieved from 2 exported instances.