Copyright © 2020 Idealliance, Inc. This document is available under the W3C Document License. See the W3C Intellectual Rights Notice and Legal Disclaimers for additional information.
This PRISM Contract Management Metadata Specification describes the metadata elements contained in the PRISM Specification to describe contract content; includes normative material.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications can be found in the W3C technical reports index at https://www.w3.org/TR/.
By publishing this document, W3C acknowledges that the Submitting Members have made a formal Submission request to W3C for discussion. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. This document is not the product of a chartered W3C group, but is published as potential input to the W3C Process. A W3C Team Comment has been published in conjunction with this Member Submission. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of W3C Membership. Please consult the requirements associated with Member Submissions of section 3.3 of the W3C Patent Policy. Please consult the complete list of acknowledged W3C Member Submissions.
The status of this document is:
Draft |
10/30/2014 |
|
|
Released for Public Comment |
12/01/2014 |
|
Final Release |
03/27/2015 |
The location of this document is:
Version Number |
Release Date |
Editor |
Description |
3.1 Specification |
|
Kennedy |
Final Release |
The PRISM Documentation Package has been reorganized and some specifications renamed to more accurately reflect the nature of each specification module. The PRISM documentation package includes the following specifications and documents:
This document provides compliance specification.
Document |
Description |
PRISM Compliance [PRISMCOMP] |
Describes three profiles of PRISM compliance for content and systems; includes normative material. |
This is the set of documents that outline the prism metadata fields and values by PRISM metadata category. PRISM has modularized its metadata specification by namepace so users may pick those modules that meet their unique business requirements without having to implement the entire PRISM specification.
Document |
Description |
PRISM Advertising Metadata Specification [PRISMADMS] |
Describes advertising metadata elements including those drawn from AdsML, GWG and Ad-ID; includes normative material. |
The PRISM Basic Metadata Specification [PRISMBMS] |
Describes the basic metadata elements contained in the PRISM namespace to describe article content; includes normative material. |
The PRISM Contract Management Metadata Specification [PRISMCMMS] |
Describes metadata elements from the PRISM Contract Management Metadata (pccm:) namespace that are used to describe contracts and legal documents. |
The PRISM Crafts Metadata Specification [PRISMCMS] |
Describes the metadata elements contained in the PRISM Crafts Metadata Namespace (pcm:). Includes normative material. |
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]. |
This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message (PAM) and other aggregator messages. This set of documents includes:
Document |
Description |
The PRISM PAM Markup Specification [PRISMPAMMS] |
Describes the XML elements and attributes used to encode the PRISM Aggregator Message from both the pam: and pim: namespaces; includes normative material. |
The PRISM PAM Markup for Web Content Specification [PRISMPAMWMS] |
Describes the XML elements and attributes used to encode the PRISM Aggregator Message for Web Content. This Specification draws from both the pam: and pim: namespaces and includes normative material. PAMW is used to automate the harvesting of Web Content so that it may be sent to aggregators or stored in a publishers PAM-based content management system. |
This module documents the PRISM Inline Markup Elements and Attributes for use with the PRISM Aggregator Message. This set of documents includes:
Document |
Description |
The PRISM Inline Markup Specification [PRISMIMS] |
Describes the XML elements used to encode the inline markup for the PRISM Aggregator Message. Includes normative material. |
These modules are new with PRISM 3.0. All controlled vocabularies and their terms are documented in this publication set.
Document |
Description |
The PRISM Controlled Vocabulary Markup Specification [PRISMCVMS] |
Describes the metadata fields in the PRISM Controlled Vocabulary Namespace that can be used to describe a controlled vocabulary. Actual PRISM controlled vocabularies are now placed in the PRISM Controlled Vocabularies Specification [PRISMCVS] |
The PRISM Controlled Vocabularies Specification [PRISMCVS] |
The PRISM Controlled Vocabularies are now documented in this document. |
• The Guide to the PRISM Aggregator Message [PAMGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.
• The Guide to the PRISM Aggregator Message for Web Content [PAMWGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.
• Guide to the PSV Aggregator/Distributor Message Package [PAMPGUIDE] documents how to use the PRISM metadata fields and pamP XML messaging tags to deliver content to content aggregators/distributors. The Guide documents the pamP XML message structure and provides the pamP XSD and document samples.
• The Guide to PRISM Contract Management [CONTRACTSGUIDE] documents an XML-based PRISM contract management model. The Guide is accompanied by an XSD that can be used as the basis for developing a contract management system that interfaces with the PRISM Rights Summary to populate ODRL policy statements. Reference [ODRLRSGUIDE]
• The Guide to PRISM Metadata for Images [IMAGEGUIDE] documents an XML-based PRISM Profile 1 application for the expression of the structure and use of PRISM Metadata for Images and can be used as the basis for developing an image management system based on PRISM Metadata for Images and for implementing PMI in XML.
• The Guide to PRISM Recipe Metadata and XML Encoding [RECIPEGUIDE] documents the XML-based recipe model for developing a recipe database, for tagging a wide variety of recipes in XML and for tagging recipes within a PAM Message.
• The Guide to PRISM Usage Rights [RIGHTSGUIDE] documents an XML-based PRISM application for the expression of PRISM Usage Rights. The Guide is accompanied by an XSD that can be used as the basis for developing a digital rights management system based on PRISM Usage Rights.
• PAM to PSV_Guide [PAMPSVGUIDE] documents mappings from PAM XML to PSV XML.
In 2010, Idealliance developed a series of specifications collectively known as the PRISM Source Vocabulary. The use case for PSV is to encode semantically rich content for transformation and delivery to any platform. This Specification is made up of a modular documentation package that builds on PRISM 3.0 and HTML5. Over time new modules may be added to the documentation package. The documentation package for PSV, PRISM Source Vocabulary Specification Version 1.0 consists of:
Document |
Description |
PRISM Source Vocabulary Specification Overview [PSVSO] |
The Introduction to the PRISM Source Vocabulary provides an introduction and a non-technical overview of the PRISM Source Vocabulary. |
PRISM Source Vocabulary Specification [PSVS] |
The PRISM Source Vocabulary Specification defines semantically rich for source metadata and content markup that can be transformed and served to a wide variety of output devices including eReaders, mobile tablet devices, smart phones and print. |
PRISM Source Vocabulary Markup Specification [PSVMS] |
The PSV Markup Specification documents the XML tags in the PSV namespace that are used to encode XML Source Content. |
While PRISM is primarily a metadata specification, it also includes some XML schemas that define encoding of specific kinds of content for publication and interchange. The PRISM schemas include:
• Contracts_xsd.zip contains a schema that can be used to encode publication contracts.
• Crafts_xsd.zip contains a schema that can be used to encode crafts.
• Image_xsd.zip contains a schema that can be used to encode images.
• PAM_xsd.zip contains a schema that can be used to encode a PRISM aggregator message.
• pamW_xsd.zip contains a schema that can be used to encode a PRISM aggregator message for Web content.
• pamP_xsd.zip contains a schema that can be used to encode a PRISM aggregator/distributor message package.
• PSV_xsd.zip contains a schema that can be used to encode content in PRISM Source Vocabulary.
• Recipe_xsd.zip contains a schema that can be used to encode recipes.
• Rights_xsd.zip contains a schema that can be used to encode usage rights.
PRISM has defined 38 controlled vocabularies using PRISM controlled vocabulary markup. See The PRISM Controlled Vocabulary Specification [PRISMCVS]. All CVs are available in CVs.zip.
PRISM namespace declarations can be found in Namespaces.zip. The following are the recommended Namespaces for PRISM metadata:
Usage Vocabulary |
Namespace |
PRISM Basic Metadata |
basic: |
PRISM Aggregator Message (PAM) Markup |
pam: |
PRISM Controlled Vocabulary Markup |
pcv: |
PRISM Source Vocabulary |
psv” |
PRISM Inline Markup |
psm |
Dublin Core metadatap |
dc: |
RDF |
rdf: |
PAM aggregator/distributor package |
pamp: |
PRISM Crafts metadata |
pcm: |
PRISM Contract Management metadata |
pccm: |
PRISM advertising metadata |
prism-ad: |
PRISM rights language metadata |
prl: |
PRISM recipe metadata |
prm: |
PRISM usage rights metadata |
pur: |
In order to assist implementers develop a PSV-based federated content management solution, 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.
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].
This is the first version of the PRISM Contract Management Metadata.
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.
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.
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 |
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 |
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 |
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) |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |
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 |