PBCore: Review of Changes from v1.0 to v1.1

PBCore Elements
Review of Changes from v1.0 to v1.1

Context
PBCore Changes from v1.0 to v1.1
Other Element Views

Context

Since the initial publication (April 2005) of the Public Broadcasting Metadata Dictionary--PBCore v1.0, many stations, organizations and information systems have used its 48 elements to describe the intellectual content, property rights, and instantiations/formats of their media items and intellectual properties.

During 2006, the PBCore project was finalizing its XML Schema Definition (XSD) (for a discussion of XSD see The PBCore XML Schema web page). This XSD is the main framework upon which all the PBCore elements, their relationships, vocabulary picklists, and data types are organized and defined. The purpose of building an accurate and meticulous XSD is to ensure that when PBCore compliant metadata descriptions are shared between data systems, the contributing system and the receiving system are both able to "machine read" and faultlessly interpret and display the descriptions.

In the process of creating the PBCore XSD, we determined that enhancements to the underlying structure of PBCore v1.0 were necessary, resulting in PBCore v1.1. For the most part, these enhancements are related to binding together related metadata elements (such as *title* and *titleType*) into new "Element Containers." In a hierarchical arrangement, each Element Container collects and houses associated "child" Elements that are thematically related. Basically, what was a "flat" arrangement of the 48 PBCore elements has become a more structured "hierarchical" model of 53 elements, arranged in 15 containers and 3 sub-containers, all organized under 4 content classes.

An advantage to using the Element Container approach is that, unlike the basically flat arrangement of elements found in Dublin Core (http://www.dublincore.org), PBCore is able to bind together the data found in related elements and keep them that way. For example, a *title* and its associated *titleType* can be catalogued and bound together as one instance of the container *pbcoreTitle*. The container *pbcoreTitle* can be repeated within a single metadata record, with another *title* and *titleType*. For example, a working title or an alternative title can be specified, but still be part of one data record, instead of making multiple data records, each with redundant metadata (descriptions, keywords, coverage, etc.). Similarly a particular format (and its associated specifications) for a media item can be described within the container *pbcoreInstantiation*, and repeated multiple times for different formats/instantiations, all within a single metadata record.

A more complete explanation is provided on the PBCore web page entitled Hierarchical Relationships and Interdependencies between Metadata Elements.

The roots, branches, and leaves of the hierarchies implied in PBCore v1.1 are alternatively expressed in a data model as "Content Classes," "Containers," "Sub-Containers," and "Elements."

CONTENT CLASSES
In the hierarchy of objects in the PBCore XSD Description Document, Content Classes are created as "conceptual wrappers" that cluster together a list or structure of thematically-related Elements (metadata fields and their attributes and properties). PBCore maintains four Content Classes as the conceptual wrappers for its various metadata elements:

PBCoreIntellectualContent
9 containers; 16 elements
(metadata elements describing the actual intellectual content of a media asset or resource)

PBCoreIntellectualProperty
4 containers; 7 elements
(metadata elements related to the creation, creators, usage, permissions, constraints, and use obligations associated with a media asset or resource)

PBCoreInstantiation
1 container; 3 sub-containers; 28 elements
(metadata elements that identify the nature of the media asset as it exists in some form or format in the physical world or digitally)

PBCoreExtensions
1 container; 2 elements
(additional descriptions that have been crafted by organizations outside of the PBCore 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 unique to their needs and community requirements)

ELEMENT CONTAINERS & SUB-CONTAINERS (aka Schema Tag and Schema Sub-Tag, alternatively "branches"):
Elements are objects in the PBCore schema hierarchy that define a metadata field and its values, attributes and properties. An element may be standalone. If several metadata fields are thematically related to each other, they can be bound together under an Element Container. Related elements are subsumed by a larger theme, and should be bound together when data is shared (particularly if an Element Container is a repeatable description with multiple instances of its related Elements). Examples of related Elements bound within a Container are *title* and its associated *titleType*, that are bound together by the Element Container *PBCoreTitle*. Within hierarchical structures, a Container may house Sub-Containers, which themselves bind together related Elements. In PBCore, there are Sub-Containers found within the Content Class PBCoreInstantiation.

ELEMENTS (aka "leaves"):
Elements are objects that define a metadata field and its values, semantics, attributes, and properties (for a list of the attributes defined for PBCore elements, see our web page PBCore Element Attributes). An Element is the actual "thing" that carries the descriptive metadata about a media item, such as a title, a date, keywords, rights information, mime types, media types, etc. The metadata elements are what a cataloger interacts with (creating descriptions) within a cataloging tool or asset management system.

The underlying meaning and attributes of the PBCore elements are not changing. However, their interdependencies and structural arrangements are, along with some modifications to data entry options. These PBCore Changes from v1.0 to v1.1 are itemized below.

Likewise, the entire PBCore Website, http://www.pbcore.org, is re-edited and updated in support of v1.1 of the metadata elements...

The PBCore User Guide has been revised and updated to reflect the changes in PBCore v1.1
Full Documentation is provided on an element-by-element basis, with notations of element interdependencies
A Cheat Sheet is added as a quick reference guide to using the elements for cataloging
Different views offer enhanced "at-a-glance" snapshots of the elements in v1.1
Significant Changes from PBCore v1.0 to v1.1 are itemized
Sample Metadata Records for different media types are provided
Case Examples of PBCore Implementations have been researched and posted
Mappings of PBCore to other metadata standards and schemes are documented
A Cataloging Tool to facilitate data entry and interoperability with other information systems is available
The PBCore v1.1 XML Schema Definition (XSD) is published
Training Sessions for PBCore (live WebEx and On-Demand) are available
A specific PBCore Namespace is identified
The Metadata Primer is updated

PBCore Changes from v1.0 to v1.1

This table of PBCore elements is organized by the Four Content Classes of PBCore (Intellectual Content, Intellectual Property, Instantiations, and Extensions). Associated Containers, Sub-Containers, and Elements as defined in PBCore v1.1 are included; each entry has an active hyperlink to a separate page that defines and describes that element in full.

Version 1.1 of PBCore maintains:

53 elements,
arranged in 15 containers and
3 sub-containers,
all organized under 4 content classes.

Based on this outline of PBCore v1.1 metadata elements, changes are noted in the migration from v1.0, on an element-by-element basis. Note that the numbering scheme for the elements has been revised, although that should have minimal impact on actual database or cataloging implementations.

Click on the name of an element (displayed in bold and italicized text) to review the changes for a particular metadata element in more detail. Global changes to PBCore (e.g., hierarchical data modeling) are discussed above in the section labeled Context.

Provided for your convenience are the following two indexes to the element list. One by Content Classes, the other an Alphabetical directory.

Content Class Index of Elements for Cheat Sheet

Intellectual Content elements

Intellectual Property elements

Instantiation elements

Extension elements

Alphabetical Index of Elements for Cheat Sheet


alternativeModes	description	formatFrameSize	identifierSource
annotation	descriptionType	formatGenerations	language
audienceLevel	extension	formatIdentifier	publisher
audienceRating	extensionAuthorityUsed	formatIdentifierSource	publisherRole
contributor	formatAspectRatio	formatLocation	relationIdentifier
contributorRole	formatBitDepth	formatMediaType	relationType
coverage	formatChannelConfiguration	formatPhysical	rightsSummary
coverageType	formatColors	formatSamplingRate	subject
creator	formatDataRate	formatStandard	subjectAuthorityUsed
creatorRole	formatDigital	formatTimeStart	title
dateAvailableEnd	formatDuration	formatTracks	titleType
dateAvailableStart	formatEncoding	genre
dateCreated	formatFileSize	genreAuthorityUsed
dateIssued	formatFrameRate	identifier

Go to Index

Content Classes (4)	Containers (15)	*Sub-Container**s (3)*	Elements (53)	Version Changes to 1.1
INTELLECTUAL CONTENT	This Content Class contains metadata elements describing the actual intellectual content of a media asset or resource.
	9 containers		*16 elements*
01.00	pbcoreIdentifier			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions. This Element Container is repeatable if the related child elements provide additional data descriptions.

01.01			identifier	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Unlike the element formatIdentifier, this element is used to describe the entire asset and any of its repeated formats.

01.02			identifierSource	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Unlike the element formatIdentifierSource, this element is used to describe the entire asset and any of its repeated formats.
Go to Index
02.00	pbcoreTitle			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

02.01			title	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

02.02			titleType	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Revised the picklist of possible titleTypes to embrace a variety of media types and allow a better expression of the type of title being displayed or identified.
Go to Index
03.00	*pbcoreSubject*			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

03.01			subject	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the possible subject terms to be used by referencing both the PBS PODS Data Dictionary of Subject Terms and the Content Depot and Public Radio International Program Service Data Consortium's ID3 tags for music types.

03.02			subjectAuthorityUsed	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the possible subject authorities by referencing both the PBS PODS Data Dictionary of Subject Terms and the Content Depot and Public Radio International Program Service Data Consortium's ID3 tags for music types.
Go to Index
04.00	*pbcoreDescription*			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

04.01			description	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

04.02			descriptionType	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Revised and expanded the picklist of possible descriptionTypes beyond that of "Abstract" and "Table of Contents."
Go to Index
05.00	pbcoreGenre			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

05.01			genre	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

05.02			genreAuthorityUsed	NEW ELEMENT IN v1.1 Element was created to identify established authorities or picklists of vocabulary terms used to define the genre descriptions being used. Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
06.00	pbcoreRelation			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

06.01			relationType	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

06.02			relationIdentifier	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
07.00	pbcoreCoverage			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

07.01			coverage	NEWLY DEFINED ELEMENT IN v1.1 To leverage the power of Element Containers and their repeatability, the previously defined coverageSpatial and coverageTemporal elements of v1.0 were combined into a single element called coverage. The distinction between spatial and temporal coverage is maintained, but is now defined in the related element coverageType. Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

07.02			coverageType	NEW ELEMENT IN v1.1 To leverage the power of Element Containers and their repeatability, the previously defined coverageSpatial and coverageTemporal elements of v1.0 were combined into a single element called coverage. The distinction between spatial and temporal coverage descriptions found in the related element coverage is maintained, but is now defined by coverageType. New picklist added for v1.1. Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
08.00	*pbcoreAudienceLevel*			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

08.01			audienceLevel	Hierarchically bound to a parent Element Container. This element is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
09.00	*pbcoreAudienceRating*			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

09.01			audienceRating	Same meaning as in v1.0; however, the FCC-TV (V-Chip) picklist of ratings are revised to match that of the PBS PODS picklist of terms. Hierarchically bound to a parent Element Container. This element is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
INTELLECTUAL PROPERTY	This Content Class contains metadata elements related to the creation, creators, usage, permissions, constraints, and use obligations associated with a media asset or resource.
	4 containers		*7 elements*
15.00	pbcoreCreator			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

15.01			creator	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

15.02			creatorRole	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the possible creatorRoles by adding PBS PODS Data Dictionary role vocabulary.
Go to Index
16.00	pbcoreContributor			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

16.01			contributor	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

16.02			contributorRole	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the possible contributorRoles by adding PBS PODS Data Dictionary role vocabulary.
Go to Index
17.00	pbcorePublisher			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

17.01			publisher	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

17.02			publisherRole	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
18.00	pbcoreRightsSummary			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

18.01			rightsSummary	Hierarchically bound to a parent Element Container. This element is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the narrative in the Guidelines for Usage to reference the ODRL Open Digital Rights Language and to summarize the three basic types of rights: Permissions, Constraints, and Obligations.
Go to Index
INSTANTIATIONS	This Content Class contains metadata elements that identify the nature of the media asset as it exists in some form or format in the physical world or digitally.
	1 container	*3 sub-containers*	*28 elements*
25.00	pbcoreInstantiation			New element container, with its three sub-containers and their associated child elements listed as shown.

25.01			dateCreated	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.02			dateIssued	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.03			formatPhysical	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.04			formatDigital	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Updated picklist of digital formats to reflect contemporary MIME Media Types as assigned by the IANA, Internet Assigned Numbers Authority (2006).
Go to Index
25.05			formatLocation	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.06			formatMediaType	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.07			formatGenerations	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.08			formatStandard	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
25.09			formatEncoding	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.10			formatFileSize	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.11			formatTimeStart	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.12			formatDuration	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
25.13			formatDataRate	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.14			formatBitDepth	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.15			formatSamplingRate	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.16			formatFrameSize	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Revised picklist of frameSizes to more closely parallel commonly used terminology in use today when referring to ATSC frame dimensions (including interlaced i or progressively p scanned screen rasters).
Go to Index
25.17			formatAspectRatio	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the narrative in the Guidelines for Usage to reference additional websites offering context and background information about aspect ratios.

25.18			formatFrameRate	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item). Enhanced the picklist of possible terms available to identifiy formatFrameRates.

25.19			formatColors	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.20			formatTracks	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
25.21			formatChannelConfiguration	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.22			language	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

25.23			alternativeModes	Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index
25.24.0		pbcoreDateAvailable		New Element Sub-container, with its associated child elements listed as shown. This Element Sub-container is repeatable if the related child elements provide additional data descriptions.

25.24.1			dateAvailableStart	Hierarchically bound to a parent Element Sub-container. This element (and any associated "sibling" elements) is applied only once within its Element Sub-container (which itself can be applied multiple times as needed for each rendition of a media item within the parent Element Container pbcoreInstantiation).

25.24.2			dateAvailableEnd	Hierarchically bound to a parent Element Sub-container. This element (and any associated "sibling" elements) is applied only once within its Element Sub-container (which itself can be applied multiple times as needed for each rendition of a media item within the parent Element Container pbcoreInstantiation).
Go to Index
25.25.0		pbcoreFormatID		New Element Sub-container, with its associated child elements listed as shown. This Element Sub-container is repeatable if the related child elements provide additional data descriptions.

25.25.1			formatIdentifier	Hierarchically bound to a parent Element Sub-container. This element (and any associated "sibling" elements) is applied only once within its Element Sub-container (which itself can be applied multiple times as needed for each rendition of a media item within the parent Element Container pbcoreInstantiation). Unlike the element identifier, this element is used to ID a specific format instantiation.

25.25.2			formatIdentifierSource	Hierarchically bound to a parent Element Sub-container. This element (and any associated "sibling" elements) is applied only once within its Element Sub-container (which itself can be applied multiple times as needed for each rendition of a media item within the parent Element Container pbcoreInstantiation). Unlike the element identifierSource, this element is used to ID a specific format instantiation.
Go to Index
25.26.0		*pbcoreAnnotation*		New Element Sub-container, with its associated child elements listed as shown. This Element Sub-container is repeatable if the related child elements provide additional data descriptions.

25.26.1			annotation	Hierarchically bound to a parent Element Sub-container. This element (and any associated "sibling" elements) is applied only once within its Element Sub-container (which itself can be applied multiple times as needed for each rendition of a media item within the parent Element Container pbcoreInstantiation).
Go to Index
EXTENSIONS	This Content Class contains additional descriptions that have been crafted by organizations outside of the PBCore 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 unique to their needs and community requirements.
	1 container		*2 elements*
99.00	pbcoreExtension			New Element Container, with its associated child elements listed as shown. This Element Container is repeatable if the related child elements provide additional data descriptions.

99.01			extension	NEW ELEMENT IN v1.1 If a community or speciality need for expanded metadata is desired, PBCore v1.1 is able to embrace these additions by using the element extension and extensionAuthorityUsed within the repeatable parent Element Container pbcoreExtension. Thus, locally defined metadata can be defined and appended to the PBCore standard without "breaking" or "corrupting" the underlying structures of PBCore. Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).

99.02			extensionAuthorityUsed	NEW ELEMENT IN v1.1 If a community or speciality need for expanded metadata is desired, PBCore v1.1 is able to embrace these additions by using the element extension and extensionAuthorityUsed within the repeatable parent Element Container pbcoreExtension. Thus, locally defined metadata can be defined and appended to the PBCore standard without "breaking" or "corrupting" the underlying structures of PBCore.. Hierarchically bound to a parent Element Container. This element (and any associated "sibling" elements) is applied only once within its Element Container (which itself can be applied multiple times for a media item).
Go to Index

Other Element Views for PBCore

Listed below are quick jumps to other organizational views of the PBCore elements.

PBCore Element Views

Quick Index View

Graphical View

Alphabetical View

Mandatory Elements List

Full Documentation for each Element

Cheat Sheet for Using the Elements

Hierarchies & Element Interdependencies

Metadata Examples

Changes for PBCore v1.1