The PBCore metadata standard (Public Broadcasting Metadata Dictionary) was created by the public broadcasting community in the United States of America for use by public broadcasters and related communities that manage audiovisual assets, including libraries, archives, independent producers, etc. PBCore is organized as a set of specified fields that can be used in database applications, and it can be used as a data model for media cataloging and asset management systems. As an XML schema, PBCore enables data exchange between media collections, systems and organizations.
Initial development funding for PBCore was provided by the Corporation for Public Broadcasting starting in 2001.
1.0 – April 2005
PBCore Version 1.0 defined 48 metadata elements which combined to describe a media asset or resource's intellectual content, creation, creators, usage, permissions, constraints, use obligations, and its form or format in the physical or digital realm.
1.1 – January 2007
PBCore Version 1.1 enhanced the binding of related metadata elements (such as Title and TitleType) into new, hierarchically-organized "Element Containers." In that arrangement, each Element Container collects and houses associated "child" Elements that are thematically related. Basically, what was a "flat" arrangement of the 48 PBCore elements became a more "nested" structure of 53 elements, arranged in 15 containers and 3 sub-containers.
1.2.1 – December 2008
PBCore version 1.2.1 was published to better accommodate the possibility that a media asset may have multiple instantiations with various technical attributes. A new container called "pbcoreEssenceTrack" contains all other new elements to express different attributes associated with multiple instantiations. PBCore v1.2.1 used 61 elements organized into 15 containers and 4 sub-containers.
1.3 – August 2010
PBCore version 1.3 added a new top-level element, a new attribute of string values, and removed the previous requirement to describe one or more instantiations of any asset. Its new element, "pbcoreAssetType," could be used to explicitly declare the asset's broad business purpose, and its new attribute "source" could help clarify the text value of an element, much like the attribute "version" has done. PBCore v1.3 used 62 elements organized into 15 containers and 4 sub-containers.
2.0 - November 2011
PBCore version 2.0 was released at the annual conference of the Association of Moving Image Archivists in November 2011. This was a major revision of the schema, with the addition of two new top-level elements:
Another significant change in PBCore 2.0 was the addition of optional attributes for many elements, including source, ref, version, annotation, startTime, endTime, and timeAnnotation. The source attribute allows for the specification of a source of subject terms and other values, while the ref attribute may contain a URI for the subject term itself. The version and annotation attributes allow for the inclusion of versioning for the value, and narrative information intended to clarify the nature of the data used in the element. The startTime, endTime, and timeAnnotation attributes allow for the inclusion of time-based metadata, for example the location in the media timeline when a subject, name, or location was relevant. A third major change to the schema was the addition of pbcorePart as an optional element of the root element pbcoreDescriptionDocument, and recursively another pbcorePart element, which allows for defining segments, stories, or episodes of a larger media work.
As part of the American Archive of Public Broadcasting initiative, PBCore entered a new phase of development in 2014. The American Archive team established a PBCore Advisory Subcommittee of the Association of Moving Image Archivists to reassess the schema, continue outreach to users and potential adopters, create resources for the PBCore community and improve the website.
The PBCore standard is built on the foundation of the Dublin Core (ISO 15836), an international standard for resource discovery, and has been reviewed, though not endorsed, by the Dublin Core Metadata Initiative Usage Board. [1]
PBCore extends Dublin Core by adding a number of elements specific to audiovisual (AV) assets. These AV assets can be physical analog media items, or digital media objects. PBCore provides a standard for cataloging and describing media objects in three general ways:
PBCore provides an XSD allowing validation of PBCore XML records. PBCore XML can be used to exchange detailed metadata about media assets, and optionally the media assets themselves, among systems configured for the PBCore standard. The schema is used by organizations within the public media community as well as in archives and libraries across the world.
Although a PBCore record potentially contains a great many elements, the only required elements are any one of the root elements, pbcoreIdentifier, and pbcoreTitle
Root Elements
Intellectual Content
Intellectual Property
Extensions
Instantiation
The Dublin Core vocabulary, also known as the Dublin Core Metadata Terms (DCMT), is a general purpose metadata vocabulary for describing resources of any type. It was first developed for describing web content in the early days of the World Wide Web. The Dublin Core Metadata Initiative (DCMI) is responsible for maintaining the Dublin Core vocabulary.
Material Exchange Format (MXF) is a container format for professional digital video and audio media defined by a set of SMPTE standards. A typical example of its use is for delivering advertisements to TV stations and tapeless archiving of broadcast TV programs. It is also used as part of the Digital Cinema Package for delivering movies to commercial theaters.
MPEG-7 is a multimedia content description standard. It was standardized in ISO/IEC 15938. This description will be associated with the content itself, to allow fast and efficient searching for material that is of interest to the user. MPEG-7 is formally called Multimedia Content Description Interface. Thus, it is not a standard which deals with the actual encoding of moving pictures and audio, like MPEG-1, MPEG-2 and MPEG-4. It uses XML to store metadata, and can be attached to timecode in order to tag particular events, or synchronise lyrics to a song, for example.
XBRL is a freely available and global framework for exchanging business information. XBRL allows the expression of semantics commonly required in business reporting. The standard was originally based on XML, but now additionally supports reports in JSON and CSV formats, as well as the original XML-based syntax. XBRL is also increasingly used in its Inline XBRL variant, which embeds XBRL tags into an HTML document. One common use of XBRL is the exchange of financial information, such as in a company's annual financial report. The XBRL standard is developed and published by XBRL International, Inc. (XII).
Learning Object Metadata is a data model, usually encoded in XML, used to describe a learning object and similar digital resources used to support learning. The purpose of learning object metadata is to support the reusability of learning objects, to aid discoverability, and to facilitate their interoperability, usually in the context of online learning management systems (LMS).
Encoded Archival Description (EAD) is a standard for encoding descriptive information regarding archival records.
The Department of Defense Discovery Metadata Specification is a Net-Centric Enterprise Services (NCES) metadata initiative. DDMS is loosely based on the Dublin Core vocabulary. DDMS defines discovery metadata elements for resources posted to community and organizational shared spaces. It is sometimes (incorrectly) referred to as DoD Discovery Metadata Standard. The project focuses both on the process of developing a central taxonomy for metadata, and defining a way of discovering resources by their metadata using that taxonomy.
The e-Government Metadata Standard, e-GMS, is the UK e-Government Metadata Standard. It defines how UK public sector bodies should label content such as web pages and documents to make such information more easily managed, found and shared.
This article describes the technical specifications of the OpenDocument office document standard, as developed by the OASIS industry consortium. A variety of organizations developed the standard publicly and make it publicly accessible, meaning it can be implemented by anyone without restriction. The OpenDocument format aims to provide an open alternative to proprietary document formats.
RDFa or Resource Description Framework in Attributes is a W3C Recommendation that adds a set of attribute-level extensions to HTML, XHTML and various XML-based document types for embedding rich metadata within Web documents. The Resource Description Framework (RDF) data-model mapping enables its use for embedding RDF subject-predicate-object expressions within XHTML documents. It also enables the extraction of RDF model triples by compliant user agents.
Digital Item is the basic unit of transaction in the MPEG-21 framework. It is a structured digital object, including a standard representation, identification and metadata.
Geospatial metadata is a type of metadata applicable to geographic data and information. Such objects may be stored in a geographic information system (GIS) or may simply be documents, data-sets, images or other objects, services, or related items that exist in some other native environment but whose features may be appropriate to describe in a (geographic) metadata catalog.
The Metadata Encoding and Transmission Standard (METS) is a metadata standard for encoding descriptive, administrative, and structural metadata regarding objects within a digital library, expressed using the XML schema language of the World Wide Web Consortium (W3C). The standard is maintained as part of the MARC standards of the Library of Congress, and is being developed as an initiative of the Digital Library Federation (DLF).
PREservation Metadata: Implementation Strategies (PREMIS) is the de facto digital preservation metadata standard.
Metadata is "data that provides information about other data", but not the content of the data itself, such as the text of a message or the image itself. There are many distinct types of metadata, including:
EPUB is an e-book file format that uses the ".epub" file extension. The term is short for electronic publication and is sometimes stylized as ePUB. EPUB is supported by many e-readers, and compatible software is available for most smartphones, tablets, and computers. EPUB is a technical standard published by the International Digital Publishing Forum (IDPF). It became an official standard of the IDPF in September 2007, superseding the older Open eBook (OEB) standard.
A metadata standard is a requirement which is intended to establish a common understanding of the meaning or semantics of the data, to ensure correct and proper use and interpretation of the data by its owners and users. To achieve this common understanding, a number of characteristics, or attributes of the data have to be defined, also known as metadata.
The Office Open XML file formats are a set of file formats that can be used to represent electronic office documents. There are formats for word processing documents, spreadsheets and presentations as well as specific formats for material such as mathematical formulas, graphics, bibliographies etc.
The SMMCorestandard is Singapore's national metadata standard for B2B content exchange. In 2008, seeing a need for the adoption of best practices and standards for managing the storage of digital content through a set of metadata frameworks, the Infocomm Development Authority of Singapore (IDA) organized an industry roundtable through which Mediacorp chaired the Metadata Standardization Subgroup, working with other industry providers, such as Disney and Ascent Media, to define a set of practices for metadata used in the local media industry. Initially, SMMCore was built on the foundation of PBCore. However, with its second revision in 2011, harmonization work has been carried out with the European Broadcasting Union (EBU), revising the SMMCore framework to be built on the foundation of the EBU Core. Harmonization allows for support from a larger metadata community of people versed in the field, access to knowledge on semantic web and linked data for which EBU and therefore SMMCore are ready, adoption by the industry, sharing resources in research, development, and maintenance of the metadata specifications.
The SAML metadata standard belongs to the family of XML-based standards known as the Security Assertion Markup Language (SAML) published by OASIS in 2005. A SAML metadata document describes a SAML deployment such as a SAML identity provider or a SAML service provider. Deployments share metadata to establish a baseline of trust and interoperability.