The order of these is significant: the HEADER must come first and TRLR must be last, with any RECORDs in between.
RECORD :=HEADER :=n HEAD {1:1} g7:HEAD
+1 GEDC {1:1} g7:GEDC
+2 VERS <Special> {1:1} g7:GEDC-VERS
+1 SCHMA {0:1} g7:SCHMA
+2 TAG <Special> {0:M} g7:TAG
+1 SOUR <Special> {0:1} g7:HEAD-SOUR
+2 VERS <Special> {0:1} g7:VERS
+2 NAME <Text> {0:1} g7:NAME
+2 CORP <Text> {0:1} g7:CORP
+3 <<ADDRESS_STRUCTURE>> {0:1}
+3 PHON <Special> {0:M} g7:PHON
+3 EMAIL <Special> {0:M} g7:EMAIL
+3 FAX <Special> {0:M} g7:FAX
+3 WWW <Special> {0:M} g7:WWW
+2 DATA <Text> {0:1} g7:HEAD-SOUR-DATA
+3 DATE <DateExact> {0:1} g7:DATE-exact
+4 TIME <Time> {0:1} g7:TIME
+3 COPR <Text> {0:1} g7:COPR
+1 DEST <Special> {0:1} g7:DEST
+1 DATE <DateExact> {0:1} g7:HEAD-DATE
+2 TIME <Time> {0:1} g7:TIME
+1 SUBM @<XREF:SUBM>@ {0:1} g7:SUBM
+1 COPR <Text> {0:1} g7:COPR
+1 LANG <Language> {0:1} g7:HEAD-LANG
+1 PLAC {0:1} g7:HEAD-PLAC
+2 FORM <List:Text> {1:1} g7:HEAD-PLAC-FORM
+1 <<NOTE_STRUCTURE>> {0:1}The header pseudo-structure provides metadata about the entire dataset. A few substructures of note:
GEDC identifies the specification that this document conforms to. It is recommended that GEDC be the first substructure of the header.SCHMA gives the meaning of extension tags; see Extensions for more details.SOUR describes the originating software.CORP describes the corporation creating the software.HEAD.SOUR.DATA describes a larger database, electronic data source, or digital repository this data is extracted from.LANG and PLAC give a default value for the rest of the document.HEAD.SOUR.DATA is now deprecated and applications should use HEAD.SOUR.NAME instead.