Putting the revision number in the document has problems.  Notice that git, for 
example, doesn't have classic file revision numbers like SVN.  Simple numbers 
need to be dished out by an authority, rather than just incremented each time 
the file is saved.  After all, different people can each save the file.  The 
versioning, whatever it is, needs to be tied with the versioning =system=.  In 
the case of files stored on Alfresco, that's Alfresco's version number.  When 
you refer to some revision, it's not just "some copy I got from so-and-so via 
some passing around", but some place you can go and get a "committed" version 
from.  Furthermore, you have some weak ordering so you know if an available 
version is newer than the one you were using before.

For files that are not gotten from Alfresco, wherever you got them from needs 
some versioning system.

So, I stick by my analysis, but amend it to decorate the version number with 
the authority that produced that number.  As a community, we can have a (very 
small) registration of codes and their repositories, along with a description 
of each.  
So, you might refer to document 0202WG3-[AF]2.2-en, where [AF] refers to this 
group's existing Alfresco system, and the component could be omitted when it is 
not necessary.  0202WG3-2.2 omits two components, for example.

We also need to ensure that document numbers are assigned uniquely.  A 
systematic approach with wildcards can be used to register a whole book of many 
files, and this list is kept to ensure that new ids are assigned uniquely when 
someone wants one, but they are still short and reasonably mnemonic.
Perhaps we want to flip it around from the current file names so the wild part 
is always a suffix:  WG3* is "Writer's Guide for major version 3" with the 
per-book note on how chapter numbers are filled to two digits and suffixed to 
that.

So we need, perhaps on a Wiki page, two lists:  The unique id base part 
assignment, and the versioning authority information.

-- 
Unsubscribe instructions: E-mail to documentation+h...@libreoffice.org
List archive: http://listarchives.libreoffice.org/www/documentation/
*** All posts to this list are publicly archived for eternity ***

Reply via email to