Copyright © 2020 Idealliance, Inc. This document is available under the W3C Document License. See the W3C Intellectual Rights Notice and Legal Disclaimers for additional information.
This PRISM PSV Markup Specification describes the XML markup used to exchange content encoded in PRISM Source Vocabulary; includes normative material.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications can be found in the W3C technical reports index at https://www.w3.org/TR/.
By publishing this document, W3C acknowledges that the Submitting Members have made a formal Submission request to W3C for discussion. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. This document is not the product of a chartered W3C group, but is published as potential input to the W3C Process. A W3C Team Comment has been published in conjunction with this Member Submission. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of W3C Membership. Please consult the requirements associated with Member Submissions of section 3.3 of the W3C Patent Policy. Please consult the complete list of acknowledged W3C Member Submissions.
The status of this document is:
|
• |
Draft |
November 8, 2011 |
|
• |
Released for Public Comment |
December 12, 2011 |
|
• |
Final Draft Released |
June 12, 2012 |
|
• |
Final Spec Released |
September 27, 2012 |
The location of this document is:
|
Version Number |
Release Date |
Editor |
Description |
|
12/15/2011 |
Kennedy |
Draft for Public Comment |
|
|
1.0 |
06/12/2012 |
Kennedy |
Final Draft |
|
1.0 |
09/27/2012 |
Kennedy |
Final Specification |
PSV is described in a set of formal, modularized documents that, taken together, represent “the nextPub Specification”. Together these documents comprise the nextPub Documentation Package.
Documents in the nextPub PSV Documentation Package may contain both normative and non-normative material.
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.
The PRISM Documentation Package has been reorganized and some specifications renamed to more accurately reflect the nature of each specification module. The PRISM documentation package includes the following specifications and documents:
This document provides compliance specification.
|
Document |
Description |
|
PRISM Compliance [PRISMCOMP] |
Describes three profiles of PRISM compliance for content and systems; includes normative material. |
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 |
|
PRISM Advertising Metadata Specification [PRISMADMS] |
Describes advertising metadata elements including those drawn from AdsML, GWG and Ad-ID; includes normative material. |
|
The PRISM Basic Metadata Specification [PRISMBMS] |
Describes the basic metadata elements contained in the PRISM namespace to describe article content; includes normative material. |
|
The PRISM Contract Management Metadata Specification [PRISMCMMS] |
Describes metadata elements from the PRISM Contract Management Metadata (pccm:) namespace that are used to describe contracts and legal documents. |
|
The PRISM Crafts Metadata Specification [PRISMCMS] |
Describes the metadata elements contained in the PRISM Crafts Metadata Namespace (pcm:). Includes normative material. |
|
Describes the metadata elements from the Dublin Core namespace that are included in PRISM; includes normative material. |
|
|
The PRISM Image Metadata Specification [PRISMIMS] |
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] |
Describes the metadata elements contained in the PRISM Recipe Metadata Namespace (prm:). Includes normative material. |
|
The PRISM Rights Summary Metadata Specification [PRISMRSMS] |
Describes the metadata elements contained in the PRISM Rights Summary Metadata Namespace (prsm:). Includes normative material. |
|
The PRISM Usage Rights Metadata Specification [PRISMURMS] |
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. Some elements from PUR are referenced from the newer, more comprehensive PRISM Rights Summary Metadata Specification [PRISMRSMS]. |
This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message (PAM) and other aggregator messages. This set of documents includes:
|
Document |
Description |
|
The PRISM PAM Markup Specification [PRISMPAMMS] |
Describes the XML elements and attributes used to encode the PRISM Aggregator Message from both the pam: and pim: namespaces; includes normative material. |
|
The PRISM PAM Markup for Web Content Specification [PRISMPAMWMS] |
Describes the XML elements and attributes used to encode the PRISM Aggregator Message for Web Content. This Specification draws from both the pam: and pim: namespaces and includes normative material. PAMW is used to automate the harvesting of Web Content so that it may be sent to aggregators or stored in a publishers PAM-based content management system. |
This module documents the PRISM Inline Markup Elements and Attributes for use with the PRISM Aggregator Message. This set of documents includes:
|
Document |
Description |
|
The PRISM Inline Markup Specification [PRISMIMS] |
Describes the XML elements used to encode the inline markup for the PRISM Aggregator Message. Includes normative material. |
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] |
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] |
The PRISM Controlled Vocabularies are now documented in this document. |
The Guide to the PRISM Aggregator Message [PAMGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.
The Guide to the PRISM Aggregator Message for Web Content [PAMWGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.
Guide to the PSV Aggregator/Distributor Message Package [PAMPGUIDE] documents how to use the PRISM metadata fields and pamP XML messaging tags to deliver content to content aggregators/distributors. The Guide documents the pamP XML message structure and provides the pamP XSD and document samples.
The Guide to PRISM Contract Management [CONTRACTSGUIDE] documents an XML-based PRISM contract management model. The Guide is accompanied by an XSD that can be used as the basis for developing a contract management system that interfaces with the PRISM Rights Summary to populate ODRL policy statements. Reference [ODRLRSGUIDE]
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 recipe model for developing a recipe database, for tagging a wide variety of recipes in XML and for tagging recipes within a PAM Message.
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.
PAM to PSV_Guide [PAMPSVGUIDE] documents mappings from PAM XML to PSV XML.
In 2010, Idealliance 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 PSV, PRISM Source Vocabulary Specification Version 1.0 consists of:
|
Document |
Description |
|
PRISM Source Vocabulary Specification Overview [PSVSO] |
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] |
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] |
The PSV Markup Specification documents the XML tags in the PSV namespace that are used to encode XML Source Content. |
While PRISM is primarily a metadata specification, it also includes some XML schemas that define encoding of specific kinds of content for publication and interchange. The PRISM schemas include:
• Contracts_xsd.zip contains a schema that can be used to encode publication contracts.
• Crafts_xsd.zip contains a schema that can be used to encode crafts.
• Image_xsd.zip contains a schema that can be used to encode images.
• PAM_xsd.zip contains a schema that can be used to encode a PRISM aggregator message.
• pamW_xsd.zip contains a schema that can be used to encode a PRISM aggregator message for Web content.
• pamP_xsd.zip contains a schema that can be used to encode a PRISM aggregator/distributor message package.
• PSV_xsd.zip contains a schema that can be used to encode content in PRISM Source Vocabulary.
• Recipe_xsd.zip contains a schema that can be used to encode recipes.
• Rights_xsd.zip contains a schema that can be used to encode usage rights.
PRISM has defined 38 controlled vocabularies using PRISM controlled vocabulary markup. See The PRISM Controlled Vocabulary Specification [PRISMCVS]. All CVs are available in CVs.zip.
PRISM namespace declarations can be found in Namespaces.zip. The following are the recommended Namespaces for PRISM metadata:
|
Usage Vocabulary |
Namespace |
|
PRISM Basic Metadata |
basic: |
|
PRISM Aggregator Message (PAM) Markup |
pam: |
|
PRISM Controlled Vocabulary Markup |
pcv: |
|
PRISM Source Vocabulary |
psv” |
|
PRISM Inline Markup |
psm |
|
Dublin Core metadatap |
dc: |
|
RDF |
rdf: |
|
PAM aggregator/distributor package |
pamp: |
|
PRISM Crafts metadata |
pcm: |
|
PRISM Contract Management metadata |
pccm: |
|
PRISM advertising metadata |
prism-ad: |
|
PRISM rights language metadata |
prl: |
|
PRISM recipe metadata |
prm: |
|
PRISM usage rights metadata |
pur: |
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.
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.
The purpose of this document is to describe the basic XML elements and attributes that the nextPub Working Group has defined in the psv: namespace.
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.
This is the first version of this Specification.
The nextPub psv: namespace has been developed to support an XML tag set (with a schema) specifically designed to encode PSV source content. PSV metadata fields and controlled vocabularies are not encoded within the PSV namespace. These fields and controlled vocabularies are taken from prism: and related metadata namespaces. The psv: namespace is reserved for containing elements for metadata fields developed within the PRISM metadata specifications. PSV is an XML tag set that provides high-level markup structures and uses PRISM metadata for a very specific purpose. PRISM remains the core specification for metadata and controlled vocabularies.
The recommended namespace for PSV markup is:
xmlns:psv =”http://prismstandard.org/namespaces/psv/1.0/”
PSV builds upon the foundation of PRISM Specifications. PSV defines XML structures for tagging source content, but it does not define its own metadata fields or controlled vocabularies. PSV is built upon PRISM and relies on the metadata fields and controlled vocabularies defined by PRISM. Of necessity, the development of PSV has mandated an update to the current version of PRISM because new metadata fields and controlled vocabularies and terms must be added to support nextPub functionality. Therefore PRISM 3.0 will be published simultaneously with the publication of nextPub 1.0 and will be highly referenced by the PRISM Source Vocabulary Specification [PSVS]. See Figure 4.1.
PAM is the PRISM Aggregator Message. PAM is an XML tag set (with a schema) built on the foundation of PRISM metadata and controlled vocabularies. PAM defines XML structures for tagging content to be sent to aggregators, but it does not define its own metadata fields or controlled vocabularies. The use case for PAM was originally to encode magazine articles in XML to deliver content to aggregators. While some publishers currently use PAM XML as a content source, that was not the original intent. PAM is an application of PRISM, but PAM and PRISM are not synonymous. PAM is an XML tag set that uses PRISM metadata for a very specific purpose while PRISM remains the core specification for metadata and controlled vocabularies. See Figure 4.1.
Figure 4.1 Relationship of PSV to PRISM and PAM
Note: Because nextPub is not build directly on PAM, A PAM to nextPub Transformation Guide to document the transformation from PAM encoded content to nextPub XML will be part of the future nextPub Documentation Set. This Guide will enable those publishers currently using PAM XML to encode their source content to move to nextPub as the XML Content Source in the future. An additional nextPub to PAM Transformation Guide will also be developed so those publishers using nextPub XML as their content source can continue to deliver PAM XML to aggregators.
The documentation for the psv: namespace elements are listed alphabetically.
|
Name |
Ad Booking |
|
Identifier |
psv:adBooking |
|
Definition |
This element is a container for the metadata fields associated with the ad booking transaction. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
See PRISM Advertising Metadata Specification[PRISMADMS] for the structure and a full description of the ad booking metadata fields. |
|
Attributes |
None |
|
Model |
adsml-at:SellerPlacementID, adsml-at:BuyerName, prism-ad:adPosition, prism-ad:targetAudience, gwg-at:PartVersion, adsml-at:Remarks |
|
Occurs In |
psv:description |
|
Example |
<psv:adBooking> <adsml-at:BuyerName>Media Associates</adsml-at:BuyerName> <prism-ad:adPostion>BC</prism-ad:adPosition> </psv:adBooking> |
|
Name |
Ad Identification Block |
|
Identifier |
psv:adIDBlk |
|
Definition |
This element is a container for Ad identification metadata fields |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
See PRISM Advertising Metadata Specification [PRISMADMS] for the structure and a full description of the ad identification metadata fields. |
|
Attributes |
None |
|
Model |
adsml-at:PrimaryMaterialsID, prism-ad:IDType?, prism-ad:adTitle |
|
Occurs In |
psv:uniqueIdentifier |
|
Example |
<psv:adIDBlk> <adsml-at:PrimaryMaterialsIdentifier>ACDV1234567</adsml-at:PrimaryMaterialsIdentifier> <prism-ad:IDType>Ad-ID</prism-ad:IDType> <prism-ad:adTitle>Mac & Cheese is for adults too! </prism-ad:adTitle> </psv:adIDBlk> |
|
Name |
Ad Materials |
|
Identifier |
psv:adMaterials |
|
Definition |
This element is a container for the metadata fields associated with the ad materials production. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
See PRISM Advertising Metadata Specification [PRISMADMS] for the structure and a full description of the ad materials metadata fields. |
|
Attributes |
None |
|
Model |
(adsml-at:CreatorName?, adsml-at:AdvertiserName?, adsml-at:AdvertisedProduct?, adsml-at:PrintFixArea? |
|
Occurs In |
psv:description |
|
Example |
<psv:adMaterials> <adsml-at:CreatorName>ABC Agency</adsml-at:CreatorName> <adsml-at:AdvertiserName>Kraft Foods</adsml-as:AdvertiserName> </psv:adMaterials> |
|
Name |
Aggregation Info |
|
Identifier |
psv:aggregationInfo |
|
Definition |
This element is a container for the metadata fields associated with the aggregation where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
(prism:aggregationType, dc:identifier, prism:platform?, prism:device*) |
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:aggregationInfo> <prism:aggregationType>book</prism:aggregationType> <dc:identifier>K1213</dc:identifier> </psv:aggregationInfo> |
|
Name |
Article Info |
|
Identifier |
psv:publicationInfo |
|
Definition |
This element is a container for the metadata fields associated with the article where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
|
|
Occurs In |
psv:description |
|
Example |
<psv:articleInfo> <prism:startingPage>24</prism:startingPage> <prism:section>Lifestyle</prism:section> </psv:articleInfo> |
|
Name |
Blog Entry Info |
|
Identifier |
psv:blogEntryInfo |
|
Definition |
This element is a container for the metadata fields associated with a blog entry where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
*prism:publicationDate, dc:title, meta |
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:blogEntryInfo> <prism:publicationDate>09/21/2012</prism:publicationDate> <dc:title>In a Panic</dc:title> </psv:blogEntryInfo> |
|
Name |
Blog Info |
|
Identifier |
psv:blogInfo |
|
Definition |
This element is a container for the metadata fields associated with the blog where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
Prism:blogtitle, prism:blogURL?, meta? |
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:blogInfo> <prism:blogTitle>Dianne Kennedy’s Blog</prism:blogTitle> <prism:blogID>568879</prism:blogID> </psv:blogInfo> |
|
Name |
Chapter Info |
|
Identifier |
psv:chapterInfo |
|
Definition |
This element is a container for the metadata fields associated with a chapter where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
prism:chapterNumber?, dc:title?, prism:startingPage?, prism:endingPage?, prism:pageCount?, prism:samplePageRange?, prism:section?, meta* |
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:chapterInfo> <prism:chapterNumber>10</prism:chapterNumber>
<dc:title>Main Dishes</dc:title> </psv:chapterInfo> |
|
Name |
Components |
|
Identifier |
psv:components |
|
Definition |
This element is a container for the metadata fields associated with components of an article or other nextPub content. |
|
Occurrence |
Occurs 0 to 1 time |
|
Comment |
|
|
Attributes |
None |
|
Model |
Attributes: refines= , componentType= dc:identifier, dc:title, psv:creators?, psv:usageRights?, psv:meta* |
|
Occurs In |
psv:metadata |
|
Example |
<psv:components> <psv:otherComponent> <dc:identifier>234KY8</dc:identifier> <dc:title>Recipe Tip #1</dc:title> <psv:otherComponent> </psv:components> |
|
Name |
Component Type |
|
Identifier |
psv:componentType |
|
Definition |
This element indicates the type of component for which metadata is being expressed. |
|
Occurrence |
1 time |
|
Comment |
|
|
Attributes |
None |
|
Model |
text |
|
Occurs In |
psv:metadata |
|
Example |
<psv:componentType>image</psv:componentType> |
|
Name |
Content |
|
Identifier |
psv:content |
|
Definition |
This element is a container for nextPub content coded in HTML5 |
|
Occurrence |
Occurs 1 time |
|
Comment |
|
|
Attributes |
None |
|
Model |
html5:head, html5:body |
|
Occurs In |
psv:nextPub |
|
Example |
<psv:nextPub> <psv:metadata> . . . </psv:metadata> <psv:content> . . . </psv:content> </psv:nextPub> |
|
Name |
Creators Block |
|
Identifier |
psv:creator |
|
Definition |
This element is a container for nextPub creator/contributor metadata |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
|
|
Attributes |
None |
|
Model |
dc:creator*, dc:contributor* |
|
Occurs In |
psv:metadata |
|
Example |
<psv:metadata> <psv:creators> <dc:creator prism:role="writer">Phil Taylor</dc:creator> </psv:creators> </psv:metadata> |
|
Name |
Description |
|
Identifier |
psv:description |
|
Definition |
This element is a container for the metadata fields describing a unit of content such as an article or advertisement. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
|
|
Attributes |
None |
|
Model |
prism:genre*, dc:subject*, dc:description?, dc:language*, prism:keyword*, dc:creator*, dc:contributor*, prism:flipDirection?, prism:wordCount?, prism:byteCount?, prism:event*, prism:industry*, prism:field*, prism:location*, prism:object*, prism:organization*, prism:person*, prism:timePeriod*, prism:ticker*, psv:adMaterials?, psv:adBooking?, psv:meta* |
|
Occurs In |
psv:metadata |
|
Example |
<psv:description> <prism:genre>feature</prism:genre> <prism:genre>opinion</prism:genre> <dc:creator prism:role="writer">Phil Taylor</dc:creator> <prism:wordcount>2175</prism:wordcount> <prism:organization>Colorado Rockies</prism:organization> </psv:description> |
|
Name |
Identification Block |
|
Identifier |
psv:metadata |
|
Definition |
This element is a container for the metadata fields that provide identification for non-advertising content. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
See [PAMGUIDE] for the structure and a full description of pam:article. |
|
Attributes |
xmlns:pam=, xmlns:prism=, xmlns:dc=, xmlns:pim= |
|
Model |
head (body)? (redefined in the PAM DTD to serve as containers) See [PAMGUIDE]. |
|
Occurs In |
psv:uniqueID |
|
Example |
<psv:uniqueID> <psv:IDBlk> <dc:identifier>20110502044</dc:identifier> <dc:title> Oh, The Places They'll Go</dc:title> </psv:IDBlk> </psv:uniqueID> |
|
Name |
Issue Info |
|
Identifier |
psv:issueInfo |
|
Definition |
This element is a container for the metadata fields associated with the issue where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
(prism:versionIdentifier?, prism:productCode?, prism:issn?, prism:eIssn?, , prism:uspsNumber?, prism:volume?, prism:numbe?, prism:edition?, prism:coverDate?, prism:coverDisplayDate, prism:publicationDate, prism:publicationDisplayDate?, prism:onSaleDate?, prism:offSaleDate?, prism:issueName?, prism:issueType?, prism:aggregateIssueNumber?, prism:issueIdentifier?, prism:issueTeaser?, prism:meta?) |
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:issueInfo> <prism:coverDate>05/05/2005</prism:coverDate> <prism:issueName>Mobile Advertising Issue</prism:issueName> </psv:issueInfo> |
|
Name |
Meta |
|
Identifier |
psv:meta |
|
Definition |
This element allows for the encoding of metadata from specifications outside IDEAlliance PRISM. |
|
Occurrence |
Occurs 0 to many times |
|
Comment |
|
|
Attributes |
prefix=, name=, content= |
|
Model |
Empty |
|
Occurs In |
psv:description, psv:mediaDescription |
|
Example |
<meta prefix=”adsml-at” name=”color” content=”BW”/> |
|
Name |
Metadata Block |
|
Identifier |
psv:metadata |
|
Definition |
This element is a container for all nextPub metadata fields. |
|
Occurrence |
Occurs 1 time |
|
Comment |
All metadata goes inside the nextPub metadata block. Metadata is not allowed witin the HTML5 <head element. |
|
Attributes |
None |
|
Model |
prism:contentType, psv:uniqueID, psv:description?, psv:relations?, psv:usageRights?, psv:components?, psv:whereUsed? |
|
Occurs In |
psv:nextPub |
|
Example |
<psv:nextPub> <psv:metadata> <prism:contentType>article</prism:contentType> <psv:uniqueID> <psv:IDBlk> <dc:identifier>20110502044</dc:identifier> <dc:title> Oh, The Places They'll Go</dc:title> </psv:IDBlk> </psv:uniqueID> <psv:description> <prism:genre>feature</prism:genre> <prism:genre>opinion</prism:genre> <dc:creator prism:role="writer">Phil Taylor</dc:creator> <prism:wordcount>2175</prism:wordcount> <prism:organization>Colorado Rockies</prism:organization> </psv:description> <psv:whereUsed> <prism:aggregationType>magazine</prism:aggregationType> <prism:platform>tablet</prism:platform> <prism:device>iPad 1</prism:device> <prism:publisher>Time, Inc.</prism:publisher> <prism:publicationName>Sports Illustrated</prism:publicationName> <prism:issueIdentifier>SI20110502</prism:issueIdentifier> <prism:coverDate>2011-05-02</prism:coverDate> <prism:coverDisplayDate>May 2, 2011</prism:coverDisplayDate> <prism:volume>114</prism:volume> <prism:number>18</prism:number> <prism:issn>0038-822X</prism:issn> <prism:startingPage>44</prism:startingPage> <prism:section>BASEBALL</prism:section> <prism:subsection1>THE ROCKIES</prism:subsection1> </psv:whereUsed> </psv:metadata> |
|
Name |
PRISM Source Vocabulary |
|
Identifier |
psv:psv |
|
Definition |
This element is the container for one unit of content |
|
Occurrence |
Occurs 1 time |
|
Comment |
This is the Root Element for PSV |
|
Attributes |
None |
|
Model |
psv:metadata, psv:content |
|
Occurs In |
-- |
|
Example |
<psv:psv> <psv:metadata> . . . </psv:metadata> <psv:content> . . . </psv:content> </psv:psr> |
|
Name |
Publication Info |
|
Identifier |
psv:publicationInfo |
|
Definition |
This element is a container for the metadata fields associated with the publication where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
(prism:publisher?, prism:publicationName?, prism:corporateEntity?, prism:sellingAgency?, prism:publishingFrequency?, prism:onSaleDay?, prism:meta?) |
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:publicationInfo> <prism:publisher>IDEAlliance</prism:publisher> <prism:publicationName>Spectrum</prism:publicationName> </psv:publicationInfo> |
|
Name |
Relations Metadata |
|
Identifier |
psv:relations |
|
Definition |
This element is a container for the metadata fields that provide relationship information among content units such as articles |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
See The PRISM Dublin Core Metadata Specification [PRISMDCMS] for more information about the relations metadata fields. Note that values for the relations fields must be non-literal values such as a URI. |
|
Attributes |
None |
|
Model |
dcterms:hasPart*, dcterms:isPartOf*, dcterms:requires*, dcterms:isRequiredBy* |
|
Occurs In |
psv:metadata |
|
Example |
<psv:relations> <dcterms:isPartOf>/usnews/articles/June/2011/kkry02.xml</dcterms:isPartOf> </psv:relations. |
|
Name |
Supplement Info |
|
Identifier |
psv:supplementInfo |
|
Definition |
This element is a container for the metadata fields associated with the supplement where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
|
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:supplementInfo> <prism:supplementTitle></prism:supplementTitle> </psv:supplementInfo> |
|
Name |
Unique Identifier |
|
Identifier |
psv:uniqueID |
|
Definition |
This element is a container for the metadata fields that provide a unique identifier for any unit of nextPub content. |
|
Occurrence |
Occurs 1 time |
|
Comment |
A unique identifier is required for each nextPub content unit. |
|
Attributes |
None |
|
Model |
IDBlk or adIDBlk |
|
Occurs In |
pam:message |
|
Example |
<psv:uniqueID> <psv:IDBlk> <dc:identifier>20110502044</dc:identifier> <dc:title> Oh, The Places They'll Go</dc:title> </psv:IDBlk> </psv:uniqueID> |
|
Name |
Usage Rights |
|
Identifier |
psv:usageRights |
|
Definition |
This element is a container for the metadata fields associated with the usage rights of a content unit. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
See The PRISM Usage Rights Metadata Specification [PRISMURMS] for the structure and a full description of usage rights metadata. |
|
Attributes |
None |
|
Model |
pur:reuseProhibited?, pur:agreement*, pur:permissions*, pur:restrictions*, pur:copyright*, pur:creditLine*, pur:rightsAgent*, pur:rightsOwner*, pur:expirationDate*, pur:embargoDate*, pur:exclusivityEndDate*, pur:optionEndDate*, pur:adultContentWarning*, |
|
Occurs In |
pam:message |
|
Example |
<psv:usageRights> <pur:reuseProhibited>No</pur:reuseProhibited> <pur:restrictions>No rights in Europe</pur:restrictions> </psv:usageRights> |
|
Name |
Article Info |
|
Identifier |
psv:websiteInfo |
|
Definition |
This element is a container for the metadata fields associated with the website where this content is used.. |
|
Occurrence |
Occurs 0 or 1 time |
|
Attributes |
None |
|
Model |
|
|
Occurs In |
psv:whereUsed |
|
Example |
<psv:websiteInfo> <prism:url>http://www.idealliance.org/spectrummagazine/</prism:url> </psv:websiteInfo> |
|
Name |
Where Used |
|
Identifier |
psv:whereUsed |
|
Definition |
This element is a container for the metadata fields associated with usage for a unit of content such as an article or media asset. |
|
Occurrence |
Occurs 0 to many times |
|
Comment |
The intent of this field is to track each use of a unit of content such as an article. When an article is published in print, on a smart phone and on two tablets, 4 instances of use may be recorded. |
|
Attributes |
None |
|
Model |
psv:aggregationInfo? psv:publicationInfo?, psv:issueInfo?, psv:articleInfo?, psv::websiteInfo?, psv: supplementInfo?, psv:bookInfo?, psv:chapterInfo?, psv:blogInfo?, psv:blogEntryInfo? |
|
Occurs In |
psv:metadata |
|
Example |
<psv:whereUsed> <prism:aggregationInfo> <prism:aggregationType>magazine</prism:aggregationType> <prism:platform>tablet</prism:platform> <prism:device>iPad 1</prism:device> </prism:aggregationType> </psv:whereUsed> |