• DAM Record #YNK457-5678-23467
• Catalog #F1678.52
• KUED-TV Database File 14-5; Record 1904
• Excel Document Archives_3000-3999.xls; Entry A:3245
• Program ID number for PRSS catalog
• 
• More Metadata Examples

Another descriptor named formatIdentifier is used to reference or identify a particular rendition/instantiation of a media item.

Best practice is to identify the resource by means of a string or number corresponding to an established or formal identification system generated within an international standard or as a local identification scheme. If using a digital asset management system, media asset management system, or content management system, the identfier is often automatically assigned by the system once an entry or record is created. The key is that the identifier always be unique. PBcore recommends the use of the companion descriptor, identifierSource, to indicate who assigned a particular identification number or designation. Thus PBCore provides not only a locator number, but also indicates an agency or institution who assigned it.

• Smith, Jedidiah
• Minnesota Public Radio
• KUED-TV
• Wisconsin Public Television. Extension Division
• Central Intelligence Agency
• State of Utah. Film Commission
• University of Utah. Department of Communication
• Prostate Cancer Awareness Project
• White Mountain Films
• Simpson, Lisa, Ph.D.
• More Metadata Examples

The descriptor identifierSource is used in combination with the unambiguous reference or identifier for a media item found in the descriptor identifier. Thus PBCore provides not only a locator number, but also an agency or institution who assigned it. Both exist at the top level for a PBCore description and its associated description document (XML).

Another element named formatIdentfierSource is used in combination with the element formatIdentifier to reference or identify a particular rendition/instantiation for a media item.

Use an authority file to determine how to properly enter names and organizations. In general, PBCore recommends the following rules:

FOR PERSONAL NAMES: Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES: Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group.
• If a particular subdivision of an organization is intended, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by , then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core.

• Geography of Utah, The
• National Parks in the State of Utah
• Delicate Arch Olympic Flame Ceremony
• American Experience
• Frontline
• Day in the Life of Alan Smithee, A
• More Metadata Examples

PBCore encourages producers, stations, and catalogers to assign titles to items by using more of a natural language grammar (English language) that is understandable in what is often called a "human readable form" (as opposed to "machine readable"). PBCore recommends that you:

• Assign a title that is distinctive, authoritative, descriptive, accurate, and consistent.
• Don't use leading articles, e.g., A, An, The. Place leading articles at the end of a title using the convention of a comma followed by a space and then the leading article.
• Use upper and lower case.
• Use punctuation as needed.

Titles are typically "proper" or "given" titles supplied by the original creator of a media item. However, there are situations in which no proper or given title is available, e.g., photographs or segments harvested from a longer work or program. In these situations a "supplied title" must be invented and used to name the media item. In creating a "supplied title," be considerate of and sensitive to the end user who is attempting to search for your media item. After all, you do want others to successfully discovery and retrieve information about your media item. Don't be vague or nondescript.

Because a title for an item may be associated with or related to a series, an episode, an excerpted segment, or even an alternative title in a different language, use the companion descriptor titleType to indicate the type of title you are assigning to a media item.

• Project
• Series
• Program
• Episode
• Segment
• Alternative
• Pledge Version
• More Metadata Examples

Select from a PBCore aggregated picklist of recommended vocabulary terms.

Because a title for a media item may be associated with or related to a series, an episode, an excerpted segment, or even an alternative title in a different language, use the descriptor titleType to indicate the type of title you are assigning to a media item. 

• Where the original item is in a foreign language and a translated version is easier to search
• To spell out numbers appearing in the first five words of a title
• To express a shorter title where the original, proper title includes an author or creator's name
• For commonly used titles which differ from the official, proper title

Specific examples of Alternative Titles include:

• Utah Geography
  [where the proper TITLE is actually "The Geography of Utah")
• The Geography of Utah. Program 16
  [where the proper TITLE is actually "National Parks in the State of Utah"]
• Twelve Monkeys
  [where the proper TITLE is actually "12 Monkeys"]
• The Boat
  [where the original, proper German film TITLE is "Das Boot"]
• Farnsworth
  [where the original TITLE is "American Experience. Big Dream, Small Screen"]
• Dark Sun
  [where the original TITLE is "American Experience. Race for the Superbomb"]
• Ascent of Man
  [where the original TITLE is "Jacob Bronowski's Ascent of Man"]

• National Parks. Natural Bridges. Delicate Arch. Arches National Park. Grand County. Utah.
• Afro-American artists - Boston - Massachusetts
• Afro-American authors
• United States - Relations - Cuba
• United States - History
• More Metadata Examples

PBCore does not dictate a single subject authority or classification scheme from which to select keywords, topics, and terms. However, if subjects are assigned to a media item and the terms used are derived from a specific authority or classification scheme, use the companion descriptor subjectAuthorityUsed to identify whose vocabularies and terms are being used.

PBS PODS: PROGRAM OFFER DATA SERVICE
METADATA DICTIONARY SUBJECT TERMS...
PBCore can recommend the use of the PBS TOPIC KEYWORD TABLE used in the Public Broadcasting Service's Program Offer Data Service: PODS. The PBS staff developed the Topic Keyword List in the late 1980s to support the Program Database (PDB), a system for managing production, content, rights and funding metadata about PBS programs. The list was compiled using a variety of internal sources, most notably a glossary used to code PBS programs with public interest categories for the production of FCC ascertainment reports sent to public television stations. This rich list has been updated regularly over the years to reflect new content areas and is maintained using the Broadview traffic and program management system, which replaced the PDB in April, 2006 at PBS. To view the actual vocabulary list, use this link (no password or login authentication is required)...
https://secure.connect.pbs.org/pbsdocuments/pbs/PBCore/

ID3 PSD...
In the realm of the radio medium, the PRI PSD Consortium (Public Radio International's Program Service Data) has released its "Recommended Field Descriptions for Program Service Data" in public radio programming. The tags are based on ID3 which is a very popular audio file data tagging format in active use by software and hardware developers around the world. ID3 tags are supported in software such as iTunes, Windows Media Player (with Microsoft proprietary modifications), WinAmp, YME, MusicMatch and hardware players like the iPod, Creative Zen, Toshiba Gigabeat and Sony Walkman. In HD radio, the PSD information is embedded in transmitted audio files and can be displayed on radios with text screens. Artist names, Song title, Year, and Genre are common tags. The ID3 Genre tag contains a comprehensive list of terms used to describe music types and can be used as a source of vocabulary when describing the subject of music media items. The numbers associated with the genre tags are the actual numeric codes carried in the ID3 data stream that are then decoded into human-readable form.
http://www.mpx.cz/mp3manager/tags.htm

NAMES...
If the subject is a person's name or the name of an organization or company, PBCore recommends using the form, structure, and grammar found in the AACR2 Cataloging Rules (Anglo-American Cataloging Rules, 2nd edition) for names.
http://www.aacr2.org/

FOR PERSONAL NAMES: Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES: Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group.
• If a particular subdivision of an organization is intended , identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

If you are entering free-form text descriptions for a media item, don't use the descriptor subject for this purpose. Instead, use another PBCore element called description.

If you have the interest or expertise to exploit third party subject authorities (such as PBS PODS and PRI ID3 PDS), below are listed a small sample of different subject authorities that may be appropriate for study and use.

PBS PODS: Program Offer Data Service Metadata Dictionary
Subject Terms
https://secure.connect.pbs.org/pbsdocuments/pbs/PBCore/

PRI ID3 PDS: Public Radio International Consortium ID3 Program Data Service
Music Genre Tags
http://psd.publicbroadcasting.net
http://www.mpx.cz/mp3manager/tags.htm

World Wide Web Consortium Thesauri and Controlled Vocabularies Available for the Choice of Controlled Subject Terms
http://www.lub.lu.se/metadata/subject-help.html

Library of Congress Authorities http://authorities.loc.gov/
http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html
http://authorities.loc.gov/cgi-bin/Pwebrecon.cgi?DB=local&PAGE=First
http://authorities.loc.gov/help/subj-auth.htm

DDC: Dewey Decimal Classification
http://www.oclc.org/dewey/index.htm

IPTC: International Press Telecommunications Council
http://www.iptc.org/pages/index.php
http://www.iptc.org/metadata/

GEM: Gateway to Educational Materials
ASN-Achievement Standards Network
Subject/Topic Vocabulary
http://www.thegateway.org
ASN Subject/Topic Vocabulary List

HEAL: Health Education Assets Library
http://www.healcentral.org
HEAL Metadata Schema

Getty Art & Architecture Thesaurus
http://www.getty.edu/research/conducting_research/vocabularies/aat/

• https://secure.connect.pbs.org/pbsdocuments/pbs/PBCore/#keyword
• http://www.lub.lu.se/metadata/subject-help.html
• http://www.iptc.org/metadata/
• http://www.thegateway.org/about/asn-documentation/asn-controlled-vocabularies/asn-topic-vocabulary/
• http://www.nlm.nih.gov/mesh/meshhome.html
• http://www.healcentral.org/services/servicesMetadataSchema.jsp
• More Metadata Examples

PBCore does not dictate a single authority from which to review and select keywords, topics and terms. Dozens of authorities, schemes, and vocabularies have been developed. Some are useful for assigning general keywords. Others are highly specific to certain disciplines, fields of study, and industries. If a particular authority is used, identify it.

Use a URL where possible or practical. If the authority is identified by a personal name or corporporate/organizational name, PBCore recommends the following rules to specify the authority:

FOR PERSONAL NAMES: Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES: Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group.
• If a particular subdivision of an organization is intended, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

If you are entering free-form text descriptions for a media item, don't use the descriptor subject for this purpose. Instead, use another PBCore element called description.

If you have the interest or expertise to exploit third party subject authorities (such as PBS PODS and PRI ID3 PDS), below are listed a small sample of different subject authorities that may be appropriate for study and use.

PBS PODS: Program Offer Data Service Metadata Dictionary
Subject Terms
PBCore can recommend the use of the PBS TOPIC KEYWORD TABLE used in the Public Broadcasting Service's Program Offer Data Service: PODS. The PBS staff developed the Topic Keyword List in the late 1980s to support the Program Database (PDB), a system for managing production, content, rights and funding metadata about PBS programs. The list was compiled using a variety of internal sources, most notably a glossary used to code PBS programs with public interest categories for the production of FCC ascertainment reports sent to public television stations. This rich list has been updated regularly over the years to reflect new content areas and is maintained using the Broadview traffic and program management system, which replaced the PDB in April, 2006 at PBS. To view the actual vocabulary list, use this link (no password or login authentication is required)...
https://secure.connect.pbs.org/pbsdocuments/pbs/PBCore/#keyword

PRI ID3 PDS: Public Radio International Consortium ID3 Program Data Service
Music Genre Tags
In the realm of the radio medium, the PRI PSD Consortium (Public Radio International's Program Service Data) has released its "Recommended Field Descriptions for Program Service Data" in public radio programming. The tags are based on ID3 which is a very popular audio file data tagging format in active use by software and hardware developers around the world. ID3 tags are supported in software such as iTunes, Windows Media Player (with Microsoft proprietary modifications), WinAmp, YME, MusicMatch and hardware players like the iPod, Creative Zen, Toshiba Gigabeat and Sony Walkman. In HD radio, the PSD information is embedded in transmitted audio files and can be displayed on radios with text screens. Artist names, Song title, Year, and Genre are common tags. The ID3 Genre tag contains a comprehensive list of terms used to describe music types and can be used as a source of vocabulary when describing the subject of music media items. The numbers associated with the genre tags are the actual numeric codes carried in the ID3 data stream that are then decoded into human-readable form.
http://psd.publicbroadcasting.net
http://www.mpx.cz/mp3manager/tags.htm

World Wide Web Consortium Thesauri and Controlled Vocabularies Available for the Choice of Controlled Subject Terms
http://www.lub.lu.se/metadata/subject-help.html

Library of Congress Authorities http://authorities.loc.gov/
http://lcweb.loc.gov/catdir/cpso/lcco/lcco.html
http://authorities.loc.gov/cgi-bin/Pwebrecon.cgi?DB=local&PAGE=First
http://authorities.loc.gov/help/subj-auth.htm

DDC: Dewey Decimal Classification
http://www.oclc.org/dewey/index.htm

IPTC: International Press Telecommunications Council
http://www.iptc.org/pages/index.php
http://www.iptc.org/metadata/

GEM: Gateway to Educational Materials
ASN-Achievement Standards Network
Subject/Topic Vocabulary
http://www.thegateway.org
ASN Subject/Topic Vocabulary List

HEAL: Health Education Assets Library
http://www.healcentral.org
HEAL Metadata Schema

Getty Art & Architecture Thesaurus
http://www.getty.edu/research/conducting_research/vocabularies/aat

• Narrated by Ken Burns.
• Recorded from the live web broadcast 2000-01-28.
• An animated tutorial on School, Parent & Community Involvement in Pupil Development.
• In this film, a gangster, a 7-year-old, an astronomer and other real life characters ponder, among other topics: creation, identity, sex, crime, madness, and love.
• Program Eighteen of the Geography of Utah series is a video tour of Utah's spectacular national parks and recreation areas. Zion National Park, Bryce National Park, Capitol Reef, Canyonlands, Arches National Park, Flaming Gorge National Recreation Area, Dinosaur National Monument, and the Glen Canyon National Recreation Area are all visited. The controversy of land use and environmental preservation is considered in interviews with San Juan County Commissioner Cal Black and Benjamin Zerbey of the National Park Service. Rainbow Bridge National Monument and Canyonlands National Park are only two examples of the land use debate.
• The Museum Without Walls Billboard Art Project was first conceived by Professor Roger Des Rosiers, Chairman of the Department of Art at the University of Utah in the early 1970s. The idea was to invite twenty-one Utah Artists to participate in the exhibition of their works on existing outdoor billboards in the Salt Lake Valley. Called "Museum Without Walls" by Lukman Glasgow, Project Director, he stated that "such works of art in an outdoor setting must compete with the whole environment." Further, "It was an experiment with public art works designed to be understood by a much broader and more general art audience than is normal to the museum or gallery environment. Such a project then should be seen, hopefully, as a beginning and not simply an isolated event. Too long have the works of contemporary artists been regarded as a set of experiences for the eyes of only small or even elitist groups. Therefore, 'public art,' because it properly speaks to a majority in our society, is perhaps the most vital art movement occurring today."
• 01;23;14;10 - 01;30;15;29 Introduction
  01;30;16;00 - 01;34;18;05 The Meaning of Life
  01;34;18;06 - 01;40;00;00 The Meaning of Work
  01;40;00;01 - 01;45;20;00 The Meaning of Play
  01;45;20;01 - 01;50;16;13 Conclusions
• Segment 1: Introduction of guests (03:00)
  Segment 2: Two-minute remarks by individual guests (10:00)
  Segment 3: Q&A between commentator and guests (15:00)
  Segment 4: Audience questions (15:00)
  Segment 5: Summary comments by guests (10:00)
  Segment 6: Closing (02:00)
• More Metadata Examples

Use natural language to enter descriptions. Specialized descriptions, such as rundowns and edit decision lists, should conform to the standards used by your industry or community.

Use the metadata element description for general notes, abstracts, or summaries about a media item, including text and words that are not found in the more highly structured and authority controlled descriptor subject. Use description for general purposes.

The information may be in the form of a paragraph giving an individual program description, anecdotal interpretations, or brief content reviews. The description may also consist of outlines, lists, bullet points, rundowns, edit decision lists, indexes, tables of content, or even content flags for questionable material or language. Specialized descriptions, such as rundowns, segment sequencing, and edit decision lists, should conform to any standards used by your industry or community.

If the description is a highly complicated index or a lengthy transcript, it is best not to insert so much text into a database field. Instead, generate a separate, stand-alone document. If the stand-alone document has exactly the same "intellectual content" descriptions as the seminal media item, then the stand-alone document could be entered as a separate rendition of the original where the pbcoreInstantiation container is repeated. For example, a video program and its companion transcript have the same intellectual descriptions and could be catalogued as a single metadata record, with two instantiations/formats.

Under other circumstances, where the "intellectual content" is different for two associated media items, use the pbcoreRelation container and its metadata elements to establish the relationship between the two linked assets and their separate metadata records.

• Abstract
• Package
• Project
• Collection
• Series
• Episode
• Program
• Segment
• Clip
• Selection or Excerpt
• Segment Sequence
• Table of Contents
• Segment Sequence
• Rundown
• Playlist
• Script
• Transcript
• Descriptive Audio
• PODS
• PSD
• Anecdotal Comments & Reflections
• Listing Services
• Content Flags
• More Metadata Examples

Select from a PBCore picklist of recommended vocabulary terms.

The element descriptionType contains identifiers or flags to indicate what type of information is entered in the companion metadata field description. Below is a brief explanation of each of the terms used in the recommended picklist. Although some have very similar meanings, different terms are included to appeal to practices in different industries and organizations.

"Abstract"
If you are earmarking a description as an "Abstract," then the narrative entered in the metadata element description contains a narrative review, an individual program description, or some other summary indication of the program's content.

"Package"
If you are earmarking a description as a "Package," then the narrative entered in the metadata element description is relative to an entire array of media items, ancillary materials, promotional materials, previews, or educational materials that are bound together into a single packaged offering.

"Project"
If you are earmarking a description as a "Project," then the narrative entered in the metadata element description is relative to the combined resources specific to a defined project or initiative.

"Collection"
If you are earmarking a description as a "Collection," then the narrative entered in the metadata element description is relative to the related media items that together constitute a collected works or standalone aggregation of materials

"Series"
If you are earmarking a description as a "Series," then the narrative entered in the metadata element description is relative to an overview of all the combined episodes found within that series.

"Episode"
If you are earmarking a description as an "Episode," then the narrative entered in the metadata element description is relative to a specific episode or program that is part of a larger series of related program or media items.

"Program"
If you are earmarking a description as a "Program," then the narrative entered in the metadata element description is relative to a specific, standalone media item that is not part of any series or collection of related items.

"Segment"
If you are earmarking a description as a "Segment," then the narrative entered in the metadata element description is relative to a specific, logical chapter or self-contained sequence with a discernable beginning, middle, and end for its intellectual content. In describing a sequence of stand-alone segments, use the descriptionType "Segment Sequence."

"Clip"
If you are earmarking a description as a "Clip," then the narrative entered in the metadata element description is relative to a portion of a larger media item. Clip is a term with specific meaning and semantic importance for video and audio materials, especially when used in editing.

"Selection or Excerpt"
If you are earmarking a description as a "Selection or Excerpt ," then the narrative entered in the metadata element description is relative to a small extraction of material from a larger media item. Selections and Excerpts are typically smaller in scope than Segments or Clips, and are intended to represent a snippet of content.

"Table of Contents"
If you are earmarking a description as a "Table of Contents," then the narrative entered in the metadata element description contains some sort of outline or sequential list of headings identifying a representative name for chunks of content found within a media item. If the scope of the Table of Contents is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text) and catalog it as another instantiation of the original asset.

"Segment Sequence "
If you are earmarking a description as a "Segment Sequence," then the narrative or index entered in the metadata element description displays each of the stand-alone segments or parts, possibly identifying them by order, name or title, time stamp, and an individual segment description. If the scope of the Segment Sequence is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text)and catalog it as another instantiation of the original asset. 

"Rundown"
If you are earmarking a description as a "Rundown," then the narrative entered in the metadata element description contains a time sequence of discernable and distinct portions of a total media item's content. If the scope of the Rundown is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text) and catalog it as another instantiation of the original asset.

"Playlist"
If you are earmarking a description as a "Playlist," then the narrative entered in the metadata element description contains an organized compilation of separate media items assembled into a coherent presentation with related intellectual content. If the scope of the Playlist is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text) and catalog it as another instantiation of the original asset.

"Script"
If you are earmarking a description as a "Script," then the narrative entered in the metadata element description contains the original script for a media item. The metadata field description is likely to contain script material for very short duration media items, since databases on which MAM, DAM or CMS systems are implemented often limit the total number of characters allowed within a metadata field (typically no more than 4000 characters). If the Script is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text) and catalog it as another instantiation of the original asset.

"Transcript"
If you are earmarking a description as a "Transcript," then the narrative entered in the metadata element description contains a verbatim transcript for a media item. The metadata field description is likely to contain transcript material for very short duration media items, since databases on which MAM, DAM or CMS systems are implemented often limit the total number of characters allowed within a metadata field (typically no more than 4000 characters). If the Transcript is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text) and catalog it as another instantiation of the original asset.

"Descriptive Audio"
If you are earmarking a description as a "Descriptive Audio," then the narrative entered in the metadata element description contains specialized audio descriptions of screen activity and locations for a visual media item. The metadata field description is likely to contain descriptive audio material for very short duration media items, since databases on which MAM, DAM or CMS systems are implemented often limit the total number of characters allowed within a metadata field (typically no more than 4000 characters). If the Transcript is lengthy, consider generating a separate stand-alone media item (e.g., PDF or Text) and catalog it as another instantiation of the original asset.

"PODS"
If you are earmarking a description as "PODS," then the narrative entered in the metadata element description is relative to program information provided by PBS (Public Broadcasting Service) to its constituents in its Program Offer Data Service.

"PSD"
If you are earmarking a description as "PSD," then the narrative entered in the metadata element description is relative to the information provided by NPR (National Public Radio) to its constituents in its Program Service Data. [Each audio stream in an HD Radio multicast has a companion data stream which contains Program Service Data (PSD), often referred to as Program Associated Data (PAD), intended to describe or complement the audio program being heard by the listener.]

"Anecdotal Comments & Reflections "
If you are earmarking a description as "Anecdotal Comments & Reflections," then the narrative entered in the metadata element description contains additional remarks and opinions about a media item that are less suited to a formal "individual program description" but appropriate for enhancing the understanding of the nature, focus, and intent behind the intellectual content for a media item.

"Listing Services"
A full, rich program description is often offered on websites, viewer guides, and other promotional materials. However, the Listing Services and online electronic viewer guides use very abbreviated program descriptions, in addition to Genre tags, Date Created, and hosts/actors. The picklist for descriptionType includes the option "Listing Services" in order to identify the special, highly edited, short descriptions that are expected in program guides and schedules.

"Content Flags "
If you are earmarking a description as "Content Flags," then the narrative entered in the metadata element description identifies (by description and/or timestamps) content of a questionable (or for some communities, offensive and objectionable) nature or language.

"Other"
An "Other" option is provided to accommodate other types of descriptions that PBCore cannot envision at this time or that is required by another organization or community.

• Adventure
• Children
• Collectibles
• Cooking
• Talk
• Aerobics
• Speed skating
• Olympics
• Aviation
• Holiday-special
• More Metadata Examples

• Minnesota Public Radio
• PBCore v1.1
  http://www.pbcore.org
• Public Broadcasting Service
  PODS Program Offer Data Service Metadata Dictionary
• Central Intelligence Agency
• State of Utah. Film Commission
• University of Utah. Marriott Library Digital Collections
• More Metadata Examples

PBCore supplies its own picklist of terms that are alligned with TiVo, the Tribune Media tags, and the PBS Program Offer Data Service (PODS).

If another picklist is employed, it is important that its authority be identified by using this metadata field.

Use a URL where possible or practical when identifying the genre authority used. If the authority is identified by a personal name or corporporate/organizational name, PBCore recommends the following rules to specify the authority:

FOR PERSONAL NAMES: Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES: Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group.
• If a particular subdivision of an organization is intended, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

• Has Format
• 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
• More Metadata Examples

The descriptor relationType identifies 12 ways in which the media item you are cataloguing is related by intellectual content to some other media item. For most information and digital asset management systems, the related item is its own asset and retains its own separate metadata record.

The distinguishing question to ask yourself is...

"Does this related media item share exactly the same intellectual content descriptions and intellectual property terms as the original media item?"

If the answer is "yes," then create a single PBCore metadata record, but repeat the container pbcoreInstantiation to indicate the existence of a different rendition of the same asset (e.g., a QuickTime and a WindowsMedia digital movie file; or a Beta-SP tape and a PDF transcript of the same program).

If the answer is "no," and the two media items are linked to one another, but do not share the same intellectual content and intellectual property descriptions, generate two separate PBCore metadata records. Document that the two media items and their metadata records are related by using the PBCore elements relationType and relationIdentifier.  

Once the type of relationship is identified, then the companion descriptor relationIdentifier is used to provide a name, locator, accession, identification number or ID where a related item can be obtained or found.

The bond between the media item you are cataloging and its related media item is selected from this list of 12 types:

"Has Format"
Used to indicate if the media item you are cataloging exists in another format, elsewhere. For example, your media item may be an interview segment, but it exists in another format, such as a documentary. Format, in this context, refers to the intellectual content and not another tape format or different rendition of a digital file. Use the "format" descriptors in the PBCore container pbcoreInstantiation to identify media format variations or renditions, repeating the container multiple times, as needed.

"Is Format Of"
Used to indicate if the media item you are cataloging is a variation on the format of another media item, but with essentially the same intellectual content. Format, in this context, refers to the intellectual content and not another tape format or variation on a digital file. Use the "format" descriptors in the PBCore container pbcoreInstantiation to identify media format variations or renditions, repeating the container multiple times, as needed.

"Has Part"
Used to indicate if the media item you are cataloging has a companion media item that is a subset or smaller part of your item.

"Is Part Of"
Used to indicated if the media item you are cataloging is a subset or part of another media item. For example, your program may be part of a larger series.

"Has Version"
Used to indicate if the media item you are cataloging has a version, edition, or adaptation named elsewhere. Version, in this context, refers to the intellectual content and not a variation on tape format or digital file. Use the "format" descriptors in the PBCore container pbcoreInstantiation to identify media format variations or renditions, repeating the container multiple times, as needed.

"Is Version Of"
Used to indicate if the media item you are cataloging is a version, edition, or adaptation of another media item. Changes in version imply substantive changes in content rather than differences in format.

"References"
Used to indicate if the media item you are cataloging cites or otherwise points to another media item you are referencing.

"Is Referenced By"
Used to indicate if the media item you are cataloging is referenced, cited, or otherwise pointed to by another media item.

"Replaces"
Used to indicate if the media item you are cataloging supplants, displaces, or supersedes another media item.

"Is Replaced By"
Used to indicate if the media item you are cataloging is supplanted, displaced, or superseded by another media item.

"Requires"
Used to indicate if the media item you are cataloging requires a companion media item to support its function, delivery, or coherence of content.

"Is Required By"
Used to indicate if the media item you are cataloging is required by a companion media item, either physically or logically.

• /public/items/PBCore_DC03PaperFinal.pdf
• Room 217: Section C: Shelf 5
• ISBN 0-07-135026-8
• Program ID number for PRSS catalog
• 
• Accession Number
• From the series Geography of Utah
  
• More Metadata Examples

Use free-text for data entry.

Based on the Type of Relation that is specified in the descriptor relationType, an associated and specific locator, accession, or identification is designated by using relationIdentifier.

Use an authority file to determine how to properly enter names and organizations. In general, PBCore recommends the following rules for entering personal names and corporate or organizational names:

FOR PERSONAL NAMES: Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES: Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group.
• If a particular subdivision of an organization is intended, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

• Boston, MA
• The Great Basin
• Panguitch, Utah
• Geo-spatial Data (as available)
• Arches National Park. Delicate Arch. Grand County. Utah.
• 1995-1996
• 17th century
• 1984 ?
• US Civil War Era; 1861-1865
• Year:
  YYYY (eg 1997)
• Year and month:
  YYYY-MM (eg 1997-07)
• Complete date:
  YYYY-MM-DD (eg 1997-07-16)
• More Metadata Examples

Coverage in intellectual content may be expressed spatially by geographic location. Actual place names may be used. Numeric coordinates and geo-spatial data are also allowable, if useful or supplied.

Coverage in intellectual content may also be expressed temporally by a date, period, era, or time-based event.

The PBCore metadata element coverage houses the actual spatial or temporal keywords. The companion descriptor coverageType is used to identify the type of keywords that are being used.

Because the metadata element coverage can house both spatial and temporal keywords or descriptors, the refinements and encoding schemes are discussed separately below.

SPATIAL COVERAGE...
When the coverageType is identified as *spatial*, PBCore recommends you use free-form text to enter data. PBCore does not maintain its own authority file for geographic or place names. However, there are several resources you can employ to obtain well-formed geographic or spatial names:

USGS Geographic Names Information Services (GNIS)
Query the online database:
http://geonames.usgs.gov/pls/gnis/web_query.gnis_web_query_form

The Geographic Names Information System (GNIS), developed by the USGS in cooperation with the U.S. Board on Geographic Names (BGN), contains information about almost 2 million physical and cultural geographic features in the United States and its territories. The Federally recognized name of each feature described in the data base is identified, and references are made to a feature's location by State, county, and geographic coordinates. The GNIS is the official repository of domestic geographic names information for the United States and its territories.

United Nations Statistics Division of the Department of Economic and Social Affairs
Links to web sites relevant to geographical names standardization:
http://unstats.un.org/unsd/geoinfo/links.htm

TEMPORAL COVERAGE...
When the coverageType is identified as *temporal*, PBCore recommends you use free-form text to enter a date, period, era, or time-based event. Where and if appropriate, you may prefer to use the specific date/time encoding rules established in the ISO 8601 profile of the international standard for the representation of dates and times:ISO 8601 Profile. If the pure ISO 8601 Profile is too cumbersome or restrictive, you may prefer to employ the syntax it suggests for entering dates (e.g., YYYY-MM-DD). (http://www.w3.org/TR/NOTE-datetime)

In principle, PBCore's use of *coverage* is similar to that of Dublin Core. However, we do not define two separate metadata elements, one for coverageSpatial and one for coverageTemporal. Instead, PBCore allows for the repeatability of the container pbcoreCoverage, which itself houses the keywords for coverage and the designations for the type of coverage being expressed. Actual implementation of coverage is, as always, dependent on the information or digital asset management system being employed.

SPATIAL COVERAGE GUIDELINES... When entering place names, coordinates or geo-spatial data, care should be taken to provide consistent information that can be interpreted by end users attempting to search for media items. The descriptor coverage, when using spatial keywords and descriptions, implies physical boundaries and logical jurisdictions. and should be used in order to support more precise searching than possible with the information found in the descriptors title, subject or description. When applicable, utilize the standards based names found in the USGS and United Nations web sites noted above.

TEMPORAL COVERAGE GUIDELINES... When entering date and time data, care should be taken to provide consistent information that can be interpreted by end users attempting to search for media items. The descriptor coverage, when using temporal keywords and descriptions, implies temporal boundaries, and should be used to provide additional information that identifies the date/time period for the intellectual content of a media item you are cataloging. NOTE: temporal coverage must not be confused with copyright dates. Temporal coverage relates to the intellectual content of a media item. Copyright dates refer to ownerships and rights over the media item itself. If a date is approximate, add a question mark but separate the date from the question mark by a space so that the question mark is not interpreted as part of the date value by a search engine, e.g., 1972 ? .

This descriptor should be used in order to support more precise searching than possible with the information found in the descriptors title, subject or description.

Where and if appropriate, you may prefer to use the specific date/time encoding rules established in the ISO 8601 profile of the international standard for the representation of dates and times:
(http://www.w3.org/TR/NOTE-datetime).
If the pure ISO 8601 Profile is too cumbersome or restrictive, you may prefer to employ the syntax it suggests for entering dates (e.g., YYYY-MM-DD).

• Spatial
• Temporal
• More Metadata Examples

Whereas the PBCore metadata element coverage uses keywords and descriptors to identify a span of space or time that is expressed by the intellectual content of a media item, coverageType is used to identify the actual type of keywords that are being used. Coverage in intellectual content may be expressed spatially by geographic location. Coverage in intellectual content may also be expressed temporally by a date, period, era, or time-based event. coverageType provides a picklist of coverage types, namely *spatial* or *temporal*.

Best practice is to select from the provided picklist of terms for identifying the type of coverage as either *spatial* or *temporal*.

In principle, PBCore's use of *coverage* is similar to that of Dublin Core. However, we do not define two separate metadata elements, one for coverageSpatial and one for coverageTemporal. Instead, PBCore allows for the repeatability of the container pbcoreCoverage, which itself houses the keywords for coverage and the designations for the type of coverage being expressed. Actual implementation of coverage is, as always, dependent on the information or digital asset management system being employed.

SPATIAL COVERAGE GUIDELINES... When entering place names, coordinates or geo-spatial data in the companion metadata field coverage, care should be taken to provide consistent information that can be interpreted by end users attempting to search for media items. The descriptor coverage, when using spatial keywords and descriptions, implies physical boundaries and logical jurisdictions. and should be used in order to support more precise searching than possible with the information found in the descriptors title, subject or description. Select the term *spatial* when such keywords are used.

TEMPORAL COVERAGE GUIDELINES... When entering date and time data in the companion metadata field coverage, care should be taken to provide consistent information that can be interpreted by end users attempting to search for media items. The descriptor coverage, when using temporal keywords and descriptions, implies temporal boundaries, and should be used to provide additional information that identifies the date/time period for the intellectual content of a media item you are cataloging. NOTE: temporal coverage must not be confused with copyright dates. Temporal coverage relates to the intellectual content of a media item. Copyright dates refer to ownerships and rights over the media item itself. Select the term *temporal* when such keywords are used.

• K-12 (general)
• Pre-school (kindergarten)
• Primary (grades 1-6)
• Intermediate (grades 7-9)
• High School (grades 10-12)
• College
• Post Graduate
• General Education
• Educator
• Vocational
• Adult
• Special Audiences
• General
• Male
• Female
• Other
• More Metadata Examples

PBCore recommends a picklist using the Library of Congress groupings.

View LOC Educational Sectors - K-12 (general) Pre-school (kindergarten) Primary (grades 1-6) Intermediate (grades 7-9) High School (grades 10-12) College Post Graduate General Education Educator Vocational Adult Special Audiences General Male Female Other

The ability to designate the intended users of a media item is especially important when matching a program's usefulness to a specific age range, audience grouping, or educational level.

The television (FCC) and motion picture (MPAA) industries have crafted audience ratings. The PBCore picklist combines the two into a single list, although the presentation below is divided into two pulldown lists in order to associate each list with a referenced URL.

TV Parental Guidelines
http://www.fcc.gov/vchip/#guidelines
http://www.mpaa.org/tv/index.htm
https://secure.connect.pbs.org/pbsdocuments/pbs/PBCore/#Vchip

MPAA Movie Ratings
http://www.mpaa.org/movieratings/index.htm

PBCore recommends using the Federal Communications Commission (FCC) TV Parental Guidelines or the Motion Picture Association of American (MPAA) audience ratings system, depending on whether the resource is intended for broadcast or movie theatre presentation. Below are extended explanations of these audience ratings systems: 

TV PARENTAL GUIDELINES:
The FCC TV Parental Guidelines append one or more flags for fantasy violence (FV), violence (V), sexual situations (S), language (L), and suggestive dialogue (D) to seven broader categories that describe the appropriateness of program material for various audiences.

The picklist of terms for this PBCore element provides you with all the permutations of these flags when associated with the different audiences. Explanations of these audiences and the increasing severity of the flags (V,S,L,D,FV) are provided here.

The following categories apply to programs designed solely for children:

1. TV-Y All Children
   This program is designed to be appropriate for all children. Whether animated or live-action, the themes and elements in this program are specifically designed for a very young audience, including children from ages 2-6. This program is not expected to frighten younger children.
2. TV-Y7 Directed to Older Children
   This program is designed for children age 7 and above. It may be more appropriate for children who have acquired the developmental skills needed to distinguish between make-believe and reality. Themes and elements in this program may include mild fantasy violence or comedic violence, or may frighten children under the age of 7. Therefore, parents may wish to consider the suitability of this program for their very young children. Note: For those programs where fantasy violence may be more intense or more combative than other programs in this category, such programs will be designated TV-Y7-FV (fantasy violence).
   

The following categories apply to programs designed for the entire audience:

1. TV-G General Audience
   Most parents would find this program suitable for all ages. Although this rating does not signify a program designed specifically for children, most parents may let younger children watch this program unattended. It contains little or no violence, no strong language and little or no sexual dialogue or situations.
2. TV-PG Parental Guidance Suggested
   This program contains material that parents may find unsuitable for younger children. Many parents may want to watch it with their younger children. The theme itself may call for parental guidance and/or the program contains one or more of the following:
   (V) moderate violence
   (S) some sexual situations
   (L) infrequent coarse language
   (D) suggestive dialogue
3. TV-14 Parents Strongly Cautioned
   This program contains some material that many parents would find unsuitable for children under 14 years of age. Parents are strongly urged to exercise greater care in monitoring this program and are cautioned against letting children under the age of 14 watch unattended. This program contains one or more of the following:
   (V) intense violence
   (S) intense sexual situations
   (L) strong coarse language
   (D) intensely suggestive dialogue
4. TV-MA Mature Audience Only
   This program is specifically designed to be viewed by adults and therefore may be unsuitable for children under 17. This program contains one or more of the following:
   (V) graphic violence
   (S) explicit sexual activity
   (L) crude, indecent language
5. E No Rating

The value lists used by PBCore are structured in the same fashion as those used by the PBS PODS: Program Offer Data Service Metadata Dictionary. In the 1990s, the National Association of Broadcasters, the National Cable Television Association and the Motion Picture Association of America created the TV Parental Guidelines, a voluntary ratings system for television programs. Since 2000, the FCC has required that all TV sets 13 inches or larger contain a V-chip allowing parents to block the viewing of programs with specific ratings. The PBS VChip Table describes all possible permutations of the ratings and subratings defined by the TV parental Guidelines list. The list is made available from this special PBS webpage:
https://secure.connect.pbs.org/pbsdocuments/pbs/PBCore/#Vchip

1. G
   Intended for general audiences. All ages are admitted.
2. PG
   Parental guidance is suggested. Some material may not be suitable for children.
3. PG-13
   Parents strongly cautioned. Some materials may be inappropriate for children under 13.
4. R
   Restricted. Under 17 requires accompanying parent or adult guardian.
5. NC-17
   No one 17 and under admitted.
6. NR
   Not rated.

• Smith, Jedidiah
• Minnesota Public Radio
• KUED-TV
• Wisconsin Public Television. Extension Division
• Central Intelligence Agency
• State of Utah. Film Commission
• University of Utah. Department of Communication
• Prostate Cancer Awareness Project
• White Mountain Films
• Simpson, Lisa, Ph.D.
• More Metadata Examples

Use an authority file to determine how to properly enter names and organizations. For example,AACR2 Cataloging Rules (Anglo-American Cataloging Rules, 2nd edition) http://www.aacr2.org/
In general, PBCore recommends the following rules:

FOR PERSONAL NAMES:
Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES:
Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group who is considered the creator.
• If a particular subdivision of an organization is the actual creator, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

FOR CREATOR ROLES:
To identify the specific role associated with a creator, use the companion descriptor creatorRole. To identify other important people or groups who contributed to the creation of a media item, use the descriptors contributor and contributorRole.

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

• Artist
• Associate Producer
• Cinematographer
• Composer
• Co-Producer
• Creator
• Director
• Editor
• Essayist
• Executive Producer
• Host
• Illustrator
• Interviewer
• Moderator
• Photographer
• Producer
• Production Unit
• Reporter
• Writer
  -
• Other
• More Metadata Examples

Unlike print resources, there is usually no single role, like an author, who has primary responsibility for the creation of media items such as audio, video, film assets, and their digital renditions. For these media, creators can fill many different roles, such as the instructor for a video course, the interviewee from a video history program, or the director of a program or film (if they are identified as the primary creator for a media item).

Select from a picklist of creator roles.

For a creator, identify the role played by that person or organization. Preference is to use a pre-defined list of creator roles rather than entering informal, free-form text. To identify other important people or groups who contributed to the creation of a media item, use the descriptors contributor and contributorRole.

• Smith, Jedidiah
• Minnesota Public Radio
• KUED-TV
• Wisconsin Public Television. Extension Division
• Central Intelligence Agency
• State of Utah. Film Commission
• University of Utah. Department of Communication
• Prostate Cancer Awareness Project
• White Mountain Films
• Simpson, Lisa, Ph.D.
• More Metadata Examples

Use an authority file to determine how to properly enter names and organizations. For example,AACR2 Cataloging Rules (Anglo-American Cataloging Rules, 2nd edition) http://www.aacr2.org/
In general, PBCore recommends the following rules:

FOR PERSONAL NAMES:
Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES:
Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group who is considered the contributor.
• If a particular subdivision of an organization is the actual contributor, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

FOR CREATOR ROLES:
To identify the specific role associated with a contributor, use the companion descriptor contributorRole.

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

• Commentator
• Conductor
• Writer
• Narrator
• Host
• Funder
• Production Engineering
• More Metadata Examples

Select from a picklist of contributor roles.
    

For a contributor, specify the role played by that person or organization. Preference is to use a pre-defined list of contributor roles rather than entering informal, free-form text. Novel entries may be justified, however. If not identified elsewhere, use this descriptor to identify important production credits for a resource, e.g., producer, director, writer, special thanks, funding agencies, programmers, designers, graphics, instructional design, etc.

• University of Utah Press
• Minnesota Public Radio
• KUED-TV
• Wisconsin Public Television. Extension Division
• University of Utah. Department of Communication
• State of Utah. Film Commission
• Prostate Cancer Awareness Project
• White Mountain Films
• More Metadata Examples

Use an authority file to determine how to properly enter names and organizations, e.g., AACR2 Cataloging Rules (Anglo-American Cataloging Rules, 2nd edition)
http://www.aacr2.org/. In general, PBCore recommends the following rules:

FOR PERSONAL NAMES:
Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES:
Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group who is considered the publisher.
• If a particular subdivision of an organization is the actual publisher, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

FOR PUBLISHER ROLES:
To identify the specific role associated with a publisher, use the companion descriptor publisherRole.

ADDITIONAL NOTES:
According to Dublin Core, the intent of using the descriptor publisher is to identify the entity that provides access to a media item. If the nature of the responsibility is ambiguous, the recommended practice is to use publisher for organizations, and creator for individuals. In cases of lesser responsibility, other than creation, use the descriptor contributor.

A distributor may be considered as a publisher. AMIA defines a distributor as "the person or corporate body which sells, leases, rents, or in some matter makes available moving image works."

For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

• Copyright Holder
• Distributor
• Presenter
• Publisher
• Release Agent
• More Metadata Examples

Select from a picklist of publisher roles.

For a publisher, identify the role played by that individual or organization. Preference is to use a pre-defined list of publisher roles rather than entering informal, free-form text. A distributor may be considered as a publisher. AMIA defines a distributor as "the person or corporate body which sells, leases, rents, or in some matter makes available moving image works." Thus distributor is a role played by a publisher.

• Copyright 2004, Alan Smithee Productions
• Broadcast
• World Wide Web
• Restricted to non-commercial, educational use
• For private, home viewing. No public performance allowed.
• You may download and display or play this media item in perpetuity, with no time or frequency limitations.
• Fair Use
• Broadcast Rights: From First Broadcast:Ê 5 plays in 6 years beginning 01/23/2004
• Fee Waived. Requires Attribution: Used by permission of Media Solutions, University of Utah
• More Metadata Examples

Use free-form text entry.

Rights entered into this descriptor include how an item may be used, re-used, re-purposed, reproduced, played out, or distributed, e.g., for broadcast, for World Wide Web, for education/classroom use or home use. Information contained in rightsSummary should help answer questions about when, where and how a resource may be used, seen or heard. Time limitations, availabilities, blackouts, territorial restrictions, retirement, copyrights, and other such conditions may be included. If dates, time and availability periods are associated with a right, include them. This is a free-form text-based container field, so narrative summaries are encouraged in order to adequately describe a particular right and its associated time periods.

The rights and use limitations that are associated with a media item can be grouped into three categories: Permissions, Constraints, and Obligations. These categories are a distillation of the The Open Digital Rights Language (ODRL) which is a proposed language for the Digital Rights Management (DRM) community for the standardization of expressing rights information over content. The ODRL is intended to provide flexible and interoperable mechanisms to support transparent and innovative use of digital resources in publishing, distributing and consuming of electronic publications, digital images, audio and movies, learning objects, computer software and other creations in digital form. The ODRL has no license requirements and is available in the spirit of "open source" software.
ODRL Initiative home page
http://odrl.net/
ODRL DRM definitions and terms
http://www.w3.org/TR/odrl/

PERMISSIONS...
Permissions metadata specifies the actual usages or activities allowed or transferable over or with a media item in its entirety or as an extract harvested from the original. These permissions translate into how a media item can by played or consumed, how it can be reused, and how the media item can be transferred to others. The information found under "Permissions" answers the question "What can an end user do with a media item?" Another way to summarize this metadata is to indicate that "You are permitted to..."

CONSTRAINTS...
Contraints metadata is a narrative or statement summarizing the constraints that limit the permissions granted for using a media item. These constraints translate into limitations on audiences and use groups, devices for display, playback, or transmission, bounds on the number of usages, and geographic and temporal restrictions. The information found under "Constraints" answers the question "What can't an end user do with a media item?" Another way to summarize this metadata is to indicate "Under these constraints..."

OBLIGATIONS...
Compliance Requirements metadata specifies the obligations needed to exercise the Permission (e.g., Pay $5 each time you Play the video; or Publish an attribution or credit statement). The information found under "Compliance Requirements/Obligations" answers the question "What must an end user do to be able to use a media item?" Another way to summarize this metadata field indicates "With these obligations..."

Each time a different right is available, enter it as another repetition of this descriptor within its container pbcoreRightsSummary. One repetition could articulate the Permissions, another repetition for the Constraints, and a third repetition for specified Obligations.

Digital Rights Management and Intellectual Property Rights Management are complex issues. Many content and digital asset management systems actually purchase third-party DRM modules that can be integrated into the data models for a DAM or CRM system. Public Broadcasting maintains complex rights management metadata, which for the purposes of PBCore integration, should be summarized as best possible.

• Year:
  YYYY
  1997
• Year and month:
  YYYY-MM
  1997-07
• Complete date:
  YYYY-MM-DD
  1997-07-16
• Complete date with a 24 hour clock time stamp with seconds precision:
  YYYY-MM-DD (hh:mm:ss)
  1997-07-16 (16:30:00)
• Complete date with a 24 hour clock time stamp with decimal fraction precision:
  YYYY-MM-DD (hh:mm:ss.df)
  1997-07-16 (16:30:00.34)
• Approximate year
  1998 ?
• Complete ISO 8601 compliant date plus hours and minutes with Time Zone:
  YYYY-MM-DDThh:mmTZD
  1997-07-16T19:20+01:00
• Complete ISO 8601 date plus hours, minutes and seconds with Time Zone:
  YYYY-MM-DDThh:mm:ssTZD
  1997-07-16T19:20:30+01:00
• Complete ISO 8601 date plus hours, minutes, seconds and a decimal fraction of a second with Time Zone:
  YYYY-MM-DDThh:mm:ss.sTZD
  1997-07-16T19:20:30.45+01:00
• More Metadata Examples

The descriptor dateCreated refers to the creation date for a particular version or rendition of a media item across its entire life cycle. A specific time may also be associated the date.

Do not confuse dateCreated with the dates and times indicated in the descriptor coverage and its companion element coverageType when it equals "Temporal." A creation date refers to the moment in time that the media item was finalized during its production process and forwarded to other divisions or agencies to make it ready for publication or distribution (dateIssued). The information for the descriptor coverage when it is of coverageType "Temporal" describes the time-bound identifiers for the intellectual content found within a media item, e.g., a photograph of the aftermath on the attack on Pearl Harbor might have a creation date of December 10, 1941 (1941-12-10), but an intellectual content time stamp (coverage) of December 7, 1941 (1941-12-07).

DATE FORMATTING:
PBCore recommends that you employ the syntax ISO 8601 suggests for entering dates (e.g., YYYY-MM-DD), but by no means is the entire Date+Time string required as you enter a date or time stamp for your media item. The date and/or time designated is essentially an open-ended text string with highly recommended syntax for entering years, months, and days.

The recommended format consists of a text string for the representation of dates YYYY-MM-DD (1998-01-24).

• Year (YYYY) is defined as 0000 to 9999.
• Month (MM) is defined as 01 to 12.
• Day (DD) is defined as 01 to 28, 29, 30 or 31 as applicable.
• The separator between date fields is a hyphen, (-).

If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Many other syntaxes are possible, but if used, they may not be easily interpreted, searchable, or shareable.

If a date is approximate, add a question mark but separate the date from the question mark by a space so that the question mark is not interpreted as part of the date value by a search engine, e.g., 1922 ? . Generally, a year or year-month-day designation will provide enough precision.

If needed, a specific time stamp may directly follow the date designation. The time stamp can be enclosed within parentheses. The time format (hh:mm:ss) consists of two digit designations for hours, minutes and seconds (19:20:30) in a 24 hour clock mode. If necessary, the seconds may be further defined by a decimal fraction of a second (19:20:30.45).

ISO 8601 requests the inclusion of a time zone designator (TZD) to complete a date/time statement, but PBCore does not require or mandate that specification.

• Year:
  YYYY
  1997
• Year and month:
  YYYY-MM
  1997-07
• Complete date:
  YYYY-MM-DD
  1997-07-16
• Complete date with a 24 hour clock time stamp with seconds precision:
  YYYY-MM-DD (hh:mm:ss)
  1997-07-16 (16:30:00)
• Complete date with a 24 hour clock time stamp with decimal fraction precision:
  YYYY-MM-DD (hh:mm:ss.df)
  1997-07-16 (16:30:00.34)
• Approximate year
  1998 ?
• Complete ISO 8601 compliant date plus hours and minutes with Time Zone:
  YYYY-MM-DDThh:mmTZD
  1997-07-16T19:20+01:00
• Complete ISO 8601 date plus hours, minutes and seconds with Time Zone:
  YYYY-MM-DDThh:mm:ssTZD
  1997-07-16T19:20:30+01:00
• Complete ISO 8601 date plus hours, minutes, seconds and a decimal fraction of a second with Time Zone:
  YYYY-MM-DDThh:mm:ss.sTZD
  1997-07-16T19:20:30.45+01:00
• More Metadata Examples

The descriptor dateIssued refers to the date for a particular version or rendition of a media item that has been officially released or issued for consumption, publication or distribution. It is likely a date later than the creation date indicated in dateCreated. A specific time may also be associated with the date.

Do not confuse dateIssued with the dates and times indicated in the descriptor coverage and its companion element coverageType when it equals "Temporal." A date of issue refers to the release date for consumption of a particular rendition of a media item. The information for the descriptor coverage when it is of coverageType "Temporal" describes the time-bound identifiers for the intellectual content found within a media item, e.g., a photograph of the aftermath on the attack on Pearl Harbor might have a date of issue of December 15, 1941 (1941-12-15), but an intellectual content time stamp (coverage) of December 7, 1941 (1941-12-07).

DATE FORMATTING:
PBCore recommends that you employ the syntax ISO 8601 suggests for entering dates (e.g., YYYY-MM-DD), but by no means is the entire Date+Time string required as you enter a date or time stamp for your media item. The date and/or time designated is essentially an open-ended text string with highly recommended syntax for entering years, months, and days.

The recommended format consists of a text string for the representation of dates YYYY-MM-DD (1998-01-24).

• Year (YYYY) is defined as 0000 to 9999.
• Month (MM) is defined as 01 to 12.
• Day (DD) is defined as 01 to 28, 29, 30 or 31 as applicable.
• The separator between date fields is a hyphen, (-).

If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Many other syntaxes are possible, but if used, they may not be easily interpreted, searchable, or shareable.

If a date is approximate, add a question mark but separate the date from the question mark by a space so that the question mark is not interpreted as part of the date value by a search engine, e.g., 1922 ? . Generally, a year or year-month-day designation will provide enough precision.

If needed, a specific time stamp may directly follow the date designation. The time stamp can be enclosed within parentheses. The time format (hh:mm:ss) consists of two digit designations for hours, minutes and seconds (19:20:30) in a 24 hour clock mode. If necessary, the seconds may be further defined by a decimal fraction of a second (19:20:30.45).

ISO 8601 requests the inclusion of a time zone designator (TZD) to complete a date/time statement, but PBCore does not require or mandate that specification.

• 1 inch videotape
• DVC-Pro 50
• DVD-Video Disc
• Manuscript
• Photograph
• More Metadata Examples

Best practice is to select from a controlled vocabulary list. If the media item was never "born" in a physical format, but only exists digitally, then ignore this descriptor.

Select from picklists of physical formats.

• application/vnd.ms-powerpoint
• audio/x-aiff
• image/jpeg
• text/pdf
• video/quicktime
• More Metadata Examples

Best practice is to select from the PBCore Aggregate Picklist

View PBCore Digital Formats - not specified - video/3gpp video/3gpp2 video/3gpp-tt video/BMPEG video/BT656 video/CelB video/DV video/H261 video/H263 video/H263-1998 video/H263-2000 video/H264 video/JPEG video/MJ2 video/MP1S video/MP2P video/MP2T video/mp4 video/MP4V-ES video/MPV video/mpeg video/mpeg4-generic video/nv video/parityfec video/pointer video/quicktime video/raw video/rtx video/SMPTE292M video/vc1 video/vnd.dlna.mpeg-tts video/vnd.fvt video/vnd.hns.video video/vnd.motorola.video video/vnd.motorola.videop video/vnd.mpegurl video/vnd.nokia.interleaved-multimedia video/vnd.nokia.videovoip video/vnd.objectvideo video/vnd.sealed.mpeg1 video/vnd.sealed.mpeg4 video/vnd.sealed.swf video/vnd.sealedmedia.softseal.mov video/vnd.vivo - audio/32kadpcm audio/3gpp audio/3gpp2 audio/ac3 audio/AMR audio/AMR-WB audio/amr-wb+ audio/asc audio/basic audio/BV16 audio/BV32 audio/clearmode audio/CN audio/DAT12 audio/dls audio/dsr-es201108 audio/dsr-es202050 audio/dsr-es202211 audio/dsr-es202212 audio/eac3 audio/DVI4 audio/EVRC audio/EVRC0 audio/EVRC1 audio/EVRCB audio/EVRCB0 audio/EVRCB1 audio/EVRC-QCP audio/G722 audio/G7221 audio/G723 audio/G726-16 audio/G726-24 audio/G726-32 audio/G726-40 audio/G728 audio/G729 audio/G7291 audio/G729D audio/G729E audio/GSM audio/GSM-EFR audio/iLBC audio/L8 audio/L16 audio/L20 audio/L24 audio/LPC audio/mobile-xmf audio/MPA audio/mp4 audio/MP4A-LATM audio/mpa-robust audio/mpeg audio/mpeg4-generic audio/parityfec audio/PCMA audio/PCMU audio/prs.sid audio/QCELP audio/RED audio/rtp-midi audio/rtx audio/SMV audio/SMV0 audio/SMV-QCP audio/t140c audio/t38 audio/telephone-event audio/tone audio/VDVI audio/VMR-WB audio/vnd.3gpp.iufp audio/vnd.4SB audio/vnd.audiokoz audio/vnd.CELP audio/vnd.cisco.nse audio/vnd.cmles.radio-events audio/vnd.cns.anp1 audio/vnd.cns.inf1 audio/vnd.digital-winds audio/vnd.dlna.adts audio/vnd.everad.plj audio/vnd.hns.audio audio/vnd.lucent.voice audio/vnd.nokia.mobile-xmf audio/vnd.nortel.vbk audio/vnd.nuera.ecelp4800 audio/vnd.nuera.ecelp7470 audio/vnd.nuera.ecelp9600 audio/vnd.octel.sbc audio/vnd.rhetorex.32kadpcm audio/vnd.sealedmedia.softseal.mpeg audio/vnd.vmx.cvsd - image/cgm image/fits image/g3fax image/gif image/ief image/jp2 image/jpeg image/jpm image/jpx image/naplps image/png image/prs.btif image/prs.pti image/t38 image/tiff image/tiff-fx image/vnd.adobe.photoshop image/vnd.cns.inf2 image/vnd.djvu image/vnd.dwg image/vnd.dxf image/vnd.fastbidsheet image/vnd.fpx image/vnd.fst image/vnd.fujixerox.edmics-mmr image/vnd.fujixerox.edmics-rlc image/vnd.globalgraphics.pgb image/vnd.microsoft.icon image/vnd.mix image/vnd.ms-modi image/vnd.net-fpx image/vnd.sealed.png image/vnd.sealedmedia.softseal.gif image/vnd.sealedmedia.softseal.jpg image/vnd.svf image/vnd.wap.wbmp image/vnd.xiff - text/calendar text/css text/csv text/directory text/dns text/ecmascript (obsolete) text/enriched text/html text/javascript (obsolete) text/parityfec text/plain text/prs.fallenstein.rst text/prs.lines.tag text/RED text/rfc822-headers text/richtext text/rtf text/rtx text/sgml text/t140 text/tab-separated-values text/troff text/uri-list text/vnd.abc text/vnd.curl text/vnd.DMClientScript text/vnd.esmertec.theme-descriptor text/vnd.fly text/vnd.fmi.flexstor text/vnd.in3d.3dml text/vnd.in3d.spot text/vnd.IPTC.NewsML text/vnd.IPTC.NITF text/vnd.latex-z text/vnd.motorola.reflex text/vnd.ms-mediapackage text/vnd.net2phone.commcenter.command text/vnd.sun.j2me.app-descriptor text/vnd.trolltech.linguist text/vnd.wap.si text/vnd.wap.sl text/vnd.wap.wml text/vnd.wap.wmlscript text/xml text/xml-external-parsed-entity - application/http application/hyperstudio application/javascript application/mac-binhex40 application/marc application/mbox application/mediaservercontrol+xml application/mp4 application/mpeg4-generic application/mpeg4-iod application/mpeg4-iod-xmt application/msword application/mxf application/pdf application/postscript application/rdf+xml application/rtf application/rtx application/sgml application/sgml-open-catalog application/smil (OBSOLETE) application/smil+xml application/soap+fastinfoset application/soap+xml application/ssml+xml application/vnd.adobe.xfdf application/vnd.apple.installer+xml application/vnd.framemaker application/vnd.google-earth.kml+xml application/vnd.google-earth.kmz application/vnd.HandHeld-Entertainment+xml application/vnd.lotus-1-2-3 application/vnd.lotus-approach application/vnd.lotus-freelance application/vnd.lotus-notes application/vnd.lotus-organizer application/vnd.lotus-screencam application/vnd.lotus-wordpro application/vnd.mozilla.xul+xml application/vnd.ms-artgalry application/vnd.ms-asf application/vnd.ms-cab-compressed application/vnd.mseq application/vnd.ms-excel application/vnd.ms-fontobject application/vnd.ms-htmlhelp application/vnd.msign application/vnd.ms-ims application/vnd.ms-lrm application/vnd.ms-powerpoint application/vnd.ms-project application/vnd.ms-tnef application/vnd.ms-wmdrm.lic-chlg-req application/vnd.ms-wmdrm.lic-resp application/vnd.ms-wmdrm.meter-chlg-req application/vnd.ms-wmdrm.meter-resp application/vnd.ms-works application/vnd.ms-wpl application/vnd.ms-xpsdocument application/vnd.palm application/vnd.paos.xml application/vnd.Quark.QuarkXPress application/vnd.visio application/vnd.wordperfect application/wordperfect5.1 application/xhtml+xml application/xml application/xml-dtd application/xml-external-parsed-entity application/zip

Best practice is to select from a controlled vocabulary list.

For a review of the meaning behind the digital formats and MIME types, consult these websites:

IANA: Internet Assigned Numbers Authority
http://www.iana.org/assignments/media-types/

IMT: Internet Media Types documented by Wikipedia
with extensive and helpful hyperlinks
http://en.wikipedia.org/wiki/Internet_media_type

IMT: Internet Media Types
http://graphcomp.com/info/specs/mime.html

Text and Text-Related Types
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#text

HTML Stylesheet
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#styl

Image
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#imag

Audio/Voice/Music
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#audi

Video
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#vide

2D/3D Data/Virtual reality
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#vrml

Scientific/Math/CAD
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#math

Special HTTP/Web Application
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#spec

Application Type: Text-related
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#trel

Application Type: Archive/Compressed Archives
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#arch

Application Type: Program/Scripts
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#prog

Application Type: Animation/Multimedia
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#anim

Application Type: Presentation
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#pres

Application Type: Special Embedded Object
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#spece

Application Type: General Applications
http://www.utoronto.ca/webdocs/HTMLdocs/
Book/Book-3ed/appb/mimetype.html#gene

• Lindemann/Phillips 66 Oil Industry Archives of Bartlesville, OK
• Eccles Broadcast Center; Vault Room 217; Section C: Shelf 5
• Utah Education Network Licensed PBS Media DAM System
  http://www.uen.org/PBS
• Utah Education Network K-12 e-Media DAM System
  http://www.uen.org/emedia
• J. Willard Marriott Library: Special Collections
• 
• More Metadata Examples

Use free-form text entry.

The data for formatLocation may be a URL, URI, physical location ID, barcode, etc.

formatLocation can be thought of as holdings, where holdings are controlled by a Gatekeeper or Organization or Caretaker that has assumed responsibility for a media item, separate from the responsibilities of a Publisher. The information found in the descriptor formatLocation may contain data about the Holding's Organization, the Holding's Department, and a Holding's Location, whether physically or virtually defined.

• Moving Image
• Static Image
• Text
• Sound
• Video
• Presentation
• More Metadata Examples

Select from this PBCore Aggregate Picklist

In identifying the general nature of the manner in which content is presented to an observer, the descriptor formatMediaType is a very high level view of the media type for a media item. Its meaning goes no deeper than to merely indicate if a media item is an animation, a moving image, a sound, or perhaps text (see the recommended picklist). The actual type of format is expressed through two other descriptors, formatPhysical and formatDigital (mime types).

• Audio/Narration
• Moving image/Promo
• Static image/Postcard
• Text/Cue sheet
• More Metadata Examples

Best practice is to select from a picklist of values.

The terms used identify the general type of media (e.g., audio, moving image, static image, artifact, text, container) and associated generational renditions usually associated with the media type.

PBCore Aggregate Picklist

• NTSC-interlaced
• PAL
• Dolby Digital AC3 Audio
• MPEG
• ATSC-progressive
• More Metadata Examples

Best practice is to select from a picklist of terms.

Video Format Technical Standards
View Video/Film Format Standards - Film MPEG video NTSC video (interlaced) NTSC video (progressive) ATSC video (interlaced) ATSC video (progressive) PAL video SECAM video QuickTime RealSystems Windows Media Flash Video

Audio Format Technical Standards
View Audio Format Standards - Linear PCM Audio Dolby Digital AC3 Audio MPEG Audio DTA Audio SDDS Audio

• Sorenson 3
• MPEG-1
• MPEG-2
• MPEG-2 4:2:2
• MPEG-4
• M-JPEG A
• Real Media 9
• Windows Media 9
• MP3
• AAC
• MXF
• More Metadata Examples

Use free-form text entry to identify the specific encoding and parameters for the media item. PBCore decided that a comprehensive picklist of terms or values from which to pick encoding schemes would have been overwhelming and probably frozen in time as new schemes emerge monthly. Instead, enter what you know you are using to encode your media item.

• 4000 bytes
• Use 409600 bytes for a 400 kilobyte file
• Use 1258291.2 bytes for a 1.2 megabyte file
• Use 4831838208 bytes for a 4.5 gigabyte file
• More Metadata Examples

Express the measurement in bytes. Do not use kilobytes, megabytes or gigabytes.
The exact conversion is as follows:
1 Byte = 8 bits
1 Kilobyte = 1024 Bytes
1 Megabyte = 1048576 Bytes
1 Gigabyte = 1073741824 Bytes

If your digitizing or media conversion technology automatically specifies file size, you are good to go. Many digital asset management systems and their associated media ingestion tools will automatically generate the structural metadata associated with a specific digital file, including its size in bytes.

If you need to manually convert a file size into bytes, PBCore suggests using an online byte calculator. Below are four recommendations:

• http://www.matisse.net/bitcalc/
• http://webdeveloper.earthweb.com/repository/
  javascripts/2001/04/41291/byteconverter.htm
• http://www.techtutorials.com/reference/byteconverter.shtml
• http://www.beesky.com/newsite/bit_byte.htm

• 01:23:45:09 (SMPTE Timecode nondrop frame-NTSC)
• 01;23;45;09 (SMPTE Timecode dropframe-NTSC)
• 01:23:45.365 (Milliseconds Timecode)
• 02:34:35 (HH:MM:SS)
• More Metadata Examples

PBCore recommends the use of...

AES46-2002
http://www.w3.org/TR/NOTE-datetime

SMPTE 12M-1999
Television, Audio and Film – Time and Control Code
http://www.smpte.org/smpte_store/standards/

Obviously, formatTimeStart is only applicable to media items that are time-based.

PBCore recommends flexibility in expressing time stamps. Radio producers often prefer the simple HH:MM:SS designation. Television producers prefer the SMPTE time code standards HH:MM:SS:FF. Some multimedia architectures express time in HH:MM:SS.mmm, where the mmm represents milliseconds.

Consequently, the best practice is to match the time stamp designation to your preferred method:

• HH:MM:SS
• HH:MM:SS.mmm
• HH:MM:SS:FF (SMPTE Timecode nondrop frame-NTSC)
• HH;MM;SS;FF (SMPTE Timecode drop frame-NTSC)

• 01:23:45:09 (SMPTE Timecode nondrop frame-NTSC)
• 01;23;45;09 (SMPTE Timecode dropframe-NTSC)
• 01:23:45.365 (Milliseconds Timecode)
• 02:34:35 (HH:MM:SS)
• More Metadata Examples

PBCore recommends the use of...

AES46-2002
http://www.w3.org/TR/NOTE-datetime

SMPTE 12M-1999
Television, Audio and Film – Time and Control Code
http://www.smpte.org/smpte_store/standards/

Obviously, formatDuration is only applicable to media items that are time-based.

formatDuration does not describe the time required to utilize a resource in a setting (such as a classroom), but is rather a strict playback time, TimeStart to TimeEnd.

PBCore recommends flexibility in expressing time stamps. Radio producers often prefer the simple HH:MM:SS designation. Television producers prefer the SMPTE time code standards HH:MM:SS:FF. Some multimedia architectures express time in HH:MM:SS.mmm, where the mmm represents milliseconds.

Consequently, the best practice is to match the time stamp designation to your preferred method:

• HH:MM:SS
• HH:MM:SS.mmm
• HH:MM:SS:FF (SMPTE Timecode nondrop frame-NTSC)
• HH;MM;SS;FF (SMPTE Timecode drop frame-NTSC)

• 32 kilobits/sec
• 200 kilobits/sec
• 300 kilobytes/sec
• 1.2 megabits/sec
• 8.0 megabits/sec
• More Metadata Examples

Enter a number, followed by the data rate scale you employ, measured on a per second basis. The measurement scale applied to a data rate is variable depending on the intended purpose of the file (editing, distribution over LAN or Internet, etc.) The measurment scale may also be dictated by a particular DAM, CMS, or playout storage system. Enter a number followed by the measurement scale:

• kilobits/second
• bytes/second
• kilobytes/second
• megabits/second

When entering data rate information, determine which data rate information is needed for your indexing purposes and by your users. Total data rate expresses the complete data transfer load for a file and is likely the most useful. If cataloging the separate data rates for video and/or audio tracks is of importance, then either or both of these should be indicated.

The pbcoreInstantiation container should not be repeated in order to express a video data rate and an associated audio data rate. The two combined are part of a single instantiation for an asset. If, however, a separate audio file is derived from the asset (such as a standalone mp3 file), it is considered a separate rendition of that asset and worthy of a repeated instantiation set of metadata.

PBCore suggests you indicate which data rate you are reporting. For example..

• Video 1930 kilobits/sec
• Audio 230 kilobits/sec
• Total 1930 kilobits/sec; Video 1700 kilobits/sec; Audio 230 kilobits/sec

• 8 bit
• 16 bit
• 20 bit
• 24 bit
• More Metadata Examples

Best practice is to select from a picklist of values.

• 11 kHz
• 22.050 kHz
• 32 kHz
• 44.1 kHz
• 48 kHz
• 96 kHz
• More Metadata Examples

Best practice is to select from a picklist of values.

• 320x240
• 352x240 (MPEG-1 NTSC)
• 720x480 (MPEG-1 NTSC & DV)
• 1280x720
• 1920x1080
• 1080i > 1920x1080, interlaced scan
• 1080p > 1920x1080, progressive scan
• 720i > 1280x720, interlaced scan
• 720p > 1280x720, progressive scan
• 480i > 704x480, interlaced scan
• 480p > 704x480, progressive scan
• 640x480, interlaced scan
• More Metadata Examples

Best practice is to select from a picklist of values.

ATSC Frame Size Variations
View ATSC Frame Size Variations (Common Name > Horiz x Vertical) - 1080i > 1920x1080, interlaced scan) 1080p > 1920x1080, progressive scan) 720i > 1280x720, interlaced scan 720p > 1280x720, progressive scan 480i > 704x480, interlaced scan 480p > 704x480, progressive scan 640x480, interlaced scan

If a static image is the media item being described, the horizontal x vertical resolution will typically need to entered as an "other" option or customized data entry, depending on the information or digital asset management system in use.

Note that in the ATSC standards, the different frame sizes are colloquially referenced by the number of vertical pixels displayed and by the interlaced or progressive scan mode with which the signal is produced, distributed, and displayed.

Consequently, the ATSC standard known as 1080i measures 1920 pixels horizontally and 1080 pixels vertically, in an interlaced scan mode. A 720p signal measures 1280 pixels horizontally and 720 pixels vertically, in a progressive scan mode.

For a comprehensive review of ATSC TV resolutions, read the Wikipedia article entitled ATSC.

For a review of different scanning methods, read the Wikipedia articles entitled Progressive Scan and Interlace Scan.

• 4:3
• 4:3 (16:9 letterbox)
• 4:3 (16:9 anamorphic)
• 16:9
• 5.5:3
• 7:3 (Panavision or CinemaScope)
• 2.35:1
• 1.85:1
• More Metadata Examples

Best practice is to select from a picklist of values.

If the aspect ratio of a media item being described is outside of an expected video/film aspect ratio, then enter the data as an "other" option or customized data entry, depending on the information or digital asset management system in use.

For a comprehensive review of digital video and the evolution of our past, current, and upcoming digital video horizons, please reference an intriguing web site called gruntmedia whose mission "is to use the podcasting platform as a means for publishing short videos that tell stories about the basics of things." One of their service channels is named videogrunt where a growing directory of podcast videos clearly illustrates the concept of aspect ratios for digital video and HDTV.

• 60 fps
• 59.94 fps
• 30 fps (60 fields/sec)
• 29.97 fps (59.94 fields/sec)
• 25 fps
• 24 fps
• 23.976 fps
• 15 fps
• 12 fps
• 10 fps
• 7 fps
• 5 fps
• 2 fps
• 1 fps
• 33 rpm
• 45 rpm
• 78 rpm
• 1 7/8 ips
• 3 3/4 ips
• 7 1/2 ips
• 15 ips
• 30 ips
• More Metadata Examples

Best practice is to select from picklist of values.

• B&W
• Grayscale
• Color
  -
• B&W with grayscale sequences
• B&W with color sequences
• Grayscale with B&W sequences
• Grayscale with color sequences
• Color with B&W sequences
• Color with grayscale sequences
• More Metadata Examples

Best praactice is to select from a picklist of values.

Indicates the possible color, grayscale, or black and white color schemes or combinations for a media item. If the media item is primarily color, grayscale, or black and white, then use one of these three simple terms from the picklist. If the media item has a primary color scheme, but includes significant embedded sequences of another color set, then a color combination from the picklist can be used to show the primary and secondary color schemes

The descriptor formatColors is not intended to measure or identify specific color metrics of pixels in a static image or moving image, but describes the media item in a more generalized way in order to inform consumers what to expect during media delivery and/or playback.

• 1 video track
• 2 video tracks
• 4 audio tracks
• 1 caption track
• 3 subtitle tracks
• 4 sprite layers
• 1 VITC timecode track
• More Metadata Examples

Use free-form text entry to identify the number and type of information tracks in an analog or digital media item with formatTracks. This descriptor is simply intended to flag what tracks are present and how many. Whether digital or analog in nature, a media item can have many different types of tracks, including timecode tracks, video tracks, audio tracks, sprite tracks, text tracks, etc. Each form of new media is likely to have different types of tracks available to contain the content or information of a media item.

Other configuration information specific to these identified tracks should be described using formatChannelConfiguration

• 1 track-mono
• 2 track-stereo
• 5.1
• video track with linear alpha channel
• sprite track with navigation links
• More Metadata Examples

Use free-form text entry. Whereas the descriptor formatTracks identifies the number and kind of tracks present in a media item (digital or analog), formatChannelConfiguration delves deeper by describing other configuration information specific to the tracks identified in formatTracks. Where it is important to share this information, indicate specific arrangements of layers or channels within a track.

• eng [for English]
• fre [for French]
• eng;fre [for two primary languages in the media item]
• mas [for Masai]
• yid [for Yiddish]
• ara [for Arabic]
• More Metadata Examples

PBCore recommends using the three-letter language codes defined by ISO 639-2 instead of 2-letter codes.

• http://www.w3.org/WAI/ER/IG/ert/iso639.htm
• http://www.oasis-open.org/cover/iso639a.html

If the media item has more than one language that is considered part of the same primary audio or text, then a combination statement can be crafted, e.g., eng;fre for the presence of both English and French in the primary audio. Separating three-letter language codes with a semi-colon (no additional spaces) is preferred.

Alternative audio or text tracks and their associated languages should be identified using the descriptor alternativeModes.

• DVI in English
• DVI in Spanish
• SAP1 in Spanish
• CC1 in English
• CC4 in French
• Open Caption in German
• Subtitle in Thai
• Subtitle in Klingon
• Transcript in Spanish
• Dubbed in Japanese
• More Metadata Examples

For each instance of available alternativeModes, the mode and its associated language should be identified together, if applicable. Examples include "SAP in English," "SAP in Spanish," "Subtitle in French," "OpenCaption in Arabic."

Use free-text entry, but follow PBCore's recommended structure for entering data (noted below).

The descriptor alternativeModes is a catch-all metadata element that indicates the presence of one or more alternatives to the primary visual, audio or textual presentation or display for a media item. The actual content of the alternative track or mode is not entered here, just an indication that exists.

The alternative modes that are encountered most frequently include:

• DVI: Descriptive Video Information
• SAP: Supplementary Audio Program
• CC: Closed Captions
• OC: Open Captions
• Caption Track
• Subtitle
• Dubbed
• Transcript

The WGBH National Center for Accessible Media (NCAM) is working with the IMS Global Learning Consortium to publish a specification: Accessibility for Learner Information Package (LIP). This specification and metadata schema is intended to address user needs and preferences for alternative presentations of content found in a media item.
http://ncam.wgbh.org/news/pr_20030430.html
http://www.imsglobal.org/accessibility/

In the interest of simplicity, the PBCore will not be folding in the accessibility metadata at this time. However, we have created this container field called alternativeModes into which equivalent alternatives to what is seen, heard, and read can be identified, along with the language associated with that mode.

Because there may be more than one alternative track, the descriptor alternativeModes can be repeated for each instance.

Because various alternative tracks may use a different language than the primary language of the media item (see the descriptor language), PBCore recommends that the alternative language associated with an alternative track be identified as well. The structure of your data entry should be:

• Identify the alternative mode for seeing, hearing, or reading the content for a media item,
• Followed by a space,
• Followed by the word "in",
• Followed by another space, and...
• Append the language for that alternative mode.

• Year:
  YYYY
  1997
• Year and month:
  YYYY-MM
  1997-07
• Complete date:
  YYYY-MM-DD
  1997-07-16
• Complete date with a 24 hour clock time stamp with seconds precision:
  YYYY-MM-DD (hh:mm:ss)
  1997-07-16 (16:30:00)
• Complete date with a 24 hour clock time stamp with decimal fraction precision:
  YYYY-MM-DD (hh:mm:ss.df)
  1997-07-16 (16:30:00.34)
• Approximate year
  1998 ?
• Complete ISO 8601 compliant date plus hours and minutes with Time Zone:
  YYYY-MM-DDThh:mmTZD
  1997-07-16T19:20+01:00
• Complete ISO 8601 date plus hours, minutes and seconds with Time Zone:
  YYYY-MM-DDThh:mm:ssTZD
  1997-07-16T19:20:30+01:00
• Complete ISO 8601 date plus hours, minutes, seconds and a decimal fraction of a second with Time Zone:
  YYYY-MM-DDThh:mm:ss.sTZD
  1997-07-16T19:20:30.45+01:00
• More Metadata Examples

The descriptor dateAvailableStart refers to the beginning date that a version or rendition of a media item is officially available for publication, broadcast or distribution. A specific time may also be associated with the date.

To avoid problems in indicating date ranges for a media item's availability, PBCore has spawned two separate descriptors to capture specific dates that are independently searchable:
dateAvailableStart and
dateAvailableEnd

DATE FORMATTING:
PBCore recommends that you employ the syntax ISO 8601 suggests for entering dates (e.g., YYYY-MM-DD), but by no means is the entire Date+Time string required as you enter a date or time stamp for your media item. The date and/or time designated is essentially an open-ended text string with highly recommended syntax for entering years, months, and days.

The recommended format consists of a text string for the representation of dates YYYY-MM-DD (1998-01-24).

• Year (YYYY) is defined as 0000 to 9999.
• Month (MM) is defined as 01 to 12.
• Day (DD) is defined as 01 to 28, 29, 30 or 31 as applicable.
• The separator between date fields is a hyphen, (-).

If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Many other syntaxes are possible, but if used, they may not be easily interpreted, searchable, or shareable.

If a date is approximate, add a question mark but separate the date from the question mark by a space so that the question mark is not interpreted as part of the date value by a search engine, e.g., 1922 ? . Generally, a year or year-month-day designation will provide enough precision.

If needed, a specific time stamp may directly follow the date designation. The time stamp can be enclosed within parentheses. The time format (hh:mm:ss) consists of two digit designations for hours, minutes and seconds (19:20:30) in a 24 hour clock mode. If necessary, the seconds may be further defined by a decimal fraction of a second (19:20:30.45).

ISO 8601 requests the inclusion of a time zone designator (TZD) to complete a date/time statement, but PBCore does not require or mandate that specification.

• Year:
  YYYY
  1997
• Year and month:
  YYYY-MM
  1997-07
• Complete date:
  YYYY-MM-DD
  1997-07-16
• Complete date with a 24 hour clock time stamp with seconds precision:
  YYYY-MM-DD (hh:mm:ss)
  1997-07-16 (16:30:00)
• Complete date with a 24 hour clock time stamp with decimal fraction precision:
  YYYY-MM-DD (hh:mm:ss.df)
  1997-07-16 (16:30:00.34)
• Approximate year
  1998 ?
• Complete ISO 8601 compliant date plus hours and minutes with Time Zone:
  YYYY-MM-DDThh:mmTZD
  1997-07-16T19:20+01:00
• Complete ISO 8601 date plus hours, minutes and seconds with Time Zone:
  YYYY-MM-DDThh:mm:ssTZD
  1997-07-16T19:20:30+01:00
• Complete ISO 8601 date plus hours, minutes, seconds and a decimal fraction of a second with Time Zone:
  YYYY-MM-DDThh:mm:ss.sTZD
  1997-07-16T19:20:30.45+01:00
• More Metadata Examples

To avoid problems in indicating date ranges for a media item's availability, PBCore has spawned two separate descriptors to capture specific dates that are independently searchable::
dateAvailableStart and
dateAvailableEnd

DATE FORMATTING:
PBCore recommends that you employ the syntax ISO 8601 suggests for entering dates (e.g., YYYY-MM-DD), but by no means is the entire Date+Time string required as you enter a date or time stamp for your media item. The date and/or time designated is essentially an open-ended text string with highly recommended syntax for entering years, months, and days.

The recommended format consists of a text string for the representation of dates YYYY-MM-DD (1998-01-24).

• Year (YYYY) is defined as 0000 to 9999.
• Month (MM) is defined as 01 to 12.
• Day (DD) is defined as 01 to 28, 29, 30 or 31 as applicable.
• The separator between date fields is a hyphen, (-).

If the full date is unknown, month and year (YYYY-MM) or just year (YYYY) may be used. Many other syntaxes are possible, but if used, they may not be easily interpreted, searchable, or shareable.

If a date is approximate, add a question mark but separate the date from the question mark by a space so that the question mark is not interpreted as part of the date value by a search engine, e.g., 1922 ? . Generally, a year or year-month-day designation will provide enough precision.

If needed, a specific time stamp may directly follow the date designation. The time stamp can be enclosed within parentheses. The time format (hh:mm:ss) consists of two digit designations for hours, minutes and seconds (19:20:30) in a 24 hour clock mode. If necessary, the seconds may be further defined by a decimal fraction of a second (19:20:30.45).

ISO 8601 requests the inclusion of a time zone designator (TZD) to complete a date/time statement, but PBCore does not require or mandate that specification.

To avoid problems in indicating date ranges, PBCore has spawned two separate qualified dates to mark the availability of a resource:
dateAvailableStart
dateAvailableEnd

• /public/
  items/PBCore_DC03PaperFinal.pdf
• Room 217: Section C: Shelf 5
• ISBN 0-07-135026-8
• GlenCanyonDamSpillways.wmf
• GlenCanyonDamSpillways.mov
• Beta-SP 467-34: Glen Canyon Dam Spillways
• DVC-Pro50 467-102: Glen Canyon Dam Spillways
• Transcript: GlenCanyonDamSpillways.doc
• Podcast: GlenCanyonDamSpillways.mp3
• More Metadata Examples

The descriptor formatIdentifier employs an unambiguous reference or identifier for a particular rendition/instantiation of a media item. Best practice is to identify the media item (whether analog or digital) by means of a string or number corresponding to an established or formal identification system if one exists. Otherwise, use an identification method that is in use within your agency, station, production company, office, or institution.

Another element named identfier is used to reference or identify the entire record of metadata descriptions for a media item and exists at the top level for a PBCore description and its associated description document (XML).

Use free-form text entry.

Best practice is to identify the resource (media item) by means of a string or number corresponding to an established or formal identification system generated within an international standard or as a local identification scheme. Examples include analog location number (box, folder, shelf, desk drawer, etc), ISBN/ISSN (for published text) and URLs (which include the file name) for digital data.

PBcore recommends the use of the companion descriptor, formatIdentifierSource (within the sub-container pbcoreFormatID), to indicate who assigned a particular identification number or designation. Thus PBCore provides not only a locator number, but also indicates an agency or institution who assigned it.

• Smith, Jedidiah
• Minnesota Public Radio
• KUED-TV
• Wisconsin Public Television. Extension Division
• Central Intelligence Agency
• State of Utah. Film Commission
• University of Utah. Department of Communication
• Prostate Cancer Awareness Project
• White Mountain Films
• Simpson, Lisa, Ph.D.
• More Metadata Examples

The descriptor formatIdentifierSource is used in combination with the unambiguous reference or identifier for a rendition/instantiation of a media item as found in the descriptor formatIdentifier. Thus PBCore provides not only a locator number, but also indicates an agency or institution who assigned it.

Another element named identfierSource is used in combination with the element identifier to reference or identify the entire record of metadata descriptions for a media item and from which source the identifier is derived. Both exist at the top level for a PBCore description and its associated description document (XML).

Use an authority file, such as AACR2 Cataloging Rules (Anglo-American Cataloging Rules, 2nd edition) http://www.aacr2.org/ , to determine how to properly enter names and organizations. Use a URL where possible or practical. If the authority is identified by a personal name or corporporate/organizational name, PBCore recommends the following rules:

FOR PERSONAL NAMES:
Enter personal names in inverted form using commas as indicated here:

• LastName, FirstName MiddleName, Suffix.
• Substitute a MiddleInitial for a MiddleName as appropriate, or ignore if not available.
• The suffix is any type of academic credential (Ph.D., Ed.D.) or familial lineage (Smithee, Alan, III)

FOR CORPORATE OR ORGANIZATIONAL NAMES:
Enter corporate names in full direct form.

• Use the most specific and commonly used official name for an organization if it is distinctive enough to identify the group.
• If a particular subdivision of an organization is intended, identify both the more encompassing group as well as the subdivisions.
  • The hierarchy (main group and subdivision) starts with the main group, followed by <period space>, then the subdivision.
  • For example:
    • State of Utah. Film Commission
    • Smithee Productions. Educational Division
    • Wisconsin Public Television. Extension Division

ADDITIONAL NOTES:
For a very enlightening discussion on the complexities of entering and displaying names, see "Representing People's Names in Dublin Core."

• The subject headings for this media resource use entries from MeSH: Medical Subject Headings (http://www.nlm.nih.gov/mesh/meshhome.html).
• Many segments of this program were made possible through the funding generosity of the John and Alma Hivner Educational Foundation.
• The four parts of this history series are part of a larger collection of primary research resources found in the Lindemann Historical Archives, Bartlesville, Oklahoma.
• More Metadata Examples

Use free-form text entry.

The descriptor annotation is envisioned as a Post-it® Note containing comments or narrative that further explains or documents the descriptions of a media item. If the pre-defined elements and sub-elements in PBCore require further explanation, use annotation to present this information.

Additionally, annotation may be useful in cases where an established controlled vocabulary does not adequately represent certain qualities of an asset and you wish to embellish your description.

• audience:general [DC-Ed]
• audienceMediator:facilitator [DC-Ed]
• typicalLearningTime:4 hours [IEEE LOM]
• usoe_gradelevel:Grade 4|Grade 5|Grade 6|Grade 7|Grade 8|Grade 9|Grade 10|Grade 11|Grade 12 [UMAP]
• umap_academic_disciplines:History; Science-Geography; Society and Culture [UMAP]
• drmCopyrightStatus:Public Domain [UMAP]
• drm_enduser_permissions:You may download and display or play this media item in perpetuity, with no time or frequency limitations. [UMAP]
• drm_enduser_constraints:Restricted to non-commercial, educational use. [UMAP]
• drm_enduser_obligations:Fee Waived. Requires Attribution-- *Used by permission of Media Solutions, University of Utah* [UMAP]
• drmLicenseConstraintsTimeAccumulated:4 weeks [UMAP]
• asset_EpisodeSeason:Fall 2007 [PBS PODS]
• asset_EpisodeNumber:32 [PBS PODS]
• rights_BlackoutStart:2008-02-015 [PBS PODS]
• rights_BlackoutEnd:2008-06-23 [PBS PODS]
• reup_SchoolRights:2009-12-31 [PBS PODS]
• reup_SchoolEachBroadcastMonths:9 [PBS PODS]
• reup_SchoolEachBroadcastDays:180 [PBS PODS]
• More Metadata Examples

DISCUSSION...
Use the refinements and encoding schemes that are specified by the particular metadata element you are using to extend PBCore's core descriptors.

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.

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 Content Depot (Public Radio Satellite Service).

HOW TO ENTER DATA FOR THIS ELEMENT...
With the element extension, you are able to identify the following information:

1. identify the actual name of the external element
2. enter the actual description or values for the media asset
3. 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).

• Dublin Core Metadata Element Set, Version 1.1
  http://purl.org/dc/elements/1.1
• DCMES 1.1 XML Schema Namespace
  http://dublincore.org/schemas/xmls/qdc/2006/01/06/dc.xsd
• PBCore Metadata Element Set, Version 1.1
  /PBCore/PBCoreNamespace.html
• More Metadata Examples

PBCore recommends that the organizational authority responsible for the existence, maintenance, and sustainability of a particular metadata descriptor be identified using the Namespace or Registration Authority associated with that metadata element. Best practice is to use an actual URL or URI.

There are several sources that discuss the unique identification of a particular metadata element within a metadata schema.

---

XML schemas to support the Guidelines for implementing Dublin Core in XML--Recommendation:

• http://dublincore.org/schemas/xmls/

---

Wikipedia article on XML Namespace:

• http://en.wikipedia.org/wiki/XML_Namespace

---

W3C Recommendation on Namespaces in XML:

• http://www.w3.org/TR/REC-xml-names/

---

W3C Review on XML Namespaces as a method to avoid metadata element conflicts:

• http://www.w3schools.com/xml/xml_namespaces.asp

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).