The source entity seems an ideal place to apply use of templates as described on the Use Of Templates
Page. How might sources be structured to best accommodate an expandable source template concept?
Sources are the foundation on which much genealogical research is based. Most modern genealogy programs support reasonably well-formatted sources. In addition, most information included in a published genealogy that is referred to as a citation is in fact information housed in the source entity within a computer database. These two are easily confused when speaking about the work of genealogy as it is expressed in genealogy technology databases.
BetterGEDCOM exports will serve different purposes and will need to represent source citations for each bit of data as originally described in the maker's originating file. In addition, to reflect true sourcing of information, BetterGEDCOM files should express their source data as though each source of information is the identified BetterGEDCOM itself and the "source of the source" is that which was described in the maker's source file when data transfer between users is the intended purpose of the generated BetterGEDCOM file.
Using a template model for sources, the great majority of source elements would be generic fields mapped to templates. One source might best be comprised of dozens of elements. How can such elements be structured?
Beyond variable fields for sources, what universal elements do all sources need?
Please develop source templates ideas within the Use Of Templates