This Content Class contains metadata elements describing the actual intellectual content of a media asset or resource.

There are 9 containers and a total of 16 elements in the Intellectual Content grouping.

• Dublin Core defines its element *identifier* with regard to a unique designation for a media item itself, and not an identifier for a entire metadata record associated with a media item and all of its descriptions, formats, renditions and instantiations.
• PBCore's *identifier* element is different than Dublin Core's *identifier*, although it is tempting to map the two elements because of the similarity in names.
• PBCore's *formatIdentifier* more closely parallels the definition and usage of Dublin Core's *identifier*.

• derivation from Dublin Core Metadata Registry

• PBCore does not maintain a separate and distinct element for an *Alternative Title* to the formal *Title* given a media item (a refinement to Dublin Core's *Title*). Instead PBCore repeats the pbcoreTitle container, supplies the *Alternative Title*, then from the element *titleType,* selects *Alternative* from the picklist of terms.

• derivation from Dublin Core Metadata Registry

• PBCore recommends several related schemes (as does Dublin Core) and supplies additional authorities, some of which are specific to Public Broadcasting applications.

• derivation from Dublin Core Metadata Registry

• PBCore maintains a robust list of description types, many of which are unique to media production and Public Broadcasting applications. Two of the suggested 22 *descriptionType* terms are refinements derived from Dubin Core...
  • abstract
  • tableOfContents

• Although Dublin Core uses the word "genre" in its definition of *type*, it must not be confused with PBCore's element *genre* that has a completely different definition and usage more closely aligned with program keywords found in program guides and TiVo-like applications.

• the types of relations defined in PBCore parallel those of Dublin Core's *relation* element...
  • Has Format
    NOTE: PBCore prefers to repeat the container for *pbcoreInstantiation* to catalog a different format or rendition of exactly the same intellectual content. PBCore is able to accommodate multiple renditions of an item within a single metadata record. Dublin Core requires that each rendition or format receives its own unique metadata record with rendundant intellectual content and property descriptions.
  • Is Format Of
  • Has Part
  • Is Part Of
  • Has Version
  • Is Version Of
  • References
  • Is Referenced By
  • Replaces
  • Is Replaced By
  • Requires
  • Is Required By

• equivalent to the Dublin Core element *relation* in which related resources are identified by text and/or number strings derived from specific identification systems.

• In following a "container architecture" in its metadata dictionary and schema, PBCore reconfigures the Dublin Core coverage elements of *spatial* and *temporal* into a single element that carries the descriptive data. An associated element called *coverageType* identifies the kind of descriptive data, i.e., *spatial* or *temporal*.
• If both *spatial* and *temporal* coverage descriptions exist, PBCore repeats the *pbcoreCoverage* container.

• PBCore's *coverageTypes* parallel those found in Dublin Core...
  • Spatial
  • Temporal

• PBCore parallels the definition of the Dublin Core element *audience* in that it identifies for whom a media item is intended or useful.
• A refinement to Dublin Core's *audience* is *Education Level* in which a description is made of the educational or training context. A specific statement of the location of the audience in terms of its progression through an education or training context can be used.
• PBCore uses a picklist of terms derived from the Library of Congress vocabulary for educational sectors. Thus PBCore's *audienceLevel* could map to Dublin Core's *Audience Education Level*.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *audienceRating* (which parallel those of the FCC V-Chip codes and the MPAA ratings) can be mapped to the Dublin Core element *audience* as another indicator for whom a media item is intended or useful.

This Content Class contains metadata elements related to the creation, creators, usage, permissions, constraints, and use obligations associated with a media asset or resource.

There are 4 containers and a total of 7 elements in the Intellectual Property grouping.

• derivation from Dublin Core Metadata Registry

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *creatorRole* can be mapped to the Dublin Core element *creator* as another indicator or attribution to the individual or group responsible for the intellectual content of a media item.

• derivation from Dublin Core Metadata Registry

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *contributorRole* can be mapped to the Dublin Core element *contributor* as another indicator or attribution to the individual or group responsible for the intellectual content of a media item.

• derivation from Dublin Core Metadata Registry

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *publisherRole* can be mapped to the Dublin Core element *publisher* as another indicator or attribution to the individual or group responsible for the publication or distribution of a media item.

rights
date copyrighted
provenance
rights holder
license

• derivation from Dublin Core Metadata Registry
• Dublin Core maintains a separate element for the date of copyright for a media item--*date copyrighted*. PBCore does not; however that information can be entered into *rightsSummary*.
• Dublin Core maintains a separate element for the ownership or custody of a media item--*provenance*. It could be argued that such information is entered into PBCore's *rightsSummary*.
• Dublin Core maintains a separate element to designate the person or organization owning or managing rights over a media item--*rights holder*. It could be argued that such information is entered into PBCore's *rightsSummary*.
• Dublin Core maintains a separate element to identify legal documentation for usage permissions over a media item--*license*. It could be argued that such information is entered into PBCore's *rightsSummary*.

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.

There is a single parent container, with 3 sub-containers, and a total of 28 elements in the Instantiation & Formats grouping. For each new instantiation or format for a media asset/title, the entire parent container can be repeated.

• PBCore's *dateCreated* parallels the definition of Dublin Core's refinement *created* to the element *date*.
• PBCore does not restrict the data entry for temporal designations to a specific scheme, such as the W3CDTF profile of ISO 8601, although their syntax for entering dates (year month day) is recommended.

• PBCore's *dateIssued* parallels the definition of Dublin Core's refinement *issued* to the element *date*.
• PBCore does not restrict the data entry for temporal designations to a specific scheme, such as the W3CDTF profile of ISO 8601, although their syntax for entering dates (year month day) is recommended.

• PBCore separates the designation of the format for a media item into *formatPhysical* and *formatDigital* elements.
• Dublin Core uses the refinement *medium* of the element *format* to identify the material or physical carrier of the resource.

• PBCore separates the designation of the format for a media item into *formatPhysical* and *formatDigital* elements.
• The picklist of MIME types that PBCore uses for *formatDigital* parallels how Dublin Core uses the element *format*.

• PBCore offers a picklist of media types that parallels the picklist used by Dublin Core in its element *type*.
• Dublin Core uses its *format* element to describe file formats, physical media, and dimensions of a media item.
• Although Dublin Core uses the word "genre" in its definition of *type*, it must not be confused with PBCore's element *genre* that has a completely different definition and usage more closely aligned with program keywords found in program guides and TiVo-like applications.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatGenerations* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Could be argued that PBCore's definition of *formatStandard* is a near equivalent to Dublin Core's type of *relation* identified as *conformsTo*.
• In Dublin Core, *conformsTo* is defined as "A reference to an established standard to which the resource conforms."

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatEncoding* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatDataRate* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatBitDepth* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatSamplingRate* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• In Dublin Core, *extent* can be used to identify a broad range of characteristics of a media item, including "the size or duration of the resource."
• It could be argued that the *frameSize* defined in PBCore can map to Dublin Core's *extent*.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatAspectRatio* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatFrameRate* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatColors* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatTracks* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• Following the principle of "mapping down" or "dummy down," the PBCore terms for *formatChannelConfiguration* can be mapped to the Dublin Core element *format* as another indicator of the file format, physical medium, or dimensions of a media item.

• derivation from Dublin Core Metadata Registry

• Dublin Core combines the start and end dates for the availability of a media item into a single date-related element *available*.
• Dublin Core accommodates a date range for *available*.
• PBCore preferred to separate possible start and end dates in order to facilitate better searching criteria often needed in Public Broadcasting.

• Dublin Core combines the start and end dates for the availability of a media item into a single date-related element *available*.
• Dublin Core accommodates a date range for *available*.
• PBCore preferred to separate possible start and end dates in order to facilitate better searching criteria often needed in Public Broadcasting.

• Dublin Core defines its element *identifier* with regard to a unique designation for a media item itself, and not an identifier for a entire metadata record associated with a media item and all of its descriptions, formats, renditions, and instantitions.
• PBCore's *formatIdentifier* parallels the definition and usage of Dublin Core's *identifier*.

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.

There is a single container and a total of 2 elements as a starter kit for the addition of metadata extensions to the PBCore.