W3C W3C Member Submission

PRISM Rights Summary 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 Rights Summary Metadata Specification describes the metadata elements contained in the PRISM Specification to describe usage rights summary; 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

10/30/2014

 • 

Released for Public Comment

12/01/2014

 • 

Release V3.1

03/27/2015

1.2    Document Location

The location of this document is:

prism-rights-summary.html

1.3    Version History

Version Number

Release Date

Editor

Description

3.1 Specification

12/15/2014

Kennedy

Public Draft

3.2 Specification

03/27/2015

Kennedy

Final Specification

2     PRISM Documentation Structure

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

2.1    Normative and Non-normative Section

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

2.2    Requirement Wording Note

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

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

2.3    The PRISM Documentation Package

The PRISM Documentation Package 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.4    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.5    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.6    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.7    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.8    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.9    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.10 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]

pssv-markup.html

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

2.11 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.12 PRISM Controlled Vocabularies

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.

2.13 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.14 PSV Content Management Schema

In order to assist implementers develop a PSV-based federated content management solution, an XML Schema (XSD) that can serve as the basis for the design of a PSV content repository has been provided. 

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.15 New in this Version

This is the first version of the PRISM Rights Summary Metadata.

3     Element and Attribute Definitions

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

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

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

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

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

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

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

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

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

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

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

3.2.10            prs: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

3.2.11            prs: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

3.2.12            prs: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

3.2.13            prs: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>

3.2.14            prs: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>

3.2.15            prs: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

3.2.16            prs: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