PRISM is a metadata vocabulary developed for the magazine, journal, and news publishing industries, providing a standardized framework for managing content through its lifecycle from creation to syndication and aggregation. Submitted as a W3C Member Submission by Idealliance, PRISM builds on Dublin Core and RDF to define a modular suite of metadata vocabularies, controlled vocabularies, XML markup specifications, and compliance profiles.
Background
PRISM was first introduced in 2001 by the PRISM Working Group under the auspices of IDEAlliance (now Idealliance). The impetus for its creation was the growing complexity of content management in multi-channel publishing environments where the same article or feature might be distributed in print, on the web, through aggregators, and in mobile applications. Publishers needed a common vocabulary to track content identity, rights, and repurposing permissions across these channels.
The standard has gone through several major versions. The most recent W3C Member Submission, dated 10 September 2020, presents the PRISM 3.0 Specification Package authored by Dianne Kennedy of Idealliance. PRISM 3.0 reorganized the documentation package into modular specifications and introduced the PRISM Source Vocabulary (PSV) for encoding semantically rich content based on HTML5.
Purpose & Scope
PRISM defines XML metadata vocabularies for syndicating, aggregating, post-processing, and multi-purposing content from magazines, news publications, newsletters, marketing collateral, catalogs, journals, and online feeds. The specification provides:
- A framework for interchange and preservation of content and metadata
- A collection of elements to describe content, including identification, publication context, rights, and classification
- A set of 38 controlled vocabularies listing permitted values for those elements
- Compliance profiles defining three levels of PRISM conformance
PRISM metadata can be expressed in XML, RDF/XML, or XMP, and the specification is modularized by namespace so publishers may adopt only the modules relevant to their business requirements.
Modular Structure
The PRISM 3.0 specification package includes the following major components:
| Module | Description |
|---|---|
| PRISM Basic Metadata (basic:) | Core article-level metadata elements |
| PRISM Advertising Metadata (prism-ad:) | Advertising elements drawn from AdsML, GWG, and Ad-ID |
| PRISM Contract Management (pccm:) | Contract and legal document metadata |
| PRISM Image Metadata | Image-specific metadata elements |
| PRISM Recipe Metadata (prm:) | Recipe encoding metadata |
| PRISM Rights Summary (prsm:) | Rights summary metadata |
| PRISM Usage Rights (pur:) | Usage rights elements |
| PRISM Aggregator Message (pam:) | XML message format for aggregator feeds |
| PRISM Source Vocabulary (psv:) | Semantically rich source content encoding based on HTML5 |
| PRISM Controlled Vocabulary Markup (pcv:) | Definitions for controlled vocabularies |
| PRISM Inline Markup (psm:) | Inline markup for aggregator messages |
Relationship to Other Standards
The PRISM specification explicitly builds on and relates to several other standards, as documented in the W3C Member Submission:
- Dublin Core (DC) -- PRISM uses Dublin Core and its relation types as the foundation for its metadata, recommending practices for using the DC vocabulary
- RDF -- PRISM Profile 2 compliance uses a simplified profile of RDF for its metadata framework
- XMP -- XMP is one viable option for implementing PRISM metadata across assets; PRISM Profile 3 enables PRISM/XMP compliant implementations
- DOI -- Digital Object Identifiers are used for permanent resource identification
- NewsML / NITF -- PRISM's controlled vocabularies can be used in NewsML; complementary to IPTC specifications
- RSS 1.0 -- Both are RDF-conformant XML applications with extensibility via namespaces
Serializations & Technical Formats
PRISM metadata documents are an application of XML. The specification supports three serialization approaches corresponding to its three compliance profiles: well-formed XML (Profile 1), RDF/XML (Profile 2), and XMP embedding (Profile 3). The specification also provides XSD schemas for contracts, crafts, images, PAM messages, PSV, recipes, and rights.
Governance & Maintenance
PRISM was developed and maintained by the PRISM Working Group under Idealliance. The specification was submitted to the W3C as a Member Submission, most recently in September 2020 under the W3C Document License. Copyright is held by Idealliance, Inc.
Notable Implementations
- Content aggregators such as ProQuest, EBSCO, and Gale use PRISM-based feeds for article-level metadata ingestion
- Adobe InDesign and XMP -- PRISM metadata can be embedded in XMP packets within PDF and image files
- Content management systems used by major magazine publishers have supported PRISM export for aggregator feeds