-

 

 

Description: prism_specification

 

 

 

Publishing Requirements for Industry Standard Metadata

 

 

Version 3.1

 

PRISM
Contract Management
Metadata
Specification

 

 

March 27, 2015

 

 

 

 

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

2.3.3      PRISM Aggregator Message Markup Specification. 5

2.3.4      PRISM Inline Markup Specification. 5

2.3.5      PRISM Aggregator Message Web Content Markup Specification. 5

2.3.6      PRISM Controlled Vocabulary Specifications. 6

2.3.7      PRISM Guides. 6

2.3.8      Access to PRISM Documentation. 7

2.3.9      Access to PRISM Schemas. 7

2.3.10        PRISM Source Vocabulary Documentation Set 7

2.4         PSV Content Management Schema. 8

3      Introduction. 9

3.1         Purpose and Scope. 9

3.2         New in this Version. 9

4      Element and Attribute Definitions. 11

4.1         PCMM Namespace. 11

4.2         PRISM Element and Attribute Models. 11

4.2.1      pcmm:assetIDRef. 11

4.2.2      pcmm:assetRelated. 12

4.2.3      pcmm:changesNegotiated. 12

4.2.4      pcmm:contractStatus. 13

4.2.5      pcmm:contractType. 13

4.2.6      pcmm:contractVersion. 14

4.2.7      pcmm:expirationDate. 14

4.2.8      pcmm:finalizationDate. 15

4.2.9      pcmm:signatorContactAddress. 16

4.2.10        pcmm:signatorContactEmail 16

4.2.11        pcmm:signatorContactIDRef. 17

4.2.12        pcmm:signatorContactPhone. 17

4.2.13        pcmm:staffContactAddress. 18

4.2.14        pcmm:staffContactEmail 18

4.2.15        pcmm:staffContactIDRef. 19

4.2.16        pcmm:staffContactPhone. 20

4.2.17        pcmm:statusDate. 20

4.2.18        pcmm:templateIDRef. 21

4.2.19        pcmm:unionContract 21

4.2.20        pcmm:usageRightsSummaryIDRef. 22

 


1      Status

1.1     Document Status

The status of this document is:

ü

Draft

10/30/2014

ü

Released for Public Comment

12/01/2014

ü

Final Release

03/27/2015

1.2     Document Location

The location of this document is:

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

or

http://www.prismstandard.org/specifications/3.01PRISM_Contract_Metadata_3.1.htm

1.3     Version History

Version Number

Release Date

Editor

Description

3.1 Specification

 

Kennedy

Final Release


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

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

The PRISM Contract Management Metadata Specification [PRISMCMMS]
http://www.prismstandard.org/specifications/3.1/
PRISM_
Contracts_Metadata_3.1.pdf

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

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]
http://www.prismstandard.org/specifications/3.1/
PRISM_
Crafts_Metadata_3.1.pdf

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

Describes the metadata elements contained in the PRISM Crafts Metadata Namespace (pcm:).  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 (prm:).  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 Metadata Namespace (prsm:).  Includes normative material.

The PRISM Usage Rights Metadata Specification [PRISMURMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Usage_Rights_Metadata_3.0.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_Usage_Rights_Metadata_3.0.htm

Describes the metadata elements contained in the PRISM Usage Rights Namespace; includes normative material. This namespace will supersede elements in both the prism: and prl: namespaces in version 3.0 of the specification.

Some elements from PUR are referenced from the newer, more comprehensive PRISM Rights Summary Metadata Specification [PRISMRSMS].

2.3.3   PRISM Aggregator Message Markup Specification

This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message.  The PAM Message is currently Version 2.2.

Document

Description

The PRISM PAM Markup Specification [PRISMPAMMS]
http://www.prismstandard.org/specifications/2.2/
PAM_Markup_2.2.pdf

or
http://www.prismstandard.org/specifications/2.2/
PAM_Markup_2.2.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.

Document

Description

The PRISM Inline Markup Specification [PRISMIMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_PIM_Markup_Specification
_2.2.pdf

or
http://www.prismstandard.org/specifications/3.0/
PRISM_PIM_Markup_Specification_2.2.htm

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

2.3.5   PRISM Aggregator Message Web Content Markup Specification

This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message for Web content.

Document

Description

The PRISM PAM Markup for Web Content Specification [PRISMPAMWMS]
http://www.prismstandard.org/specifications/3.1/
pamw_markup_v1.0.pdf

or
http://www.prismstandard.org/specifications/3.1/
pamw_markup_v1.0.htm

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.3.6   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 for metadata elements in all modules/namespaces are documented in this Specification.

2.3.7   PRISM 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.

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 ODRL Rights Summary [ODRLRSGUIDE] documents an XML-based PRISM rights summary model designed to populate ODRL policy statements.  This model uses fields from both the prs: and pur: namespaces.  This model supercedes the PRISM Usage Rights model developed in 2004.

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.

2.3.8   Access to PRISM Documentation

PRISM Guides and Specifications are all publicly and freely available on the PRISM website, www.prismstandard.org.

2.3.9   Access to PRISM Schemas

Standard URLs have been established to access PRISM XSDs and DTDs.  All are publicly and freely available on the PRISM website, http://www.prismstandard.org/schemas/

2.3.10               PRISM Source Vocabulary Documentation Set

IDEAlliance 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 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, 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.

 


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 (pcmm:). 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     PCMM Namespace

In addition to the Dublin Core elements, the PRISM specification defines additional namespaces. The PRISM Contract Management Metadata namespace (The recommended namespace for PRISM Contract Management Metadata is: xmlns:pcmm=http://prismstandard.org/namespaces/pcmm/3.1)  This namespace contains metadata elements suitable for managing a wide range of contracts.

4.2     PRISM Element and Attribute Models

All three PRISM profiles are documented in this section. First Profile #1 is documented. The elements included in PAM are those elements that publishers plan to send to aggregators for the purpose of aggregation. Not all elements are included in PAM.

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

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

4.2.1   pcmm:assetIDRef

Name

Asset Identifier Reference

Identifier

pcmm:assetIDRef

Definition

A link to the asset in an asset management system.

Comment

 

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

URI Reference

Attributes

none

Example

<pcmm:assetIDRef>DAM123K14</pcmm:assetIDRef>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:assetIDRef rdf:resource=”pub.com/dam2/DAM123K14”/>

 

Model #2

<pcmm:assetIDRef>DAM123K14</pcmm:assetIDRef>

Profile #3 (XMP)

 

Property Value

URI

4.2.2   pcmm:assetRelated

Name

Asset Related Contract Flag

Identifier

pcmm:assetRelated

Definition

A true/false flag to indicate that this contract is related to the acqusition of a content or media asset(s).

Comment

 

Occurrence

Occurs zero or one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

Boolean (true/false)

Attributes

none

Example

<pcmm:assetRelated>true</ pcmm:assetRelated >

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

true or false

Attributes

 

Examples

Model #1

<pcmm:assetRelated rdf:resource=”http://www.pub.com/values/true/”/>

 

Model #2

<pcmm:assetRelated>true</ pcmm:assetRelated >

Profile #3 (XMP)

 

Property Value

Boolean

4.2.3   pcmm:changesNegotiated

Name

Changes Negotiated Contract Flag

Identifier

pcmm:changesNegotiated

Definition

A yes/no flag to indicate that changes from the standard template have been negotiated

Comment

 

Occurrence

Occurs zero or 1 time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

Boolean (true/false)

Attributes

none

Example

<pcmm:changesNegotiated >True</ pcmm:changesNegotiated >

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

true or false

Attributes

 

Examples

Model #1

<pcmm:changesNegotiated rdf:resource=”http://www.pub.com/values/true/”/>

 

Model #2

<pcmm:changesNegotiated >true</ pcmm:changesNegotiated >

Profile #3 (XMP)

 

Property Value

Boolean

4.2.4   pcmm:contractStatus

Name

Contract Status

Identifier

pcmm:contractStatus

Definition

Specifies the status of the contract at the time the version is stored in the system.  Standard values include: draft, being negotiated, finalized, uploaded, upload approved, upload rejected -- try again

Comment

 

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated string values.  Ideally from a contract status controlled vocabulary

Attributes

 

Example

<pcmm:contractStatus >draft </pcmm:contractStatus

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

<pcmm:contractStatus rdf:resource=”www.prismstandard.org/cv/status/#draft”/>

 

Model #2

<pcmm:contractStatus >draft </pcmm:contractStatus >

Profile #3 (XMP)

 

Property Value

Choice (draft, being negotiated, finalized, uploaded, upload approved, upload rejected -- try again)

4.2.5   pcmm:contractType

Name

Contract Type

Identifier

pcmm:contractType

Definition

A publisher-defined contract type to be used to organize contracts into logical groups. Examples are "Work for Hire" "World Wide Rights" and "All Rights" or "Contract" "Release" and "Assignment"

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

String or enumerated string values

Attributes

 

Example

<pcmm:contractType >Work for Hire</pcmm:contractType >

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:contractType rdf:resource=”pub.com/cv/contractType/#WFH”/>

 

Model #2

<pcmm:contractType >Work for Hire</pcmm:contractType >

Profile #3 (XMP)

 

Property Value

Text or Choice

4.2.6   pcmm:contractVersion

Name

Contract Version

Identifier

pcmm:contractVersion

Definition

Version number of a contract so major changes resulting in a new version can be tracked

Comment

 

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:contractVersion>1.0 </pcmm:contractVersion>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:contractVersion  rdf:resource=”pub.com/#version”/>

 

Model #2

<pcmm:contractVersion>1.0 </pcmm:contractVersion>

Profile #3 (XMP)

 

Property Value

Text

4.2.7   pcmm:expirationDate

Name

Expiration Date

Identifier

pcmm:expiration Date

Definition

The date the contract lapses or expires

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

date or dateTime

Attributes

 

Example

<pcmm:expirationDate>2014-12-12</pcmm:expirationDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:expirationDate rdf:resource=”pub.com/date”/>

 

Model #2

<pcmm:expirationDate>2014-12-12</pcmm:expirationDate>

Profile #3 (XMP)

 

Property Value

Date

4.2.8   pcmm:finalizationDate

Name

Finalization Date

Identifier

pcmm:finalizationDate

Definition

The date the contract is signed and approved by the publisher and the signator

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

date or dateTime

Attributes

 

Example

<pcmm:finalizationDate>2014-12-12</pcmm:finalizationDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:finalizationDate rdf:resource=”pub.com/date”/>

 

Model #2

<pcmm:inalizationDate>2014-12-12</pcmm:finalizationDate>

Profile #3 (XMP)

 

Property Value

Date

4.2.9   pcmm:signatorContactAddress

Name

Signator Contact Address

Identifier

pcmm:signatorContactAddress

Definition

The street address of the party signing the legal document

Comment

 

Occurrence

Occurs zero or one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:signatorContactAddress>100 Daingerfield Road, Alexandria, VA 22314</pcmm:signatorContactAddress>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:signatorContactAddress rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:signatorContactAddress>100 Daingerfield Road, Alexandria, VA 22314</pcmm:signatorContactAddress>

Profile #3 (XMP)

 

Property Value

Text

4.2.10               pcmm:signatorContactEmail

Name

Signator Contact Email

Identifier

pcmm:signatorContactEmail

Definition

The email of the party signing the legal document

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:signatorContactEmail>john.doe@pub.com</pcmm:signatorContactEmail>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:signatorContactEmail rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:signatorContactEmail>john.doe@pub.com</pcmm:signatorContactEmail>

Profile #3 (XMP)

 

Property Value

Text

4.2.11               pcmm:signatorContactIDRef

Name

Signator Contact ID Reference

Identifier

pcmm:signatorContactIDRef

Definition

A reference to the unique ID of the party signing the legal document (in a contact database)

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

URI

Attributes

 

Example

<pcmm:signatorContactIDRef> K12034B</pcmm signatorContactIDRef>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:signatorContactIDRef rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:signatorContactIDRef>K12034B</pcmm:signatorContactIDRef>

Profile #3 (XMP)

 

Property Value

URI

4.2.12               pcmm:signatorContactPhone

Name

Signator Contact Phone

Identifier

pcmm:signatorContactPhone

Definition

The phone contact of the party signing the legal document

Comment

 

Occurrence

Occurs zero to  one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:signatorContactPhone> 888-999-1234</pcmm:signatorContactPhone>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:signatorContactPhone rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:signatorContactPhone>888-999-1234</pcmm:signatorContactPhone>

Profile #3 (XMP)

 

Property Value

Text

4.2.13               pcmm:staffContactAddress

Name

Staff Contact Address

Identifier

pcmm:staffContactAddress

Definition

The street address of the staff person signing the legal document

Comment

 

Occurrence

Occurs zero or one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:staffContactAddress>100 Daingerfield Road, Alexandria, VA 22314</pcmm:staffContactAddress>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:staffContactAddress rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:staffContactAddress>100 Daingerfield Road, Alexandria, VA 22314</pcmm:staffContactAddress>

Profile #3 (XMP)

 

Property Value

Text

4.2.14               pcmm:staffContactEmail

Name

Staff Contact Email

Identifier

pcmm:staffContactEmail

Definition

The email of the staff person signing the legal document

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:staffContactEmail>john.doe@pub.com</pcmm:staffContactEmail>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:staffContactEmail rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:staffContactEmail>john.doe@pub.com</pcmm:staffContactEmail>

Profile #3 (XMP)

 

Property Value

Text

4.2.15               pcmm:staffContactIDRef

Name

Staff Contact ID Reference

Identifier

pcmm:staffContactIDRef

Definition

A reference to the unique ID of the staff person signing the legal document (in a contact database)

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:staffContactIDRef> K12034B</pcmm staffContactIDRef>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:staffContactIDRef rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:staffContactIDRef>K12034B</pcmm:staffContactIDRef>

Profile #3 (XMP)

 

Property Value

URI

4.2.16               pcmm:staffContactPhone

Name

Staff Contact Phone

Identifier

pcmm:staffContactPhone

Definition

The phone contact of the staff person signing the legal document

Comment

 

Occurrence

Occurs zero to  one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

string

Attributes

 

Example

<pcmm:staffContactPhone> 888-999-1234</pcmm:staffContactPhone>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:staffContactPhone rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:staffContactPhone>888-999-1234</pcmm:staffContactPhone>

Profile #3 (XMP)

 

Property Value

Text

4.2.17               pcmm:statusDate

Name

Status Date

Identifier

pcmm:statusDate

Definition

The date each status change is reported

Comment

 

Occurrence

Occurs zero to many times

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

date or dateTime

Attributes

 

Example

<pcmm:statusDate>2014-11-10</pcmm:statusDate>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:statusDate rdf:resource=”academic.xml/#anthropology”/>

 

Model #2

<pcmm:statusDate>2014-11-10</pcmm:statusDate>

Profile #3 (XMP)

 

Property Value

Date

4.2.18               pcmm:templateIDRef

Name

Template ID Reference

Identifier

pcmm:templateIDRef

Definition

Link to a standard contract template that was used to construct this contract

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

URI

Attributes

 

Example

<pcmm:templateIDRef> K12034B</pcmm templateIDRef>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:templateIDRef rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:templateIDRef>K12034B</pcmm:templateIDRef>

Profile #3 (XMP)

 

Property Value

URI

4.2.19               pcmm:unionContract

Name

Union Contract Flag

Identifier

pcmm:unionContract

Definition

A True/false flag to indicate the contract must adhere to provisions mandated by a union

Comment

 

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

Boolean (true/false)

Attributes

none

Example

<pcmm:unionContract>true</ pcmm:unionContract>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

true or false

Attributes

 

Examples

Model #1

<pcmm:unionContract rdf:resource=”http://www.pub.com/values/true/”/>

 

Model #2

<pcmm:unionContract>True</ pcmm:unionContract>

Profile #3 (XMP)

 

Property Value

Boolean

4.2.20               pcmm:usageRightsSummaryIDRef

Name

Usage Rights Summary ID Reference

Identifier

pcmm:usageRightsSummaryIDRef

Definition

A link to the usage rights summary

Comment

This link may be to a field in a contract management system, a rights management system or a DAM

Occurrence

Occurs zero to one time

Included in PAM?

No

Included in PSV?

No

Profile #1 (XML)

 

Model #1

 

Element Content

URI

Attributes

 

Example

<pcmm:usageRightsSummaryIDRef> K12034B</pcmm usageRightsSummaryIDRef>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

 

Attributes

 

Examples

Model #1

<pcmm:usageRightsSummaryIDRef rdf:resource=”pub.com /CDB/#ID_K12034B”/>

 

Model #2

<pcmm:usageRightsSummaryIDRef>K12034B</pcmm:usageRightsSummaryIDRef>

Profile #3 (XMP)

 

Property Value

URI