Description: prism_specification

 

 

 

Publishing Requirements for Industry Standard Metadata

 

Version 3.1

 

 

PRISM
Contract Management
Metadata
Specification

 

DRAFT for Public Comment

 

December 15, 2014

 

 

 

 

Description: idealliancelogo_cymk


Copyright and Legal Notices

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

PRISM® is a  registered trademark 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. 3

2.3.3       PRISM Aggregator Message Markup Specification. 4

2.3.4       PRISM Inline Markup Specification. 5

2.3.5       PRISM Controlled Vocabulary Specifications. 5

2.3.6       Additional PRISM Documentation. 5

2.3.7       Access to PRISM Documentation. 6

2.3.8       Access to PAM Schemas. 6

2.3.9       nextPub 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      Element and Attribute Definitions. 11

4.1         PRS Namespace. 11

4.2         PRISM Element and Attribute Models. 11

4.2.1       prs:action. 11

4.2.2       prs:agreementLink. 12

4.2.3       prs:assetLink. 12

4.2.4       prs:constraint 13

4.2.5       prs:duty. 13

4.2.6       prs:generalInfo. 14

4.2.7       prs:party. 14

4.2.8       prs:partyAddress. 15

4.2.9       prs:partyEmail 15

4.2.10         prs:partyLink. 16

4.2.11         prs:partyName. 16

4.2.12         prs:partyPhone. 17

4.2.13         prs:permission. 17

4.2.14         prs:prohibition. 18

4.2.15         prs:rightsAgent 19

4.2.16         prs:rightsOwner. 19

 


1        Status

1.1      Document Status

The status of this document is:

ü

Draft

10/30/2014

ü

Released for Public Comment

12/01/2014

 

 

 

1.2      Document Location

The location of this document is:

http://www.prismstandard.org/specifications/3.1/PRISM_Rights_Summary_Metadata_3.1.pdf

or

http://www.prismstandard.org/specifications/3.1/PRISM_Rights_Summary_Metadata_3.1.htm

1.3      Version History

Version Number

Release Date

Editor

Description

3.1 Specification

12/15/2014

Kennedy

Public Draft


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 Contract Management Metadata Specification [PRISMCMMS]
http://www.prismstandard.org/specifications/3.1/
PRISM_Contract _Metadata_3.1.pdf

or
http://www.prismstandard.org/specifications/3.1/
PRISM_Contract _Metadata_3.1.htm

Describes the metadata elements contained in the PRISM Contract Management Namespace; includes normative material.

The PRISM Rights Summary Metadata Specification [PRISMRSMS]
http://www.prismstandard.org/specifications/3.1/
PRISM_Rights_Summary _Metadata_3.1.pdf

or
http://www.prismstandard.org/specifications/3.1/
PRISM_Rights_Summary_Metadata_3.1.htm

Describes the metadata elements contained in the PRISM Rights Summary Namespace; includes normative material.

 

 

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.1/
PRISM_CV_Spec_3.1.pdf

or
http://www.prismstandard.org/specifications/3.1/
PRISM_CV_Spec_3.1.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 Contract Management [CONTRACTSGUIDE] documents an XML-based PRISM application for the expression of PRISM Contract Management.  The Guide is accompanied by an XSD that can be used as the basis for developing a contract management system based on PRISM Contract Management Metadata.  ****

The Guide to PRISM Rights Summary [RIGHTSSUMMARYGUIDE] documents an XML-based PRISM application for the expression of PRISM Rights Summary to facilitate ODRL-based right-to-use decision engines.  The Guide is accompanied by an XSD that can be used as the basis for developing a rights management system based on PRISM Rights Summary Metadata. ****

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 Usage Rights (pur:) 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

To access PRISM Contract Management (pcmm:) XSD

http://www.prismstandard.org/schemas/rights/3.1 /contractmanagement.xsd

To access PRISM Rights Summary (prs:) XSD

http://www.prismstandard.org/schemas/rights/3.1 /rightssummary.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 Contract Management Metadata namespace (pccm:). 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 Contract Management V.3.1. [CONTRACTSGUIDE].

3.2      New in this Version

This is the first version of the PRISM Contract Management Metadata.


4        Element and Attribute Definitions

4.1      PRS Namespace

In addition to the Dublin Core elements, the PRISM specification defines additional namespaces. The PRISM Rights Summary Metadata namespace (The recommended namespace for PRISM Rights Summary Metadata is: xmlns:prs=http://prismstandard.org/namespaces/prs/3.1). This namespace contains metadata elements suitable for summarizing usage rights for content/media assets.

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 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.1    prs:action

Name

Action

Identifier

prs:action

Definition

An action defines the exact permitted or prohibited usage of an asset.  This element will contain enumerated values from the PRISM Community Rights Vocabulary (CV). 

Comment

Examples of actions include use = any reasonable use of the asset; presentDisplay = to display on a screen; presentPlay = to play an asset such as an audio asset; presentPrint = to print; presentTextToSpeech = to present text as speech; aggregate = to aggregate with other assets; translate = to translate to another language; transform = to output in an alternate format.

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

string; enumerated values

Attributes

none

Example

<prs:action>presentPrint </prs:action>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<prs:action rdf:resource=”prismstandard.org/vocabularies/3.0/action.xml/#presentPrint”/>

 

Model #2

<prs:action>printPresent </prs:action>

Profile #3 (XMP)

 

Property Value

Choice

4.2.2    prs:agreementLink

Name

Agreement Link

Identifier

prs:agreementLink

Definition

A link to an agreement or contracts governing the use of a content/media asset being described by this Rights Summary.

Comment

 

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

URI

Attributes

agreementIDRef= (a URI for the agreement link)

agreementType= (a string to indicate the type of an agreement)

Example

<prs:agreementLink agreementIDRef=”http://pub.com/agreement/#AG079802/”>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Examples

Model #1

<prs:agreementLink rdf:resource=”http://pub.com/agreement/#AG079802”/>

Profile #3 (XMP)

 

Property Value

URI

4.2.3    prs:assetLink

Name

Asset Link

Identifier

prs:assetLink

Definition

A link to the content/media asset(s) being described by this Rights Summary.

Comment

 

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

URI

Attributes

assetIDRef

Example

<prs:assetLink assetIDRef=”http://pub.com/DAM/#AS121233K/”>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Examples

Model #1

<prs:assetLink assetIDRef=”http://pub.com/DAM/#AS121233K/”>

Profile #3 (XMP)

 

Property Value

URI

4.2.4    prs:constraint

Name

Constraint

Identifier

prs:constraint

Definition

A constraint places limits on the permission/restriction action.

Comment

Examples include embargoDate, exclusivity, exclusivityEndDate, option, optionEndDate, expirationDate, deliveryPlatform, distributionChannel, countryCode, inContext, inTitle, inBrand,  language, absolute size (replaces image size restriction) absolute position, relative size, relative position, resolution and adultContentWarning.

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

Empty

Attributes

constraintName=

constraintOperator=

rightOperand=

datatype=

Example

<prs:constraint constraintName=”embargoDate” constraintOperator=”gteq” rightOperand=”2014-10-10” datatype=”xs:date”/>

Profile #2 (RDF)

 

Model #1

 

Element Content

constraintName, constraintOperator, rightOperand, dataType

Attributes

 

Model #2

 

Element Content

 

Attributes

constraintName=

constraintOperator=

rightOperand=

datatype=

Examples

Model #1

<prs:constraint>

  <prs:constraintName rdf:resource=”pub.com/constraints.xml/#embargoDate”/>

  <prs:constraintOperator rdf:resource=”pub.com/constraintOperator.xml/#gteq”/>

  <prs:rightOperand rdf:resource=”pub.com/constraintOperand.xml/#2014-10-10”/>

  <prs:dataType rdf:resource=”pub.com/constraintDatatype.xml/#xs:date”/>

</prs:constraint>

Model #2

<prs:constraint constraintName=”embargoDate” constraintOperator=”gteq” rightOperand=”2014-10-10” dataType=”xs:date”/>

Profile #3 (XMP)

 

Property Value

constraintName: closed choice text; enumerations = values from the PRISM constraintName controlled vocabulary

constraintOperator: closed choice text; enumerations = values from the PRISM constraintOperator controlled vocabulary

constraintRightOperand: closed choice text; enumerations = lt, gt, eq, leq, geq

dataType: closed choice text; enumerations = any XML datatype

4.2.5    prs:duty

Name

Duty

Identifier

prs:duty

Definition

A duty is an action that a publisher must take in order to have premission to use the asset. 

Comment

Values include credit (replaces creditLine, compensate (replaces usageFee), inform and include (such as the text of the credit line, an image of the author, etc.)

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated string values.  Ideally from a duty controlled vocabulary

Attributes

 

Example

<prs:duty>credit</prs:duty>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated choice

Attributes

 

Examples

Model #1

<prs:duty rdf:resource=”www.prismstandard.org/cv/duty/#credit”/>

 

Model #2

<prs:duty>credit</prs:duty>

Profile #3 (XMP)

 

Property Value

closed choice text; enumerations from the PRISM duty controlled vocabulary

4.2.6    prs:generalInfo

Name

General Information

Identifier

prs:generalInfo

Definition

This is a virtual organizing structure to contain legacy PUR metadata that does not map into ODRL right-to-use decision policies.

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

pur:copyright, prs:rightsAgent, prs:rightsOwner

Attributes

 

Example

 

Profile #2 (RDF)

 

Model #1

 

Element Content

pur:copyright, prs:rightsAgent, prs:rightsOwner

Attributes

none

Examples

Model #1

<prs:generalInfo>

  <pur:copyright rdf:resource=”pub.com/general.xml/#copyright”/>

  <prs:rightsAgent rdf:resource=”pub.com/general.xml/#RA”/>

  <prs:rightsOwner rdf:resource=”pub.com/general.xml/#RO”/>

</prs:generalInfo>

Profile #3 (XMP)

 

Property Value

copyright: Text

rightsAgent: Text

rightsOwner: Text

4.2.7    prs:party

Name

Party

Identifier

prs:party

Definition

A field identifying a party associated with a permissions/restriction duty.   This field has a function= attribute with enumerated values such as attributedParty, informedParty, consentingParty, payeeParty and trackingParty from the PRISM party function controlled vocabulary.  Party values will map into ODRL to drive the right-to-use decision policies.

Comment

This model does what we attempted to imply with the rightsOwner/rightsAgent fields.

Occurrence

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

partyLink or party identification fields

Attributes

function = (enumerated values from the PRISM party function controlled vocabulary)

Example

<prs:party function=”creditedParty”><partyLink partyRefID=”pub.com/party/#12RL7”/>
</party>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Examples

Model #1

<prs:party rdf:resource=”pub.com/creditedParty/#12RL7”/>

Profile #3 (XMP)

 

Property Value

URI

4.2.8    prs:partyAddress

Name

Party Address

Identifier

prs:partyAddress

Definition

The street address of the party.

Comment

 

Occurrence

optional

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

none

Example

<prs:partyAddress>1600 Duke Street, Suite 420, Alexandria, VA 22314<prs:partyAddress>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<prs:partyAddress rdf:resource=”pub.com/address.xml/#idealliance”/>

Model #2

<prs:partyAddress>1600 Duke Street, Suite 420, Alexandria, VA 22314<prs:partyAddress>

Profile #3 (XMP)

 

Property Value

Text

4.2.9    prs:partyEmail

Name

Party Email

Identifier

prs:partyEmail

Definition

The email of the party.

Comment

 

Occurrence

required

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

none

Example

<prs:partyEmail>staff@idealliance.org<prs:partyEmail>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<prs:partyEmail rdf:resource=”pub.com/email.xml/#idealliance”/>

Model #2

<prs:partyEmail>staff@idealliance.org<prs:partyEmail>

Profile #3 (XMP)

 

Property Value

Text

4.2.10prs:partyLink

Name

Party Link

Identifier

prs:partyLink

Definition

This field links a party in a contracts or contacts database

Comment

 

Occurrence

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

 

Attributes

partyIDRef= (link to a party in a contracts database)

Example

<prs:partyLink partyIDRef=”pub.com/party.xml/#K34R52” />

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<prs:partyLink rdf:resource=”pub.com/party.xml/#K34R52” />

 

Model #2

<prs:partyLink partyIDRef=”pub.com/party.xml/#K34R52” />

Profile #3 (XMP)

 

Property Value

Text

4.2.11prs:partyName

Name

Party Name

Identifier

prs:partyName

Definition

The name of the party.

Comment

 

Occurrence

required

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

none

Example

<prs:partyName>John Doe </prs:partyName>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<prs:partyName rdf:resource=”pub.com/partyname.xml/#”/>

Model #2

<prs:partyName>John Doe</prs:partyName>

Profile #3 (XMP)

 

Property Value

Text

4.2.12prs:partyPhone

Name

Party Phone

Identifier

prs:partyPhone

Definition

The telephone number of the party.

Comment

 

Occurrence

required

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

none

Example

<prs:partyPhone>703-837-1070</prs:partyPhone>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<prs:partyPhone rdf:resource=”pub.com/phone.xml/#idealliance”/>

Model #2

<prs:partyPhone>703-837-1070</prs:partyPhone>

Profile #3 (XMP)

 

Property Value

Text

4.2.13prs:permission

Name

Permission

Identifier

prs:permission

Definition

A permission statement indicating the action permitted, constraints that must be applied along with any duties that must be performed by an associated party. Metadata fields in this model will map into ODRL to drive the right-to-use decision policies.

Comment

This model replaces the pur:permissions that is simply a text string that indicates permissions granted by a contract or agreement.

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

action+, constraint*, (duty,party*)*

Attributes

 

Example

<prs:permission>
   <prs:action>presentPrint</prs:action>
  <prs:action>presentDisplay</prs:action>
  <prs:action>presentTextToSpeech</prs:action>
  <constraint constraintName=”embargoDate” constraintOperator=”gteq” rightOperand=”11182014” datatype=”xs:date” />
</prs:permission>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Example

Model #1

<prs:permission  rdf:resource=”pub.com/permissions#12D4”/>

Profile #3 (XMP)

 

Property Value

<bag>

action: closed choice text; enumerations = values from the PRISM action controlled vocabulary

constraint: closed choice text; enumerations = values from the PRISM constraint controlled vocabulary

duty: closed choice text; enumerations = values from the PRISM duty controlled vocabulary

party: Text

</bag>

4.2.14prs:prohibition

Name

Prohibition

Identifier

prs:prohibition

Definition

A prohibition is made up of metadata fields (actions and constraints) that map into ODRL to drive the right-to-use decision policies

Comment

Prohibitions are held by the virtual container <prs:restrictions> in the XML model

Occurrence

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

action+, constraint*

Attributes

none

Example

<prs:prohibition>
  <prs:action>presentTextToSpeech</prs:action>
</prs:prohibition>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Examples

Model #1

<prs:prohibition rdf:resource=”pub.com/prohibition.xml/#tts”/>

 

Profile #3 (XMP)

 

Property Value

<bag>

action: closed choice text; enumerations = values from the PRISM action controlled vocabulary

constraint: closed choice text; enumerations = values from the PRISM constraint controlled vocabulary

</bag>

4.2.15prs:rightsAgent

Name

Rights Agent

Identifier

prs:rightsAgent

Definition

The Rights Agent is a general information field that provides contact information for the person or organization that has the legal right to license the use of a resource 

Comment

In the PRISM Rights Summary Rights Agent has been replaced by Party to facilitate mapping directly into the construction of ODRL usage policies.
Note: This model differs from the PUR: model because the explicit link to an agreement has been deleted in favor of agreementLink in the new rights summary model.

Occurrence

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang= to specify language

Example

<prs:rightsAgent>Jane Doe</prs:rightsAgent>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<prs:rightsAgent rdf:resource=”pub.com/agent.xml/#908R12”/>

 

Model #2

<prs:rightsAgent>Jane Doe</prs:rightsAgent>

Profile #3 (XMP)

 

Property Value

Text

4.2.16prs:rightsOwner

Name

Rights Owner

Identifier

prs:rightsOwner

Definition

The Rights Owner is a general information field that provides contact information for the person or organization that has the legal right to license the use of a resource 

Comment

In the PRISM Rights Summary Rights Owner has been replaced by Party to facilitate mapping directly into the construction of ODRL usage policies.
Note: This model differs from the PUR: model because the explicit link to an agreement has been deleted in favor of agreementLink in the new rights summary model.

Occurrence

 

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

xml:lang= to specify language

Example

<prs:rightsAgent>Jane Doe</prs:rightsAgent>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<prs:rightsAgent rdf:resource=”pub.com/agent.xml/#908R12”/>

 

Model #2

<prs:rightsAgent>Jane Doe</prs:rightsAgent>

Profile #3 (XMP)

 

Property Value

Text