Finally — an XML Markup Solution for Design-Based Publishers: Introducing the PRISM Source Vocabulary
“Until the tablet-publishing tsunami hit, design-based publications were able to justify their labor-intensive design-based publication process.
[…] We have come to believe the Source is the Solution. We must capture and store platform-agnostic content as early as possible.
[…] Source content must be semantically rich enough to enable the publisher to select content and automate layout and delivery to a wide variety of publishing platform in platform-native formats.
[…] In order to refine what we mean by the generic term article, the PRISM Content Type Controlled Vocabulary has been developed. […] Some content types that describe the unit-of-storage include an advertisement, article, blog entry, book chapter, cover, masthead, introduction and navigational aid.
[…] The Where Used metadata block allows for usage tracking. […] PSV allows for tracking the platform and even the device where the content was published. PSV also allows for tracking the section or page of the publication where the content appeared. Altogether, PSV offers nearly 40 optional fields to describe where content was used.
[…] The Usage Rights metadata block provides optional metadata fields that can be used by publishers to track usage rights of content in a repository. The 15 optional metadata fields in this block are based on the PRISM Usage Rights Metadata Specification.
[…] Unlike EPUB3, PSV makes no extensions to HTML5 and has no restrictions. PSV recommends that the new HTML5 <article tag be used as the root element for any content unit.
[…] PSV recommends a number of PRISM semantic classes that you can use to qualify any HTML5 element. Examples include box, caption, dateline, credit, and pull quote.”
(Via Simon St. Laurent at O’Reilly Radar – Applying markup to complexity).