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 Dublin Core Metadata Specification describes the Dublin Core metadata elements contained in the PRISM Specification that may be used to describe magazine article 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 |
11/04/2011 |
|
|
|
Released for Public Comment |
12/15/2012 |
|
|
Final Draft Released for Comment |
06/12/2012 |
|
|
Final Specification |
10/04/2012 |
The location of this document is:
|
Version Number |
Release Date |
Editor |
Description |
|
1.2 |
1/26/05 |
McConnell |
Converted from unmodularized PRISM spec v 1.2 |
|
1.3 |
10/01/05 |
Kennedy |
Resolve open industry comments |
|
2.0 |
2/19/08 |
Kennedy |
Final Release Version |
|
2.1 |
05/15/09 |
Kennedy |
Comments Resolved |
|
2.1 Errata 2010 |
07/01/10 |
Kennedy |
Errata Complete |
|
3.0 Draft |
12/15/2011 |
Kennedy |
Public Draft |
|
3.0 Final Draft |
06/12/2012 |
Kennedy |
Final Draft Spec, comments resolved |
|
3.0 Final |
10/04/2012 |
Kennedy |
Final Specification |
|
|
|
|
|
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.
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.
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.
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, the nextPub Working Group is providing an XML Schema (XSD) that can serve as the basis for the design of a PSV content repository.
Note: The PSV CM schema is not designed for tagging content. It is provided simply to serve as a basis for the design of a content repository. Metadata building blocks from this schema can be combined with HTML5 by publishers who wish to develop a hybrid PSV metadata and content tagging schema.
Because PSV is a flexible framework, it supports many different use case scenarios. A different schema, using the PSV metadata fields and content encoding can be developed for each different use case. In order to assist PSV implementers, the nextPub Working Group is planning to provide a number of XML Schemas (XSDs) to support common use cases including tagging an article and transmitting articles to content aggregators.
The purpose of this document is to describe the elements that PRISM includes from the Dublin Core namespace. For the Dublin Core specification, see [DCMI-TERMS]. 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 Aggregator Message V. 2.1 [PAMGUIDE].
Changes in this document include:
The normative definitions of the Dublin Core elements can be found in [DCMI] Dublin Core Metadata Element Set, Version 1.1 and [DCMI-TERMS] Dublin Core Metadata Terms, 2005-01-10. The use of some dc: elements are encouraged, others are discouraged, and others constrained. None of the Dublin Core elements are required to appear in a PRISM description -- except dc:identifier, under profile one compliance; see [PRISMCOMP] -- and all of them are repeatable any number of times.
The recommended PRISM namespace for Dublin Core is:
xmlns:dc="http://purl.org/dc/elements/1.1/"
and for Dublin Core Terms is:
xmlns:dcterms="http://purl.org/dc/terms/"
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 Guide to the PRISM Aggregator Message [PAMGUIDE] for more detailed information about the use of the element in the context of the XML PAM message.
PRISM Profile #2 (RDF/XML) is also documented in this section. In combining XML with RDF, there is far greater flexibility in tagging than we are used to when we define XML elements and attributes with an XML DTD. The remainder of this section contains the most likely element/attribute models for 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.
|
Contributor |
|
|
Identifier |
dc:contributor |
|
Definition |
An entity responsible for making contributions to the content of a media resource. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
Dublin Core recommends that dc:contributor identify a person, an organization, or a service by name.
PRISM recommends that magazine publishers use dc:contributor for people who do additional reporting, or individuals who would be called out for special acknowledgments, such as research assistants. Place and role attributes may be used in conjunction with the element to indicate the contributor’s role and place of reporting. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile 1 (XML) |
Recommended practice is to use a prism:role attribute inside dc:contributor and to specify role with values from the PRISM Controlled Vocabulary of Contributor Roles [PRISMCVS] |
|
Model #1 |
|
|
Element Content |
String |
|
Attributes |
(Optional) xml:lang = designed for identifying the human language used (Optional) prism:role= value from Contributor Role Controlled Vocabulary [PRISMCVS] (Optional) prism:place = string indicating location for the contributor (Optional) prism:contactInfo = string indicating contact information for the contributor |
|
Examples |
<dc:contributor prism:role=”writer” prism:place=”New York City”>Erin Clark</dc:contributor> |
|
Profile 2 (RDF) |
If there are multiple contributors for the resource PRISM recommends listing the multiple contributors inside one dc:contributor element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. |
|
Model #1 |
|
|
Element Content |
Plain Literal |
|
Attributes |
rdf:resource authority reference (rdf:resource) to indicate contributor type |
|
Example |
<dc:contributor rdf:resource=”contributorrole.xml#writer”>Stephanie Salmon</dc:contributor> |
|
Model #2 |
|
|
Element Content |
Plain Literal (with multiple contributors) prism:place = string indicating location for the contributor |
|
Attributes |
(Optional) xml:lang = designed for identifying the human language used (Optional) prism:role= value from Contributor Role Controlled Vocabulary [PRISMCVS] (Optional) prism:place = string indicating location for the contributor (Optional) prism:contactInfo = string indicating contact information for the contributor |
|
Examples |
Model #1
<dc:contributor prism:role=”writer” prism:location=”New York City”>Erin Clark</dc:contributor>
Model #2 <dc:contributor> <rdf:Bag> <rdf:li rdf:resource=”contributorrole.xml#writer”>Erin Clark</rdf:li> <rdf:li rdf:resource=”contributorrole.xml#editor”>Ed Stevenson</rdf:li> <rdf:li rdf:resource=”contributorrole.xml#graphicDesigner”>Lee Vetten</rdf:li> </rdf:Bag> </dc:contributor> |
|
Profile 3 (XMP) |
|
|
Property Value |
Model #1 Full interoperability with existing XMP Property Value dc:contributor bag ProperName (no support for role or place) Model #2 Parallel dc:terms element adding role and place information. Property Value dcterms:contributor bag dctermsContributor structure contributor.name Text contributor.a-role Text, closed choice prism:role controlled vocabulary contributor.a-place Text |
|
Name |
Creator |
|
Identifier |
dc:creator |
|
Definition |
An entity primarily responsible for creating the content of a media resource. |
|
Comment |
Dublin core recommends that dc:creator include a person, an organization, or a service. Place and role attributes may be used in conjunction with the element to indicate the contributor’s role and place of reporting. |
|
Occurrence |
Occurs 0 or 1 time |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile 1 (XML) |
Recommended practice is to use the prism:role attribute inside dc:creator and to use a value from the PRISM Controlled Vocabulary of Creator Roles. |
|
Model #1 |
|
|
Element Content |
String |
|
Attributes |
(Optional) xml:lang = designed for identifying the human language used (Optional) prism:role= value from Role Controlled Vocabulary [PRISMCVS] (Optional) prism:place = string indicating location for the creator (Optional) prism:contactInfo = string indicating contact information for the creator (Optional) xml:lang = designed for identifying the human language used |
|
Example |
<dc:creator prism:role=”writer” prism:location=”New York City”>Erin Clark</dc:creator> |
|
Profile 2 (RDF) |
Recommended practice for PRISM implementations is to use a value from the PRISM Controlled Vocabulary of Creator Roles [PRISMCVS], expressed as a URI reference. Implementations MUST also be able to handle text values, but interoperation with text values cannot be guaranteed. |
|
Model #1 |
|
|
Element Content |
Plain Literal |
|
Attributes |
(Optional) xml:lang = designed for identifying the human language used (Optional) prism:role= value from Role Controlled Vocabulary [PRISMCVS] (Optional) prism:place = string indicating location for the creator (Optional) prism:contactInfo = string indicating contact information for the creator (Optional) xml:lang = designed for identifying the human language used |
|
Example |
<dc:creator rdf:resource=”creatorrole.xml#writer”>Stephanie Salmon</dc:creator> |
|
Model #2 |
|
|
Element Content |
Plain Literal (with multiple contributors) |
|
Examples |
Model #1
<dc:creator prism:role=”writer” prism:location=”Carlsbad, CA”>Carl Rambert</dc:creator>
Model #2 <dc:creator> <rdf:Bag> <rdf:li rdf:resource=”creatorrole.xml#writer”>Linda Burman</rdf:li> <rdf:li rdf:resource=”creatorrole.xml#editor”>Carl Rambert</rdf:li> <rdf:li rdf:resource=”creatorrole.xml#graphicDesigner”>Allegra Hartley</rdf:li> </rdf:Bag> </dc:creator> |
|
Profile #3 (XMP) |
|
|
Property Value |
Model #1 Full interoperability with existing XMP
Property Value dc:creator seq ProperName (no support for role or place) Model #2 Parallel dc:terms element adding role and place information. Property Value dcterms:creator seq dctermsCreator structure creator.name Text creator.a-role Text, closed choice prism:role controlled vocabulary creator.a-place Text |
|
Name |
Description |
|
Identifier |
dc:description |
|
Definition |
An account of the content of the resource. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
The Dublin Core Metadata Initiative recommends that dc:description MAY contain any information (e.g., an abstract, table of contents, reference to a graphical representation of content or a free-text account of the content) that describes the resource.
For PRISM, this element describes the resource, such as an abstract or a deck head. Note that this is intended to appear in metadata for an article, not as inline markup. (In other words, a DTD for articles might have dc:description in the header, but would use elements like <abstract> or <deck> for the markup of such material in the body of the article.)
Short descriptions, such as those in the Table of Contents of a magazine, or in the results list of an online search, SHOULD be given in the prism:teaser element.
The dc:description element MAY refer to separate descriptions, such as an abstract prepared by an A&I service, by providing the URI of the description as the value of an rdf:resource attribute. In this case, the description is a separate, standalone resource which could have its own metadata. The metadata record for the separate abstract should contain a prism:genre=“abstract” and a dc:source element pointing back to the original article. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Example |
<dc:description>Browse our catalog for the right computer for you.</dc:description> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) xml:lang = (optional) designed for identifying the human language used. |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used. |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” xml:lang = (optional) designed for identifying the human language used. |
|
Examples |
Model #1 <dc:description rdf:resource= ”http://www2.rhbnc.ac.uk/Music/Archive/Disserts/attinell.html”/>
Model #2 <dc:description>Browse our catalog for the right computer for you.</dc:description>
Model #3 <dc:description rdf:parseType=”Literal”>Describes the infamous criminal and gunfighter, <em>Billy the Kid</em>.</dc:description> |
|
Profile #3 (XMP) |
|
|
Property Value |
Model #1 Full interoperability with existing XMP (0 or 1 occurrence, alternate versions by language) Property Value dc:description Lang Alt
Model #2 Parallel dcterms element to enable "0 or more" occurrences Property Value dcterms:description bag Text |
|
Name |
Format |
|
|
Identifier |
dc:format |
|
|
Definition |
The physical or digital manifestation of the resource. |
|
|
Occurrence |
Occurs 0 or 1 time |
|
|
Comment |
Dublin Core recommends that dc:format include the media-type or dimensions of the resource. Format may be used to determine the software, hardware or other equipment needed to display or operate the resource. Examples of dimensions include size and duration.
PRISM focuses on systems where resources are digital content, not physical objects. Therefore, it is strongly encouraged that PRISM-compliant systems sending PRISM records restrict values of the dc:format element to those in list of Internet Media Types[IETF-MIMETYPES] . PRISM-compliant systems receiving descriptions MAY wish to detect when format values are strings other than media types in order to allow application-appropriate handling. In general, the top-level of an Internet Media Type is used to declare the general type of data, while the subtype specifies a specific format for that type of data. For example, image/jpeg or text/plain. |
|
|
Included in PAM? |
Yes |
|
|
Included in PSV? |
Yes |
|
|
Profile #1 (XML) |
|
|
|
Element Content |
String |
|
|
Attributes |
None |
|
|
Example |
<dc:format>application/pdf</dc:format> |
|
|
Profile #2 (RDF) |
|
|
|
Model #1 |
|
|
|
Element Content |
Plain Literal |
|
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
|
Example |
<dc:format>application/pdf</dc:format> |
|
|
Profile #3 (XMP) |
|
|
|
Property Value |
MIME Type |
|
|
Name |
Has Format |
|
|
Identifier |
dcterms:hasFormat |
|
|
Definition |
Identifies another resource, which is essentially the same intellectual content as the current resource, but presented in another file format, or after some mechanical transformation such as a conversion to a different resolution, different color depth, etc. |
|
|
Occurrence |
Occurs 0 or more times |
|
|
Comment |
The dcterms:hasFormat element points from the original resource, to the alternative version derived from it. In other words, the metadata of the original resource will contain the dcterms:hasFormat element. The dcterms:isFormatOf element is used to point in the other direction, from the alternative back to the original. If the 'original' version cannot be determined, use dcterms:hasFormat for both directions of the relationship. For profile 2, if there are multiple alternative formats for the resource PRISM recommends listing the multiple formats inside one dcterms:hasFormat element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For profile 1, simple repeat the dcterms:hasFormat element multiple times. |
|
|
Included in PAM? |
No |
|
|
Included in PSV? |
No |
|
|
Profile #1 (XML) |
|
|
|
Element Content |
String |
|
|
Attributes |
None |
|
|
Example |
<dcterms:hasFormat>http://freeimages.com/pool.jpg</dcterms:hasFormat> |
|
|
Profile #2 (RDF) |
|
|
|
Model #1 |
|
|
|
Element Content |
URI Reference |
|
|
Attributes |
Resource Reference (rdf:resource) |
|
|
Model #2 |
|
|
|
Element Content |
Plain Literal |
|
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
|
Model #3 |
|
|
|
Element Content |
XML Literal |
|
|
Attributes |
rdf:parseType=”Literal” |
|
|
Examples |
Model #1 <dcterms:hasFormat rdf:resource=“http://wap.wanderlust.com/2000/08/Belize.wml”/>
<dcterms:hasFormat rdf:resource="doi:123/p92-1293"/>
Model #2 <dcterms:hasFormat>photo1293.jpg</dcterms:hasFormat>
Model #3 <dcterms:hasFormat rdf:parseType=”Literal”> doi&colon:123/p92&endash;1293</dcterms:hasFormat> |
|
|
Profile 3 (XMP) |
|
|
|
Qualifier Value |
bag Text, a refined version of dc:relation |
|
|
Name |
Has Part |
|
Identifier |
dcterms:hasPart |
|
Definition |
The described resource includes the referenced resource either physically or logically. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
dcterms:hasPart allows the metadata for an article to identify images, sidebars, tables, graphs, maps, illustrations, etc. in the article which exist as separate, identifiable, resources. The metadata for those resources can then be fetched, based on the identifier for the included resource. The identifier must be non-literal, typically a URI. Recommended best practice is to describe photos, etc. as separate objects, rather than embedding their metadata in the metadata for an article, in order to ease their reuse and to simplify data maintenance when the resources are reused. Best practice is also to identify the resources with URIs, rather than human-readable text descriptions, in order to enable automated handling of the resource. For profile 2, if there are multiple parts for the resource, PRISM recommends listing the multiple parts inside one dcterms:hasPart element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For profile 1, simply repeat the dcterms:hasPart element multiple times. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Example |
<dcterms:hasPart>http://freeimages.com/pool.jpg</dcterms:hasPart> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference |
|
Attributes |
Resource Reference (rdf:resource) xml:lang = (optional) designed for identifying the human language used |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1
<dcterms:hasPart rdf:resource=
Model #2 <dcterms:hasPart>http://www.travelmongo.com/2000/08/BelizePhoto.jpg </dcterms:hasPart>
Model #3 <dcterms:hasPart rdf:parseType=”Literal”>dam&endash;obj&endash;32485u2</dcterms:hasPart> |
|
Profile 3 (XMP) |
|
|
Qualifier Value |
bag Text, a refined version of dc:relation |
|
Name |
Has Version |
|
|
Identifier |
dcterms:hasVersion |
|
|
Definition |
Identifies the next version of the current resource. |
|
|
Occurrence |
Occurs 0 or 1 time |
|
|
Comment |
Changes in version imply substantive changes in intellectual content rather than differences in format. For changes in format, use the dcterms:hasFormat element. For the special case of versions known as “corrections”, use prism:hasCorrection to point from the current resource to correction blocks. Use dcterms:hasVersion to point from the corrected resource back to the earlier one. |
|
|
Included in PAM? |
No |
|
|
Included in PSV? |
No |
|
|
Profile #1 (XML) |
|
|
|
Element Content |
String |
|
|
Attributes |
None |
|
|
Example |
<dcterms:hasVersion>http://freeimages.com/pool.jpg</dcterms:hasVersion> |
|
|
Profile #2 (RDF) |
|
|
|
Model #1 |
|
|
|
Element Content |
URI Reference (empty element) |
|
|
Attributes |
Resource Reference (rdf:resource) |
|
|
Model #2 |
|
|
|
Element Content |
Plain Literal |
|
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
|
Model #3 |
|
|
|
Element Content |
XML Literal |
|
|
Attributes |
rdf:parseType=”Literal” |
|
|
Examples |
Model #1 <dcterms:hasVersion rdf:resource= “http://travelmongo.com/2000/08/BelizeTravelUpdate.xml”/>
Model #2 <dcterms:hasVersion>BelizeTravelUpdate_04.xml</dcterms:hasVersion>
Model #3 <dcterms:hasVersion rdf:parseType=”Literal”> dam&endash;obj&endash;32485u2</dcterms:hasVersion> |
|
|
Profile 3 (XMP) |
|
|
|
Qualifier Value |
Text, a refined version of dc:relation |
|
|
Name |
Identifier |
|
Identifier |
dc:identifier |
|
Definition |
An unambiguous reference to the resource, within a given context. |
|
Occurrence |
Required 1 time for an article. May also be used for each media asset to uniquely identify that asset. |
|
Comment |
In PRISM, dc:identifier provides a place for the unique identification of a resource. PRISM requires the use a single dc:identifier statement with a unique identifier to identify a particular published item. Other PRISM identifiers can be applied to provide further identification that is required. You may identify the resource by means of a unique string or number conforming to a formal identification system or generate your own unique identifier. Example formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)) or the Digital Object Identifier (DOI). If you identify the asset with a DOI or URL in addition to a unique dc:identifier, you may identify the DOI with the prism:DOI element and the URL with the prism:URL. Consistent and thorough use of identifiers is essential for PRISM conformance. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dc:identifier>10-234/3245</dc:identifier> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Examples |
Model #1 <dc:identifier rdf:resource=”doi:10.1030/03054”/>
Model #2 <dc:identifier>10.1030/03054</dc:identifier> <prism:doi>http://dx.doi.org/10.1030/03054</prism:doi> |
|
Profile 3 (XMP) |
|
|
Property Value |
Text |
|
Name |
Is Format Of |
|
Identifier |
dcterms:isFormatOf |
|
Definition |
The current resource is the same intellectual content of the referenced resource, but presented in another format. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
This is the inverse of the dcterms:hasFormat relation. It is used to point from the modified version to an earlier version. It is only used when it is known that the referenced resource is closer to being the 'original' than the current resource. For profile 2, If there are multiple formats for the resource PRISM recommends listing the multiple formats inside one dcterms:isFormatOf element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For profile 1, simple repeat the dcterms:isFormatOf element multiple times. |
|
Included in PAM? |
No |
|
Included in PSV? |
No |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dcterms:isFormatOf>Beize.pdf</dcterms:isFormatOf> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1 <dcterms:isFormatOf rdf:resource=”http://wanderlust.com/2000/08/Belize.qxd”/>
Model #2 <dcterms:isFormatOf>Beize.pdf</dcterms:isFormatOf>
Model #3 <dcterms:isFormatOf rdf:parseType=”Literal”> doi&colon:123/p92&endash;1293</dcterms:isFormatOf> |
|
Profile 3 (XMP) |
|
|
Qualifier Value |
bag Text, a refined version of dc:relation |
|
Name |
Is Part Of |
|
Identifier |
dcterms:isPartOf |
|
Definition |
The described resource is a physical or logical part of the referenced resource. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
This is the inverse of the dcterms:hasPart relation. Note that it is NOT required to always have both sides of the relationship asserted, as one can be derived from the other. Recommended best practice is to identify the containing resource with a URI. However, textual identifiers are possible so implementations SHOULD be able to accept them, possibly with reduced functionality.
|
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Example |
<dcterms:isPartOf>BelizeArticle.html</dcterms:isPartOf> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) xml:lang = (optional) designed for identifying the human language used |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1
<dcterms:isPartOf rdf:resource=
Model #2 <dcterms:isPartOf>BelizeArticle.html</dcterms:isPartOf>
Model #3
<dcterms:isPartOf rdf:parseType=”Literal”>dam&endash;obj&endash;32485u2 |
|
Profile 3 (XMP) |
|
|
Qualifier Value |
bag Text, a refined version of dc:relation |
|
Name |
Is Required By |
|
Identifier |
dcterms:isRequiredBy |
|
Definition |
The described resource is required by the referenced resource, either physically or logically. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
This is the inverse of the dc:requires relation. For profile 2, If there are multiple “is required by” elements for the resource PRISM recommends listing the multiple values inside one dcterms:isRequiredBy element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For profile 1, simple repeat the dcterms:isRequiredBy element multiple times. |
|
Included in PAM? |
No |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dcterms:isRequiredBy>dl123452345.xml</dcterms:isRequiredBy> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1 <dcterms:isRequiredBy rdf:resource= “http://wanderlust.com/2000/08/BelizePhoto.jpg”/>
Model #2 <dcterms:isRequiredBy>dl123452345.xml</dcterms:isRequiredBy>
Model #3
<dcterms:isRequiredBy rdf:parseType=”Literal”> |
|
Profile 3 (XMP) |
|
|
Qualifier Value |
bag Text, a refined version of dc:relation |
|
Name |
Is Version Of |
|
Identifier |
dcterms:isVersionOf |
|
Definition |
The described resource is a version, edition, or adaptation of the referenced resource. Changes in version imply substantive changes in intellectual content rather than differences in format. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
This is the inverse of dcterms:hasVersion. PRISM considers versions to be iterative and to have the same dc:identifier.
For corrections, use the subproperty prism:isCorrectionOf.
For alternative versions that do not have substantive changes in intellectual content, use dcterms:isAlternativeFor. |
|
Included in PAM? |
No |
|
Included in PSV? |
No |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dcterms:isVersionOf>Ovid’s Ars Amatoria</dcterms:isVersionOf> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1
<dcterms:isVersionOf rdf:resource=
Model #2 <dcterms:isVersionOf>http://travelmongo.com/2000/08/BelizeTravel.xml </dcterms:isVersionOf>
Model #3 <dcterms:isVersionOf rdf:parseType=”Resource”> dam&endash;obj&endash;32485u2</dcterms:isVersionOf> |
|
Profile 3 (XMP) |
|
|
Qualifier Value |
Text, a refined version of dc:relation |
|
Name |
Language |
|
Identifier |
dc:language |
|
Definition |
A language of the intellectual content of the resource. |
|
Occurence |
Occurs 0 to many times |
|
Comment |
Recommended best practice for the values of the Language element is defined by RFC 3066 [RFC-3066]. It specifies the use of a two-letter (or three-letter) Language Code taken from the ISO 639 standard [ISO-639] (or from ISO 639-2), optionally followed by a two-letter Country Code (taken from the ISO 3166 standard [ISO-3166]). For example, 'en' for English, 'fr' for French, or 'en-GB' for English used in the United Kingdom. |
|
Included in PAM? |
No |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dc:language>en-US</dc:language> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Examples |
Model #1 <dc:language rdf:resource="https://www.din.de/gremien/nas/nabd/iso3166ma/a3ptnorm.htm">
Model #2 <dc:language>en-US</dc:language> |
|
Profile 3 (XMP) |
|
|
Property Value |
bag Text, first entry (dc:language/*[1]) closed choice RFC 3066 [RFC-3066] controlled vocabulary |
Note: dc:language is defined by Adobe as bag Text. PRISM specifies 0 or 1 occurrences. Compromise is to use just the first entry in the unordered list.
|
Name |
Publisher |
|
Identifier |
dc:publisher |
|
Definition |
The entity responsible for making the resource available. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
The organization or individual that released the resource for publication. For magazine title use prism:publicationName. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dc:publisher>Wanderlust</dc:publisher> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1 <dc:publisher rdf:resource=”http://wanderlust.com/”/>
Model #2 <dc:publisher>Wanderlust</dc:publisher>
Model #3 <dc:publisher rdf:parseType=”literal”>Town & Country</dc:publisher> |
|
Profile 3 (XMP) |
|
|
Property Value |
bag ProperName, first entry (dc:publisher/*[1]) |
|
Name |
Relation |
|
Identifier |
dc:relation |
|
Definition |
A reference to a related resource. |
|
Occurence |
Occurs 0 or more times (0 for Profile #1) |
|
Comment |
Because the notion of “related resource” is vague in Profile #1, PRISM recommends that this element not be used for Profile #1. Preference should be given to the more specific Dublin Core [DCMI-TERMS] and PRISM relationship elements [PRISMBMS]. Relation is used for Profile 2 (RDF) and Profile 3, where it is refined by more specific dcterms elements. |
|
Included in PAM? |
No |
|
Included in PSV? |
No |
|
Profile #1 (XML) |
Not recommended |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
Empty Node |
|
Attributes |
Resource Reference (rdf:resource) |
|
Example |
Model #1 <dc:relation> <dcterms:isRequiredBy>dl123452345.xml</dcterms:isRequiredBy> </dc:relation> |
|
Profile 3 (XMP) |
|
|
Property Value |
bag Text |
|
Name |
Requires |
|
Identifier |
dcterms:requires |
|
Definition |
The described resource requires the referenced resource, either physically or logically. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
This is the inverse of the dc:isRequiredBy relation. For profile 2, If there are multiple “requires” elements for the resource PRISM recommends listing the multiple values inside one dcterms:requires element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For profile 1, simple repeat the dcterms:requires element multiple times. |
|
Included in PAM? |
No |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dcterms:requires>dl123452345.xml</dcterms:requires> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Examples |
Model #1 <dcterms:requires rdf:resource=“dl123452345.xml”/>
Model #2 <dcterms:requires>dl123452345.xml</dcterms:requires> |
|
Profile 3 (XMP) |
|
|
Qualifier Value |
bag Text, a refined version of dc:relation |
|
Name |
Rights |
|
Identifier |
dc:rights |
|
Definition |
Information about rights held in and over the resource. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
The PRISM Specification provides the PRISM Usage Rights Metadata Specification [PRISMURMS] for sophisticated rights handling. Best practice is to use elements from this namespace.
The dc:rights element, however, has been retained for those implementors who need to express simple rights and would like to utilize a single element. dc:rights is not documented in the PRISM Rights Guide and should be treated as a standalone element. |
|
Included in PAM? |
No |
|
Included in PSV? |
No |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dc:rights>Permissions Unknown</dc:rights> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Example |
Model #1 <dc:rights rdf:resource=”rights.xml#permissionsUnknown”/> |
|
Profile 3 (XMP) |
|
|
Property Value |
Lang Alt |
|
Name |
Source |
|
Identifier |
dc:source |
|
Definition |
A reference to a resource from which the present resource is derived. The present resource may be a performance, production, derivation, adaptation or interpretation of the referenced resource.
The intent is to deprecate this element in favor of dcterms:source in a future release of PRISM (v3.0). |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
When possible, use a URI for an unambiguous reference to the source. Otherwise, a textual identifier of the source may be provided. |
|
Included in PAM? |
No |
|
Included in PSV? |
No |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dc:source>Adapted from "The River" by Bruce Springsteen</dc:source> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Model #3 |
|
|
Element Content |
XML Literal |
|
Attributes |
rdf:parseType=”Literal” |
|
Examples |
Model #1 <dc:source rdf:resource= “http://example.com/classics/Romeo%20and%20Juliet”/>
Model #2 <dc:source>Adapted from "The River" by Bruce Springsteen</dc:source>
Model #3 <dc:source>Adapted from <strong>The River</strong> by Bruce Springsteen</dc:source> |
|
Profile 3 (XMP) |
|
|
Property Value |
Not Used in XMP, use dcterms:source |
|
Name |
Source |
|
Identifier |
dcterms:source |
|
Definition |
A reference to a resource from which the present resource is derived. The present resource may be a performance, production, derivation, adaptation or interpretation of the referenced resource. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
When possible, use a URI for an unambiguous reference to the source. Otherwise, a textual identifier of the source may be provided. |
|
Included in PAM? |
No |
|
Included in PSV? |
No |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Examples |
Model #1 <dcterms:source rdf:resource= “http://example.com/classics/Romeo%20and%20Juliet”/>
|
|
Comment |
PRISM Best Practice is to reserve dcterms:source when a URI is given as the value for this field. dc:source should be used in other instances. |
|
Name |
Subject |
|
Identifier |
dc:subject |
|
Definition |
The main topic or topics of the content of the resource. Defines “aboutness”. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
Dublin Core and PRISM recommend that dc:subject be expressed as a value from a controlled vocabulary, if available. PRISM defines several elements for more specific types of subjects, such as when events, locations, objects, organizations and people are the subject of the resource. Those elements SHOULD be used in preference to the dc:subject element if appropriate. You may use dc:subject to indicate that such things as a concept, a disease or a theory are the subject of an article because there is no special PRISM element to cover these types of subjects. For profile 2, if there are multiple subjects for the resource PRISM recommends listing the multiple subjects inside one dc:subject element using the RDF containers such as rdf:Bag, rdf:Seq or rdf:Alt to be XMP compatible. For profile 1, simple repeat the dc:subject element multiple times. If local operations on the name(s) or definition(s) of the vocabulary elements is needed, PRISM’s recommended practice is to provide the value of the dc:subject element using the pcv:Descriptor element and its allowed elements of pcv:vocab, pcv:code, and pcv:label. Remember, PRISM element types are specified in camel case. The exception is that when elements denote Classes in the sense of the RDF Schema [W3C-RDFS], they must begin with an uppercase letter. The only PRISM element to do so is pcv:Descriptor. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used. prism:namespace= specifies the namespace of the subject in order to link to the appropriate subject vocabulary |
|
Example |
<dc:subject>Seasonal Affective Disorder</dc:subject> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) prism:namespace= specifies the namespace of the subject in order to link to the appropriate subject vocabulary |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used prism:namespace= specifies the namespace of the subject in order to link to the appropriate subject vocabulary |
|
Examples |
Model #1 <dc:subject rdf:resource=”http://prismstandard.org/vocabs/lcc/QA76”/>
Model #2 <dc:subject>Seasonal Affective Disorder</dc:subject> |
|
Profile 3 (XMP) |
|
|
Property Value |
Model #1 Full interoperability with existing XMP Property Value dc:subject bag Text (no support for prism:namespace attribute) Model #2 Use dcterms:subject property adding prism:namespace information. |
|
Name |
Subject |
||
|
Identifier |
dcterms:subject |
||
|
Definition |
The main topic or topics of the content of the resource. Defines “aboutness”. |
||
|
Occurrence |
Occurs 0 or more times |
||
|
Comment |
PRISM Best Practice is to reserve dcterms:source when a URI is given as the value for this field. dc:source should be used in other instances. |
|
|
|
Included in PAM? |
Yes |
||
|
Included in PSV? |
Yes |
||
|
Profile #2 (RDF) |
|
||
|
Model #1 |
|
||
|
Element Content |
URI Reference (empty element) |
||
|
Attributes |
Resource Reference (rdf:resource) prism:namespace= specifies the namespace of the subject in order to link to the appropriate subject vocabulary |
||
|
Name |
Title |
|
Identifier |
dc:title |
|
Definition |
The name given to the resource. |
|
Occurrence |
Occurs 0 or 1 time |
|
Comment |
Dublin Core recommends that dc:title be a name by which the resource is formally known.
PRISM recommends that magazine publishers use dc:title for the headline of an article. The name of the magazine in which the article appears can be provided in the prism:publicationName element.
The PRISM Specification allows titles to contain special markup characteristics. In such cases the rdf:parseType=”Literal” MUST be given. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used. |
|
Example |
<dc:title>Man of the Year 2002</dc:title> |
|
Profile #2 (RDF) |
|
|
Model #1 |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Resource Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Examples |
Model #1 <dc:title rdf:resource=”http://www.usatoday.economy”/>
Model #2 <dc:title>Man of the Year 2002</dc:title> <prism:publicationName>Time Magazine</prism:publicationName> <dc:publisher>Time Inc.</dc:publisher> |
|
Profile 3 (XMP) |
|
|
Property Value |
Lang Alt |
|
Name |
Type |
|
Identifier |
dc:type |
|
Definition |
The style of presentation of the resource’s content, such as image vs. a table. |
|
Occurrence |
Occurs 0 or more times |
|
Comment |
The ‘type’ of a resource can be many different things. In PRISM descriptions, the dc:type element takes values that indicate the style of presentation of the content, such as “Map”, “Table”, or “Chart”. This is in contrast to prism:genre, which represents the intellectual content type, of the resource. For example, the genre ‘electionResults’ can be presented in a map, a table, or a chart. Recommended practice for PRISM implementations is to use a value from Table 8.0 [PRISMCVS] Controlled Vocabulary of Presentation Styles, expressed as a URI reference. Implementations MUST also be able to handle text values, but interoperation with text values cannot be guaranteed. To describe the physical size or digital file format of the resource, use the dc:format element. |
|
Included in PAM? |
Yes |
|
Included in PSV? |
Yes |
|
Profile #1 (XML) |
|
|
Element Content |
String |
|
Attributes |
None |
|
Example |
<dc:type>photo</dc:type> |
|
Profile #2 (RDF) |
|
|
Element Content |
URI Reference (empty element) |
|
Attributes |
Authority Reference (rdf:resource) |
|
Model #2 |
|
|
Element Content |
Plain Literal |
|
Attributes |
xml:lang = (optional) designed for identifying the human language used |
|
Examples |
The three examples below show how prism:type, prism:genre, and dc:format all describe different aspects of a resource. For brevity, the examples below use relative URI references. Assume that they are within the scope of a base URI declaration:
Model #1 <dc:type rdf:resource=”resourcetype.xml#photo”/> <prism:genre rdf:resource=”genre.xml#cover”/> <dc:format>image/jpeg</dc:format>
Model #2 <dc:type>http://idealliance.resourcetype.xml#photo/> <prism:genre rdf:resource="genre.xml#cover"/> <dc:format>image/jpeg</dc:format> |
|
Profile #3 (XMP) |
|
|
Property Value |
bag Text, closed vocabulary |