EBU Tech 3285 definition:

• ASCII string (maximum 256 characters) containing a free description of the sequence. To help applications which only display a short description, it is recommended that a resume of the description is contained in the first 64 characters, and the last 192 characters are use for details.

FADGI recommendations:

1. Two capital letters which must be derived from ISO 3166 Country Codes
2. One comma
3. One space
4. Acronym. The great majority of acronyms are one word in all caps but there are some acronyms that are more than one word. The resource GovSpeak: A Guide to Government Acronyms and Abbreviations is suggested as a source but not required.
5. If string entered is under 32 characters, allow free-text string of up to 32 characters. End field with a null character.
6. This string should be automatically entered into the IARL data space.

COMMENT: This element is recommended as a container for identifiers for the work at hand and/or as pointers to additional, non-embedded (externally maintained) metadata. Members of the Working Group have repeatedly encountered the need to provide multiple identifiers for a given item. The resulting extent of data cannot be accommodated in the OriginatorReference element. For these reasons, the Working Group's recommendations for the Description element deviate from the EBU specification.

In some cases, the 256-character limit will prevent an agency from listing all of its identifiers; the most important or helpful should be provided.

Do not embed identifiers which could pose a possible security risk, e.g., by exposing exact pathnames.

NOTE: The Working Group perceived value in two practices but wished to leave these as optional. The first is the tagging of identifiers (see examples, typically URLs) to permit them to be properly understood. The second is the repetition of the principal identifier (as provided without tagging) in OriginatorReference as the first identifier in Description, where labeling as to its origin or purpose can be provided. Comments from readers are welcome.

FADGI Requirements:

• Strongly recommended (if the Working Group had authority: "required")

FADGI Formatting:

• If labeled: Identifier [comma space] type [comma space] comment [semicolon-space if more than one identifier]
• If no labeling: Identifier

FADGI Examples:

• 58979818, local, principal ID original filename; 306-MUSA-9658B, local, RG-Series-Item
• http://hdl.loc.gov/loc.mbrsmi/westhpp.2033, URL, principal ID handle
• http://hdl.loc.gov/loc.mbrsmi/westhpp.2033
• ark.cdlib.org.org/ark:/13030/tf5p30086k, URL, ARK

EBU Tech 3285 definition:

• ASCII string (maximum 32 characters) containing the name of the originator/producer of the audio file. If the length of the string is less than 32 characters, the field is ended by a null character.

FADGI Application:

• This element contains the entity responsible for the "archiving" (creation, maintenance, preservation) of this digital item. Entity designations should be as specific as possible including a two-character county code to avoid the potential for conflict in the archiving entity’s name.

  If space permits within the 32 character limit, the archival entity should be identified at the most specific level within the institution.

  Use a standard abbreviation of entity names such as those found in the Guide to Government Acronyms & Abbreviations. If an entity is not on this list, use a familiar abbreviation. Use the standard two-character ISO 3166 alpha 2 country code list.

FADGI Requirements:

• Strongly recommended (if the Working Group had authority: "required")

FADGI Examples:

• US, LOC/RSS
• US, NARA
• US, EPA

EBU Tech 3285 definition:

• ASCII string (maximum 32 characters) containing a non ambiguous reference allocated by the originating organization. If the length of the string is less than 32 characters, the field is ended by a null character.
• Note: The EBU has defined a format for the OriginatorReference field. See EBU Technical Recommendation R99-1999.

FADGI recommendations:

• This element contains the principal identifier or the "best" identifier which uniquely differentiates one object from another, preferably at the file level.
• If the principal identifier string is less than 32 characters, enter the entire identifier string.
• If the principal identifier string is longer than 32 characters, enter this text: "See Description for identifiers."
• Do not embed identifiers which could pose a possible security risk, e.g., by exposing exact pathnames.
• NOTE: The Working Group perceived value in the practice of repeating the principal identifier as the first identifier in the BEXT Description element (which has 256 available characters) but did not make this detail a strong recommendation. Comments from readers are welcome.

FADGI Requirements:

• Strongly recommended (if the Working Group had authority: "required")

FADGI Examples:

• US, LOC/RSS
• US, NARA
• US, EPA

EBU Tech 3285 definition:

• Ten ASCII characters containing the date of creation of the audio sequence. The format is YYYY-MM-DD (year-month-day).
• Year is defined from 0000 to 9999 Month is define from 1 to 12 Day is defined from 1 to 28,29,30 or 31
• The separator between the items can be anything but it is recommended that one of the following characters is used: hyphen, underscore, colon, space, or stop (period).

FADGI recommendations:

This element contains the file creation date. This is understood to mean the local date in the timezone for the archival entity; the structure of the bext chunk does not permit ISO 8601 datetime indication, which unambiguously indicates date and time in terms of UTC (Coordinated Universal Time or Temps Universel Coordonné).

• Year only: YYYY (eg 1997)
• Year and month: YYYY-MM (eg 1997-07)
• Complete date: YYYY-MM-DD (eg 1997-07-16)
   
• Where YYYY = four-digit year
• Where MM = two-digit month (01=January, etc.) Month is defined from 01 to 12 (use leading zeroes if less than 10);
• Where DD = two-digit day of month (01 through 31) Day is defined from 01 to 28, 29, 30 or 31 (use leading zeroes if less than 10).
   
• Use a hyphen as a separator between data elements.
• If string entered is under 10 characters, end field with a null character.

FADGI Formatting:

• ISO 8601 YYYY-MM-DD. Year is defined from 0000 to 9999; Month is defined from 01 to 12 (use leading zeroes if less than 10); Day is defined from 01 to 28, 29, 30 or 31 (use leading zeroes if less than 10). The separator between the items is a hyphen [-] with no spaces. Note: the Working Group adheres to the ISO 8601 truncation convention: the year should always be given but, if unknown, values for month and day are omitted. Thus the string length may be four, seven, or ten. If the string entered is less than ten characters, end it with a null character.

FADGI Requirements:

• Strongly recommended (if the Working Group had authority: "required")

FADGI Examples:

• 2005-11-09

EBU Tech 3285 definition:

• This field contains the timecode of the sequence. It is a 64-bit value which contains the first sample count since midnight. The number of samples per second depends on the sample frequency which is defined in the field <nSamplesPerSec> from the <format chunk>.

FADGI recommendations:

• The Working Group believes that TimeReference can be used in a manner that supports the management of files that are parts of multitrack or multisegment works and plans to provide recommendations in the future.

FADGI Requirements:

• Optional but recommended for complex recordings

EBU Tech 3285 definition:

• Eight ASCII characters containing the time of creation of the audio sequence. The format is HH-MM-SS (hours-minutes-seconds).
• Hour is defined from 0 to 23. Minute and second are defined from 0 to 59.
• The separator between the items can be anything but it is recommended that one of the following characters is used: hyphen, underscore, colon, space, or stop (period).

FADGI recommendations:

This element contains the file creation time. This is understood to mean the local time in the timezone for the archival entity; the structure of the bext chunk does not permit ISO 8601 datetime indication, which unambiguously indicates date and time in terms of UTC (Coordinated Universal Time or Temps Universel Coordonné).

Follow the ISO 8601 model which allows for some flexibility depending upon how much time information is available:

• Hours and Minutes only: hh:mm
• Hours, minutes and seconds: hh:mm:ss
  
• Where hh = two digits of hour (00 through 23) (am/pm NOT allowed) Hour is defined from 00 to 23 (use leading zeroes if less than 10).
• Where mm = two digits of minute (00 through 59)
• Where ss = two digits of second (00 through 59) Minute and second are defined from 00 to 59 (use leading zeroes if less than 10).

If string entered is under 8 characters, end field with a null character

FADGI Requirements:

• Optional

EBU Tech 3285 definition:

• Non-restricted ASCII characters, containing a collection of strings terminated by CR/ LF. Each string contains a description of a coding process applied to the audio data. Each new coding application is required to add a new string with the appropriate information. This information must contain the type of sound (PCM or MPEG) with its specific parameters:
  • PCM : mode (mono, stereo), size of the sample (8, 16 bits) and sample frequency:
  • MPEG : sample frequency, bit-rate, layer (I or II) and the mode (mono, stereo, joint stereo or dual channel).
• It is recommended that the manufacturers of the coders provide an ASCII string for use in the coding history.
• Note: The EBU has defined a format for CodingHistory which will simplify the interpretation of the information provided in this field. See EBU Technical Recommendation R98-1999.

FADGI recommendations:

• This element is designed to hold data on the digitizing process including signal chain specifics, sample rate and bit depth, and other elements. It is defined as a collection of strings, each presented on a separate line, containing a history of the coding processes applied to the file. The first line documents the analog source recording, the second line contains data on the capture process, the third line of data records information on the storage of the file. A new line is added when the coding history related to the file is changed.

FADGI Requirements:

• Optional