Version 1.0 the PRISM Source Vocabulary PAM to PSV Guide

Version 1.0

The PRISM Source Vocabulary PAM to PSV Guide

September 27, 2012

PRISM® and nextPub® are registered trademarks of the International Digital Enterprise Alliance, Inc. (IDEAlliance). This document may be downloaded and copied provided that the above copyright notice and this Notice are included on all such copies. This document itself may not be modified in any way, except as needed for the purpose of developing International Digital Enterprise Alliance, Inc. (“IDEAlliance”) specifications. Use of the specification or standard set forth in this document shall not create for the user any rights in or to such specification or standard or this document, which rights are exclusively reserved to IDEAlliance or its licensors or contributors. Use of this document and any specification or standard contained herein is voluntary. By making use of this document or any specification or standard contained herein, the user assumes all risks and waives all claims against IDEAlliance, its licensors and contributors. By making this document available, IDEAlliance is not providing any professional services or advice to any person or entity. Any person or entity utilizing this document or any specification or standard contained herein should rely upon the advice of a competent professional before using any such information. NO WARRANTY, EXPRESSED OR IMPLIED, IS MADE REGARDING THE ACCURACY, ADEQUACY, COMPLETENESS, LEGALITY, RELIABILITY OR USEFULNESS OF ANY INFORMATION CONTAINED IN THIS DOCUMENT OR IN ANY SPECIFICATION OR STANDARD OR OTHER PRODUCT MADE AVAILABLE BY IDEALLIANCE. THIS DOCUMENT AND THE INFORMATION CONTAINED HEREIN AND INCLUDED IN ANY SPECIFICATION OR STANDARD OR OTHER PRODUCT OR SERVICE OF IDEALLIANCE IS PROVIDED ON AN "AS IS" BASIS. IDEALLIANCE DISCLAIMS ALL WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ANY ACTUAL OR ASSERTED WARRANTY OF NON-INFRINGEMENT OF PROPRIETARY RIGHTS, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL IDEALLIANCE, ITS LICENSEES, CONTRIBUTORS OR THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, REPRESENTATIVES, SUPPLIERS OR CONTENT OR SERVICE PROVIDERS BE LIABLE FOR DAMAGES OF ANY KIND, INCLUDING WITHOUT LIMITATION, DIRECT, INDIRECT, COMPENSATORY, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION DAMAGES FROM DATA LOSS OR BUSINESS INTERRUPTION) EVEN IF MADE AWARE OF THE POSSIBILITY OF SUCH DAMAGES, WHETHER IN AN ACTION UNDER CONTRACT, TORT OR ANY OTHER THEORY, ARISING OUT OF OR IN CONNECTION WITH THE USE, INABILITY TO USE OR PERFORMANCE OF THIS DOCUMENT, THE SPECIFICATION OR STANDARD CONTAINED HEREIN, OR ANY OTHER DOCUMENT OR SPECIFICATION OR STANDARD MADE AVAILABLE BY IDEALLIANCE. Some states do not allow the disclaimer or limitation of damages, so the disclaimers set forth above apply to the maximum extent permitted under applicable law. IDEAlliance takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed or implicated with respect to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available. IDEAlliance does not represent that it has made any effort to identify any such rights. Information on IDEAlliance's procedures with respect to rights in IDEAlliance specifications can be found at the IDEAlliance website at www.idealliance.org. Copies of third-party claims of rights, assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification, can be obtained from the President of IDEAlliance at [email protected]. IDEAlliance requests interested parties to disclose any copyrights, trademarks, service marks, patents, patent applications, or other proprietary or intellectual property rights which may cover technology that may be required to implement this specification. Please address the information to the President of IDEAlliance at [email protected]. PAM to PSV Guide Table of Contents 1 Introduction ...... 1

1.1 Purpose and Scope ...... 1

1.2 Relationship of PSV to PRISM ...... 1

1.3 Relationship of nextPub to PAM ...... 1

1.4 The PSV Namespace ...... 2

1.5 Diagrams ...... 2

1.6 The PSV Documentation Package ...... 3

1.7 The PRISM Documentation Package ...... 4

1.7.1 General Documents ...... Error! Bookmark not defined.

1.7.2 PRISM Metadata Specifications ...... Error! Bookmark not defined.

1.7.3 PRISM Controlled Vocabulary Specifications ...... Error! Bookmark not defined.

1.7.4 PRISM Aggregator Message Markup Specification ...... Error! Bookmark not defined.

1.7.5 PRISM Inline Markup Specification ...... Error! Bookmark not defined.

1.8 PSV Content Management Schema ...... 4

1.9 Other PSV Schemas ...... 7

2 Tagging Overview ...... 9

2.1 Unit of Content Tagging ...... 9

2.1.1 Content Types ...... 9

2.1.2 Genres ...... 9

2.2 HTML5 PSV vs. XHTML PAM ...... 10

2.2.1 Elimination of pam: and pim: Elements ...... 10

2.2.2 Handling the

2.2.3 Addition of New HTML5 Elements ...... 11

2.3 Comparison of High Level Structures ...... 11

2.3.1 PAM Structure ...... 11

2.3.2 PSV Structure ...... 12

3 Tagging Article Metadata ...... 13

3.1 Comparison of PSV Metadata to PAM Metadata ...... 13

i PAM to PSV Guide 3.2 New PSV Metadata Fields ...... 14

3.2.1 Content Type Field ...... 14

3.2.2 Unique ID Field ...... 14

3.2.3 Relations Metadata Fields ...... 15

3.2.4 Usage Rights Metadata Fields ...... 15

3.2.5 Component Metadata Fields ...... 16

3.2.6 Where Used Metadata Fields ...... 17

3.2.6.1 Aggregation Information Metadata ...... 17

3.2.6.2 Publication Information ...... 18

3.2.6.3 Issue Information ...... 18

3.2.6.4 Article Information ...... 19

3.2.6.5 Website Information...... 20

3.2.6.6 Book Information ...... 20

3.2.6.7 Chapter Information ...... 21

3.2.6.8 Blog Information ...... 21

3.2.6.9 Blog Entry Information ...... 21

3.2.7 PAM to PSV Mapping Table ...... 22

3.2.8 Example Metadata Tagging ...... 24

4 Tagging Content ...... 27

4.1 What Does this Mean? ...... 27

4.2 Sample Coding for Body Content ...... 27

5 Tagging Media ...... 29

5.1 About PAM Media ...... 29

5.2 About nextPub Media ...... 29

5.3 Sample Coding ...... 30

5.4 About Tagging Media Metadata in nextPub ...... 31

Appendix A PAM Sample Tagging ...... 35

Appendix B Sample PSV Tagging ...... 41

ii PAM to PSV Guide

i PAM to PSV Guide

1 INTRODUCTION

1.1 Purpose and Scope The IDEAlliance PSV Specification defines an encoding for XML elements and attributes in the psv: namespace to encode semantically rich source content. Metadata fields and values used in this specification are drawn from the IDEAlliance PRISM Metadata and Controlled Vocabulary Specifications. This Guide provides insights for those currently using the PRISM Aggregator Message about how PAM content can be expressed in PSV XML markup and about how these two markup schemas are different.

1.2 Relationship of PSV to PRISM PSV builds upon the foundation of PRISM Specifications. PSV defines XML structures for tagging source content, but it does not define its own metadata fields or controlled vocabularies. nextPub is built upon PRISM and relies on the metadata fields and controlled vocabularies defined by PRISM. Of necessity, PSV will require an update to the current version of PRISM because new metadata fields and controlled vocabularies and terms must be added to support PSV functionality. Therefore PRISM 3.0 will be published simultaneously with the publication of nextPub 1.0 and will be highly referenced by the nextPub XML Source Specification. See Figure 1.1.

1.3 Relationship of nextPub to PAM PAM is the PRISM Aggregator Message. PAM is an XML tag set built on the foundation of PRISM metadata and controlled vocabularies. The use case for PAM was originally to encode magazine articles in XML to deliver content to aggregators. While some publishers currently use PAM XML as a content source, that was not the original intent. PAM is an application of PRISM, but PAM and PRISM are not synonymous. PAM is an XML tag set that uses PRISM metadata for a very specific purpose while PRISM remains the core specification for metadata and controlled vocabularies. See Figure 1.1.

1 PAM to PSV Guide

Figure 1.1 Relationship of PRISM to PSV and PAM

1.4 The PSV Namespace Dublin Core, PRISM, PRISM Usage Rights, PRISM Recipe Metadata and other relevant PRISM metadata namespaces along with the new psv: namespace will be utilized as appropriate. XML Structures unique to this specification for content encoding will be given the namespace nextPub: The recommended namespace for nextPub markup is: xmlns:psv =”http://prismstandard.org/namespaces/psv/1.0/”

1.5 Diagrams

In this Specification, the PSV XML model and the PAM XML models are illustrated using model diagrams produced with the XML Spy product. These diagrams show the element and attribute structures.

The legend for reading XML model diagrams is shown in Figure 1.2. Elements that are required by the model are shown in a solid box. Elements that are optional are shown in a dotted box. Likewise attributes may be required (solid box) or optional (dotted box). A repeatable occurrence of elements is indicated by numbers below each element box to the right.

The diagrams also indicate how elements are assembled. When building some models, elements may occur in a sequence with a specified order. Other models provide a choice from among a number of elements. The legend in Figure 1.2 shows the connectors for sequence and choice.

2 PAM to PSV Guide

Figure 1.2 Legend for XML Diagrams

Note:There is no official schema for HTML5. However, nextPub has developed a schema for the PRISM Source Vocabulary Specification. This schema is specifically designed to be more restrictive than a true HTML5 schema would be in order to make source content encoding and transformations to delivery channel formats much more straightforward. The design goal is to define a valid HTML5 subset for the content encoding portion of nextPub.

1.6 The PSV Documentation Package The nextPub Working Group has developed a series of specifications collectively known as the PRISM Source Vocabulary. The use case for PSV is to encode semantically rich content that can be transformed and delivered to any platform in that platform-native format. This Specification is made up of a modular documentation package that builds on PRISM 3.0 and HTML5. Over time new modules may be added to the documentation package. The documentation package for the nextPub PRISM Source Vocabulary Specification Version 1.0 consists of:

3 PAM to PSV Guide

Document Description

PRISM Source Vocabulary Specification Overview The Introduction to the PRISM Source [PSVSO] Vocabulary provides an introduction http://www.prismstandard.org/specifications/psv/ and a non-technical overview of the 1.0/PSV_overview.pdf PRISM Source Vocabulary. or http://www.prismstandard.org/specifications/psv/ 1.0/PSV_overview.htm PRISM Source Vocabulary Specification [PSVS] The PRISM Source Vocabulary http://www.prismstandard.org/specifications/psv/ Specification defines semantically rich 1.0/PSV.pdf for source metadata and content or markup that can be transformed and http://www.prismstandard.org/specifications/psv/ served to a wide variety of output 1.0/PSV.htm devices including eReaders, mobile tablet devices, smart phones and print. PRISM Source Vocabulary Markup Specification The PSV Markup Specification [PSVMS] documents the XML tags in the PSV http://www.prismstandard.org/specifications/psv/ namespace that are used to encode 1.0/PSV_markkup.pdf XML Source Content. or http://www.prismstandard.org/specifications/psv/ 1.0/PSV_markup.htm PAM to PSV_Guide [PAMPSVGUIDE] This Guide documents mappings from http://www.prismstandard.org/specifications/psv/ PAM XML to PSV XML. It is normative 1.0/PAM_PSV.pdf only. or http://www.prismstandard.org/specifications/psv/ 1.0/PAM_PSV.htm

1.7 The PRISM Documentation Package Because PSV is built on PRISM 3.0, there is a close relationship between the two specifications. In fact, access to the PRISM 3.0 Documentation Package is critical to the implementation of PSV. The PRISM 3.0 Documentation Package consists of:

1.8 The PRISM 3.0 Documentation Package The PRISM Documentation Package consists of: Because PSV is built on PRISM 3.0, there is a close relationship between the two specifications. In fact, access to the PRISM 3.0 Documentation Package is critical to the implementation of PSV. The PRISM 3.0 Documentation Package consists of:

1.8.1 General Documents

This is a set of general or overview documents that apply to PRISM.

Document Description

PRISM Introduction [PRISMINT] Overview, background, purpose and

4 PAM to PSV Guide

Document Description http://www.prismstandard.org/specifications/3.0/ scope of PRISM; examples; contains PRISM_introduction_3.0.pdf no normative material. or http://www.prismstandard.org/specifications/3.0/ PRISM_introduction_3.0.htm PRISM Compliance [PRISMCOMP] Describes three profiles of PRISM http://www.prismstandard.org/specifications/3.0/ compliance for content and systems; includes normative material. PRISM_compliance_3.0.pdf or http://www.prismstandard.org/specifications/3.0/ PRISM_compliance_3.0.htm

1.8.2 PRISM Metadata Specifications

This is the set of documents that outline the prism metadata fields and values by PRISM metadata category. PRISM has modularized its metadata specification by namepace so users may pick those modules that meet their unique business requirements without having to implement the entire PRISM specification.

Document Description

The PRISM Basic Metadata Specification [PRISMBMS] Describes the basic metadata elements http://www.prismstandard.org/specifications/3.0/ contained in the PRISM namespace to PRISM_Basic_Metadata_3.0.pdf describe article content; includes or normative material. http://www.prismstandard.org/specifications/3.0/ PRISM_Basic_Metadata_3.0.htm PRISM Advertising Metadata Specification Describes advertising metadata [PRISMADMS] elements including those drawn from http://www.prismstandard.org/specifications/3.0/ AdsML, GWG and Ad-ID; includes PRISM_Advertising_Metadata_3.0.pdf normative material. or http://www.prismstandard.org/specifications/3.0/ PRISM_Advertising_Metadata_3.0.htm The PRISM Subset of Dublin Core Metadata Describes the metadata elements from Specification [PRISMDCMS] the Dublin Core namespace that are http://www.prismstandard.org/specifications/3.0/ included in PRISM; includes normative PRISM_Dublin_Core_Metadata_3.0.pdf material. or http://www.prismstandard.org/specifications/3.0/ PRISM_Dublin_Core_Metadata_3.0.htm The PRISM Image Metadata Specification [PRISMIMS] Describes the metadata elements http://www.prismstandard.org/specifications/3.0/ contained in the PRISM Metadata for PRISM_Image_Metadata_Specification_3.0.pdf Images Namespace and other related or image namespaces, includes normative http://www.prismstandard.org/specifications/3.0/ material. PRISM_Image_Metadata_Specification_3.0.htm

5 PAM to PSV Guide

Document Description

The PRISM Recipe Metadata Specification Describes the metadata elements [PRISMRMS] contained in the PRISM Recipe http://www.prismstandard.org/specifications/3.0/ Metadata Namespace, includes PRISM_Recipe_Metadata_3.0.pdf normative material or http://www.prismstandard.org/specifications/3.0/ PRISM_Recipe_Metadata_3.0.htm The PRISM Usage Rights Metadata Specification Describes the metadata elements [PRISMURMS] contained in the PRISM Usage Rights http://www.prismstandard.org/specifications/3.0/ Namespace; includes normative PRISM_Usage_Rights_Metadata_3.0.pdf material. This namespace will supersede or elements in both the prism: and prl: http://www.prismstandard.org/specifications/3.0/ namespaces in version 3.0 of the PRISM_Usage_Rights_Metadata_3.0.htm specification.

1.8.3 PRISM Aggregator Message Markup Specification

This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message. At the time of the publication of the Introduction to PRISM, the PAM Message remains at version 2.1. This set of documents includes:

Document Description

The PRISM PAM Markup Specification Describes the XML elements and [PRISMPAMMS] attributes used to encode the PRISM http://www.prismstandard.org/specifications/2.1/ Aggregator Message from both the PRISM_PAM_Markup_2.1.pdf pam: and pim: namespaces; includes or normative material. http://www.prismstandard.org/specifications/2.1/ PRISM_PAM_Markup_2.1.htm

1.8.4 PRISM Inline Markup Specification

This module documents the PRISM Inline Markup Elements and Attributes for use with the PRISM Aggregator Message. This set of documents includes:

Document Description

The PRISM Inline Markup Specification [PRISMIMS] Describes the XML elements used to http://www.prismstandard.org/specifications/2.1/ encode the inline markup for the PRISM PRISM_PIM_Markup_Specification 3.0.pdf Aggregator Message. Includes or normative material. http://www.prismstandard.org/specifications/2.1/ PRISM_PIM_Markup_Specification 3.0.htm

6 PAM to PSV Guide

1.8.5 PRISM Controlled Vocabulary Specifications

These modules are new with PRISM 3.0. All controlled vocabularies and their terms are documented in this publication set.

Document Description

The PRISM Controlled Vocabulary Markup Describes the metadata fields in the Specification [PRISMCVMS] PRISM Controlled Vocabulary http://www.prismstandard.org/specifications/3.0/ Namespace that can be used to describe PRISM_Controlled_Vocabulary_Markup_3.0.pdf a controlled vocabulary. Actual PRISM or controlled vocabularies are now placed http://www.prismstandard.org/specifications/3.0/ in the PRISM Controlled Vocabularies PRISM_Controlled_Vocabulary_Markup_3.0.htm Specification [PRISMCVS] The PRISM Controlled Vocabularies Specification The PRISM Controlled Vocabularies are [PRISMCVS] now documented in this document. http://www.prismstandard.org/specifications/3.0/ PRISM_CV_Spec_3.0.pdf or http://www.prismstandard.org/specifications/3.0/ PRISM_CV_Spec_3.0.htm

1.9 PSV Content Management Schema In order to assist implementers develop a PSV-based federated content management solution, the nextPub Working Group is providing an XML Schema (XSD) that can serve as the basis for the design of a PSV content repository. Note: The PSV CM schema is not designed for tagging content. It is provided simply to serve as a basis for the design of a content repository. Metadata building blocks from this schema can be combined with HTML5 by publishers who wish to develop a hybrid PSV metadata and content tagging schema.

1.10 Other PSV Schemas Because PSV is a flexible framework, it supports many different use case scenarios. A different schema, using the PSV metadata fields and content encoding can be developed for each different use case. In order to assist PSV implementers, the nextPub Working Group is planning to provide a number of XML Schemas (XSDs) to support common use cases including tagging an article and transmitting articles to content aggregators. These PSV sample schemas will be available from the nextPub website (http://www.nextpub.org) and documented in the nextPub PSV Implementation Guide that will be published following the publication of this specification..

PAM to PSV Guide

2 TAGGING OVERVIEW

This section provides an overview of source encoding for PAM and PSV. The philosophy for moving from the existing PRISM Aggregator Message will be discussed. Then a high-level overview of the source structure will be highlighted.

2.1 Unit of Content Tagging When defining PSV source content tagging, a new concept, the content type was developed. In fact PSV XML tagging requires that the unit of storage, or prism:contentType must be specified. In addition the prism:genre has been updated so that prism:genre is used to refine the prism:contentType. For the purposes of mapping PAM to PSV a direct mapping with the article as the default unit of content is assumed. Note: The use cases for nextPub have expanded the scope of PRISM metadata fields and controlled vocabularies beyond the scope of magazines, newsletters and journals. PAM mapping will only consider those fields and controlled vocabulary terms that relate to the use case for PAM and that is magazines.

2.1.1 Content Types

The use cases for nextPub have expanded the scope of PRISM beyond the article. This, in turn, has introduced the concept of a prism:contentType to the PRISM Specification. Content Type has not been included in PAM for the purposes of marking up magazine content for delivery to aggregators as the assumption is that PAM will remain as a method for delivering article content to aggregators and will not extend to other content types.

2.1.2 Genres

The PRISM Genre Controlled Vocabulary has been enhanced to refine the intellectual description of core content units in PRISM 3.0 and for PSV. Because PAM assumes only the delivery of article content, only the genre that can refine the description of an article need be considered. Again, since the scope of PSV is broader than the scope for PAM, only a limited number of the new PRISM 3.0 genre terms make sense for use with PAM markup. Those fields include:

• abstract (refines article) • adaptation (refines article) • analysis (refines article) • autobiography (refines article) • biography (refines article) • calendar (refines article) • chronology (refines article) • clarification (refines article) • column (refines article) • correction (refines article) • coverStory (refines article) • coverPackageArticle (refines article) • department (refines article)

9 PAM to PSV Guide

• electionResults (refines article) • essay (refines article) • excerpt (refines article) • fashionShoot (refines article) • faq (refines article) • feature (refines article) • featurePackageArticle (refines article) • fiction (refines article) • financialStatement (refines article) • interview (refines article) • letters (refines article) • list (refines article) • newsBulletin (refines article) • notice (refines article) • obituary (refines article) • opinion (refines article) • photoEssay (refines article) • profile (refines article) • qAndA (refines article) • quotation (refines article) • ranking (refines article) • reprint (refines article) • resources (refines article) • response (refines article) • review (refines article) • schedule (refines article) • supplementArticle (refines article) • transcript (refines article) • userComments (refines article) • userReview (refines article) • wireStory (refines article)

2.2 HTML5 PSV vs. XHTML PAM When work began on the nextPub XML Source Specification, the majority of participants favored retaining PRISM/PAM XHTML as the source format and extending that source to take into account functionality required by the new use cases for content delivered to tablets, eReaders, smart phones and beyond. However, as work progressed and transforms into the two key target delivery formats were considered, it became apparent that nextPub needed to be based on HTML5 rather than XHTML as PAM is. Benefits of basing nextPub on HTML5 included the ability to easily transform into key delivery formats for new digital devices and the enhanced ability to handle rich media. So what does this mean?

2.2.1 Elimination of pam: and pim: Elements

When PAM tagging was designed, the PRISM Working Group extended XHTML with new XML elements in the pam: namespace.

10 PAM to PSV Guide

For PSV we made the decision that we will NOT extend the HTML5 tag set that native HTML5 browsers and processors are expecting. Hence this leads to some changes in how PSV article content is tagged when compared to PAM tagging. And it means we no longer have use of

2.2.2 Handling the

HTML5 has a quote (. Note that browsers often put quotation marks in the display when

2.2.3 Addition of New HTML5 Elements

When designing PSV tagging schema, the decision was made to leverage several new HTML5 tags. These new tags include:

•

2.3 Comparison of High Level Structures PAM is all about tagging article level content to send to content aggregators. nextPub is about tagging content to store in a content management system for assembly into publication products.

2.3.1 PAM Structure

PAM tagging supports sending a message containing one or more articles. Articles allow metadata entry in the

Figure 2.1 PAM Structure

11 PAM to PSV Guide

2.3.2 PSV Structure

PSV has a different XML model than does PAM. Since PSV is designed as a storage format for source content, it has a very well-organized and robust metadata block followed by a block for content which is a parsable subset of HTML5. Note: Although there is an optional

Figure 2.2 PSV Structure

12 PAM to PSV Guide

3 TAGGING ARTICLE METADATA

This section provides an overview of metadata tagging for PAM and PSV. Differences between the two approaches to tagging metadata will be discussed. Elements currently in PAM that are not used in PSV will be discussed.

3.1 Comparison of PSV Metadata to PAM Metadata Because PSV metadata is built on PRISM but not directly on PAM and because PSV has a completely different use case, there are differences in the metadata blocks describing an article. The major differences between PAM and PSV metadata encoding are: • In PAM, all metadata is included in the XHTML

13 PAM to PSV Guide

Figure 3.1 PAM Metadata

The nextPub use cases rely on the metadata in the

Figure 3.2 PSV Metadata

3.2 New PSV Metadata Fields PSVadds prism:contentType to indicate the of the nature of the asset that is tagged and stored. This is being added to PAM 2.2 as well. See Section 2.1.1 and 2.1.2 for information about the content types and genre that apply to PAM tagging for magazine content. In addition, PSV adds new categories of metadata.

3.2.1 Content Type Field

PSV has many publication types and content units within its scope. The same is not true for PAM. To map PAM to PSV the prism:contentType field should be set to the value “article”.

3.2.2 Unique ID Field

In PAM 2.2, a unique ID in the form of dc:identifier is required. This maps directly into the psv:uniqueID block of PSV. See Figure 3.3.

Figure 3.3 ID Block Structure

14 PAM to PSV Guide

3.2.3 Relations Metadata Fields

In PAM 2.2, relationship metadata fields were included in the

Figure 3.4 Relations Metadata Structure

3.2.4 Usage Rights Metadata Fields

In PAM 2.1, usage rights metadata fields were included in the

15 PAM to PSV Guide

Figure 3.5 Usage Rights Metadata

3.2.5 Component Metadata Fields

New metadata found in PSV but not in PRISM is component metadata. In PAM, metadata can be coded in the body of the article using

16 PAM to PSV Guide

Figure 3.6 Component Metadata

3.2.6 Where Used Metadata Fields

Because PSV is about tagging content to store in a content management system for assembly into publication products, the prism:originPlatform does not make sense for inclusion in the PSV tag set. In its place a metadata block,

Figure 3.7 Where Used Metadata

3.2.6.1 Aggregation Information Metadata The prism:aggregationType field is included in PAM and in PSV. It should be included in the psv:aggregationInfo block. If prism:platform is available, it will be mapped into this block as well. See Figure 3.7.

17 PAM to PSV Guide

Figure 3.7 Aggregation Info Structure

3.2.6.2 Publication Information PAM includes numerous fields that specify information about the publication in the

Figure 3.8 Publication Info Structure

3.2.6.3 Issue Information PAM includes numerous fields that specify information about the issue in the

18 PAM to PSV Guide

Figure 3.9 Issue Info Structure

3.2.6.4 Article Information PAM includes numerous fields that specify information about the article in the

19 PAM to PSV Guide

Figure 3.10 Article Info Structure

3.2.6.5 Website Information PAM includes numerous fields that specify information about a website in the

Figure 3.11 Website Info Structure

3.2.6.6 Book Information PAM includes book ISBN in the

20 PAM to PSV Guide

Figure 3.12 Book Info Structure

3.2.6.7 Chapter Information PAM does not contain chapter information so no data should be mapped from PAM to PSV for this block. See Figure 3.13.

Figure 3.13 Chapter Info Structure

3.2.6.8 Blog Information PAM does not contain blog information so no data should be mapped from PAM into PSV for this block. See Figure 3.14.

Figure 3.14 Blog Info Structure

3.2.6.9 Blog Entry Information PAM does not contain blog entry information so no data should be mapped from PAM into PSV for this block. See Figure 3.15.

Figure 3.15 Blog Entry Info Structure

21 PAM to PSV Guide

3.2.7 PAM to PSV Mapping Table

The following table contains all possible elements found in the PAM 2.2

PAM Heading Element PSV Metadata Mapping

dc:identifier psv:uniqueID > psv:IDBlk dc:contributor psv:description dc:creator psv:description dc:description psv:description dc:publisher psv:whereUsed > psv:publicationInfo dc:subject psv:description dc:title psv:uniqueID > psv:IDBlk dcterms:hasPart psv:relations dcterms:isPartOf psv:relations pam:status NO Mapping prism:academicField psv:description prism:aggregateIssueNumber psv:whereUsed > psv:issueInfo prism:aggregationType psv:whereUsed > psv:aggregationInfo prism:alternateTitle psv:uniqueID > psv:IDBlk prism:channel psv:whereUsed > psv:websiteInfo prism:channel1 psv:whereUsed > psv:websiteInfo prism:channel2 psv:whereUsed > psv:websiteInfo prism:channel3 psv:whereUsed > psv:websiteInfo prism:channel4 psv:whereUsed > psv:websiteInfo prism:copyright psv:usageRights = pur:copyright prism:corporateEntity psv:whereUsed > psv:publicationInfo prism:coverDate psv:whereUsed > psv:issueInfo prism:coverDisplayDate psv:whereUsed > psv:issueInfo prism:dateReceived NO Mapping prism:doi psv:whereUsed > psv:articleInfo prism:edition psv:whereUsed > psv:issueInfo prism:eIssn psv:whereUsed > psv:issueInfo prism:embargoDate psv:usageRights = pur:embargoDate prism:event psv:description prism:expirationDate psv:usageRights = pur:expirationDate prism:genre psv:description prism:hasCorrection psv:relations prism:industry psv:description prism:isbn psv:whereUsed > psv:bookInfo prism:issn psv:whereUsed > psv:issueInfo

22 PAM to PSV Guide

PAM Heading Element PSV Metadata Mapping

prism:issueIdentifier psv:whereUsed > psv:issueInfo prism:issueName psv:whereUsed > psv:issueInfo prism:issueTeaser psv:whereUsed > psv:issueInfo prism:issueType psv:whereUsed > psv:issueInfo prism:keyword psv:description prism:link psv:description prism:location psv:description prism:number psv:whereUsed > psv:issueInfo prism:object psv:description prism:organization psv:description prism:originPlatform No Mapping prism:pageRange psv:whereUsed > psv:articleInfo prism:person psv:description prism:profession psv:description prism:publicationDate psv:whereUsed >:issueInfo prism:publicationName psv:whereUsed > psv:publicationInfo prism:section psv:whereUsed > psv:articleInfo prism:seriesNumber psv:whereUsed > psv:issueInfo prism:seriesTitle psv:whereUsed > psv:issueInfo prism:sport psv:description prism:startingPage psv:whereUsed > psv:articleInfo prism:subsection1 psv:whereUsed > psv:articleInfo prism:subsection2 psv:whereUsed > psv:articleInfo prism:subsection3 psv:whereUsed > psv:articleInfo prism:subsection4 psv:whereUsed > psv:articleInfo prism:subtitle psv:uniqueID > psv:IDBlk prism:supplementDisplayID psv:whereUsed > psv:articleInfo prism:supplementStartingPage psv:whereUsed > psv:articleInfo prism:supplementTitle psv:whereUsed > psv:articleInfo prism:teaser psv:description prism:ticker psv:description prism:timePeriod psv:description prism:url psv:whereUsed > psv:websiteInfo prism:uspsNumber psv:whereUsed > psv:issueInfo prism:versionIdentifier psv:whereUsed > psv:issueInfo prism:volume psv:whereUsed > psv:issueInfo prism:wordCount psv:articleInfo publicationDisplayDate psv:whereUsed > psv:issueInfo pur:adultContentWarning psv:usageRights

23 PAM to PSV Guide

PAM Heading Element PSV Metadata Mapping

pur:agreement psv:usageRights pur:copyright psv:usageRights pur:creditLine psv:usageRights pur:embargoDate psv:usageRights pur:exclusivityEndDate psv:usageRights pur:expirationDate psv:usageRights pur:imageSizeRestriction psv:usageRights pur:optionEndDate psv:usageRights pur:permissions psv:usageRights pur:restrictions psv:usageRights pur:reuseProhibited psv:usageRights pur:rightsAgent psv:usageRights pur:rightsOwner psv:usageRights

3.2.8 Example Metadata Tagging

Here is an example of the metadata head coded in PRISM/PAM markup:

20110502044 SI20110502 Oh, The Places They'll Go Phil Taylor Sports Illustrated 0038-822X 2011-05-02 May 2, 2011 114 18 44 BASEBALL THE ROCKIES 2175 feature Colorado Rockies Here is the new nextPub metadata block divided into blocks for easy access and to aid transformations into EPUB3:

article 20110502044 Oh, The Places They'll Go

24 PAM to PSV Guide

feature Phil Taylor 2175 baseball Colorado Rockies magazine tablet iPad 1 IDEAlliance Spectrum SI20110502 2011-05-02 May 2, 2011 114 18 0038-822X 44 BASEBALL THE ROCKIES

PAM to PSV Guide

4 TAGGING CONTENT

When the nextPub working group decided to base their tagging on HTML5, they had two choices. First they could extend HTML5 to provide special nextPub functionality. Or they could code content with valid HTML5 that could be handled by any HTML5 compliant browser or processor. The Working Group opted for the latter.

4.1 What Does this Mean? The implication of this decision was that no direct use of special PAM or PIM elements for the body of the article can be included in nextPub HTML5. This means that pam:media and the

4.2 Sample Coding for Body Content Here is PRISM/PAM content encoding:

Oh, The Places They'll Go

Why are fans so aglow in Colorado? Because Tulo, CarGo and Ubaldo—and a park that no longer plays like the game's highest plateau—are making the Rockies' title hopes grow

It seemed like a good idea to Troy Tulowitzki when he allowed fans to choose his walk-up music—the song played over the Coors Field public-address system as he approaches the batter's box—in an online poll before the season. But after the Rockies' prolific shortstop followed his standout 2010 (.315 average, 27 home runs and a fifth-place finish in the National League MVP voting) by going hitless in his first eight at bats of this year, he quickly dumped the people's choice, Katy Perry's Firework, for something more in his comfort zone—Baby, by Justin Bieber.

"WE TALK ALL THE TIME ABOUT HOW TO SET THE RIGHT TONE," CARGO SAYS OF TULO. "WHAT CAN WE DO TODAY TO MAKE THIS TEAM BETTER?"

Here is the same content coded in HTML5:

Oh, The Places They'll Go

Why are fans so aglow in Colorado? Because Tulo, CarGo and Ubaldo—and a park that no longer plays like the game's highest plateau—are making the Rockies' title hopes grow

27 PAM to PSV Guide voting) by going hitless in his first eight at bats of this year, he quickly dumped the people's choice, Katy Perry's Firework, for something more in his comfort zone—Baby, by Justin Bieber.

28 PAM to PSV Guide

5 TAGGING MEDIA

This section provides documentation and guidelines for encoding media blocks. The

5.1 About PAM Media The structure of

Figure 5.1 PAM Media Structure

5.2 About nextPub Media The nextPub media block concept was initially based on the pam:media element currently used in the existing PRISM Aggregator Message. A media block presents one or more media objects along with ancillary text content so it is what is known as a “grouping” structure. After the decision was made to base nextPub on HTML5, the

29 PAM to PSV Guide

Figure 5.2 Figure Model

Two PRISM Figure Content Class metadata vocabulary terms have been developed for use with any text structure allowed in the figure. The terms included in this CV map directly to PAM content elements. In nextPub, this mechanism replaces the use of

5.3 Sample Coding Here is a pam:media encoded media object:

PHOTO

30 PAM to PSV Guide

PEAK PERFORMERS Photo of two Rockies players that are prime performers ROBERT BECK Gonzalez, Tulowitzki and Jimenez are all entering their primes and locked up through at least 2014, giving the Rockies the game's best young core.

Here is the equivalent HTML5 encoding:

PEAK PERFORMERS

ROBERT BECK

Gonzalez, Tulowitzki and Jimenez are all entering their primes and locked up through at least 2014, giving the Rockies the game's best young core.

5.4 About Tagging Media Metadata in nextPub One feature of the pam:media model which is difficult to represent in nextPub HTML5 is the inclusion of metadata for each media object. In nextPub, each of these media objects (such as a photo or a video) is considered to be a Component. Metadata for each media component is encoded using the nextPub component metadata encoding model. See PRISM Source Vocabulary Specification [PSVS] for complete documentation about tagging component metadata. In this model, some fields have equivalents and for most you can use the new PSV

The title of the resource. Gives credit the provider of necessarily the same as the credit line that will appear in a publication. A brief publishable photograph. This is not the same as the title. The main topic or topics of Note: For PSV, the component model requires a reference to a unique identifier for each component that appears in the body and a title.

31 PAM to PSV Guide

While the majority of

PAM element HTML5 Element

A figure is a media block and so the figure typically presents one or more media objects along with ancillary text content. This means that the figure is what HTML5 calls a “grouping structure.” The figure bears an “id” that is unique within the article and links the media to a

32 PAM to PSV Guide

PAM to PSV Guide

Appendix A PAM Sample Tagging 20110502044 SI20110502 Oh, The Places They'll Go Phil Taylor Sports Illustrated 0038-822X 2011-05-02 May 2, 2011 114 18 44 BASEBALL THE ROCKIES

Why are fans so aglow in Colorado? Because Tulo, CarGo and Ubaldoâ€”and a park that no longer plays like the game's highest plateauâ€”are making the Rockies' title hopes grow

PHOTO PEAK PERFORMERS ROBERT BECK Gonzalez, Tulowitzki and Jimenez are all entering their primes and locked up through at least 2014, giving the Rockies the game's best young core.

It seemed like a good idea to Troy Tulowitzki when he allowed fans to choose his walk-up musicâ€”the song played over the Coors Field public-address system as he approaches the batter's boxâ€”in an online poll before the season. But after the Rockies' prolific shortstop followed his standout 2010 (.315 average, 27 home runs and a fifth-place finish in the National League MVP voting) by going hitless in his first eight at bats of this year, he quickly dumped the people's choice, Katy Perry's Firework, for something more in his comfort zoneâ€”Baby, by Justin Bieber.

35 PAM to PSV Guide

It might be a stretch to say that Tulo, as he's widely known, has Bieber fever, but he is partial to the teen pop star's music and doesn't care who knows it. He and teammate Jason Giambi took in a Bieber concert during spring training, and Tulo is willing to put up with the inevitable ribbing from the rest of the Rockies, who keep his locker at Coors stocked with Bieber-obilia. Last week his space was adorned with a glittery backpack and a T-shirt bearing the singer's likeness that most middle school girls would surely be proud to own. "Lots of comedians in this clubhouse," Tulowitzki says. "I just go with the flow."

PHOTO DOUBLE THREAT ROBERT BECK Tulowitzki and Gonzalez have a thriving partnership in the lineup, in the clubhouse and in the NL MVP balloting, where both finished in the top five last year.

Even though they might not want to trade iPods with Tulowitzki, 26, none of the Rockies would dream of suggesting he change his tune. He went on one of his familiar Tulo tears shortly after the sound track switch, almost single-handedly demolishing the Mets with home runs in four straight games, and through Sunday he was hitting .333 with seven homers, tying him with the Cardinals' Albert Pujols and Ryan Braun of the Brewers for the National League home run lead. Besides, although his new signature song isn't exactly a lyrical masterpiece, it does have one lineâ€”in fact, it's repeated so much it seems like the only lineâ€”that's especially appropriate for the Rockies: Baby, baby, baby, oh.

VIDEO A HUMOROUS LOOK AT THE COORS HUMIDOR

Put the emphasis on the oh. That's a joyful sound in Colorado these days, thanks not just to Tulo, but to CarGo and Ubaldo. CarGo is otherwise known as leftfielder Carlos Gonzalez, 25, last year's NL batting champ. The linchpin of the Rockies' staff is Ubaldo Jimenez, 27, who finished third in the NL Cy Young Award voting in 2010. Due mostly to a thumb injury that forced him to miss two starts, Jimenez has started slowly, but the Rockies haven't. Tulowitzki's performance, both with bat and glove, and solid pitching from starters Jhoulys Chacin and Jorge De La Rosa, as well as the entire bullpen, helped put Colorado atop the NL West with a 14â€”7 record through Sunday. The Rockies appear set to contend not just this year but for the foreseeable future, and it's largely, as the Biebs might say, because of their O's, baby.

It's also because of a long-term philosophy that ensures the O trio won't be leaving anytime soon. Back in the '90s, when the Rockies were playing something closer to pinball than baseball because of the way the ball carried in the mile-high altitude of their home park, finding one of baseball's most sensible organizational blueprints in Colorado would have seemed as likely as discovering a gourmet meal in an Easy-Bake Oven. But just as the introduction of a humidor at Coors in 2002â€”baseballs stored in it don't carry like golf ballsâ€”has normalized the game in Denver, the Rockies have devised a smart, down-to- earth approach.

SLIDESHOW

36 PAM to PSV Guide

SLIDESHOW: SEE THE VISITING PITCHERS WHO PERFORM BEST AT COORS FIELD ROBERT BECK TIM LINCECUM In nine career starts at Coors Field, the Freak has a 3.49 ERA, the best among all hurlers who have thrown at least 40 innings there and never played for the Rockies.

SLIDESHOW TOM GLAVINE BRIAN BAHR/GETTY IMAGES The Braves lefty made 13 starts at Coors (including eight in the prehumidor days) and had a 3.68 ERA there, second best among visitors.

SLIDESHOW DAN HAREN GARRETT W. ELLWOOD/GETTY IMAGES The righthander (now with the Angels) has made seven starts at Coors and gone 4â€”2 with a 3.80 ERA there, third best among visiting pitchers.

SLIDESHOW BRETT MYERS DUSTIN BRADFORD/ICON SMI The righty (now with the Astros) has a career ERA of 4.18”but that figure drops to 3.92 (with a 5”0 record) in his six starts at Coors.

SLIDESHOW BRAD PENNY ROBERT BECK In 11 starts at Coors, the righty (now with the Tigers) is 6’”1 with a 3.92 ERA, tying him with Myers for the fourth-best mark there among visitors.

Having been burned in the past by throwing big bucks at older free agents who failed miserably on the field and sometimes embarrassed the franchise away from it, Colorado's front office has become more selective about making major financial commitments. They focus on retaining players who appear to be entering their prime rather than signing older, more established stars, and before the Rockies offer a long-term deal, they have to be satisfied not just with a player's skills but also with the content of his character. "We found that talent that isn't also accompanied by other qualities, such as humility, accountability and integrity, really didn't work for us," says general manager Dan O'Dowd. "We've tried to build this team not just with a certain kind of player but a certain quality of person."

37 PAM to PSV Guide

Gonzalez, Jimenez and Tulowitzki are perfect templates for the Rockies' vision”young, gifted, industrious and squeaky-clean. That's why Colorado locked up CarGo with a seven-year, $80 million contract extension in January, two months after it extended Tulowitzki's contract to make it a 10-year deal worth $157.75 million. They got in on the ground floor with Jimenez as well, signing him to a four- year deal in 2009 (with team options for '13 and '14) that could earn him $22.75 million and keep him in Denver two years after he would have been eligible for free agency.

CarGo and Tulo in particular have formed a thriving partnership, not just in the middle of the order, where they bat third and fourth, but in the clubhouse. "We talk all the time about how to set the right tone," Gonzalez says. "We do our running in the outfield, and we're talking about how we can help our teammates. Is somebody in a slump? What can we do for him? What can we do today to make this team better?"

The pair complement each other so well that when Gonzalez bought a new Ferrari after his contract extension, he chose red instead of his preferred black because Tulowitzki already owns a black one. "Got to keep things balanced out," CarGo says. They work together as team leaders just as well. "Obviously the Latin guys on this team and in the minors look up to Carlos," Tulowitzki says. "Some of the other young guys come up to me and ask me questions, so that part of it works out real well."

PHOTO PRECIOUS CARGO ROBERT BECK After being traded twice in 11 months as a minor leaguer, Gonzalez showed last year why he was so sought after: He finished in the top four in the NL in every Triple Crown category.

The Rockies have had several incarnations and strategies in their 19-year history. In their infancy they stocked the team with veteran sluggers like Dante Bichette, Vinny Castilla and Larry Walker, and ran up huge run totals in the thin Denver air. In the late 1990s and 2000s they began spending heavily on free-agent pitchers who had been successful elsewhere, such as Darryl Kile, Mike Hampton and Denny Neagle, all of whom found that pitching at high altitude is hazardous to the ERA. It was the disastrous results of spending $172 million on Hampton and Neagle in 2000 that prompted the current shift in philosophy. Hampton was ineffective until the Rockies traded him two years later. Neagle was not only a bust but also was cited for patronizing a prostitute in 2004, causing the Rockies to void the last year of his contract. (The Rockies reached a $16 million settlement with him in '05, and eight months later he pleaded guilty and was sentenced to 40 hours of community service.)

The greater emphasis on personal character post-Neagle was at first seen as a religious-based movementâ€”a 2006 USA Today article described the organization as following a "Christian-based code of conduct"â€”but O'Dowd says that decisions about players have never been based on the nature of their faith. "Do we like players with character? Yes. With strong moral values? Yes," he says. "It is not required that a player be deeply religious to have those qualities."

The approach is less about religion than about an intelligent design. The effort to pay a little more to lock up promising players before they can break the bank in free agency makes good financial sense, and the ability to retain budding stars is especially appreciated by Colorado fans, who have seen some of the market's most prominent athletes, like Carmelo Anthony of the Nuggets, the Broncos' Jay Cutler and the Rockies' Matt Holliday, leave town in the last three years.

Tulowitzki is already filling some of the void left by those departures, and Gonzalez isn't far behind. With his smooth lefthanded swing and the way he glides effortlessly in the outfield, the gifted CarGo his slow start (a .228 average and one home run through Sunday) notwithstandingâ€”is one of those players who make even their

38 PAM to PSV Guide peers marvel. "One of the best things about my job is I get to watch him for free," says Tulowitzki.

Gonzalez developed his graceful style on the diamonds of Maracaibo, Venezuela, where his older brother Euro Jr. introduced him to the sport by taking him to a Venezuelan Winter League game when Carlos was eight. "I saw Bobby Abreu play, and I went home and started trying to make my stance like his," Gonzalez says, referring to the veteran outfielder now with the Angels. "After that all I wanted to do was play baseball." He and Euro would take tree branches, carve them into makeshift bats and use rolled-up socks for balls until Carlos's talent earned him a spot on youth traveling teams.

Signed at 16 by the Diamondbacks, he spent four years in the minors as a highly valued prospect until he was dealt in 2007 to Oakland with a package of players for pitcher Dan Haren. Despite showing flashes of his prodigious talent in Oakland, Gonzalez lasted only 11 months there before the A's traded him to Colorado with pitchers Huston Street and Greg Smith for Holliday.

"It feels like it took a long time," Gonzalez says, "and then it came all at once." The Rockies sent him to Triple A Colorado Springs when they first acquired him, and after they brought him up, he scuffled along, batting around .200 for a long stretch. But once he got settled in Colorado, stardom did come in a rush. He hit .284 in 89 games in 2009 before tearing through the league last year with a .336 average, 34 homers, 117 RBIs and 26 stolen bases. The key to his breakout? "Being comfortable," he says. "Getting traded twice was hard; it kind of shakes you up. Once I knew I was going to be here for good, that they really wanted me here, everything fell into place."

The one quality that Gonzalez hasn't yet developed is patience at the plate, where he shows off that sweet swing a little too often. "When he got here, his strike zone was from the bill of his cap to the top of his spikes," says manager Jim Tracy. "He still needs to be more selective, but he's getting better." According to Fangraphs.com, 37% of Gonzalez's swings last season were at pitches outside the strike zone. Only 14 hitters chased bad balls more often. So far this season he has reduced that number to 30.9%.

"I am trying to be patient and make the pitchers throw strikes, but at the same time I don't want to lose my aggressiveness," Gonzalez says. "It takes time. You have to learn from your mistakes, and in time you figure it out." That's as true for a franchise as it is for a ballplayer. In fact, the Rockies' trio of O's are the perfect symbols of their franchiseâ€”young, learning, on the cusp of something special. You get the feeling it won't be long now. They're just about to figure it out.

Now on Twitter

Follow @SI_JonHeyman and @JPosnanski for their up-to-the-minute baseball thoughts.

"WE TALK ALL THE TIME ABOUT HOW TO SET THE RIGHT TONE," CARGO SAYS OF TULO. "WHAT CAN WE DO TODAY TO MAKE THIS TEAM BETTER?"

ROCKY MOUNTAIN LOW

In their first nine seasons, the Rockies' home ERA was a lofty 6.07. But since '02, when they began using a humidor at Coors Field to make balls behave more like they do at sea level, Ubaldo Jimenez and the team's other pitchers have had that mark in free fall.

5.47 2002

5.07 2003

6.27 2004

5.18 2005

4.72 2006

39 PAM to PSV Guide

4.34 2007

4.83 2008

4.41 2009

4.25 2010

3.91 2011

PHOTO ROBERT BECK

WEBPAGE WEBPAGE WEBPAGE

40 PAM to PSV Guide

Appendix B Sample PSV Tagging article 20110502044 Oh, The Places They'll Go feature opinion Phil Taylor 2175 baseball Colorado Rockies magazine tablet iPad 1 IDEAlliance Spectrum SI20110502 2011-05-02 May 2, 2011 114 18 0038-822X 44 BASEBALL THE ROCKIES