Hi,
1) The versioning system should be totally independent of Alfresco's
versioning,
So, every time I post an updated version of a document such that it can be freely read and used by others (e.g. update it on Alfresco), I must also manually obtain a new portable version number, put that in the file when saving it, and associate where that version can be found? No thanks.
There is no need for yet another versioning system. We just require that versions exist and are weakly ordered. That already is present. We do not need the same mechanism and versioning authority to be used everywhere.
I don't think we need to update the "LibreOffice document version
system" each time we work on a document. While a document is being
worked on by the team members, before reaching publication state, we
can use the Alfresco versioning system for keeping track of progress.
We'd only need to manually update the LibO version system each time
the English docs team spits out a new version of a document for the
world to use.
However, IMHO, we really do need to have a versioning system that is
*totally independent* of the platform used to work on it.
And, for me, the document's meta data was designed for this kind of
purpose. By taking away the version info from the file name, you can
have nice, localized, human-readable file names while still being able
to keep track of versions and other worthwhile information.
Basically, what we're trying to cater to here is the project policy of
freedom of choice of working tools. That's why we don't really want to
have a versioning system tied to *one* single platform.
3 cents (higher weekend rate)
David Nelson