Familypedia:Info pages/technical guidelines

New key names
First, identify the practical benefit of encoding the data an info page. If for example the information will likely only be used in one place, or can be reliably inferred from the wikitext, then the item should not be in an info page. For example, if there is a wikipedia article on the figure, what benefit is there of encoding it in the info page? Using an AlsoWP template achieves the same result, uses fewer server resources, and if at some far future date an inferencing program wants to know what en article corresponds to the genealogy article, refering to the AlsoWP link is sufficient- they don't need an explicit declaration in the

Key naming: Strictly follow- initial first letter Cap, all others lower. No exceptions. It used to be all lower caps, but Intial cap allow the keys to be picked out more easily in wikitext code.

Languages
Info pages are not to be burdenned with general translation dictionary tasks. For example, there should not be a "Sex" key for every language. Instead, use a switch statement based on the value equaling male or female, or a template that gives what the 9th month of the year is in the local language. If the value is a value for an entity's attribute is unique to the individual, that value should have a key value if the language is being used. Do not create keys for such translated values if you cannot honestly imagine anyone accessing the value in the coming 2 years.

Data Model
We are basically following XML Gedcom (aka Gedcom 6.0)'s data model that describes entities and their attributes. The "Event" entity is omitted for now sice it is not clear that typical genealogy users would benefit from creation of such detail.
 * Unique identifier :GUIDs created by Guidgenerator.
 * Referencing- Article names are used.

Entities

 * Individual- this is a person article.
 * Attributes- see Genealogy:Info pages
 * Family- this is a children subpage of the father's article.
 * Attributes: