The Cover Pages [画像:The OASIS Cover Pages: The Online Resource for Markup Language Technologies]
SEARCH | ABOUT | INDEX | NEWS | CORE STANDARDS | TECHNOLOGY REPORTS | EVENTS | LIBRARY
Publishing Requirements for Industry Standard Metadata (PRISM)

Contents:

Overview

The Publishing Requirements for Industry Standard Metadata (PRISM) specification defines an XML metadata vocabulary for managing, aggregating, post-processing, multi-purposing and aggregating magazine, news, catalog, book, and mainstream journal content. PRISM recommends the use of certain existing standards, such as XML, RDF, the Dublin Core, and various ISO specifications for locations, languages, and date/time formats. In addition PRISM provides a framework for the interchange and preservation of content and metadata, a collection of elements to describe that content, and a set of controlled vocabularies listing the values for those elements.

Metadata is an exceedingly broad category of information covering everything from an article's country of origin to the fonts used in its layout. PRISM's scope is driven by the needs of publishers to receive, track, and deliver multi-part content. The focus is on additional uses for the content, so metadata concerning the content's appearance is outside PRISM's scope. PRISM focused on metadata for:

  • General-purpose description of resources as a whole
  • Specification of a resource's relationships to other resources
  • Definition of intellectual property rights and permissions
  • Expressing inline metadata — that is, markup within the resource itself

[June 19, 2004] "PRISM consists of two specifications. The PRISM Specification, itself, provides definition for the overall PRISM framework. A second specification, the PRISM Aggregator DTD is a new standard format for publishers to use for delivery of content to web sites and to aggregators and syndicators. It is an XML DTD that provides a simple, flexible model for transmitting content and PRISM metadata.

The PRISM Specification defines a collection of metadata elements for common publishing needs. But to apply them in specific situations, such as for delivery of content to web sites and secondary licensing partners, it is necessary to define formats, typically through a series of DTDs (Document Type Definitions), that combine PRISM metadata with content markup to support those specific processing objectives. The PRISM Aggregator Message DTD is such a specific standard.

The Aggregator XML tag set has been designed to meet the business requirements of the members of the Working Group. After examining numerous samples from every publisher, the group did an extensive review of all requirements and how an aggregator tag set could address them...

The PRISM Specification defines an XML metadata vocabulary for syndicating, aggregating, post-processing and multi-purposing magazine, news, catalog, book, and mainstream journal content. PRISM provides a framework for the interchange and preservation of content and metadata, a collection of elements to describe that content, and a set of controlled vocabularies listing the values for those elements..."

[October 06, 2000] "PRISM is an extensible XML metadata standard for syndicating, aggregating, post-processing and multi-purposing content from magazines, news, catalogs, books and mainstream journals. It is clear to most observers that the publishing industry needs a standard metadata vocabulary to realize the potential of online publishing and e-commerce in the publishing industry. PRISM provides a framework for the interchange and preservation of content and metadata. PRISM also provides a set of controlled vocabularies with which to describe the content being interchanged. Thus PRISM will provide a common interchange that greatly expands the market for licensed content."

[June 08, 2001] Description: "PRISM is a metadata specification originally intended for use in the magazine industry, where production, repurposing, aggregation, syndication, and archiving are topics of interest. Its utility extends beyond that industry, to any organization that needs to develop such functionality. Rather than reinvent the wheel, PRISM recommends certain practices, such as the use of XML, namespaces, RDF, and the Dublin Core. It then defines a few extra namespaces for more specific information. The 1.0 version of the specification is available from www.prismstandard.org. Interwoven, and several of our partners, have already announced support of the PRISM spec. Other vendors, and content providers such as Time Inc. and Getty Images, have too..." [posting from Ron Daniel 2001年06月08日]

Relationship of PRISM to other standards:

PRISM Rights Language (PRL). "Collections of PRL statements are known as PRL expressions. The purpose of a PRL expression is to determine if a person or organization may or may not make use of a resource in a particular way. PRL expressions evaluate to a Boolean value that indicates if a particular use is allowed (if the expression evaluates to true) or not (if the expression evaluates to false).... Licensing content for reuse is a major source of revenue for many publishers. Conforming to licensing agreements is a major cost -- not only to the licensee of the content but also to the licensor. For these reasons, PRISM provides elements and controlled vocabularies for the purpose of describing the rights and permissions granted to the receiver of content. The PRISM specification provides those elements in two namespaces. Basic, commonly used, elements are defined as part of the PRISM namespace. A separate namespace is defined for the elements in the PRISM Rights Language (PRL). Since the field of Digital Rights Management (DRM) is evolving so quickly, the working group decided it would be premature to recommend one of the current DRM standards for rights information, such as the eXtensible rights Markup Language or Open Digital Rights Language. The working group expects that a rights management language will eventually become an accepted standard. As an interim measure, the working group focused on specifying a small set of elements that would encode the most common rights information to allow interoperable exchange of basic rights information. To do this, the PRISM rights language makes a couple of simplifying assumption. It assumes that the sender and receiver of content are engaged in a business relation. It may be a formal contract or an informal provision of freely redistributable content. One of the parties may not know the other. Nevertheless, a relation exists and if needed we could make up an identifier for it, such as the contact number. PRL also assumes that its purpose is to reduce the costs of conformance to that relation. The working group explicitly rejected imposing any requirements on enforcing trusted commerce between unknown parties. Instead, the emphasis is on reducing the cost of compliance in common situations. Organizations implementing DRM functionality are advised that several companies have obtained patents on various techniques for implementing such functionality. Implementers of DRM functionality may wish to investigate further, the PRISM working group takes no stance on such patents nor has it investigated it... The PRISM rights and permissions vocabulary is designed to facilitate reuse and clearance processes for parties with established business relationships by explicitly specifying the rights and/or restrictions connected with a resource. PRISM is NOT concerned with digital rights enforcement. PRISM does not specify policy or provide instructions to trusted viewers and repositories on how they should behave. PRISM also does not specify fee or payment details... The design goals of rights and permissions are: (1) To be able to describe reuse rights in a precise and consistent manner; (2) To make simple cases such as no rights or unrestricted use simple to specify; (3) To provide the capability to indicate common types of uses or restriction; (4) To allow for graceful evolution to future accepted standards for specifying rights..." For related work, see OASIS Rights Language. [from PRISM: Publishing Requirements for Industry Standard Metadata" ]

Specifications for Aggregation and Syndication

Principal References

General: Articles, Papers, News, Reports

SEARCH
Advanced Search
ABOUT
Site Map
CP RSS Channel
Contact Us
Sponsoring CP
About Our Sponsors

NEWS
Cover Stories
Articles & Papers
Press Releases

CORE STANDARDS
XML
SGML
Schemas
XSL/XSLT/XPath
XLink
XML Query
CSS
SVG

TECHNOLOGY REPORTS
XML Applications
General Apps
Government Apps
Academic Apps

EVENTS
LIBRARY
Introductions
FAQs
Bibliography
Technology and Society
Semantics
Tech Topics
Software
Related Standards
Historic
Last modified: August 02, 2007

Hosted By
OASIS - Organization for the Advancement of Structured Information Standards

Sponsored By

IBM Corporation
ISIS Papyrus
Microsoft Corporation
Oracle Corporation

Primeton

XML Daily Newslink
Receive daily news updates from Managing Editor, Robin Cover.

Newsletter Subscription
Newsletter Archives
[画像:Globe Image]

Document URI: http://xml.coverpages.org/prism.htmlLegal stuff
Robin Cover, Editor: robin@oasis-open.org


AltStyle によって変換されたページ (->オリジナル) /