prism_specification

 

PRISM:

Publishing Requirements for Industry Standard Metadata

 

Version 2.2

 

 

 

The PRISM Aggregator Message
Markup Specification

 

October 4, 2012

 

idealliancelogo_cymk


Copyright and Legal Notices

© 2001 – 2012 International Digital Enterprise Alliance, Inc.  All Rights Reserved.

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 patent-disclosure@idealliance.org.

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 patent-disclosure@idealliance.org.


Table of Contents

1     Status. 1

1.1         Document Status. 1

1.2         Document Location.. 1

1.3         Version History. 1

2     PRISM Documentation Structure. 3

2.1         Normative and Non-normative Sections. 3

2.1.1      Requirement Wording Note. 3

2.2         The PRISM Documentation Package. 3

2.2.1      General Documents. 3

2.2.2      PRISM Metadata Specifications. 3

2.2.3      PRISM Aggregator Message Markup Specification.. 4

2.2.4      PRISM Markup Specifications. 5

2.2.5      PRISM Controlled Vocabulary Specifications. 5

2.2.6      Additional PRISM Documentation.. 5

2.2.7      Access to PRISM Documentation.. 6

2.2.8      Access to PAM Schemas. 6

2.2.9      PRISM Source Vocabulary Documentation Set. 6

2.3         PSV Content Management Schema. 7

2.4         Other PSV Schemas. 7

3     Introduction.. 9

3.1         Purpose and Scope. 9

3.2         New in this Version.. 9

4     PRISM Aggregator Message Documentation.. 11

4.1         PRISM Aggregator Message Namespace. 11

4.2         Other Namespaces Used in PAM 2.2. 11

4.3         Relationship to PRISM... 11

4.4         Relationship to PSV.. 11

4.5         PAM Element Definitions. 12

4.5.1      pam:article. 12

4.5.2      pam:caption.. 13

4.5.3      pam:credit. 13

4.5.4      pam:media. 13

4.5.5      pam:mediaReference. 14

4.5.6      pam:mediaTitle. 14

4.5.7      pam:message. 15

4.5.8      pam:nonpublishedMediaTitle. 15

4.5.9      pam:status. 16

4.5.10        pam:textDescription.. 16

4.6         PAM Attribute Definitions. 16

4.6.1      pam:refid.. 16


1      Status

1.1      Document Status

The status of this document is:

ü

Released for Public Comment

7/02/2012

ü

Final Specification

10/04/2012

 

1.2      Document Location

The location of this document is:

http://www.prismstandard.org/specifications/3.0/PRISM_PAM_Markkup_3.0.pdf

http://www.prismstandard.org/specifications/3.0/PRISM_PAM_Markkup_3.0.htm  

 

1.3      Version History

Version Number

Release Date

Editor

Description

1.1

2004

McConnell

Initial version of spec-style PAM documentation

1.2

10/01/05

Kennedy

Final for Release

2.0 Release

2/19/08

Kennedy

Final for Release

2.0 w Errata

7/03/08

Kennedy

Final with Errata

2.1 Final

05/15/09

Kennedy

Final

2.1 w Errata

06/01/09

Kennedy

Errata

2.2 Draft

07/02/12

Kennedy

Draft for Public Comment

2.2 Release

10/04/2012

Kennedy

Final



2      PRISM Documentation Structure

PRISM is described in a set of formal, modularized documents that, taken together, represent “the PRISM Specification”. Together these documents comprise the PRISM Documentation Package.

2.1      Normative and Non-normative Sections

Documents in the PRISM Documentation Package may contain both normative and non-normative material; normative material describes element names, attributes, formats, and the content of elements that is required in order for content or systems to comply with the PRISM Specification. Non-normative material explains, expands on, or clarifies the normative material, but it does not represent requirements for compliance. Normative material in the PRISM Documentation Package is explicitly identified as such; any material not identified as normative can be assumed to be non-normative.

2.1.1    Requirement Wording Note

The key words "MUST," "MUST NOT," "REQUIRED," "SHALL," "SHALL NOT," "SHOULD," "SHOULD NOT," "RECOMMENDED," "MAY," and "OPTIONAL" in this document are to be interpreted as described in [RFC-2119]. The PRISM Specification also uses the normative term, “STRONGLY ENCOURAGES,” which should be understood as a requirement equivalent to “MUST” in all but the most extraordinary circumstances.

Capitalization is significant; lower-case uses of the key words are intended to be interpreted in their normal, informal, English language way.

2.2      The PRISM Documentation Package

The PRISM Documentation Package consists of:

2.2.1    General Documents

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

Document

Description

PRISM Introduction [PRISMINT]
http://www.prismstandard.org/specifications/3.0/
PRISM_introduction_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_introduction_3.0.htm

Overview, background, purpose and scope of PRISM; examples; contains no normative material.

PRISM Compliance [PRISMCOMP]
http://www.prismstandard.org/specifications/3.0/
PRISM_compliance_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_compliance_3.0.htm

Describes three profiles of PRISM compliance for content and systems; includes normative material.

2.2.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]
http://www.prismstandard.org/specifications/3.0/
PRISM_Basic_Metadata_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Basic_Metadata_3.0.htm

Describes the basic metadata elements contained in the PRISM namespace to describe article content; includes normative material.

PRISM Advertising Metadata Specification [PRISMADMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Advertising_Metadata_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Advertising_Metadata_3.0.htm

Describes advertising metadata elements including those drawn from AdsML, GWG and Ad-ID; includes normative material.

The PRISM Subset of Dublin Core Metadata Specification [PRISMDCMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Dublin_Core_Metadata_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Dublin_Core_Metadata_3.0.htm

Describes the metadata elements from the Dublin Core namespace that are included in PRISM; includes normative material.

The PRISM Image Metadata Specification [PRISMIMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Image_Metadata_Specification_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Image_Metadata_Specification_3.0.htm

Describes the metadata elements contained in the PRISM Metadata for Images Namespace and other related image namespaces, includes normative material.

The PRISM Recipe Metadata Specification [PRISMRMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Recipe_Metadata_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Recipe_Metadata_3.0.htm

Describes the metadata elements contained in the PRISM Recipe Metadata Namespace, includes normative material

The PRISM Usage Rights Metadata Specification [PRISMURMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Usage_Rights_Metadata_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Usage_Rights_Metadata_3.0.htm

Describes the metadata elements contained in the PRISM Usage Rights Namespace; includes normative material. This namespace will supersede elements in both the prism: and prl: namespaces in version 3.0 of the specification.

2.2.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 [PRISMPAMMS]
http://www.prismstandard.org/specifications/2.1/
PRISM_PAM_Markup_2.1.pdf

or
http://www.prismstandard.org/specifications/2.1/
PRISM_PAM_Markup_2.1.htm

Describes the XML elements and attributes used to encode the PRISM Aggregator Message from both the pam: and pim: namespaces; includes normative material.

2.2.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]
http://www.prismstandard.org/specifications/2.1/
PRISM_PIM_Markup_Specification 3.0.pdf

or
http://www.prismstandard.org/specifications/2.1/
PRISM_PIM_Markup_Specification 3.0.htm

Describes the XML elements used to encode the inline markup for the PRISM Aggregator Message. Includes normative material.

2.2.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 Specification [PRISMCVMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Controlled_Vocabulary_Markup_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Controlled_Vocabulary_Markup_3.0.htm

Describes the metadata fields in the PRISM Controlled Vocabulary Namespace that can be used to describe a controlled vocabulary.   Actual PRISM controlled vocabularies are now placed in the PRISM Controlled Vocabularies Specification [PRISMCVS]

The PRISM Controlled Vocabularies Specification [PRISMCVS]
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

The PRISM Controlled Vocabularies are now documented in this document.

2.2.6    Additional PRISM Documentation

The Guide to the PRISM Aggregator Message [PAMGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.

The PRISM Cookbook [PRISMCB] documents implementation strategies for PRISM Profile 1 applications.

The Guide to PRISM Usage Rights [RIGHTSGUIDE] documents an XML-based PRISM application for the expression of PRISM Usage Rights.  The Guide is accompanied by an XSD that can be used as the basis for developing a digital rights management system based on PRISM Usage Rights.

The Guide to PRISM Metadata for Images [IMAGEGUIDE] documents an XML-based PRISM Profile 1 application for the expression of the structure and use of PRISM Metadata for Images and can be used as the basis for developing an image management system based on PRISM Metadata for Images and for implementing PMI in XML.

The Guide to PRISM Recipe Metadata and XML Encoding [RECIPEGUIDE] documents the XML-based PRISM Profiles for the encoding of recipes for:

·        Establish a Recipe Database

·        Establish a tagging scheme to code a wide variety of recipes in XML

·        Tag recipes within the PAM message

·        Tag recipes in nextPub XML Content Source

2.2.7    Access to PRISM Documentation

The PRISM documentation package, the PAM guide (see above), the PAM DTD, the PAM XSD and a range of other information concerning PRISM are all publicly and freely available on the PRISM website, www.prismstandard.org.

2.2.8    Access to PAM Schemas

Standard URLs have been established to access PRISM/PAM XSDs and DTDs as well as the XSD for the new PRISM Usage Rights Model.

To access PAM XSDs and DTDs:

http://www.prismstandard.org/schemas/pam/2.1/
http://www.prismstandard.org/schemas/pam/2.1/pam.xsd
http://www.prismstandard.org/schemas/pam/2.1/pam-dc.xsd
http://www.prismstandard.org/schemas/pam/2.1/pam-prism.xsd

To access PRISM Rights Model XSD

http://www.prismstandard.org/schemas/rights/3.0/rightsmodel.xsd

To access PRISM Recipe Tagging and Recipe Database XSD

http://www.prismstandard.org/schemas/recipe/3.0/recipemodel.xsd

2.2.9    nextPub PRISM Source Vocabulary Documentation Set

nextPub has developed a series of specifications collectively known as the PRISM Source Vocabulary.  The use case for PSV is to encode semantically rich content for transformation and delivery to any platform. 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:

Document

Description

PRISM Source Vocabulary Specification Overview [PSVSO]

http://www.prismstandard.org/specifications/psv/1.0/PSV_overview.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PSV_overview.htm

The Introduction to the PRISM Source Vocabulary provides an introduction and a non-technical overview of the PRISM Source Vocabulary.

PRISM Source Vocabulary Specification [PSVS]

http://www.prismstandard.org/specifications/psv/1.0/PSV.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PSV.htm

The PRISM Source Vocabulary Specification defines semantically rich for source metadata and content markup that can be transformed and served to a wide variety of output devices including eReaders, mobile tablet devices, smart phones and print.

PRISM Source Vocabulary Markup Specification [PSVMS]

http://www.prismstandard.org/specifications/psv/1.0/PSV_markkup.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PSV_markup.htm

The PSV Markup Specification documents the XML tags in the PSV namespace that are used to encode XML Source Content.

PAM to PSV_Guide [PAMPSVGUIDE]

http://www.prismstandard.org/specifications/psv/1.0/PAM_PSV.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PAM_PSV.htm

This Guide documents mappings from PAM XML to PSV XML.  It is normative only.

2.3      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.

2.4      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.



3      Introduction

3.1      Purpose and Scope

The purpose of this document is to describe the basic elements that the PRISM Working Group has defined and included in the PRISM Aggregator Message namespace. All of section 4 of this document is normative.

This document is not a complete guide to implementing PAM; users must use the [PAMGUIDE] as well.

All the element definitions appear in a uniform format. Each element definition begins with two fields – the Name and the Identifier of the element. The Name is a human-readable string that can be translated into different languages. Also, note that PRISM does NOT require that users be presented with the same labels. The Identifier is a protocol element. It is an XML element type and MUST be given as shown, modulo the normal allowance for variations in the namespace prefix used.

Note: PRISM Aggregator Message markup is XML markup. It does not follow the rules of RDF/XML, even for profile 2 PRISM Compliance (that documents encoding content using the PRISM2 profile of RDF). Likewise, PRISM Aggregator Message is never expressed using XMP [XMP] markup.

3.2      New in this Version

Changes in this document include:

·        Addition of new head elements markup tags to refine dc:subject;.  academicField, link, profession and sport

·        Addition of new issue-level elements: aggregateIssueNumber, issueTeaser, IssueType and uspsNumber, pubicationDisplayDate

·        Addition of support for series and supplements: seriesNumber, seriesTitle, supplementDisplayID, supplementTitle, supplementStartingPage

·        Addition of support for blogs: blogURL, blogTitle



4      PRISM Aggregator Message Documentation

4.1      PRISM Aggregator Message Namespace

One of the key content interchange transactions in publishing is the transmission of articles from publishers to aggregators. To provide a standard structure for these transactions, the PRISM Working Group developed the PRISM Aggregator Message (PAM). PAM is the first formal application of the PRISM standard metadata elements. It consists of a guide document [PAMGUIDE], this formal specification of the PAM namespace, and the PAM DTD or PAM XSD. In order to evaluate and implement PAM, readers will need all of these objects. All are available from www.prismstandard.org.

The recommended namespace for PRISM Aggregator Message is:
xmlns:pam=”http://prismstandard.org/namespaces/pam/2.2/”

4.2      Other Namespaces Used in PAM 2.2

PAM 2.2 is implemented using elements from other namespaces.  Because PAM is remaining stable and backwardly compatible, it does not directly use the new PRISM 3.0 namespaces.  Rather it uses special namespaces designed to retain the stability of the overall PRISM Aggregator Message.  These namespaces include:

·        xmlns:prism=http://prismstandard.org/namespaces/basic/2.2/

·        xmlns:pim="http://prismstandard.org/namespaces/pim/2.2/"

·        xmlns:dcterms="http://purl.org/dc/terms/"  

·        xmlns:pur="http://prismstandard.org/namespaces/prismusagerights/2.1/"

·        xmlns:dc="http://purl.org/dc/elements/1.1/"

4.3      Relationship to PRISM

PAM is the PRISM Aggregator Message.  The use case for PAM is to encode magazine articles in XML to deliver content to aggregators. PAM is an XML tag set built on the foundation of PRISM metadata and controlled vocabularies.  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 4.1.

4.4      Relationship to PSV

PAM is the PRISM Aggregator Message.  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. Now a new use case, to encode semantically rich content for transformation and delivery to any platform, has led to the development of a new XML tag set, the PRISM Source Vocabulary.  PSV, like PAM is also built on the foundation of PRISM metadata and controlled vocabularies,  But nextPub and PAM are not the same.  Each has a very specific use case and each has a different XML tag set.  See Figure 4.1.

Note: PSV is based on PRISM 3.0 while PAM 2.2 remains backwardly compatible and is based on PRISM 2.1 with a few extensions to include a few critical elements from PRISM 3.0.

Figure 4.1 Relationship of PAM, PRISM and nextPub

4.5      PAM Element Definitions

Although much of PAM is implemented using elements defined in the other PRISM namespaces, a small set of additional elements and attributes were required to meet the unique needs of this application. Those elements and attributes are documented here. 

4.5.1    pam:article

Name

Article

Identifier

pam:article

Definition

(Element) Contains the metadata and markup for one article.

Occurrence

Occurs 0 or 1 time

Comment

See [PAMGUIDE] for the structure and a full description of pam:article.

nextPub Mapping

<html5:article

Attributes

xmlns:pam=, xmlns:prism=, xmlns:dc=, xmlns:pim=

Model

head (body)? (redefined in the PAM DTD to serve as containers) See [PAMGUIDE].

Occurs In

pam:message

Example

<pam:message>

               <pam:article>

                              <head>

...

                              </head>

                              <body>

...

                              </body>

               </pam:article>

</pam:message>

4.5.2    pam:caption

Name

Caption

Identifier

pam:caption Allows for capture of published text that describes the media object.

Definition

(Element)

Occurrence

Occurs 0 or 1 time

Comment

Permits capture of captions for media associated with an article.

 

Do NOT use the XHTML caption element for capturing caption text, unless the text is for a table.

nextPub Mapping

photoshop:Headline

Attributes

None

Model

#PCDATA mixed with XHTML elements

Occurs In

pam:media

Example

<pam:caption>This Clinton campaign again offers &quot;two for one,&quot; but the aspiring First <b>Laddie</b>Laddie and strategist in chief, shown with Hillary in New Hampshire, is trying not to outshine his wife</pam:caption>

4.5.3    pam:credit

Name

Credit

Identifier

pam:credit

Definition

(Element) A caption-style attribution for a media object.

Occurrence

Occurs 0 or more times

Comment

Permits capture of credits for media associated with an article, especially where the credit is different than the overall article credit, captured in dc:creator.

pur:creditLine specifies the credit that is contractually required.  This may differ from what appears in print, which is captured by pam:credit.

nextPub Mapping

photoshop:Credit

Attributes

None

Model

#PCDATA

Occurs In

pam:media

Example

<pam:credit>PHOTOGRAPH BY ANTONIN KRATOCHVIL/VII</pam:credit>

<pam:credit>FRED WESTBROOK</pam:credit>

4.5.4    pam:media

Name

Media

Identifier

pam:media

Definition

(Element) An alternative to the XHTML img element. Permits referring to and providing metadata for a media object related to an article.

Occurrence

Occurs 0 or more times

Comment

pam:media provides a method for publishers to transmit image captions, descriptions, and credits to aggregators. pam:media includes elements and attributes from Dublin Core (like dc:type), PRISM Aggregator Message (e.g. pam:credit), PRISM (e.g. prism:copyright) and PRISM Usage Rights (e.g. pur:rightsOwner).

 

XHTML will be treated as the default namespace in a PAM document, so that XHTML elements in the document’s examples will not have a namespace prefix. The body element in the example below is an example using xhtml: as the default namespace.

nextPub Mapping

<html5:figure

Attributes

xmlns:pam=, xmlns:prism=, xmlns:dc=

Model

Elements in order: (dc:type?, dc:format?, dc:identifier?, dc:creator*,

dc:contributor*, pam:mediaReference?, pam:mediaTitle?, pam:nonpublishedMediaTitle?,

pam:credit*, pam:caption?, pam:textDescription?)

 

Occurs In

pam:article

Example

<pam:media>

   <dc:format>image/jpeg</dc:format>

   <pam:mediaTitle>Bill Clinton</pam:mediaTitle>

   <pam:credit>BROOKS KRAFT--CORBIS FOR TIME</pam:credit>

   <pam:caption>This Clinton campaign again offers &quot;two for one,&quot; but the aspiring First Laddie and strategist in chief, shown with Hillary in New Hampshire, is trying not to outshine his wife</pam:caption>

    <pam:textDescription>Image of Hillary & Bill Clinton</pam:textDescription>

</pam:media>

4.5.5    pam:mediaReference

Name

Media Reference

Identifier

pam:mediaReference

Definition

(Element) Links to the media file referred to by pam:media.

Occurrence

Occurs 0 or 1 time

Comment

In a pam:media element, pam:mediaReference is a means to name the media object -- image file, sound file, video file, etc. Its attribute refid= holds the name of the file

See definitions for attributes in Section 4.3.

nextPub Mapping

<html5:img src=, <html5:video src=, <html5:audio src=

Attributes

pam:refid =

Model

Empty

Occurs In

pam:media

Example

<pam:media>

    <dc:type>chart</dc:type>

    <dc:format>image/gif</dc:format>

    <pam:mediaTitle>West day-ahead markets</pam:mediaTitle>

    <pam:mediaReference pam:refid="MD_20070103-west.gif"/>

    <pam:caption>Note: Based on averages from each region</pam:caption>

</pam:media>

4.5.6    pam:mediaTitle

Name

Media Title

Identifier

pam:mediaTitle

Definition

Published title of the media element.

Occurrence

Occurs 0 or 1 time

Comment

 

nextPub Mapping

dc:title

Attributes

None

Model

#PCDATA

Occurs In

pam:media

Example

<pam:media>

   <pam:mediaTitle>Bill Clinton</pam:mediaTitle>

   <pam:credit>BROOKS KRAFT--CORBIS FOR TIME</pam:credit>

   <pam:caption>This Clinton campaign again offers &quot;two for one,&quot; but the aspiring First Laddie and strategist in chief, shown with Hillary in New Hampshire, is trying not to outshine his wife</pam:caption>

    <pam:textDescription> Image of Hillary & Bill Clinton</pam:textDescription>

</pam:media>

4.5.7    pam:message

Name

Message

Identifier

pam:message

Definition

(Element) Root element for message from publisher to aggregator. Contains one or more article elements.

Occurrence

Occurs 0 or 1 time

Comment

See [PAMGUIDE] for the complete description of the pam:message structure.

nextPub Mapping

No mapping exists

Attributes

xmlns:pam=, xmlns:prism=, xmlns:dc=, xmlns:pim=

Model

pam:article

Occurs In

Root Element

Example

<pam:message xmlns:pam="http://prismstandard.org/namespaces/pam/2.1/"

xmlns:prism="http://prismstandard.org/namespaces/basic/2.1"

xmlns:pim="http://prismstandard.org/namespaces/pim/2.1/"

xmlns:dc="http://purl.org/dc/elements/1.1/">

<pam:article>

...

</pam:article>

<pam:article>

...

</pam:article>

</pam:message>

4.5.8    pam:nonpublishedMediaTitle

Name

Non-published Media Title

Identifier

pam:nonpublishedMediaTitle

Definition

Non-published title of the media element.

Occurrence

Occurs 0 or 1 time

Comment

 

nextPub Mapping

--

Attributes

None

Model

#PCDATA

Occurs In

pam:media

Example

<pam:media>

   <dc:type>photo</dc:type>

   <dc:format>image/jpeg</dc:format>

   <pam:nonpublishedMediaTitle>Photo of Bill Clinton</pam:nonpublishedmediaTitle>

   <pam:credit>BROOKS KRAFT--CORBIS FOR TIME</pam:credit>

   <pam:caption>This Clinton campaign again offers &quot;two for one,&quot; but the aspiring First Laddie and strategist in chief, shown with Hillary in New Hampshire, is trying not to outshine his wife</pam:caption>

</pam:media>

4.5.9    pam:status

Name

Status

Identifier

pam:status

Definition

Defines the processing status of the article.

Occurrence

Occurs 0 or 1 time

Comment

(Element) Contents of this element MUST be one of {A, C, D, U}, indicating that the article is to be Added (i.e., it's a new article, never before transmitted to the recipient), or is a Correction, a Delete request, or an Update for a previously transmitted article.

nextPub Mapping

--

Attributes

None

Model

#PCDATA

Occurs In

pam:article

Example

<pam:status>A</pam:status>

4.5.10pam:textDescription

Name

Text Description

Identifier

pam:textDescription

Definition

(Element) Contains a textual description for the item referred to in a pam:media element.

Occurrence

Occurs 0 or 1 time

Comment

Permits a fully-marked up description of a media item to accompany it.

nextPub Mapping

dc:subject

Attributes

None

Model

#PCDATA

Occurs In

pam:media

Example

<pam:textDescription>Photo of President Bush and Prime Minister Blair</pam:textDescription>

4.6      PAM Attribute Definitions

4.6.1    pam:refid

Name

Reference ID

Identifier

pam:refid

Definition

(Attribute) ID used to reference.

Comment

Use to hold the actual name of the media file in a pam:mediaReference, or a unique identifier.

Model

Empty

Occurs In

pam:mediaReference

Example

<pam:mediaReference pam:refid="MD_20070103-west.gif"/>