Thanks Marky for your input, I did not want to assume that the OP was talking about this aspect of the FACT tag, and wanted additional information before explaining GEDCOM.
For a FACT we are given the following NOTE:
The usage of IDNO or the FACT tag require that a subordinate TYPE tag be used to define what kind of identification number or fact classification is being defined. The TYPE tag can be used with each of the above tags used in this structure.
To implement a generic fact that is not in the standard set of facts in v5.5.1 GEDCOM we have two basic elements.
1) The FACT tag
2) The FACT.TYPE tag
The FACT value is defined as:
Text describing a particular characteristic or attribute assigned to an individual. This attribute value is assigned to the FACT tag. The classification of this specific attribute or fact is specified by the value of the subordinate TYPE tag selected from the EVENT_DETAIL structure.
The FACT.TYPE tag is defined as:
EVENT_OR_FACT_CLASSIFICATION:= {Size=1:90}
A descriptive word or phrase used to further classify the parent event or attribute tag. This should be used whenever either of the generic EVEN or FACT tags are used. The value of this primative is responsible for classifying the generic event or fact being cited. For example, if the attribute being defined was one of the persons skills, such as woodworking, the FACT tag would have the value of `Woodworking', followed by a subordinate TYPE tag with the value `Skills.'
1 FACT Woodworking
2 TYPE Skills
This groups the fact into a generic skills attribute, and in particular this entry records the fact that this individual possessed the skill of woodworking.
It is important to understand the example given, normally the values provided are very short one or two words, as Marky indicated 90 characters is more than enough for these items. In webtrees and future releases of GEDCOM the EVEN tag can be used in the same way.
1 EVEN Battle of the Bulge
2 TYPE Military Campaigns
