CORE Document

The CORE Document serves the purpose of BEXT and LIST-INFO metadata exchange between BWF MetaEdit and other applications. BWF MetaEdit can import and export CORE Documents as XML or CSV. Once imported into BWF MetaEdit the CORE information can be edited and embedded into audio files. For files with existing bext and LIST-INFO metadata, BWF MetaEdit can display and export this data as a CORE document. A CORE document template can be generated within BWF MetaEdit or with another application. The CORE document lists one record per audio file.
The CORE Document is essentially a list of filepaths associated with BEXT and LIST-INFO values. Please see BEXT and LIST-INFO for more information and validation documentation for information on the correct use of these standards.

CORE Document CSV Format

A CSV formatted (RFC 4180) CORE Document must use the following structure and value parameters:
Column NameDescription
FileNamerequired. full file path
For more info on LIST-INFO fields, see the BEXT help page.
Descriptionmax 256 ASCII characters
Originatormax 32 ASCII characters
OriginatorReferencemax 32 ASCII characters
OriginationDatemax 10 ASCII characters
OriginationTimemax 8 ASCII characters
TimeReference (translated)Use to express TimeReference in HH:MM:SS.mmm form (hours:minutes:seconds.milliseconds). Example 01:59:15.250
TimeReferenceUse to express TimeReference as sample count. Example 441000
BextVersionUse to express whether the Bext Chunk follows the Rules of EBU Technical document 3285 as published in 1997 (version '0') or the 2001 update which created version '1'. Version '1' adds an additional field for UMID. Example '1'.
UMID64 byte Unique Material Identifier. Expressed as a hexadecimal string in XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX format.
For more info on LIST-INFO fields, see the LIST-INFO help page.
IARLArchival Location
ICRDCreation Date
INAMName (Title)
IPRDProduct (Album)
ISRFSource Form

CORE Document XML Format

An XML formatted CORE Document must follow the schema below and follow the rules demonstrated by the sample data: Use either <TimeReference_translated> to express TimeReference in HH:MM:SS.mmm format or <TimeReference> to express TimeReference as a sample count.
<?xml version="1.0" encoding="UTF-8"?>
 <File name="/full/file/path/to/audio-A.wav">
   <Description>Descriptive info here</Description>
   <Originator>Originator data here</Originator>
   <OriginatorReference>OriginatorReference data here</OriginatorReference>
   <IARL>Archival Location data here</IARL>
   <IART>Artist data here</IART>
   <ICMS>Commissioned data here</ICMS>
   <ICMT>Comment data here</ICMT>
   <ICOP>Copyright data here</ICOP>
   <IENG>Engineer data here</IENG>
   <IGNR>Genre data here</IGNR>
   <IKEY>Keyword data here</IKEY>
   <IMED>Medium data here</IMED>
   <INAM>Title data here</INAM>
   <IPRD>Album or product data here</IPRD>
   <ISBJ>Subject data here</ISBJ>
   <ISFT>Source data here</ISFT>
   <ISRC>Source data here</ISRC>
   <ISRF>Software data here</ISRF>
   <ITCH>Technician data here</ITCH>
 <File name="/full/file/path/to/audio-B.wav">