Lists Home |
Date Index |
Michael Kay <email@example.com> writes:
> > As I replied to Dave, my leaning in this statement was
> > towards the data
> > side of the world. As you move more towards less
> structured data XML
> > becomes more and more attractive for archive.
> OK, so how would you archive the results of a national
> census? That's about as structured as you get. I would do it in XML.
There are really three issues implied in this question: archive and
public and private access. If one has to mix the concerns then XML is
as good as anything. Personally, I'd rather separate them, generating
XML for public access as needed. That leaves the private issues to be
implemented as best fits the system managing the data in the first
place. Given a clean slate that's probably a relational database
producing periodic XML format archives (for audit purposes and posterity
access) as well as having other archive mechanisms in place. If you're
assuming the census is read-only at some point in time, then I suppose
you can get rid of the relational database at that point in time.
Personally, I'd want to know more about any application requirements
before I'd say that XML alone would be sufficient.