-

 

 

Description: prism_specification

 

 

 

Publishing Requirements for Industry Standard Metadata

 

Version 3.0

 

 

PRISM
Basic Metadata Specification

 

 

October 4, 2012

 

 

 

 

Description: 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 Section.. 3

2.2         Requirement Wording Note. 3

2.3         The PRISM Documentation Package. 3

2.3.1      General Documents. 3

2.3.2      PRISM Metadata Specifications. 4

2.3.3      PRISM Aggregator Message Markup Specification.. 5

2.3.4      PRISM Inline Markup Specification.. 5

2.3.5      PRISM Controlled Vocabulary Specifications. 5

2.3.6      Additional PRISM Documentation.. 6

2.3.7      Access to PRISM Documentation.. 6

2.3.8      Access to PAM Schemas. 6

2.3.9      PRISM Source Vocabulary Documentation Set. 7

2.4         PSV Content Management Schema. 7

2.5         Other PSV Schemas. 7

3      Introduction. 9

3.1         Purpose and Scope. 9

3.2         New in this Version.. 9

4      PRISM Element and Attribute Definitions. 11

4.1         PRISM Namespace. 11

4.2         PRISM Element and Attribute Models. 11

4.2.1      prism:academicField.. 11

4.2.2      prism:aggregateIssueNumber. 12

4.2.3      prism:aggregationType. 12

4.2.4      prism:alternateTitle. 13

4.2.5      prism:blogTitle. 14

4.2.6      prism:blogURL. 15

4.2.7      prism:bookEdition.. 15

4.2.8      prism:byteCount. 16

4.2.9      prism:channel 16

4.2.10    prism:complianceProfile. 17

4.2.11    prism:contentType. 18

4.2.12    prism:copyrightYear. 19

4.2.13    prism:corporateEntity. 19

4.2.14    prism:coverDate. 20

4.2.15    prism:coverDisplayDate. 21

4.2.16    prism:creationDate. 22

4.2.17    prism:dateReceived.. 22

4.2.18    prism:device. 23

4.2.19    prism:distributor. 23

4.2.20    prism:doi 24

4.2.21    prism:edition.. 25

4.2.22    prism:eIssn.. 25

4.2.23    prism:endingPage. 26

4.2.24    prism:event. 27

4.2.25    prism:genre. 27

4.2.26    prism:hasAlternative. 28

4.2.27    prism:hasCorrection.. 29

4.2.28    prism:hasTranslation.. 30

4.2.29    prism:industry. 31

4.2.30    prism:isAlternativeOf 32

4.2.31    prism:isbn.. 33

4.2.32    prism:isCorrectionOf 34

4.2.33    prism:issn.. 35

4.2.34    prism:issueIdentifier. 36

4.2.35    prism:issueName. 36

4.2.36    prism:issueTeaser. 37

4.2.37    prism:issueType. 38

4.2.38    prism:isTranslationOf 38

4.2.39    prism:keyword.. 39

4.2.40    prism:killDate. 40

4.2.41    prism:link. 40

4.2.42    prism:location.. 41

4.2.43    prism:modificationDate. 42

4.2.44    prism:nationalCatalogNumber. 42

4.2.45    prism:number. 43

4.2.46    prism:object. 43

4.2.47    prism:onSaleDate. 44

4.2.48    prism:onSaleDay. 45

4.2.49    prism:offSaleDate. 45

4.2.50    prism:organization.. 46

4.2.51    prism:originPlatform... 47

4.2.52    prism:pageCount. 48

4.2.53    prism:pageProgressionDirection.. 48

4.2.54    prism:pageRange. 49

4.2.55    prism:person.. 49

4.2.56    prism:platform... 50

4.2.57    prism:productCode. 51

4.2.58    prism:profession.. 51

4.2.59    prism:publicationDate. 52

4.2.60    prism:publicationDisplayDate. 53

4.2.61    prism:publicationName. 53

4.2.62    prism:publishingFrequency. 54

4.2.63    prism:rating.. 55

4.2.64    prism:samplePageRange. 56

4.2.65    prism:section.. 56

4.2.66    prism:sellingAgency. 57

4.2.67    prism:seriesNumber. 58

4.2.68    prism:seriesTitle. 58

4.2.69    prism:sport. 59

4.2.70    prism:startingPage. 60

4.2.71    prism:subchannel1. 60

4.2.72    prism:subchannel2. 61

4.2.73    prism:subchannel3. 62

4.2.74    prism:subchannel4. 62

4.2.75    prism:subsection2. 64

4.2.76    prism:subsection3. 65

4.2.77    prism:subsection4. 65

4.2.78    prism:subtitle. 66

4.2.79    prism:supplementDisplayID.. 67

4.2.80    prism:supplementStartingPage. 67

4.2.81    prism:supplementTitle. 68

4.2.82    prism:teaser. 68

4.2.83    prism:ticker. 69

4.2.84    prism:timePeriod.. 70

4.2.85    prism:url 70

4.2.86    prism:uspsNumber. 71

4.2.87    prism:versionIdentifier. 72

4.2.88    prism:volume. 72

4.2.89    prism:wordCount. 73

 

 


1        Status

1.1      Document Status

The status of this document is:

ü

Draft

11/04/2011

ü

Released for Public Comment

12/15/2012

ü

Final Draft Released for Comment

06/12/2012

ü

Final Specification

10/04/2012

1.2      Document Location

The location of this document is:

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

or

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

1.3      Version History

Version Number

Release Date

Editor

Description

1.2

 

McConnell

Converted from unmodularized PRISM spec v 1.2

1.3

10/01/05

Kennedy

Resolved Industry Comments; added xml:lang attribute to translation examples.

2.0 Release

2/19/08

Kennedy

Final Release Version

2.1 Release

05/15/09

Kennedy

Final Spec with comments resolved

3.0 Draft

12/152011

Kennedy

Updated to support nextPub

3.0 Final Draft

06/12/2012

Kennedy

Final Draft with public comments resolved

3.0 Specification

10/04/2012

Kennedy

Final Specification


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 Section

Documents in the PRISM documentation package may contain both normative and non-normative material; normative material describes element names, attributes, formats, and the contents 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.2      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.3      The PRISM Documentation Package

The PRISM Documentation Package consists of:

2.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.3.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.4      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.5      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 metadata elements that the PRISM Working Group has defined and included in the PRISM namespace. All of Section 4 of this document is normative.

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: This document describes element models and provides examples for all PRISM profiles. In addition Profile #1 PRISM (well formed XML, with no requirement for RDF), is described in Guide to the PRISM Aggregator Message V.3.0. [PAMGUIDE].

3.2      New in this Version

Changes in this document include:

·        Addition of a new metadata field prism:contentType element to describe the content type of a resource. Sample content types include article, advertisement and chapter.  Values come from the new Content Type Controlled Vocabulary.

·        Addition of the new metadata elements prism:publishingFrequency, prism:publicationDisplayDate, prism:onSaleDay, prism:onSaleDate and prism:offSaleDate.

·        Updated and clarified definitions for prism:issueIdentifier, prism:coverDate, prism:coverDisplayDate and prism:publicationDate.

·        Addition of new serial issue metadata elements for prism:productCode and prism:uspsNumber.

·        Addition of new book identification elements prism:copyrightYear, prism:nationalCatalogNumber and prism:bookEdition.

·        Addition of a new metadata field prism:platform to describe a platform where content is used.  Values come from the Platform Controlled Vocabulary.

·        Addition of a new optional metadata field prism:device to further refine the definition of a platform by specifying the exact platform device such as make/model of tablet or smart phone.

·        Addition of a new metadata field prism:pageProgression Direction to describe the intended flip direction when content is displayed.

·        Addition of the new metadata field prism:pageCount to describe the total number of pages in an issue, article, book or chapter.

·        Addition of new metadata field prism:subtitle to identify the subtitle of a book or article.

·        Addition of new series metadata fields for prism:seriesTitle and prism:seriesNumber.

·        Addition of a new metadata field prism:supplementDisplayID to provide further identification for a supplement.

·        Addition of a new metadata field prism:supplementStartingPage to indicate the starting page of an article within a supplement.

·        Addition of a new metadata field prism:supplementTitle to indicate the title of a supplement within a magazine.

·        Addition of new metadata fields for prism:issueType (values from the new issueType CV) and prism: issueTeaser.

·        Addition of a new subject metadata element prism:academicField to describe an academic area of study.

·        Addition of a new subject metadata element prism:profession to describe a profession.

·        Addition of a new subject metadata element prism:sport to describe a sport

·        Addition of a new metadata subject field prism:link to describe a link such as a URL, email or even twitter hash tag.

·        Deprecated prism:embargoDate in favor of pur:embargoDate.

·        Deprecated prism:copyright in favor of pur:copyrightDate.

·        Deprecated prism:expirationDate in favor of pur:expirationDate.

·        Deprecated prism:rightsAgent in favor of pur:rightsAgent.

4        PRISM Element and Attribute Definitions

4.1      PRISM Namespace

In addition to the Dublin Core elements, the PRISM specification defines additional namespaces. The ‘prism’ namespace (http://prismstandard.org/namespaces/basic/3.0) contains elements suitable for a wide range of content publication, licensing, and reuse situations. Many of them are, in effect, extensions of the elements from Dublin Core.

The recommended namespace for PRISM is:
xmlns:prism=”http://prismstandard.org/namespaces/basic/3.0/

4.2      PRISM Element and Attribute Models

All three PRISM profiles are documented in this section. First Profile #1 is documented. The documentation for the XML only profile includes a field that indicates whether this element is included in the PRISM Aggregator Message. If the element is included in PAM, please refer to the Guide to the PRISM Aggregator Message [PAMGUIDE] for more detailed information about the use of the element in the context of the XML PAM message. The elements included in PAM are those elements that publishers plan to send to aggregators for the purpose of aggregation. Not all elements are included in PAM.

PRISM Profile #2 (RDF/XML) is also documented in this section. In combining XML with RDF, there is far greater flexibility in tagging than we are used to when we define XML elements and attributes with an XML DTD. The remainder of this section contains the most likely element/attribute models for PRISM Profile #2 PRISM. Other Profile #2 models are possible based on the interaction between XML and RDF.

PRISM Profile #3 (XMP) is also documented in this section. The documentation concentrates on the property and container values for the XMP field to provides information required to develop an XMP schema to implement PRISM in the XMP environment. Note that XMP can be particularly useful in extending the capability of encoding multimedia objects with PRISM metadata.

4.2.1    prism:academicField

Name

Academic Field (as the subject of a resource)

Identifier

prism:academicField

Definition

Refines dc:subject by specifying an academic speciality.

Comment

 

Occurrence

Occurs 0 or many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:academicField>anthropology</prism:academicField>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

string

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:academicField rdf:resource=”academic.xml/#anthropology”/>

 

Model #2

<prism:academicField>anthropology</prism:academicField>

Profile #3 (XMP)

 

Property Value

Text

4.2.2    prism:aggregateIssueNumber

Name

Aggregate Issue Number

Identifier

prism:aggregateIssueNumber

Definition

This number represents the total number of issues of a serial publication.

Comment

 

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

Non-negative number

Attributes

None

Example

<prism:aggregateIssueNumber>127</prism:aggregateIssueNumber>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Non-negative Integer

Attributes

 

Examples

Model #1

<prism:aggregateIssueNumber rdf:resource=”aggregate.xml”/>

 

Model #2

<prism:aggregateIssueNumber>127</prism:aggregateIssueNumber>

 

Profile #3 (XMP)

 

Property Value

Integer

4.2.3    prism:aggregationType

Name

Aggregation Type

Identifier

prism:aggregationType

Definition

The aggregation type specifies the unit of aggregation for a content collection.

Comment

PRISM recommends that the PRISM Aggregation Type Controlled Vocabulary be used to provide values for this element.

 

Note: PRISM recommends against the use of the #other value currently allowed in this controlled vocabulary. In lieu of using #other please reach out to the PRISM group at info@prismstandard.org to request addition of your term to the Aggregation Type Controlled Vocabulary.

Occurrence

Occurs 0 or 1 time

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

For PRISM Profile #1 (XML) best practice is to use a value from the PRISM Aggregation Type Vocabulary [PRISMCVS] to specify the aggregation unit of the resource.

Model #1

 

Element Content

String

Attributes

None

Example

<prism:aggregationType>journal</prism:aggregationType>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:aggregationType rdf:resource=”aggregation.xml#journal”/>

 

Model #2

<prism:aggregationType>journal</prism:aggregationType>

Profile #3 (XMP)

 

Property Value

Text

4.2.4    prism:alternateTitle

Name

Alternate Title

Identifier

prism:alternateTitle

Definition

An alternate title or alternate headline for a resource that may be used in a table of contents, a popup etc. and can vary with platform.

Comment

PRISM recommends that dc:title will be a name by which the resource is formally known on its origin platform. This element provides an alternate title or headline for use on another platform.

Occurrence

Occurs 0 or more times

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

For PRISM Profile #1 (XML) a required attribute specifies the delivery platform type.  Best practice is to use a value from the PRISM Platform Controlled Vocabulary [PRISMCVNS] to specify the platform where this title is used.

Model #1

 

Element Content

String

Attributes

platform = (value from prism:platform controlled vocabulary)

Example

<dc:title>Time Magazine’s Person of the Year</dc:title>

<prism:alternateTitle platform=”web”>2002 Person of the Year</prism:alternateTitle>

Profile #2 (RDF)

For PRISM Profile #2 (XML/RDF) you can combine the attributes from the PRISM namespace with RDF attributes. Indication of the platform for the alternate title is required.

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<dc:title rdf:resource=”http://www.timeinc.com/person2002” rdf:resource=”platform.xml#web”/>

<prism:alternateTitle rdf:resource=”http://www.time.com/online/person2002/” rdf:resource=”platform.xml#web”/>

 

Model #2

<prism:alternateTitle>Person of the Year 2002</prism:alternateTitle>

Profile #3 (XMP)

Platform is assumed by media object type

Property Value

bag prismAlternateTitle structure
     alternateTitle.text        Text

     alternateTitle.a-platform           Text, closed choice prism:platform

     alternateTitle.a-lang    Text, closed choice RFC 3066 controlled vocabulary

4.2.5    prism:blogTitle

Name

Blog Title

Identifier

prism:blogTitle

Definition

The title of a blog.

Occurrence

Occurs 0 or one times

Comment

The blog title applies to all blog entries.  Typically the blog title appears in the header of the blog.  Blog titles often have double meanings and often serve as a teaser for the blog.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:blogTitle>Dianne Kennedy’s Blog </prism:blogTitle>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

 

 

Model #2

 

Element Content

Plain Literal

Example

Model #1
<prism:blogTitle rdf:resource=”http://www.blogspot.com/dkennedy.xml” />

 

Model #2

<prism:blogTitle>Dianne Kennedy’s Blog </prism:blogTitle>

Profile #3 (XMP)

 

Property Values

Text

4.2.6    prism:blogURL

Name

Blog URL

Identifier

prism:blogURL

Definition

The URL for a Blog. .

Occurrence

Occurs 0 or one times

Comment

This element is a refinement of URL.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

anyURI

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:blogURL>http://idealliance1.blogspot.com/</prism:blogURL>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

 

 

Model #2

 

Element Content

Plain Literal

Example

Model #1
<prism:b
logURL rdf:resource=” http://idealliance1.blogspot.com/” />

 

Model #2

<prism:blogURL>http://idealliance1.blogspot.com/</prism:blogURL>

Profile #3 (XMP)

 

Property Values

Text

4.2.7    prism:bookEdition

Name

Book Edition

Identifier

prism:bookEdition

Definition

The edition of a book, usually associated with a timeframe or printing location.

Occurrence

Occurs 0 or more times

Comment

Book Edition should be used for books, while prism:edition defines the edition of a magazine or serial publication that indicates a regional variation of a magazine or serial publication.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:bookEdition>Tenth Edition</prism:bookEdition>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

 

 

Model #2

 

Element Content

Plain Literal

Example

Model #1
<prism:bookEdition rdf:resource=”http://www.timeinc.com/timemagazine_edition.xml” />

 

Model #2

<prism:bookEdition>Tenth Edition</prism:bookEdition>

Profile #3 (XMP)

 

Property Values

Text

4.2.8    prism:byteCount

Name

Byte Count

Identifier

prism:byteCount

Definition

Size, in 8-bit bytes, of the resource.

Occurrence

Occurs 0 or 1 time

Comment

Typically, prism:byteCount is the size of a file. It might be used to display an estimate of download time to a user, to serve as a quick check on whether a file was transmitted correctly between systems, etc. If the resource is compressed, such as a JPEG image, byteCount gives its compressed size, which is much easier to obtain.

 

Abbreviations, such as KB and MB MUST NOT be used.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:byteCount>2938472</prism:byteCount>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

 

 

Model #2

 

Element Content

Plain Literal

Example

Model #1
<prism:byteCount rdf:Resource=”http://www.idealliance.com/byte.xml/>

 

Model #2

<prism:byteCount>2938472</prism:byteCount>

Profile #3 (XMP)

 

Property Values

Integer

4.2.9    prism:channel

Name

Channel

 

Identifier

prism:channel

 

Definition

Web channel assigned to the resource.

 

Occurrence

Occurs 0 or more times

 

Comment

A resource may be assigned to one or more online channels.

 

This may be a different organization than indicated by the section, as channels address online navigation whereas sections address organization.  Channel organization may cross publications when content is placed online, and may combine sections or cut across sections. The channel often becomes part of the URL, whereas a section name may or may not be.

 

The four subchannel elements should be used to denote a hierarchy of subchannels. In other words, a subchannel2 should not be used unless a subchannel1 is present, a subchannel3 should not be used unless a subchannel2 is present, etc.

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

 

Model #1

 

 

Element Content

String

 

Attributes

xml:lang = (optional) designed for identifying the human language used

 

Example

<prism:channel>Sports</prism:channel>

 

Profile #2 (RDF)

 

 

Model #1

 

 

Element Content

URI Reference (empty element)

 

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

 

Model #2

 

 

Element Content

Plain Literal

 

Attributes

xml:lang = (optional) designed for identifying the human language used

 

Example

Model #2

<prism:channel rdf:Resouce=”channel.xml#Sports”/>

 

Model #2

<prism:channel>Sports</prism:channel>

 

Profile #3 (XMP)

 

 

Property Values

bag prismChannel structure
     channel.channel                          Text

     channel.subchannel1                 Text

     channel.subchannel2                 Text

     channel.subchannel3                 Text

     channel.subchannel4                 Text

     channel.a-lang                                            Text, closed choice RFC 3066 controlled vocabulary

 

 

4.2.10prism:complianceProfile

Name

Compliance Profile

Identifier

prism:complianceProfile

Definition

The PRISM specification compliance profile that the resource adheres to.

Occurrence

Occurs 0 or 1 time

Comment

Best Practice is to use a reference from the PRISM Compliance Profile Controlled Vocabulary [PRISMCVNS]. If the element is not present, consuming systems MAY treat the resource's compliance profile as unknown, or they MAY treat it as specified in a contractual, human-interpretable assertion -- that is, "Our contract with this producer says that they are Profile #2 compliant, so my consuming system will assume that it is." If the element is present and populated with values from the controlled vocabulary, consuming systems MUST assume that compliance is as asserted in the element. If the element is present and unpopulated or populated with a value other than as specified here, the behavior of the consuming system is undefined.

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

Recommended practice is to specify values from the PRISM Controlled Vocabulary for Compliance Profile [PRISMCVNS].

Model #1

Profile #1 (XML)

Element Content

String. Value from PRISM Compliance Controlled Vocabulary(one, two, three)

Attributes

None

Example

<prism:complianceProfile>one</prism:complianceProfile>

Profile #2 (RDF)

Recommended practice is to reference values from PRISM Controlled Vocabulary for Compliance Profile [PRISMCVNS] as URIs using the rdf:resource attribute. A second model allows text values, so implementations MUST be capable of handling text values, although interoperation with text value references cannot be guaranteed.

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)
(only two is valid for RDF/XML)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used
(only two is valid for RDF/XML)

Examples

Model #1

<prism:complianceProfile rdf:resource=”complianceprofile.xml#two”/>

 

Model #2

<prism:complianceProfile>two</prism:complianceProfile>

Profile #3 (XMP)

Recommended practice is to specify values from the PRISM Controlled Vocabulary for Compliance Profile [PRISMCVNS].

Property Value

Text, closed: three (three is the only valid value for XMP)

4.2.11prism:contentType

Name

Content Type

Identifier

prism:contentType

Definition

Describes the content type of the resource.  This

Occurrence

Occurs 0 or 1 time

Comment

Recommended practice is to use a value from the PRISM Content Type controlled vocabulary.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:contentType>article</prism:contentType>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:contentType rdf:resource=”contenttype.xml#article”/>

 

Model #2

<prism:contentType>article</prism:contentType>

Profile #3 (XMP)

 

Property Value

Text, closed choice prism:contentType controlled vocabulary

4.2.12prism:copyrightYear

Name

Copyright Year

Identifier

prism:copyrightYear

Definition

Identifies the copyright year of a book

Occurrence

Occurs 1 or more times

Comment

This field is to identify a book.  Is not used with magazines or other serial publications.

Included in PAM?

No

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:copyrightYear>2012</prism:copyrightYear>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

The two examples below show how dc:type, prism:genre, and dc:format all describe different aspects of a resource. For brevity, the examples below use relative URI references. Assume that they are within the scope of a base URI declaration:

 

Model #1

<prism:copyrightYear rdf:resource=”copyright.xml#year”/>

 

Model #2

<prism:copyrightYear>2012</prism:copyrightYear>

Profile #3 (XMP)

 

Property Value

Text

4.2.13prism:corporateEntity

Name

Corporate Entity

Identifier

prism:corporateEntity

Definition

The name(s) of publisher’s organizational units related to the resource, either as the financial owner or group responsible for the resource, and at a lower hierarchical level than the corporate entity named in dc:publisher.

Occurrence

Occurs 0 or more times

Comment

Not a model for identifying a corporate organization mentioned in the article.  prism:organization should be used to describe content about a corporation.

For Profile #2, if there are multiple corporate entities for the resource PRISM recommends listing the multiple entities inside one prism:corporateEntity element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, simple repeat the prism:corporateEntity element multiple times.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

None

Example

<prism:corporateEntity>Consumer Publications Business Unit</prism:corporateEntity>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Resource (no element content)

Attributes

Resource Reference.(rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:corporateEntity rdf:resource=”http://www.cpab.org/”>

 

Model #2

<prism:corporateEntity>Consumer Publications Business Unit</prism:corporateEntity>

 

Model #3

<prism:corporateEntity rdf:parseType=”Literal”>Consumer Publications Business Unit</prism:corporateEntity>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.14prism:coverDate

Name

Cover Date

Identifier

prism:coverDate

Definition

The cover date is the numeric form of the issue date (cover display date) printed on the cover of a magazine; suitable for storing in a database field with a 'date' data type.

Occurrence

Occurs 0 or 1 time

Comment

The cover date is not to be confused with either the publication date or with the offSaleDate.  It is simply the numeric expression of the date printed on the cover.

 

Note: Either a cover date or a publication date is required.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

none

Example

<prism:coverDate>2002-12-25</prism:coverDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

 Plain Literal

Attributes

 

Example

<prism:coverDate rdf:datatype=”http://www.w3.org/TR/xmlschema-2/#dateTime”>2002-07-14</prism:coverDate>

Profile #3 (XMP)

 

Property Value

Date

4.2.15prism:coverDisplayDate

Name

Cover Display Date

Identifier

prism:coverDisplayDate

Definition

The cover display date is the issue date printed on the cover of a magazine as a text string. 

Occurrence

Occurs 0 or 1 time

Comment

This field has the same meaning as the prism:coverDate element – the last date an issue should be displayed for sale. However, many issues will not have a simple date which can be loaded into a database field of a “date” datatype. For example, “Spring 2002.” Such dates should be placed in this element.

 

For the convenience of applications which allow the user to search content within a specified range of dates, both the prism:coverDate and the prism:coverDisplayDate elements may be provided. In applications where the cover date is to be displayed to a user, this element SHOULD be used in preference to prism:coverDate. The prism:coverDate element SHOULD be used for the date comparisons.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:coverDisplayDate>Spring 2002</prism:coverDisplayDate>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model#1

<prism:coverDisplayDate>Spring 2002</prism:coverDisplayDate>

 

Model#2

<prism:coverDisplayDate rdf:parseType=”Literal”>Fall &mdash; Winter, 2002 &mdash; 2003</prism:coverDisplayDate>

Profile #3 (XMP)

 

Property Value

Text

4.2.16prism:creationDate

Name

Creation Date

Identifier

prism:creationDate

Definition

Date (and potentially the time) the identified resource was first created.

Occurrence

Occurs 0 or 1 time

Comment

A publisher will not usually send this information to external parties, but will only use it in internal applications such as editorial workflow. The prism:coverDate element will be more commonly sent to others.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

none

Example

<prism:creationDate>2002-12-25</prism:creationDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Literal

Attributes

None

Example

<prism:creationDate>2002-12-25</prism:creationDate>

Profile #3 (XMP)

 

Property Value

Date

4.2.17prism:dateReceived

Name

Date Received

Identifier

prism:dateReceived

Definition

Date (and potentially time) the resource was received on current system.

Occurrence

Occurs 0 or 1 time

Comment

This element will not usually be provided by a publisher. Instead, it is provided so recipients can inform their providers of the time when the resource was received from the publisher.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

None

Example

<prism:dateReceived>2002-12-25</prism:dateReceived>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Example

<prism:dateReceived rdf:datatype=”http://www.w3.org/TR/xmlschema-2/#dateTime”>2001-12-25T06:30:00</prism:dateReceived>

Profile #3 (XMP)

 

Property Value

Date

4.2.18prism:device

Name

Device

Identifier

prism:device

Definition

Specification of a device to refine delivery platform by adding more specific targeting for the content.  Typically used to further differentiate electronic delivery platforms such as smart phones or tablets.

Occurrence

Occurs 0 or 1 time

Comment

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:device>iPhone 4S</prism:device>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

None

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

<prism:device>iPhone 4S</prism:device>

Profile #3 (XMP)

 

Property Value

Text

4.2.19prism:distributor

Name

Distributor

Identifier

prism:distributor

Definition

An identifier for the distributor of the resource.

Occurrence

Occurs 0 or 1 time

Comment

The organization or individual that most recently made the resource available, typically as part of a value-added service such as aggregation, syndication, or distribution. If the Publisher is the most recent distributor, omit this field.

 

Advanced practice is to use a URI for the distributor as a value for the rdf:resource attribute.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:distributor>LexisNexis</prism:distributor>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:distributor rdf:resource=

      ”http://prismstandard.org/vocabs/NYSE/NEWS”/>

 

Model #2

<prism:distributor>LexisNexis</prism:distributor>

 

Model #3

<prism:distributor rdf:parseType=”Literal”>Lexis&mdash;Nexis</prism:distributor>

Profile #3 (XMP)

 

Property Value

Text

4.2.20prism:doi

Name

Digital Object Identifier

Identifier

prism:doi

Definition

The Digital Object Identifier, DOI, for the article.

Occurrence

Occurs 0 or 1 time

Comment

 The DOI may also be used as the dc:identifier. If used as a dc:identifier, the URI form should be captured, and the bare identifier should also be captured using prism:doi. If an alternate unique identifier is used as the required dc:identifier, then the DOI should be specified as a bare identifier within prism:doi only.

If the URL associated with a DOI is to be specified, then prism:url may be used in conjunction with prism:doi in order to provide the service endpoint (i.e. the URL).

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<dc:identifier>doi:10.1030/03054</dc:identifier>

<prism:doi>10.1030/03054</prism:doi>

<prism:url>http://dx.doi.org/10.1030/03054</prism:url>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<dc:identifier rdf:resource=”doi:10.1030/03054”/>

<prism:doi>10.1030/03054”</prism:doi>

<prism:url rdf:resource=”http://dx.doi.org/10.1030/03054”/>

Profile #3 (XMP)

 

Property Value

Text

4.2.21prism:edition

Name

Edition of a Magazine

Identifier

prism:edition

Definition

An identifier for one of several alternate issues of a magazine or other resource.

Occurrence

Occurs 0 or 1 time

Comment

An issue of a magazine may be produced in multiple editions, with each edition providing content customized for a particular demographic or geographic group. Fortune, for example, is produced in a Domestic edition, a European edition, and an Asian edition. While much of the content overlaps, there is some content that is unique to each edition.

 

Note:  Not to be confused with a book edition (prism:bookEdition) that specifies a particular “printing” of a book, often associated with a timeframe or press location.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:edition>Domestic</prism:edition>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:edition>Domestic</prism:edition>

 

Model #2

<prism:edition rdf:parseType=”Literal”>Large <em>Type</em></prism:edition>

Profile #3 (XMP)

 

Property Value

Text

4.2.22prism:eIssn

Name

E(lectronic) Issn

Identifier

prism:eIssn

Definition

ISSN for an electronic version of the issue in which the resource occurs.

Occurrence

Occurs 0 or 1 time

Comment

Permits publishers to include a second ISSN, identifying an electronic version of the issue in which the resource occurs (therefore e(lectronic)Issn. If used, prism:eIssn MUST contain the ISSN of the electronic version. See prism:issn.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

None

Example

<prism:eIssn>0015-8259</prism:eIssn>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Example

Model #1

<prism:eIssn>0015-8259</prism:eIssn>

 

Model #2

<prism:eIssn rdf:parseType=”Literal”>0015&ndash;8259</prism:eIssn>

Profile #3 (XMP)

 

Property Value

Text

4.2.23prism:endingPage

Name

Ending Page

Identifier

prism:endingPage

Definition

Identifies the last page number for the printed resource.

Occurrence

Occurs 0 or 1 time

Comment

For use in bibliographic citation of resources. This element, when used, MUST hold the last page number on which any part of the resource occurs, regardless of sequential breaks or skips in page numbering. It MUST NOT be used in conjunction with the prism:startingPage element to arrive at a page count, since the resource may be printed across a non-contiguous page range.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:endingPage>21</prism:endingPage>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:endingPage>21</prism:endingPage>

 

Model #2

<prism:endingPage rdf:parseType=”Literal”>B&ndash;7</prism:endingPage>

Profile #3 (XMP)

 

Property Value

Text

4.2.24prism:event

Name

Event (as the subject of a resource)

Identifier

prism:event

Definition

A refinement of dc:subject.  An event (social gathering, phenomenon, or more generally something that happened at a specifiable place and time) referred to in order to indicate a subject of the resource.

Occurrence

Occurs 0 or more times

Comment

If there is more than one event related to a resource, include a separate instance of prism:event for each event. The value may be a text string or an authority file reference.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:event>1968 Democratic National Convention</prism:event>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:event rdf:resource=”http://www.SuperbowlXXXIV.com/desc/”>

 

Model #2

<prism:event>1968 Democratic National Convention</prism:event>

<prism:event>Woodstock</prism:event>

 

Model #3

<prism:event rdf:parseType=”Literal”>The Dog &amp: Pony Show</prism:event>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.25prism:genre

Name

Genre

Identifier

prism:genre

Definition

Refines the intellectual content of the resource as specified by prism:contentType.

Occurrence

Occurs 0 or more times

Comment

Recommended practice is to use a value from the PRISM Genre controlled vocabulary.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:genre>column</prism:genre>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:genre rdf:resource=”genre.xml#column”/>

 

Model #2

<prism:genre>column</genre>

Profile #3 (XMP)

 

Property Value

bag Text, closed choice prism:genre controlled vocabulary

4.2.26prism:hasAlternative

Name

Has Alternative

Identifier

prism:hasAlternative

Definition

Identifies an alternative resource in case the current resource cannot be used (typically because of rights restrictions) or there is a platform-based alternative.

Occurrence

Occurs 0 or more times

Comment

Identifies another resource that can be substituted in place of the current resource. This provides a means for avoiding unsightly things like printing blank rectangles containing "No rights to reproduce this image". It also allows for relating content that differs intellectually when delivered on alternate platforms. 

 

Alternatives are not simply a reformatting of the original work; they are a separate intellectual work. To point to alternatives which are a different resolution, color space, file format, or different delivery platform etc. see dc:hasFormat. For alternatives which are newer or older versions of the same intellectual work, see dcterms:hasVersion.

As an example, imagine a publisher distributing an article containing a stock photo to which they did not secure Brazilian rights. If the publisher sent the article to Brazil, they might describe the original image that was published, but suggest an alternative to their syndication partners using prism:hasAlternative.

Included in PAM?

No

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:hasAlternative>http://freeimages.com/pool.jpg
</prism:hasAlternative>

<prism:hasAlternative>http://www.usnews.com</prism:hasAlternative>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:hasAlternative rdf:resource= ”http://freeimages.com/Pool.jpg”/>

 

Model #2

<prism:hasAlternative>http://freeimages.com/pool.jpg
</prism:hasAlternative>

 

Model #3

<prism:hasAlternative rdf:parseType=”Literal”>ISBN&colon;5555-2345-122</prism:hasAlternative>

Profile #3 (XMP)

 

Property Value

bag Text, a refined version of dc:relation

4.2.27prism:hasCorrection

Name

Has Correction

Identifier

prism:hasCorrection

Definition

Identifies any known corrections to the current resource.

Occurrence

Occurs 0 or more times

Comment

The prism:hasCorrection element identifies the "correction block,” not a corrected version of the current resource. Corrected versions of the resource can be identified with the dcterms:hasVersion element.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

(optional) platform= (value from prism:platform controlled vocabulary) “email,” “mobile”, “broadcast,” “web,” “print,” “recordableMedia,” and “other” with a default of “all”

Example

<prism:hasCorrection>Published November 4, 2002 page 24 Clarification: The graphic in [PERSONAL TIME: YOUR TECHNOLOGY, Oct. 7] referred to B3D. We said that B3D allows your PC's spare computer power to be used by Brilliant's network. This power-sharing feature has not yet been activated, and, the company says, it will not be used without the computer owner's specific consent.</prism:hasCorrection>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource=)

 

(optional) platform= (value from prism:platform controlled vocabulary) “email,” “mobile,” “broadcast,” “web,”  “print,” “recordableMedia,” “other” with a default of “all.”

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

 

(optional) platform= (value from prism:platform controlled vocabulary – see Model #1 above)

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

(optional) platform= (value from prism:platform controlled vocabulary – see Model #1 above)

Examples

Model #1

<prism:hasCorrection rdf:resource="2002-08-corrections.xml”/>

 

Model #2

<prism:hasCorrection>Published November 4, 2002 page 24 Clarification: The graphic in [PERSONAL TIME: YOUR TECHNOLOGY, Oct. 7] referred to B3D. We said that B3D allows your PC's spare computer power to be used by Brilliant's network. This power-sharing feature has not yet been activated, and, the company says, it will not be used without the computer owner's specific consent.</prism:hasCorrection>

 

Model #3

<prism:hasCorrection rdf:parseType=”Literal”>Published November 4, 2002 page 24 Clarification:<el> The graphic in [PERSONAL TIME: YOUR

TECHNOLOGY, Oct. 7] referred to B3D. We said that B3D allows your PC's spare computer power to be used by Brilliant's network. This power-sharing feature has not yet been activated, and, the company says, it will not be used without the computer owner's specific consent.</prism:hasCorrection>

Profile #3 (XMP)

 

Property Value

bag prismHasCorrection structure

     hasCorrection.text                    Text

     hasCorrection.a-platform          Text, closed choice prism:platform controlled vocabulary

     hasCorrection.a-lang                  Text, closed choice RFC 3066 controlled vocabulary

Note: not a refined version of dc:relation

4.2.28prism:hasTranslation

Name

Has Translation

Identifier

prism:hasTranslation

Definition

The described resource has been translated into another language, and the referenced resource is that translation.

Occurrence

Occurs 0 or more times

Comment

Points from the original article to the translation(s), which must have a different identifier than the original resource. The language of the translated version can be determined by looking up the metadata for the translated version.

Recommended best practice is to identify the translated version with a URI. For Profile #2, if there are multiple translations for the resource PRISM recommends listing the multiple translations inside one prism:hasTranslation element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, just repeat the prism:hasTranslation element multiple times.

Included in PAM?

No

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:hasTranslation xml:lang=”it”>Romeo y Giulietta</prism:hasTranslation>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:hasTranslation rdf:resource=
”http://example.com/classics/Romeo y Giulietta”/>

 

Model #2

<prism:hasTranslation xml:lang=”it”>Romeo y Giulietta</prism:hasTranslation>

 

Model #3

<prism:hasTranslation rdf:parseType=”Literal”>Romeo &amp; Giulietta
</prism:hasTranslation>

Profile #3 (XMP)

 

Property Value

bag Text, a refined version of dc:relation

4.2.29prism:industry

Name

Industry (as the subject of a resource)

Identifier

prism:industry

Definition

An industry or industry sector, referred to in order to indicate a subject of the resource.

Occurrence

Occurs 0 or more times

Comment

Values can come from a controlled vocabulary such as SIC (Standard Industry Classification) and NAICS (North American Industry Classification Specification).

 

For Profile #2, if there is more than one industry related to a resource, PRISM recommends listing the multiple industries inside one prism:industry element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, simply repeat the prism:industry element multiple times.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:industry>Health Care &amp; Medicine</prism:industry>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Model #4

 

Element Content

Resource Node (contains pcv:Descriptor )

Attributes

Rdf:parseType attribute must be specified as “Resource”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:industry rdf:resource=

      ”http://prismstandard.org/vocabs/SIC/21395502”/>

 

Model #2

<prism:industry>Luxury goods</prism:industry>

 

Model #3

<prism:industry rdf:parseType=”Literal”>Health Care &amp; Medicine</prism:industry>

 

Model #4

<prism:industry rdf:parseType=”Resource”>

  <pcv:Descriptor>

    <pcv:label>Electric Power Generation</pcv:label>

  </pcv:Descriptor>

</prism:industry>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.30prism:isAlternativeOf

Name

Is Alternative Of

Identifier

prism:isAlternativeOf

Definition

Identifies this resource as an alternative to another.

Occurrence

Occurs 0 or more times

Comment

Identifies this resource as one that can be substituted in place of another resource. This provides a means for avoiding unsightly things like printing blank rectangles containing "No rights to reproduce this image". It also allows for relating content that differs intellectually when delivered on alternate platforms. 

 

Alternatives are not simply a reformatting of the original work; they are a separate intellectual work. To point to alternatives which are a different resolution, color space, file format, or different delivery platform etc. see dc:hasFormat. For alternatives which are newer or older versions of the same intellectual work, see dcterms:hasVersion.

As an example, imagine a publisher distributing an article containing a stock photo to which they did not secure Brazilian rights. If the publisher sent the article to Brazil, they might describe the original image that was published, but suggest an alternative to their syndication partners using prism:hasAlternative.

Included in PAM?

No

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:isAlternativeOf>http://freeimages.com/pool.jpg
</prism:isAlternativeOf>

<prism:isAlternativeOf>http://www.usnews.com</prism:isAlternativeOf>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:isAlternativeOf rdf:resource= ”http://freeimages.com/Pool.jpg”/>

 

Model #2

<prism:isAlternativeOf>http://freeimages.com/pool.jpg
</prism:isAlternativeOf>

 

Model #3

<prism:isAlternativeOf rdf:parseType=”Literal”>ISBN&colon;5555-2345-122</prism:isAlternativeOf>

Profile #3 (XMP)

 

Property Value

bag Text, a refined version of dc:relation

4.2.31prism:isbn

Name

ISBN

Identifier

prism:isbn

Definition

The ISBN for the publication in which the resource was published.

Occurrence

Occurs 0 or more times

Comment

For use with book serials where each volume has an ISBN.

 

This element can be used 0 or more times in recognition of the necessity to capture both an ISBN-10 and an ISBN-13 during the industry’s transition to ISBN-13. Whenever possible use an ISBN-13 value over an ISBN-10. For information on the transition visit http://www.isbn.org/standards/home/isbn/transition.asp.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:isbn>978-0-444-50928-4</prism:isbn>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:isbn>978-0-444-50928-4</prism:isbn>

 

Model #2

<prism:isbn rdf:parseType=”Literal”>0&ndash;12&ndash;373687&ndash;0</prism:isbn>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.32prism:isCorrectionOf

Name

Is Correction Of

Identifier

prism:isCorrectionOf

Definition

The described resource is a corrected version of the referenced resource.

Occurrence

Occurs 0 or more times

Comment

Note that this is NOT the inverse of the prism:hasCorrection element, which points to a correction block instead of a corrected resource.

For Profile #2, If there are multiple corrections for the resource PRISM recommends listing the multiple corrections inside one prism:isCorrectionOf element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, simply repeat the prism:isCorrectionOf element multiple times.

Included in PAM?

No

Included in PSV?

No

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:isCorrectionOf>http://wanderlust.com/2000/08/BelizeTravel.xml
</prism:isCorrectionOf/>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:isCorrectionOf rdf:resource=

“http://wanderlust.com/2000/08/BelizeTravel.xml”/>

 

Model #2

<prism:isCorrectionOf>http://wanderlust.com/2000/08/BelizeTravel.xml
</prism:isCorrectionOf>

 

Model #3

<prism:isCorrectionOf rdf:parseType=”Literal”>
dam&endash;obj&endash;32485u2</prism:isCorrectionOf>

Profile #3 (XMP)

 

Property Value

bag Text, a refined version of dc:relation

4.2.33prism:issn

Name

ISSN

Identifier

prism:issn

Definition

The ISSN for the publication in which the resource was published.

Occurrence

Occurs 0 or 1 time

Comment

If there are separate ISSNs for print and electronic versions, and if prism:ISSN is used, it MUST contain the ISSN for the print version. See prism:eIssn.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:issn>0015-8259</prism:issn>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:issn>0015-8259</prism:issn>

 

Model #2

<prism:issn rdf:parseType=”Literal”>0015&ndash;8259</prism:issn>

Profile #3 (XMP)

 

Property Value

Text

4.2.34prism:issueIdentifier

Name

Issue Identifier

Identifier

prism:issueIdentifier

Definition

A system generated unique publisher identifier for the issue of a serial publication.   The issue identifies should not be confused with the "special" issue name element, prism:issueName.

Occurrence

Occurs 0 or 1 time

Comment

This element is often used as the dc:identifier because it is unique within the publication.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:issueIdentifier>2121</prism:issueIdentifier>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:issueIdentifier>2121</prism:issueIdentifier>

Profile #3 (XMP)

 

Property Value

Text

4.2.35prism:issueName

Name

Issue Name

Identifier

prism:issueName

Definition

A special issue name, typically used for major issues of a magazine or other resource.

Occurrence

Occurs 0 or 1 time

Comment

Certain issues of a magazine may be commonly known by a name like "Swimsuit Issue" or "Buyer's Guide Issue." These are frequently memorable issues and contain materials of great reference value. Issues may be tied to a particular day, but still be known by a name, such as the "Halloween Issue." If an issue is known by a general date, such as "Spring 2002," use the prism:coverDisplayDate element instead.

 

The issue name is not a unique identifier.  The element issueIdentifier or dc:identifier should be used for that purpose.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:issueName>Swimsuit Issue</prism:issueName>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

 

 

Examples

Model #1

<prism:issueName>Swimsuit Issue</prism:issueName>

 

Model #2

<prism:issueName rdf:parseType=”Literal”>1997 Buyer&apos;s Guide</prism:issueName>

Profile #3 (XMP)

 

Property Value

Text

4.2.36prism:issueTeaser

Name

Issue Teaser

Identifier

prism:issueTeaser

Definition

A teaser that is used to increase interest in an issue of a magazine or other serial publication.

Occurrence

Occurs 0 or 1 time

Comment

The issue teaser should not be confused with the special issue name. 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used prism:platform = (optional) designed for identifying platform for teaser

Example

<prism:issueName>Swimsuit Issue</prism:issueName>

<prism:issueTeaser>The Hottest Swimsuits for 2012</prism:issueTeaser>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used prism:platform = (optional) designed for identifying platform for teaser

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used
prism:platform = (optional) designed for identifying platform for teaser

 

 

Examples

Model #1

<prism:issueTeaser>The Hottest Swimsuits for 2012</prism:issueTeaser>

Profile #3 (XMP)

 

Property Value

Text

4.2.37prism:issueType

Name

Issue Type

Identifier

prism:issueType

Definition

Defines the type of serial publication issue.

Occurrence

Occurs 0 or 1 time

Comment

Serial publications often have two different types of issues.  Regular issues are part of the subscription while Special Issues have a unique focus and content.  Special Issues are typically not included with the magazine subscription.

Note:  Best practice is to use values from the Issue Type Controlled Vocabulary

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:issueType>regularIssue</prism:issueType>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:issueType>regularIssue</prism:issueType>

Profile #3 (XMP)

 

Property Value

Text

4.2.38prism:isTranslationOf

Name

Is Translation Of

Identifier

prism:isTranslationOf

Definition

The described resource is a human-language translation of the referenced resource.

Occurrence

Occurs 0 or 1 time

Comment

This is a more specific version of prism:hasTranslation. This element is used when pointing from the translated resource back to the original. If the original resource is not known, the prism:hasTranslation element should be used for both directions of the relationship.

 

Best practice is to identify the original resource with a URI, but text identifiers are acceptable.

Included in PAM?

No

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:isTranslationOf>Ovid’s Ars Amatoria</prism:isTranslationOf>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:isTranslationOf rdf:resource=

“http://example.com/classics/Romeo and Juliet”/>

 

Model #2

<prism:isTranslationOf xml:lang=”it”>Ovid’s Ars Amatoria</prism:isTranslationOf>

 

Model #3

<prism:isTranslationOf rdf:parseType=”Literal”>Ovid&apos;s Ars Amatoria</prism:isTranslationOf>

Profile #3 (XMP)

 

Property Value

Text, a refined version of dc:relation

4.2.39prism:keyword

Name

Keyword

Identifier

prism:keyword

Definition

An element used to tag keywords likely to be used in search queries.

Occurrence

Occurs 0 or more times

Comment

Note that this differs from a subject or elements such as dc:subject, prism:person, prism:event, or prism:organization that are the subject of the article. Best practice is to use values from a keyword controlled vocabulary.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:keyword>virus</prism:keyword>

Profile #2

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:keyword>virus</prism:keyword>

 

Model #2

<prism:keyword rdf:parseType=”Literal”>0015&ndash;8259</prism:keyword>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.40prism:killDate

Name

Kill Date

 

Identifier

prism:killDate

 

Definition

Date (and potentially the time) the identified resource is to be removed from websites.

 

Occurrence

Occurs 0 or 1 time

 

Comment

This element is reserved for website content.  A new element, prism:offSaleDate should be used to specify when content (either print or digital) is to be removed from newsstands or online storefronts.

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

 

Model #1

 

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

 

Attributes

 

 

Example

<prism:killDate>2002-12-25</prism:killDate>

 

Profile #2 (RDF)

 

 

Model #1

 

 

Element Content

Plain Literal

 

Attributes

 

(optional) platform = (a value from prism:platform controlled vocabulary) “mobile” or “web” with a default assumed to match that specified by prism:originPlatform

 

Example

<prism:killDate>2002-12-25</prism:killDate>

 

Profile #3 (XMP)

 

 

Property Value

bag prismKillDate structure

    killDate.date                  Date

 

4.2.41prism:link

Name

Link (as a subject for a resource)

Identifier

prism:link

Definition

Describes a link to an outside resource such as a website, email or hash tag.

Occurrence

Occurs 0 or more times

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

None

Example

<prism:link>#xmlconference</prism:link>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

 

Examples

 

Model #1

<prism:link>#xmlconference</prism:link>

 

Model #2

<prism:link>#xmlconference</prism:link>

Profile #3 (XMP)

 

Property Value

Text

4.2.42prism:location

Name

Geographic Location (as the subject of a resource)

Identifier

prism:location

Definition

A geospatial location, referred to in order to indicate a subject of the resource.

Occurrence

Occurs 0 or more times

Comment

As with other subject identifiers, the best practice is NOT to tag locations which are only mentioned in passing. The staff doing the tagging should assume that a full-text engine will be available to find those. The location element, on the other hand, is to call out those locations which are a subject for the story, no matter how many times they are mentioned in the story. As a test, the tagging staff should ask themselves “if I was searching for information on location X, would I want to get this story as one of the search results?” If so, then it should be tagged with that location, otherwise not.

 

For Profile #2, if there is more than one location related to a resource, PRISM recommends listing the multiple locations inside one prism:location element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, just repeat the prism:location element multiple times.

The value may be a string or an authority file reference.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:location>Mississippi River Delta</prism:location>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:location rdf:resource=

      ”http://prismstandard.org/vocabs/ISO-3166/GR”/>

Profile #3 (XMP)

 

Property Value

bag Text

 

4.2.43prism:modificationDate

Name

Modification Date

Identifier

prism:modificationDate

Definition

Date and time the resource was last modified.

Occurrence

Occurs 0 or 1 time

Comment

Publishers will not usually send this information to external parties, but will use it for internal applications.

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

None

Profile #2 (RDF)

 

Model #1

 

Element Content

Literal

Attributes

 

Example

<prism:modificationDate 2000-02-28T23:55:38</prism:modificationDate>

Profile #3 (XMP)

 

Property Value

Date

4.2.44prism:nationalCatalogNumber

Name

National Catalog Number

Identifier

prism:nationalCatalogNumber

Definition

A national catalog number is a unique identification number that is assigned by a national body (such as the Library of Congress in the United States) to the catalog record created for each book in its cataloged collections. This number is, at times assigned before the publication of a book and is printed as part of the identification for that book.

Occurrence

Occurs 0 or 1 time

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:nationalCatalogNumber>**** </prism:nationalCatalogNumber>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

None

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang (optional) designed for identifying the human language used

Example

<prism:nationalCatalogNumber>40551</prism:nationalCatalogNumber>

Profile #3 (XMP)

 

Property Value

Text

4.2.45prism:number

Name

Number

Identifier

prism:number

Definition

Indication of the magazine issue within a volume.

Occurrence

Occurs 0 or 1 time

Comment

This element is intended to be used in combination with the prism:volume element to specify the magazine issue using the common scheme of Volume and Number. In the case of a double issue, the prism:number element may contain multiple identifiers. Separators are not specified by PRISM and are left to the publisher’s discretion.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

none

Example

<prism:number>11</prism:number>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:number>11</prism:number>

Profile #3 (XMP)

 

Property Value

Text

4.2.46prism:object

Name

Object (as the subject of a resource)

Identifier

prism:object

Definition

The name of a physical or virtual object, referred to in order to indicate a subject of the resource.

Occurrence

Occurs 0 or more times

Comment

This element is particularly intended for use when categorizing content by products, such as for product reviews. For example, <prism:object>Dodge Viper<prism:object> would be used to indicate that a subject of the story was a certain high-performance automobile.

For Profile #2, if there are multiple objects for the resource PRISM recommends listing the multiple entities inside one prism:object element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, simple repeat the prism:object element multiple times.

The element pim:object is available to specify an object as inline markup.

Note: In previous versions of the specification this element was known as prism:objectTitle.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:object>Eame’s chair</prism:object>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:object rdf:resource=”urn:upc:3847-4837-4”/>

 

Model #2

<prism:object>Eame’s chair</prism:object>

 

Model #3

<prism:object>Eame&apos;s chair</prism:object>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.47prism:onSaleDate

Name

On Sale Date

Identifier

prism:onSaleDate

Definition

The on sale date is the numeric date when a publication is made available for retail sale; suitable for storing in a database field with a 'dateTime' data type.

Occurrence

Occurs 0 or more times

Comment

Because the on sale date may vary by platform, it is the best practice to specify the platform using the PRISM Controlled Vocabulary for platform.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:onSaleDate platform=”print”>2002-12-25</prism:onSaleDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:onSaleDate>2001-03-01T06:30Z</prism:onSaleDate>

Profile #3 (XMP)

 

Property Value

bag prismOnSaleDate structure

    onSaleDate.date            Date

    onSaleDate.a-platform Text, closed choice prismPlatform controlled vocabulary

4.2.48prism:onSaleDay

Name

On Sale Day

Identifier

prism:onSaleDay

Definition

 

Occurrence

Occurs 0 or more times

Comment

The day that new issues of a publication are regularly made available for retail sale.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:onSaleDay platform=”print”>Tuesday</prism:onSaleDay>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:onSaleDay>Tuesday</prism:onSaleDay>

Profile #3 (XMP)

 

Property Value

bag prismOnSaleDay structure

    onSaleDay.       Text

    onSaleDate.a-platform Text, closed choice prismPlatform controlled vocabulary

4.2.49prism:offSaleDate

Name

Off Sale Date

Identifier

prism:offSaleDate

Definition

The specific date when a magazine issue is to be removed from retail sale. This date may be printed on the cover with words such as “Display Until”. Values are to be in W3C dateTime format (ccyy-mm-dd). The prism:offSaleDate value may be the same as that of the prism:coverDate, however the two serve different purposes.

Occurrence

Occurs 0 or more times

Comment

Because the off sale date may vary by platform, it is the best practice to specify the platform using the PRISM Controlled Vocabulary for platform.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:offSaleDate platform=”print”>2002-12-25</prism:offSaleDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:offSaleDate>2001-03-01T06:30Z</prism:offSaleDate>

Profile #3 (XMP)

 

Property Value

bag prismOffSaleDate structure

    offSaleDate.date           Date

    offSaleDate.a-platform Text, closed choice prismPlatform controlled vocabulary

4.2.50prism:organization

Name

Organization (when used as the subject of a resource)

Identifier

prism:organization

Definition

The name of an organization, referred to in order to indicate a subject of the resource.

Occurrence

Occurs 0 or more times

Comment

This element is used to indicate a company, government agency, non-profit organization, etc. as a subject of the current resource. If there is more than one organization related to a resource, include a separate instance of prism:organization for each. Many authority files exist that provide a comprehensive listing of organizations.

Not to be confused with prism:corporateEntity that is used to specify the publisher business unit tied to a resource.

 

The element pim:organization is available to specify organization as inline markup.

 

For Profile #2, If there are multiple organizations related to the resource PRISM recommends listing the multiple entities inside one prism:organization element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, simple repeat the prism:organization element multiple times.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:organization>Dept. of Energy</prism:organization>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:organization rdf:resource=

      ”http://prismstandard.org/vocabs/NYSE/IBM”/>

<prism:organization rdf:resource=

      ”http://prismstandard.org/vocabs/NASDAQ/MSFT”/>

 

Model #2

<prism:organization>Dept. of Energy</prism:organization>

 

Model #3

<prism:organization>Teacher&apos;s Union</prism:organization>

Profile #3 (XMP)

 

Property Value

bag Text

4.2.51prism:originPlatform

Name

Origin Platform

Identifier

prism:originPlatform

Definition

The original platform where a resource’s intellectual content was delivered.

Occurrence

Occurs 0 or more times

Comment

In case of simultaneous origin, this metadata field may be specified more than once. For example, the origin may simultaneously be mobile and online and should be indicated with two origins specified.

 

PRISM recommends against the use of the #other value allowed in the PRISM Platform controlled vocabulary. In lieu of using #other please reach out to the PRISM group at info@prismstandard.org to request addition of your term to the Platform Controlled Vocabulary.

Included in PAM?

Yes

Included in PSV?

No

Profile #1 (XML)

Recommended practice is to specify values from the PRISM Controlled Vocabulary for Platform [PRISMCVNS].

Model #1

 

Element Content

Empty

Attributes

(Required) platform = (value from prism:platform controlled vocabulary)

Example

<prism:originPlatform platform=”web”/>

Profile #2 (RDF)

Recommended practice is to reference values from PRISM Platform Controlled Vocabulary [PRISMCVNS] as URIs using the rdf:resource attribute. A second model allows text values, so implementations MUST be capable of handling text values, although interoperation with text value references cannot be guaranteed.

Model #1

 

Element Content

URI Resource (no element content)

Attributes

Authority Reference.(rdf:resource)

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1
<prism:originPlatform rdf:resource=”platform.xml#web”/>

 

Model #2
<prism:originPlatform>web</prism:originPlatform>

Profile #3 (XMP)

Recommended practice is to specify values from the PRISM Controlled Vocabulary for Platform [PRISMCVNS].

Property Value

bag Text, Closed: Choice: “email,” “mobile”, “broadcast,” “web,” “print,” “recordableMedia,” “tablet,” “smartphone” and “other.”

4.2.52 prism:pageCount

Name

Page Count

Identifier

prism:pageCount

Definition

Specifies the total page count for the published print version of the resource.

Comment

Page count is a non-negative integer. It may specify the page count for any print publication or component such as an article or chapter

Occurrence

Occurs 0 or 1 time

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

Non-negative integer

Example

<prism:pageCount>5</prism:pageCount>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal 

Attributes

None

Example

<prism:pageCount>5</prism:pageCount>

Profile #3 (XMP)

 

Property Value

Integer

4.2.53prism:pageProgressionDirection

Name

Page Progression Direction

Identifier

prism:pageProgressionDirection

Definition

Describes the page progression direction or flip direction of content as it is presented.

Occurrence

Occurs 0 or 1 time

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

Enumerated values LTR and RTL

Attributes

None

Example

<prism:pageProgressionDirection>LTR</prism:pageProgressionDirection>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

 

Model #1

<prism:pageProgressionDirection>LTR</prism:pageProgressionDirection>

 

Model #2

<prism:pageProgressionDirection>LTR</prism:pageProgressionDirection>

Profile #3 (XMP)

 

Property Value

Text, closed choice (LTR, RTL)

4.2.54prism:pageRange

Name

Page Range

Identifier

prism:pageRange

Definition

Identifies the page range for the published print version of the resource.

Comment

Page range is a string. Sequential pages are to be separated with a dash. Nonsequential pages are to be separated with a comma.

Occurrence

Occurs 0 or 1 time

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Example

<prism:pageRange>1,4-5</prism:pageRange>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal 

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:pageRange>1,4-5</prism:pageRange>

Profile #3 (XMP)

 

Property Value

Text

4.2.55prism:person

Name

Person (when used as the subject of a resource)

Identifier

prism:person

Definition

The proper name of a person, referred to in order to indicate a subject of the resource.

Occurrence

Occurs 0 or more times

Comment

Recommended best practice is to cite an entry into a controlled vocabulary of people. However, textual names are acceptable and are expected to be commonly used.

As with other subject identifiers, do not mark a resource for every person mentioned in the resource, only those which it is “about”.

PRISM makes no recommendation on the issue of direct vs. sort order for names (in other words, we do not recommend “Smith, Jane Q.” vs. “Jane Q. Smith”).

For Profile #2, if there is more than one person as the subject of a resource, PRISM recommends listing each inside one prism:person element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For Profile #1, just repeat prism:person element multiple times.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:person>David Steinhardt</prism:person>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:person rdf:resource=

    ”http://example.org/vocabs/People.xml#172”/>

 

Model #2

<prism:person>David Steinhardt</prism:person>

Profile #3 (XMP)

 

Property Value

bag Proper Name

4.2.56prism:platform

Name

Platform

Identifier

prism:platform

Definition

The delivery platform where a resource was delivered.

Occurrence

Occurs 0 or more times

Comment

Recommended best practice is to cite an entry in the PRISM Platform Controlled Vocabulary.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:platform>smartPhone</prism:platform>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:platform rdf:resource=

    ”http://example.org/vocabs/platform.xml#172”/>

 

Model #2

<prism:platform>smartPhone</prism:platform>

Profile #3 (XMP)

 

Property Value

Text

4.2.57prism:productCode

Name

Product Code

Identifier

prism:productCode

Definition

The product code, or bar code for a publication.  This may be a bipad or even a full UPC or Magazine barcode for periodicals.  For books the product code will be an EAN-13 barcode.

Occurrence

Occurs 0 or more times

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prism:productCode>**** </prism:productCode >

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

None

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang (optional) designed for identifying the human language used

Examples

Model #1

<prism:productCode rdf:resource=”http://www.AviationWeek.com/pubname/”/>

 

Model #2

<prism:productCode>40551</prism:productCode >

Model #3

<prism:productCode>40551</prism:productCode >

Profile #3 (XMP)

 

Property Value

Text

4.2.58prism:profession

Name

Profession (as the subject of a resource)

Identifier

prism:profession

Definition

Refines dc:subject.  Describes a profession.

Occurrence

Occurs 0 or 1 time

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang (optional) designed for identifying the human language used

Example

<prism:profession>law</prism:profession>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)
xml:lang (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:profession rdf:resource=“profession.xml/#law”/>

 

Model #2

<prism:profession>law</prism:profession>

Profile #3 (XMP)

 

Property Value

Text

4.2.59prism:publicationDate

Name

Publication Date

Identifier

prism:publicationDate

Definition

This is the close date in date time format for a print publication and the post date for digital content; suitable for storing in a database field with a 'date' data type.

Occurrence

Occurs 0 or more times

Comment

It is NOT the cover date. See prism:coverDate, and prism:coverDisplayDate for that information.

 

This is not to be confused with pur:embargoDate which is very specific for usage rights.

 

This is not to be confused with onSaleDate which specifies the day the content is available for sale.

 

Because the publication date may vary by platform, it is the best practice to specify the platform using the PRISM Controlled Vocabulary for platform.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String conforming with the PRISM dateOrTime format that allows for the specification of an ISO date or ISO date+time

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:publicationDate platform=”print”>2002-12-25</prism:publicationDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)

Example

<prism:publicationDate>2001-03-01T06:30Z</prism:publicationDate>

Profile #3 (XMP)

 

Property Value

bag prismPublicationDate structure

    publicationDate.date   Date

    publicationDate.a-platform        Text, closed choice prismPlatform controlled vocabulary

4.2.60prism:publicationDisplayDate

Name

Publication Display Date

Identifier

prism:publicationDisplay Date

Definition

This is the close date in date time format for a print publication and the post date for digital content expressed as a text string.

Occurrence

Occurs 0 or more times

Comment

It is NOT the cover date. See prism:coverDate, and prism:coverDisplayDate for that information.

 

This is not to be confused with pur:embargoDate which is very specific for usage rights.

 

This is not to be confused with onSaleDate which specifies the day the content is available for sale.

 

Because the publication date may vary by platform, it is the best practice to specify the platform using the PRISM Controlled Vocabulary for platform.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)
xml:lang (optional) designed for identifying the human language used

Example

<prism:publicationDisplayDate platform=”print”>January 25, 2011</prism:publicationDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(optional) platform = (value from prism:platform controlled vocabulary)
xml:lang (optional) designed for identifying the human language used

Example

<prism:publicationDisplayDate>January 25, 2011</prism:publicationDisplayDate>

Profile #3 (XMP)

 

Property Value

bag prismPublicationDate structure

    publicationDate.date   Text

    publicationDate.a-platform        Text, closed choice prismPlatform controlled vocabulary

4.2.61prism:publicationName

Name

Publication Name

Identifier

prism:publicationName

Definition

Title of the magazine, or other publication, in which a resource was/will be published.

Occurrence

Occurs 0 or 1 time

Comment

Typically this will be used to provide the name of the magazine an article appeared in, as metadata for the article, along with information such as the article title, the publisher, volume, number, and cover date.

 

Note: Publication name can be used to differentiate between a print magazine and the online version if the names are different such as “magazine” and “magazine.com.”

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang (optional) designed for identifying the human language used

Example

<prism:publicationName>Time Magazine</prism:publicationName>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:publicationName rdf:resource=”http://www.AviationWeek.com/pubname/”/>

 

Model #2

<prism:publicationName>Time Magazine</prism:publicationName>

 

Model #3

<prism:publicationName>Town &amp; Country</prism:publicationName>

Profile #3 (XMP)

 

Property Value

Text

4.2.62prism:publishingFrequency

Name

Publishing Frequency

Identifier

prism:publishingFrequency

Definition

The frequency with which a magazine or serial publication is published

Occurrence

Occurs 0 or 1 time

Comment

Best practice is to use values from the PRISM Publishing Frequency Controlled vocabulary.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang (optional) designed for identifying the human language used

Example

<prism:publishingFrequency>weekly</prism:publishingFrequency>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
xml:lang (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:publishingFrequency rdf:resource=”http://www.prismstandard.org/frequency.xml/#weekly”/>

 

Model #2

<prism:publishingFrequency>weekly</prism:publishingFrequency>

Profile #3 (XMP)

 

Property Value

Text. open choice (continually, daily, weekly, biweekly, monthly, bimonthly, quarterly, semiannually, annual, other)

4.2.63prism:rating

Name

Rating

Identifier

prism:rating

Definition

The rating of the media asset

Occurrence

Occurs 0 to many times

Comment

Media assets are often required to post a rating, especially when presented online or on mobile platforms.  A number of different rating schemes are available.  Best practice is to provide the rating system using the attribute on this element.

Example ratings schemes include ESRB (Entertainment Software Ratings Board) ,MPRS (Motion Picture Rating System) and TV Parental Guidelines.

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang (optional) designed for identifying the human language used

Example

<prism:rating ratingSystem=”ESRB“>E</prism:rating>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)
prism:ratingSystem (optional) identifies the rating system being referenced
xml:lang (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

prism:ratingSystem (optional) identifies the rating system being referenced
xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:rading rdf:resource=”http://www.prismstandard.org/esrb.xml/#E”/>

 

Model #2

<prism:rating ratingSystem=”ESRB“>E</prism:rating>

Profile #3 (XMP)

 

Property Value

Text

4.2.64prism:samplePageRange

Name

Sample Page Range

Identifier

prism:samplePageRange

Definition

Identifies the page range for sample pages of the resource that will be made freely available as a preview of the content.

Comment

Sample page range is a string. Sequential pages are to be separated with a dash. Nonsequential pages are to be separated with a comma.

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Example

<prism:samplePageRange>1,4-5</prism:samplePageRange>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal 

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:samplePageRange>1,4-5</prism:samplePageRange>

Profile #3 (XMP)

 

Property Value

Text

4.2.65prism:section

Name

Section

Identifier

prism:section

Definition

Name of the publication section in which the resource is categorized. A section is a logical subdivision of a publication which helps to identify the general subject domain of the contained content.

Occurrence

Occurs 0 or 1 time

Comment

In general, sections are named, may contain one or more stories, and may be either recurring or one-time. Stories may or may not be associated with a section.

 

Corresponds to magazine and newspaper sections. Sections without story content, such as "Table of Contents" and "Letters to the Editor" are also possible. Some sections will have subsections – for example a section on “Economy” might have subsections for Europe, Asia, the US, and Latin America. See the prism:subsection1, prism:subsection2, prism:subsection3, and prism:subsection4 elements for marking subsections and sub-subsections.

 

Some demographically-targeted editions may contain sections which are not available in the other editions of an issue.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang (optional) designed for identifying the human language us

Example

<prism:section>Travel</prism:section>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:section>Travel</prism:section>

 

Model #2

<prism:section rdf:parseType=”Literal”>Health &amp; Beauty / Cosmetics</prism:section>

Profile #3 (XMP)

 

Property Value

Text

4.2.66prism:sellingAgency

Name

Selling Agency

Identifier

prism:sellingAgency

Definition

The agency that sells the publication.

Occurrence

Occurs 0 to many times

Comment

The organization or individual that is responsible for the sales of the publication

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:sellingAgency>Ka wan, Inc</prism:sellingAgency>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:sellingAgency rdf:resource=

      ”http://jmpa.org/vocabs/Agencies/#kawaninc”/>

 

Model #2

<prism:sellingAgency>Ka wan, Inc</prism:sellingAgency>

Profile #3 (XMP)

 

Property Value

Text

4.2.67prism:seriesNumber

Name

Series Number

Identifier

prism:seriesNumber

Definition

The number of an issue within a series of issues, typically focused on a special topic.

Occurrence

Occurs 0 to 1 time

Comment

The number of this issue within the series

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

Non-negative Integer

Attributes

None

Example

<prism:seriesNumber>2</prism:seriesNumber>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

None

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:seriesNumber rdf:resource=

      ”http://jmpa.org/vocabs/series/#2”/>

 

Model #2

<prism:seriesNumber>2</prism:seriesNumber>

Profile #3 (XMP)

 

Property Value

Integer

4.2.68prism:seriesTitle

Name

Series Title

Identifier

prism:seriesTitle

Definition

The title of a series of serial publications.

Occurrence

Occurs 0 to 1 time

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

xml:lang = (optional) designed for identifying the human language used

Example

<prism:seriesTitle>The Master Chef Series</prism:seriesTitle>

Profile #2

 

Model #1

 

Element Content

URI Reference (empty element content)

Attributes

Resource Reference (rdf:resource)
xml:lang = (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:sellingAgency rdf:resource=

      ”http://jmpa.org/vocabs/Series/#ky32”/>

 

Model #2

<prism:seriesTitle>The Master Chef Series</prism:seriesTitle>

Profile #3 (XMP)

 

Property Value

Text

4.2.69prism:sport

Name

Sport (as the subject of a resource)

Identifier

prism:sport

Definition

Refines dc:subject.  Describes a sport, or an athletic activity requiring skill or physical prowess and often of a competitive nature.

Occurrence

Occurs 0 or 1 time

Comment

 

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1

 

Element Content

String

Attributes

xml:lang (optional) designed for identifying the human language used

Example

<prism:profession>law</prism:profession>

Profile #2

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)
xml:lang (optional) designed for identifying the human language used

Model #2

 

Element Content

Plain Literal

Attributes

xml:lang = (optional) designed for identifying the human language used

Examples

Model #1

<prism:sport rdf:resource=“sport.xml/#baseball”/>

 

Model #2

<prism:sport>baseball</prism:sport>

Profile #3 (XMP)

 

Property Value

Text

4.2.70prism:startingPage

Name

Starting Page

Identifier

prism:startingPage

Definition

Identifies the first page number for the published version of the resource.

Occurrence

Occurs 0 or 1 time

Comment

Provided to meet the needs of basic bibliographic citation of articles. A more complete description of an article’s pages is possible via prism:pageRange.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes