|
Hi,
One other thing... I do not think we should keep track of concurrent versioning information in the meta data of the ebook.
So for example:
<meta name="FileName" content="FILENAME.EXT" />
<meta name="FileVersion" content="VERSION NUMBER/NAME" />
<meta name="FileScanner" content="NAME" />
<meta name="FileComment" content="COMMENT" />
These should not be in "released" eBooks. They should in fact be tracked by the concurrent versioning system used to keep track of editing changes and things *before* a version of the book is released.
For example, CVS, Mercurial, etc are all source code versioning systems that can be adapted to support concurrent editing and versioning of ebooks being worked on. That system would keep track of editorial changes, who made them, when they were made, the files changed, etc.
That information need not be part of the metadata of an "official release" of an eBook, in much the same way that the specific changes made to software, by whom, and when is not actually part of the information made when the software is released, it is kept internally only.
That said, I can see that many different organizations may make their own releases of the exact same public domain book, and as such, we do need to see the group doing the release.
If this fits under "DC.Publisher" then all is fine. If not, then we should probably add a specific "Generator" meta element to capture this infromation:
So something like.
name="Generator" content="org or person making the release"
as free form metadata, or
YOURNAMESPACEHERE.generator style.
Again, all of this is my 2 cents, feel free to ignore all of it.
Take care,
KevinH
|