Difference between revisions of "Assigning project content to files"
From XML
(Created page with "There are no fixed guidelines about how to decide how the material to be edited should be divided into multiple files. Some things to keep in mind are: * there is a certain lo...") |
(No difference)
|
Latest revision as of 10:47, 26 April 2017
There are no fixed guidelines about how to decide how the material to be edited should be divided into multiple files. Some things to keep in mind are:
- there is a certain logic to using a single for file for one logical or physical object: one manuscript or one book could be encoded in a single XML file.
- smaller files diminish the chance that multiple persons have to work on the same file: that would argue for many files containing only part of the edited material (e.g. one file per letter)
- having many files increases the amount of work when overall changes are needed (changes in naming conventions, changes in encoding guidelines)
- especially for secundary material, projects' requirements vary wildly.
In practice, the choice is made at the project level.
