Guidelines: Embedding Metadata in Broadcast WAVE Files - BWF MetaEdit Help:
CORE Document
Back to help home
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 Name | Description |
|---|---|
| FileName | required. full file path |
| For more info on LIST-INFO fields, see the BEXT help page. | |
| Description | max 256 ASCII characters |
| Originator | max 32 ASCII characters |
| OriginatorReference | max 32 ASCII characters |
| OriginationDate | max 10 ASCII characters |
| OriginationTime | max 8 ASCII characters |
| TimeReference (translated) | Use to express TimeReference in HH:MM:SS.mmm form (hours:minutes:seconds.milliseconds). Example 01:59:15.250 |
| TimeReference | Use to express TimeReference as sample count. Example 441000 |
| BextVersion | Use 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'. |
| UMID | 64 byte Unique Material Identifier. Expressed as a hexadecimal string in XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX format. |
| CodingHistory | |
| For more info on LIST-INFO fields, see the LIST-INFO help page. | |
| IARL | Archival Location |
| IART | Artist |
| ICMS | Commissioned |
| ICMT | Comments |
| ICOP | Copyright |
| ICRD | Creation Date |
| IENG | Engineer |
| IGNR | Genre |
| IKEY | Keywords |
| IMED | Medium |
| INAM | Name (Title) |
| IPRD | Product (Album) |
| ISBJ | Subject |
| ISFT | Software |
| ISRC | Source |
| ISRF | Source Form |
| ITCH | Technician |
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.
<conformance_point_document>
<File name="/full/file/path/to/audio-A.wav">
<Core>
<Description>Descriptive info here</Description>
<Originator>Originator data here</Originator>
<OriginatorReference>OriginatorReference data here</OriginatorReference>
<OriginationDate>2010-01-05</OriginationDate>
<OriginationTime>00:00:00</OriginationTime>
<TimeReference_translated>00:00:00.000</TimeReference_translated>
<TimeReference>0</TimeReference>
<BextVersion>1</BextVersion>
<UMID>FFFFFFFF-FFFF-FFFF-FFFF-FFFFFFFFFFFF</UMID>
<CodingHistory>A=ANALOGUE,F=48000,B=16,W=16,M=joint-stereo</CodingHistory>
<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>
<ICRD>2010-01-07</ICRD>
<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>
</Core>
</File>
<File name="/full/file/path/to/audio-B.wav">
</File>
</conformance_point_document>
Last Updated: 12/07/2016