> > I think we should use the regular PalmOS version to indicate more
> > basic differences in structure.
>
> I disagree. There is a reason to why the version is included in a
> record, e.g. if you use the -c option when downloading the data and
> then some other tool to build the Plucker document you will not know
> what version to use.
Yes, I think having that version there is absolutely appropriate. I
am thinking of more radical changes to the structure, such as (gasp!)
abandoning the Palm DB format, if one day PalmOS becomes
file-system-aware. Or moving the index record. Using the
higher-level version number to indicate that kind of radical shift
seems like a good idea. That way we could still, for example, use the
68-byte header that we currently use (the PalmOS database header up
through the type and creator), and shift around the rest of the
fields.
For the moment we should specify that the version field in the
database header must have the value of 1.
Bill
