Re: what info should a dsk image archive store?

[jonnosan <jonnosan@gmail.com>]

Over the coming weekend I'm hoping to put together a strawman spec + a
sample archive incorporating the feedback received to date. But just
wanted to comment on this point:
On Aug 2, 12:10 pm, mdj <mdj....@gmail.com> wrote:
> I had assumed this application would be primarily web based? It seems
> a little redundant to have it offline these days, and raises the
> complexity considerably when you want to merge them later.

What I had imagined was, once there was a standard package format,
which included machine parsable metadata, then people could create
packages of their own dsks (using offline tools), and then upload them
to one or more archive sites, at the simplest those sites would do
nothing more than just store the packages (like currently happens with
Asimov etc) but it would also be easy to build a web app that pulled
out the metadata and presented a browsable and searchable catalogue of
images (like mobygames or lemon64).

My thinking here is based on systems like CPAN or rubygems, which have
a common package + metadata format, and a federated network of sites.