DISCUSSION...
With the presentation of version 1.1 of the
PBCore, are we finished? Probably not. As the PBCore is refined and
used by various communities, we will undoubtedly add extensions to the
existing set of metadata elements to accommodate specials needs.
Extensions are additional descriptions for
media resources that have been crafted by organizations outside of the
PBCore development Project. These extensions fulfill the metadata
requirements for these outside groups as they identify and describe
their own types of media with specialized, custom terminologies.
For example, extensions that we know are important
to Public Broadcasting are those related to the use of media resources
in educational venues. The Dublin Core has a draft proposal for metadata
elements being assembled by its Education
Working Group. There are other applicable extensions from
the IEEE
Learning Object Metadata (LOM) Project which can be viewed in our PBCore Mappings & Crosswalks section on the page for the PBCore Mapping to IEEE LOM Learning Object Metadata (in the Extension section of the Content Classes).
DC-Ed |
Audience |
DC-Ed |
Audience.Mediator |
DC-Ed |
Standard |
DC-Ed |
Standard.Identifier |
DC-Ed |
Standard.Version |
IEEE
LOM |
InteractivityType |
IEEE
LOM |
InteractivityLevel |
IEEE
LOM |
TypicalLearningTime |
As well, the Sharable Content Object Reference
Model (SCORM)
aims to foster creation of reusable learning content as "instructional
objects" within a common technical framework for computer and Web-based
learning. SCORM describes that technical
framework by providing a harmonized set of guidelines, specifications,
and standards based on the work of several distinct e-learning specifications
and standards bodies. The IEEE Learning Object Metadata is folded into
the SCORM standards.
Also of importance are descriptions
related to accessibility issues. Many of these are documented through
the IMS
Project.
Of course, there are metadata needs that public
radio and public television share. Often their needs are unique to their
own production workflows and distribution channels, requiring customized
or industry-specific descriptors.
Likewise, when you consider the activities
related to Digital Interactive TV Guides, ATSC Digital Television System
capabilities, and various playout systems for Public Broadcasting stations, including Video-On-Demand and Internet distribution channels,
the number of metadata extensions grows in order to service the unique
needs of various Public Broadcasting users and communities.
The intent of the Public Broadcasting Metadata Dictionary Project is to first spawn a core set of metadata descriptors that
are applicable to most venues and scenarios. The PBMD Project is focused on
the ability to exchange metadata between parties rather than trying
to build a completely comprehensive, all encompassing, über metadata
system that satisfies all user requirements. As extensions are evaluated
and experts help the PBMD Project incorporate their metadata, the PBCore becomes
more robust, but simple enough to be understood and usable by most of
us.
In anticipated future collaborations, PBCore may itself be appended to other information and metadata systems, such as SMPTE DMS-1 for MXF (Material eXchange Format) transport, PBS PODS (Program Offer Data Service), HD Radio PSD (Program Service Data), and PRSS ContentDepot (Public Radio Satellite Service).
HOW TO ENTER DATA FOR THIS ELEMENT...
With the element extension, you are able to identify the following information:
- identify the actual name of the external element
- enter the actual description or values for the media asset
- identify the reference standard you are using
The template to use is as follows...
element_name:description_or_values [reference_standard]
For example...
umap_academic_disciplines:History; Science-Geography; Society and Culture [UMAP]
drm_enduser_permissions:You may download and display or play this media item in perpetuity, with no time or frequency limitations. [ODRL]
To see the XML interpretation for examples of the elements extension and extensionAuthorityUsed, according to the PBCore XML Schema, refer to our web page of PBCore Metadata Examples and view the XML rendition of the descriptions for those examples employing extensions (examples 4-10). |