MESA And SMPTE Develop First Human- And Machine-Readable Language Metadata Table
In collaboration with MESA, SMPTE is bringing the media industry’s first human- and machine-readable Language Metadata Table (LMT) into its public review process, an early step toward SMPTE standardization
Published as a SMPTE Public Committee Draft (CD), the vetted and approved list of language codes will be readily available for public comment, implementation, and validation.
The LMT register is intended to give media companies, content owners, video service providers, and others a controlled vocabulary and standardized set of codes for accurately and consistently identifying spoken and written language, in turn supporting more efficient interchange of media worldwide. Reflecting many thousands of permutations, LMT codes support numerous applications including audio, written and timed text (closed captions and subtitles), accessibility, licensing, content localization, and international distribution.
“The Language Metadata Table was started at WarnerMedia in 2017 to normalize language codes within the organization, and IETF BCP 47 was selected due to its flexibility,” said Yonah Levenson, LMT chair at MESA, the LMT sponsor. “As interest in LMT as the M&E industry's language code solution increased, SMPTE recognized the value of the LMT and came on board as the technical partner/advisor.”
Work on the LMT register has begun in SMPTE Technology Committees (TCs), which will produce a SMPTE Public CD in the first half of 2021. The Public CD process allows SMPTE to put the LMT register into the public domain quickly and then start the work of gathering feedback and making improvements to both the register and guidelines for its independent management by multiple stakeholders.
“If you buy and sell media, you understand that a common vocabulary for language tagging is sorely needed,” said SMPTE Standards VP Bruce Devlin. “The LMT register accounts for all languages as well as dialects and scripts. As we see the register through the Public CD process, our hope is that the LMT register will become a canonical resource that serves the needs of all media organizations and ecosystems. Accessing this data will be as simple as clicking on a link or using an API to grab required codes.”
SMPTE TCs are reviewing the prototype LMT register to determine if the structure of the dictionary is correct and if the process for updating that dictionary is correct. After this step is complete, the dictionary and update process will enter a public review period, during which people and organizations can try out the register and use a dedicated GitHub repository at github.com/smpte to provide real-world feedback that will inform iterative improvement of the register. The Society will leverage the SMPTE Knowledge Network, which is built on a flexible Microsoft Teams environment with integrated apps including the Microsoft 365 suite and GitHub, to bring agility and efficiency to the Public CD process.
“My hope is that ultimately we will have a structure document in SMPTE that defines the LMT, presents the data itself in both human- and machine-readable form, and provides a new administrative guideline that describes how we’ll manage controlled vocabularies and ontologies for third parties. I encourage any organization or individual with a stake in the internationalization of content to join the appropriate SMPTE TC and contribute their requirements and expertise,” added Devlin.
You might also like...
Designing IP Broadcast Systems - The Book
Designing IP Broadcast Systems is another massive body of research driven work - with over 27,000 words in 18 articles, in a free 84 page eBook. It provides extensive insight into the technology and engineering methodology required to create practical IP based broadcast…
Demands On Production With HDR & WCG
The adoption of HDR requires adjustments in workflow that place different requirements on both people and technology, especially when multiple formats are required simultaneously.
If It Ain’t Broke Still Fix It: Part 2 - Security
The old broadcasting adage: ‘if it ain’t broke don’t fix it’ is no longer relevant and potentially highly dangerous, especially when we consider the security implications of not updating software and operating systems.
Standards: Part 21 - The MPEG, AES & Other Containers
Here we discuss how raw essence data needs to be serialized so it can be stored in media container files. We also describe the various media container file formats and their evolution.
NDI For Broadcast: Part 3 – Bridging The Gap
This third and for now, final part of our mini-series exploring NDI and its place in broadcast infrastructure moves on to a trio of tools released with NDI 5.0 which are all aimed at facilitating remote and collaborative workflows; NDI Audio,…