Kevin --
The Audi-Visual Working Group of the Federal Agencies Digitization
Guidelines Initiative (http://www.digitizationguidelines.gov/audio-visual/)
has published its recommendations for use of <bext> and <info> chunk
elements in BWF files:
http://www.digitizationguidelines.gov/audio-visual/documents/Embed_Guideline_090915r.pdf
Below is this group's recommendations for use of the "Originator" field of
the <bext> chunk:
*Originator*
*
*
BWF Spec: 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.
Fed Agencies Spec: This element contains the entity responsible for the
"archiving" (creation, maintenance, Application 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.
Char limit: 32
Mandatory/optional: Strongly recommended (if the Working Group had
authority: "required")
Values: [Country code]comma space[Entity name]
Example: LC -- US, LOC/RSS [RSS = Recorded Sound Section]
Example: NARA -- US, NARA
Example: EPA -- US, EPA
Hope this helps in some way.
All the best --
Bertram Lyons
AFC/LOC
On Sat, Jan 9, 2010 at 9:19 AM, <[log in to unmask]> wrote:
> Hello,
>
> It is my understanding that the "Originator" field in the BEXT chunk of
> a BWF file is not meant to indicate copyright or intellectual property
> rights ownership. Is this correct? Does anyone use it for that
> purpose?
>
> Thank you,
> Kevin Irelan
>
> SYDA Foundation
|