On Thu, 30 Jun 2005, Magnus Hagander wrote:
> How does this scheme deal with multiple versions?
> Say I (not trustworthy, remember!) cerate a document. Then Dave approves
> it for publishing. Then I edit it. At this ponit, the old version should
> be visible on the site. Then Dave approves the new version, at which
> point the old one should go away (or be kept in version history,
> probably) and the new one should be published.
That's why I suggest external pub_id, which is persistent and publicly
available id, and msg_id - another one for versionning. Then we need
mapping between pub_id and msg_id. In our CMS we have versions and revisions,
but I don't think it's needed here.
Regards,
Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83
