A few questions about the format

I spent portions of yesterday and this morning going through the mailing
list archives and Seth's sample files. Some documentation on our
decisions is startig to coagulate, but I have turned up a few questions
(mostly about the DTDs) that I need clarified.

(1) The 'type' attribute in the package element. I can see the
advantages of making this CDATA, so that we are not just restricted to
RPM and Debian-based packages, but what are the suggested values? Should
we say that this will be "rpm" for RPMs and "deb" (or what) for .debs?
Are there other types we care about at the moment?

(2) What is the 'id' attribute on the checksum element for? It is always
set to "YES" in the current version of rpm-md-dump.py, so it is not
really like an XML ID value. If it has a real purpose, can we either
make it have type ID (forcing it to be unique) or call it something
other than "id"?

(3) Should the 'type' attribute on the checksum element be an
enumeration, rather than CDATA? Should we list a set of recommended
values that we support? Currently rpm-md-dump.py puts type='md5sum'.
Multiple checksums are permitted by the DTD (which seems like a good
idea). What values should we use for other common checksum types?

(4) The 'epoch' attribute on the version element is required. Does this
make sense for .debs? (I think we discussed this, but I cannot find the
mail to back me up.)

(5) In the rpm namespace, I suspect the 'flags' attribute on the entry
element should be an enumeration of the possible flag types. There is no
real case to be made that we will need to arbitrarily extend these (is
there?), so lets just come up with the right set and enforce it.

That will do for now. :-)

Cheers,
Malcolm