Version 7.0.6
-
Deprecate
EXID
without aTYPE
.EXID
is defined in terms of itsTYPE
, and anEXID
without aTYPE
is not meaningful.EXID
.TYPE
will have cardinality{1:1}
, not{0:1}
, in the next major release. -
Add media type specification for GEDZIP.
-
Add term definitions for 5.5.1-compatibility
EXID
.TYPE
valuesAFN
,RFN
, andRIN
. -
Clarifications about
LANG
- Clarify that
LANG
is the primary language, not sole language, of a payload. For example,LANG en
can be used when most of the text is in English, even if some parts are not. - A documented extension tag can be used where
LANG
is not defined. - Provide guidance on special language tags
und
can be used if a superstructure'sLANG
does not apply here and what does apply is not known.mul
can be used if there is no single primary language, but is unlikely to provide practical functionality beyondund
.zxx
can be used for ASCII art and other non-language text, and can improve accessibility for screen readers.
- Clarify that
-
Clarify that empty payloads are encoded as missing
LineVal
s and emptyLineVal
s are not been permitted; this has been true since 7.0.0 but was easily overlooked in the previous text. -
Note cases where the same couple might be the partners in multiple
FAM
records. -
Fix wording of
ADR1
,ADR2
, andADR3
to no longer refer toCONT
or line values. -
Acknowledge that
SNOTE
has an identifier structure, whichNOTE
does not, and change recommendation to suggest usingSNOTE
if aNOTE
needs an identifier. -
Update contact information on the title page.
-
Various spelling and grammar corrections.