W3C W3C Member Submission

PRISM Usage Rights Metadata Specification

W3C Member Submission 10 September 2020

This version:
https://www.w3.org/Submission/2020/SUBM-prism-20200910/
Latest version:
https://www.w3.org/Submission/prism/
Authors:
Dianne Kennedy (Idealliance)

Abstract

This PRISM Usage Rights Metadata Specification describes the metadata elements contained in the PRISM Specification to describe content usage rights; includes normative material.

Status of this document

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.

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:

prism-usage.html

1.3    Version History

Version Number

Release Date

Editor

Description

2.1

05/15/09

Kennedy

Final Spec with comments resolved

3.0

12/15/2011

Kennedy

Public Draft

3.0

6/12/2012

Kennedy

Final Draft Spec with comments resolved

3.0

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 Sections

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.1.1  Requirement Wording Note

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

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

2.2    The PRISM Documentation Package

The PRISM Documentation Package 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:

2.3    Compliance Specification

This document provides compliance specification.

Document

Description

PRISM Compliance [PRISMCOMP]

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

2.4    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

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.

The PRISM Subset of Dublin Core Metadata Specification [PRISMDCMS]

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

2.5    PRISM Aggregator Message Markup Specifications

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.

2.6    PRISM Inline Markup Specification

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

Document

Description

The PRISM Inline Markup Specification [PRISMIMS]

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

2.7    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]

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.

 

2.8    Additional PRISM Documentation (Non-Normative Guides)

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

2.9    PRISM Source Vocabulary Specifications

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.

2.10 PRISM Schemas

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.

2.11 PRISM Controlled Vocabularies

PRISM has defined 38 controlled vocabularies using PRISM controlled vocabulary markup.  See The PRISM Controlled Vocabulary prism-cvs.html

2.12 PRISM Namespaces

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:

2.13 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.14 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.

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 Usage Rights namespace. All of section 4 of this document is normative.

Note:  Additional examples of PRISM Usage Rights are documented in the PRISM Usage Rights Guide [RIGHTSGUIDE].

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 PRISM Usage Rights V. 3.0 [RIGHTSGUIDE].

3.2    New in this Version

The PRISM Usage Rights Metadata Specification has replaced any recommendation to use the Distribution Channel Controlled Vocabulary with the new PRISM Aggregation Type Controlled Vocabulary and separated the identification of delivery platform into a separate platform attribute.  See The PRISM Controlled Vocabularies Specification [PRISMCVS] Version 3.0 for documentation about the PRISM Aggregation Type CV and the PRISM Platform CV.

The PRISM Rights Language (PRL) has been deprecated with the publication of this PRISM Usage Rights Metadata Specification.

Rights elements within the PRISM namespace have also been deprecated with the publication of this PRISM Usage Rights Metadata Specification.

3.3    About dc:rights

PRISM maintains a single rights element from the Dublin Core Namespace. Although seldom used, this element remains useful for the expression of simple rights for those that do not need to provide more detailed rights information. The Working Group will retain dc:rights as an element of the PRISM metadata set. It will not be documented within the new PRISM Rights Guide and will remain a standalone element.

Other Dublin Core and PRISM rights elements have been deprecated from this specification with the publication of Version 3.0.

4     PRISM Usage Rights Namespace

For the first release of PRISM, the PRISM WG put only the most commonly-needed rights elements into the PRISM namespace. Because of the considerable activity around specifying rights and permissions at that time, the PRISM Working Group could not recommend an existing standard to follow, as they were able to do with XML, RDF, and Dublin Core. Therefore, the Working Group simply defined a small, simple, extensible language for expressing common rights and permissions known as the PRISM Rights Language (PRL).

Today, the landscape has changed considerably. A predominant rights description metadata set for magazine content has yet to emerge. On the digital image side, considerable work has been done by the PLUS Coalition. In addition, new media technologies have complicated matters, as rights are now tied to delivery platforms and distribution channels beyond print. The PRISM Working Group launched a rights committee in late 2007 whose goal was to update the rights portions of the PRISM Specification. The result of that work is the new pur: namespace, which will supplant the existing PRISM Rights Language (PRL) namespace and some elements within the prism: namespace.

The PRISM Usage Rights Namespace (prism:usageRights) seeks to aid publishers in the description and tracking of usage rights metadata. Like the PRL namespace, it does not serve to provide rights enforcement. The elements in this namespace capture publisher information regarding permissions, restrictions, recipients, rights owners/agents, and content warnings. There are several elements that specifically pertain to rights surrounding image manipulation. The breadth of the PRISM Usage Rights Namespace greatly surpasses that previously supplied by the PRISM Rights Language (PRL).

The recommended namespace for PRISM Usage Rights is:
xmlns:pur=“http://prismstandard.org/namespaces/pur/3.0/”

4.1    PRISM Usage Rights Element and Attribute Models

All three PRISM profiles are documented in this section. First Profile #1 (XML) 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 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.

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. Other PRISM 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 provide 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    Specifying the Platform

The PRISM Usage Rights Platform attribute describes the platform for content distribution. The attribute is used for the following elements in the PRISM Usage Rights Namespace [PRISMURNS]:

•       pur:restrictions

•       pur:permissions

•       pur:copyright

•       pur:creditLine

•       pur:embargoDate

•       pur:exlusivityEndDate

•       pur:expirationDate

•       pur:optionEndDate

•       pur:adultContentWarning

PRISM recognizes that distribution channels will frequently be publisher specific, and therefore did not see fit to constrain users to a controlled vocabulary. Best practice is for each publisher to define their own controlled vocabulary for distribution channel and communicate that vocabulary to all content recipients.

4.3    Specifying the Distribution Channel

The PRISM Usage Rights Distribution Channel attribute describes a type of content recipient or a method of reuse for content distribution. The attribute is used for the following elements in the PRISM Usage Rights Namespace [PRISMURNS]:

•       pur:permissions

•       pur:restrictions

•       pur:creditLine

•       pur:embargoDate

•       pur:exlusivityEndDate

•       pur:expirationDate

•       pur:optionEndDate

•       pur:adultContentWarning

PRISM recognizes that distribution channels will frequently be publisher specific, and therefore did not see fit to constrain users to a controlled vocabulary. Best practice is for each publisher to define their own controlled vocabulary for distribution channel and communicate that vocabulary to all content recipients.

One method to define a distribution channel controlled vocabulary is to base the vocabulary on the PRISM Aggregation Type Controlled Vocabulary combined with regionalization terms such as domestic, international, and internal.  See The PRISM Controlled Vocabularies Specification [PRISMCVS] Version 3.0 for documentation about PRISM Aggregation Types.

4.4    PRISM Usage Rights Elements and Attributes

4.4.1  pur:adultContentWarning

Name

Adult Content Warning

Identifier

pur:adultContentWarning

Definition

This element defines warnings that must be used in conjunction with this resource due to the presence of adult content.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

Adult content is defined as content that contains violence, nudity, and/or sexual references.

 

If this element is used more than one time each instance of the element should be qualified by either platform or by distribution channel which can include a platform modifier.

 

PRISM recommends against the use of the #other value allowed in the PRISM Platform controlled vocabulary.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

(Optional) adultContentAge = non-negative integer
(Optional) adultContentCode = user-defined string

(Optional) countryCode = string
(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)
(Optional) xml:lang = designed for identifying the human language used

 

Example

<pur:adultContentWarning adultContentAge=”18” adultContentCode=”345” platform=”mobile” distributionChannel=”feed”>Warning: Restricted to those 18 and older due to extreme violence.</pur:adultContentWarning>

Profile #2 (RDF)

Complex RDF modeling possible

Profile #3 (XMP)

 

Property Value

bag Text

4.4.2  pur:agreement

Name

Agreement

Identifier

pur:agreement

Definition

Agreement is used to identify all contracts and releases.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

This element is used to capture a free text description of the agreement in addition to the type, status, agreementID, and xml:lang as attributes. Agreement types are suggested but are not a formal controlled vocabulary.

 

The status of an agreement comes from the USE Plus Specification for digital images includes limited, unlimited, unknown, NA, None

The Agreement ID can be used to tie the resource to a contract or release.

The rdf:resource attribute is a pointer to the location of the agreement online or in a database.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

(Optional) agreementType = property release, subject release, event release, object release, agency agreement, photographer contract, illustrator contract, writer contract.

 (Required) status = limited, unlimited, unknown, NA, none

(Optional) agreementID = string (to tie to a contract or release)

(Optional) rdf:resource = pointer to agreement

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

Example

<pur:agreement type=”property release” status=”limited” agreementID=”PR080308Tk43”>For use of personal home</pur:agreement>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

(Optional) rdf:resource = pointer to agreement

(Optional) agreementType = property release, subject release, event release, object release, agency agreement, photographer contract, illustrator contract, writer contract.

(Required) status = limited, unlimited, unknown, NA, none

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

(Optional) agreementID = string (to tie to a contract or release)

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

 

Model #2

 

Element Content

Plain Literal

Attributes

(Optional) agreementType = property release, subject release, event release, object release, agency agreement, photographer contract, illustrator contract, writer contract.

(Required) status = limited, unlimited, unknown, NA, none

(Optional) agreementID = string (to tie to a contract or release)

(Optional) rdf:resource = pointer to agreement

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

Example

<pur:agreement type=”property release” status=”limited” agreementID=”PR080308Tk43”>For use of personal home</pur:agreement>

Profile #3 (XMP)

 

Property Value

bag Text

4.4.3  pur:copyright

Name

Copyright

Identifier

pur:copyright

Definition

Copyright statement for the resource.

Occurrence

Occurs 0 or more times

Comment

Typically this field will contain the same copyright statement as appears in the magazine, book or other publication. The © character may be provided directly, or by the numeric character entity "&#169;".

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

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

Example

<pur:copyright>© Copyright 2001, Time Inc. All rights reserved.</pur:copyright>

Profile #2 (RDF)

For profile 2 (XML/RDF) you can combine the attributes from the PRISM namespace with RDF attributes.

Model #1

 

Element Content

URI Resource (no element content)

Attributes

Authority Reference.(rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

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

Model #3

 

Element Content

XML Literal

Attributes

rdf:parseType=”Literal”
(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

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

Example

Model #1

<pur:copyright rdf:resource=”http://www.timeinc.com/copyright/”>

 

Model #2

<pur:copyright>© Copyright 2001, Time Inc. All rights reserved.</pur:copyright>

 

Model #3

<pur:copyright rdf:parseType="Literal">&#169; Copyright 1995-2002, Wicked Publications Inc.</pur:copyright>

Profile #3 (XMP)

 

Property Values

bag Text

4.4.4  pur:creditLine

Name

Credit Line

Identifier

pur:creditLine

Definition

Used to encode the credit line for a media asset. The element indicates whether the credit is required by agreement and the distribution channel to which it applies.

Occurrence

Occurs 0 or more times

Comment

If this element is used more than one time, each instance of the element should be qualified by distribution channel.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

(Optional) required= (Boolean)

(Optional) agreementID = string

(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

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

Example

<pur:creditLine required=”y” distributionChannel=”internationalAggregator”>Courtesy of PETA</pur:creditLine>

Profile #2 (RDF)

Complex RDF modeling possible

Profile #3 (XMP)

 

Property Value

bag Text

4.4.5  pur:embargoDate

Name

Embargo Date

Identifier

pur:embargoDate

Definition

Earliest date (potentially including time) the resource may be made available to users or customers according to the rights agreement or to a clause in the rights agreement.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

It is common practice to embargo information – provide it to publishers in advance under an agreement that it will not be published until the embargo expires at some specific date and time. After that the information may be released to the outside world.

 

The embargoDate is not a property of the resource as much as it is a property of the agreement under which the resource is provided. Therefore, this element is considered to be a rights-based element.

 

Best practice is to use the W3C dateTime format. PRISM uses a typed literal in an XSD environment to enforce the W3C date format.

 

If this element is used more than one time, each instance of the element should be qualified by distribution channel.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)
(Optional) agreementID= string

Example

<pur:embargoDate distributionChannel=”website”>2002-12-31T13:20:00.000-05:00</pur:embargoDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)
(Optional) agreementID= string

Example

<pur:embargoDate rdf:datatype=”http://www.w3.org/TR/xmlschema-2/#dateTime”>2002-12-25</pur:embargoDate>

Profile #3 (XMP)

 

Property Value

bag Date: "If more than one, then refine using XMP Qualifer distributionChannel=

4.4.6  pur:exclusivityEndDate

Name

Exclusivity End Date

Identifier

pur:exclusivityEndDate

Definition

The date (potentially including time) when exclusive use of the resource ends according to a rights agreement.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

This is not to be confused with killDate, which is not tied to a rights agreement.

 

If this element is used more than one time each instance of the element should be qualified by distribution channel.

 

Note: Best practice is to use the W3C dateTime format. PRISM uses a typed literal in an XSD environment to enforce the W3C date format.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) distributionChannel = user defomed string
(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

(Optional) agreementID= string

Example

<pur:exclusivityEndDate distributionChannel=”magazineReuse”>2002-12-31T13:20:00.000-05:00</pur:exclusivityEndDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(Optional) distributionChannel = user defined string
(Optional) agreementID= string

Example

<pur:exclusivityEndDate rdf:datatype=”http://www.w3.org/TR/xmlschema-2/#dateTime”>2002-12-25</pur:exclusivityEndDate>

Profile #3 (XMP)

 

Property Value

bag Date: "If more than one, then refine using XMP Qualifer distributionChannel=

4.4.7  pur:expirationDate

Name

Expiration Date

Identifier

pur:expirationDate

Definition

The date (potentially including time) by which the resource must be removed from availability to users or customers according to a rights agreement.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

Since the expirationDate is a property of a rights agreement, not of the resource itself, this element is a rights-based element. This is not to be confused with killDate, which is not tied to a rights agreement.

 

This element differs from pur:exclusivityEndDate in that the expiration date indicates when a resource must be removed from availability, not the expiration of exclusive availability.

 

If this element is used more than one time each instance of the element should be qualified by distribution channel.

 

Best practice is to use the W3C dateTime format. PRISM uses a typed literal in an XSD environment to enforce the W3C date format.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

 

Note: PRISM will deprecate the prism:expirationDate element in favor of the pur:expirationDate element in PRISM 3.0. Recommended best practice is to use the element in this namespace.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) distributionChannel = user-defined string based on the PRISM Aggregation Type Controlled Vocabulary combined with qualifying prefixes

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)
(Optional) agreementID= string

Example

<pur:expirationDate distributionChannel=”buyerGuide”>2002-12-31T13:20:00.000-05:00</pur:expirationDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(Optional) distributionChannel = user-defined string based

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)
(Optional) agreementID= string

Example

<pur:expirationDate rdf:datatype=”http://www.w3.org/TR/xmlschema-2/#dateTime”>2009-09-19</pur:expirationDate>

Profile #3 (XMP)

 

Property Value

bag Date: "If more than one, then refine using XMP Qualifer distributionChannel=

4.4.8  pur:imageSizeRestriction

Name

Image Size Restriction

Identifier

pur:imageSizeRestriction

Definition

Specifies the usage restriction on image size.

Occurrence

Occurs 0 or 1 time per digital image

Comment

When horizontal and vertical maximum usage dimensions are specified they must include a unit of measure specific to the platform on which the publication will be delivered. When the publication platform is web, for example, the unit should be pixels.

 

Text describing the size restriction may be specified in place of exact maximum dimensions.  For example, the restriction may be “full page” or “spread”.

 

Note: PRISM recommends against the use of the #other value allowed in the PRISM Platform controlled vocabulary.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

(Optional) verticalDimension = (include unit of measure)

(Optional) horizontalDimension = (include unit of measure)

(Optional) platform =

(Optional) agreementID = string (to tie to a contract or release)

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

Example

<pur:imageSizeRestriction platform=”print”>full page</pur:imageSizeRestriction>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Optional) verticalDimension = (include unit of measure)

(Optional) horizontalDimension = (include unit of measure)

(Optional) platform =

(Optional) agreementID = string (to tie to a contract or release)

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

Model #2

 

Element Content

Plain Literal

Attributes

Optional) verticalDimension = (include unit of measure)

(Optional) horizontalDimension = (include unit of measure)

(Optional) platform =

(Optional) agreementID = string (to tie to a contract or release)

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

Examples

Model #1

<pur:imageSizeRestriction rdf:resource=”http://www.PhantasticPhotos.com”/>

 

Model #2

<pur:imageSizeRestriction>full page</pur:imageSizeRestrictiton>

Profile #3 (XMP)

 

Property Value

Text

4.4.9  pur:optionEndDate

Name

Option End Date

Identifier

pur:optionEndDate

Definition

The date (potentially including time) by which the resource must be used according to the rights agreement.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

If this element is used more than one time each instance of the element should be qualified by distribution channel.

 

Note: Best practice is to use the W3C dateTime format. PRISM uses a typed literal in an XSD environment to enforce the W3C date format.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) distributionChannel = string
(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

(Optional) agreementID= string

Example

<pur:optionEndDate distributionChannel=”website”>2002-12-25</pur:optionEndDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)
(Optional) agreementID= string

Example

<pur:optionEndDate rdf:datatype=”http://www.w3.org/TR/xmlschema-2/#dateTime”>2009-09-19</pur:optionEndDate>

Profile #3 (XMP)

 

Property Value

bag Date: "If more than one, then refine using XMP Qualifer distributionChannel=

4.4.10            pur:permissions

Name

Permissions

Identifier

pur:permissions

Definition

Specifies special usage permissions by distribution channel.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

If this element is used more than one time each instance of the element should be qualified by the distribution channel. Note that a usage fee may be tied to each distribution channel using the permissions element by combining the distributionChannel= attribute with the usageFee= attribute on the permissions element.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

 (Optional) code = (special user-defined permissions code)

(Optional) countryCode = (when permissions vary by country)

(Optional) agreementID = string (to tie to a contract or release)

(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary) (Optional) usageFee= string

(Optional) xml:lang (specify language of permissions statement

Example

<pur:permissions distributionChannel=”domesticMagazineReuse”>Image may be used in a spread where alcoholic beverages are advertised.</pur:permissions>

Profile #2 (RDF)

Complex RDF modeling possible

Profile #3 (XMP)

 

Property Value

bag Text; If more than one, then refine using XMP Qualifer distributionChannel=

4.4.11            pur:restrictions

Name

Restrictions

Identifier

pur:restrictions

Definition

Specifies special usage restrictions by distribution channel.

Occurrence

Occurs 0 or more times qualified by distribution channel

Comment

Recommended practice is to use the ISO 3166-1 country codes or a publisher-defined set of country codes for Country Code.

 

The values used for the attribute code could be the same as the codes used for prism:usageRights:permissions. In this case, users should take care to ensure that the code can be properly interpreted as a restriction.

 

If this element is used more than one time each instance of the element should be qualified by distribution channel.

 

Best practice for the distributionChannel attribute is for the publisher to define a controlled vocabulary defining relevant distribution channels. If distribution channel is not specified, consider the data applicable to all distribution channels.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String

Attributes

(Optional) code = (special user-defined permissions code)

(Optional) countryCode (when permissions vary by country)

(Optional) agreementID = string (to tie to a contract or release)

(Optional) distributionChannel = user-defined string

(Optional) platform = (value from the PRISM Platform Controlled Vocabulary)

(Optional) xml:lang (specify language of permissions statement

Example

<pur:restrictions distributionChannel=”domesticMagazineReuse”>Image may not be used in a spread where alcoholic beverages are advertised.</pur:restrictions>

Profile #2 (RDF)

Complex RDF modeling possible

Profile #3 (XMP)

 

Property Value

bag Text; If more than one, then refine using XMP Qualifer distributionChannel=

4.4.12            pur:reuseProhibited

Name

Reuse Prohibited

Identifier

pur:reuseProhibited

Definition

Specifies that there are no rights to reuse this resource.

Occurrence

Occurs 0 or 1 time

Comment

If not specified, some kind of reuse is assumed to be allowed.  This is a “flag” that lets users know that reuse is not an option.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Element Content

String (yes / no/ provisional/ ask)

Attributes

None

Example

<pur:reuseProhibited>yes</pur:reuseProhibited>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

Model #2

 

Element Content

Plain Literal

Attributes

None

Examples

Model #1

<pur:reuseProhibited rdf:resource=”http://www.xyzCorp.com/usage”/>

 

Model #2

<pur:reuseProhibited>Yes</pur:reuseProhibited>

Profile #3 (XMP)

 

Property Value

Text

4.4.13            pur:rightsAgent

Name

Rights Agent

Identifier

pur:rightsAgent

Definition

Name, and possibly contact information, for the person or organization that should be contacted to license the rights to use a resource.

Occurrence

Occurs 0 or more times

Comment

This element should contain human-readable information. PRISM recommends that this be a simple text element. However, the content of this element may be elements from other namespaces, such as one that gives contact information, should such a namespace be acceptable to all the parties in the PRISM communication.

 

The rights agent is not necessarily the rights owner.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) agreementID =

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

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”

(Optional) agreementID =

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

Examples

Model #1

<pur:rightsAgent rdf:resource=http://www.PhantasticPhotos.com/>

<pur:rightsOwner rdf:resource=http://www.PhantasticPhotos.com/>

 

Model #2

<pur:rightsAgent>Phantastic Photos, Philadelphia</pur:rightsAgent>

<pur:rightsOwner>Victoria’s Secret</pur:rightsOwner>

Profile #3 (XMP)

 

Property Value

Bag Text

4.4.14            pur:rightsOwner

Name

Rights Owner

Identifier

pur:rightsOwner

Definition

Name, and possibly contact information, for the person(s) or organization(s) that owns the rights to use a resource. This may differ from the rights agent.

Occurrence

Occurs 0 or more times

Comment

This element should contain human-readable information. PRISM recommends that this be a simple text element. However, the content of this element may be elements from other namespaces, such as one that gives contact information, should such a namespace be acceptable to all the parties in the PRISM communication.

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

(Optional) agreementID =

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

 

Example

<pur:rightsOwner>Victoria’s Secret</pur:rightsOwner>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Resource Reference (rdf:resource)

(Optional) agreementID =

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

Model #2

 

Element Content

Plain Literal

Attributes

(Optional) agreementID =

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

Examples

Model #1

<pur:rightsAgent rdf:resource=http://www.PhantasticPhotos.com/>

<pur:rightsOwner rdf:resource=http://www.PhantasticPhotos.com/>

 

Model #2

<pur:rightsAgent>Phantastic Photos, Philadelphia</pur:rightsAgent>

<pur:rightsOwner>Victoria’s Secret</pur:rightsOwner>

Profile #3 (XMP)

 

Property Value

bag Text