W3C W3C Member Submission

PRISM Crafts Metadata Specification

W3C Member Submission 10 September 2020

This version:
https://www.w3.org/Submission/2020/SUBM-prism-20200910/
Latest version:
https://www.w3.org/Submission/prism/
Authors:
Dianne Kennedy (Idealliance)

Abstract

This PRISM Crafts Metadata Specification describes the metadata elements contained in the PRISM Specification to describe crafting content; includes normative material.

Status of this document

This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications can be found in the W3C technical reports index at https://www.w3.org/TR/.

By publishing this document, W3C acknowledges that the Submitting Members have made a formal Submission request to W3C for discussion. Publication of this document by W3C indicates no endorsement of its content by W3C, nor that W3C has, is, or will be allocating any resources to the issues addressed by it. This document is not the product of a chartered W3C group, but is published as potential input to the W3C Process. A W3C Team Comment has been published in conjunction with this Member Submission. Publication of acknowledged Member Submissions at the W3C site is one of the benefits of W3C Membership. Please consult the requirements associated with Member Submissions of section 3.3 of the W3C Patent Policy. Please consult the complete list of acknowledged W3C Member Submissions.

1     Status

1.1    Document Status

The status of this document is:

Released for Public Comment

12/20/2014

Released

03/05/2015

 

 

 

1.2    Document Location

The location of this document [PRISMCMS] is: 1prism-crafts.html

1.3    Version History

Version Number

Release Date

Editor

Description

3.1 Draft

12/20/2014

Kennedy

First Public Working Draft

3.1 Final

03/05/2015

Kennedy

Release V3.1

 

 

 

 

2     PRISM Documentation Structure

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

2.1    Normative and Non-normative Section

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

2.2    Requirement Wording Note

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

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

2.3    The PRISM Documentation Package

The PRISM Documentation Package has been reorganized and some specifications renamed to more accurately reflect the nature of each specification module.  The PRISM documentation package includes the following specifications and documents:

2.4    Compliance Specification

This document provides compliance specification.

Document

Description

PRISM Compliance [PRISMCOMP]

Describes three profiles of PRISM compliance for content and systems; includes normative material.

2.5    PRISM Metadata Specifications

This is the set of documents that outline the prism metadata fields and values by PRISM metadata category.  PRISM has modularized its metadata specification by namepace so users may pick those modules that meet their unique business requirements without having to implement the entire PRISM specification.

Document

Description

PRISM Advertising Metadata Specification [PRISMADMS]

Describes advertising metadata elements including those drawn from AdsML, GWG and Ad-ID; includes normative material.

The PRISM Basic Metadata Specification [PRISMBMS]

Describes the basic metadata elements contained in the PRISM namespace to describe article content; includes normative material.

The PRISM Contract Management Metadata Specification [PRISMCMMS]

Describes metadata elements from the PRISM Contract Management Metadata (pccm:)  namespace that are used to describe contracts and legal documents.

The PRISM Crafts Metadata Specification [PRISMCMS]

Describes the metadata elements contained in the PRISM Crafts Metadata Namespace (pcm:).  Includes normative material.

The PRISM Subset of Dublin Core Metadata Specification [PRISMDCMS]

Describes the metadata elements from the Dublin Core namespace that are included in PRISM; includes normative material.

The PRISM Image Metadata Specification [PRISMIMS]

Describes the metadata elements contained in the PRISM Metadata for Images Namespace and other related image namespaces, includes normative material.

The PRISM Recipe Metadata Specification [PRISMRMS]

Describes the metadata elements contained in the PRISM Recipe Metadata Namespace (prm:).  Includes normative material.

The PRISM Rights Summary Metadata Specification [PRISMRSMS]

Describes the metadata elements contained in the PRISM Rights Summary Metadata Namespace (prsm:).  Includes normative material.

The PRISM Usage Rights Metadata Specification [PRISMURMS]

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

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

2.6    PRISM Aggregator Message Markup Specifications

This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message (PAM) and other aggregator messages.     This set of documents includes:

Document

Description

The PRISM PAM Markup Specification [PRISMPAMMS]

Describes the XML elements and attributes used to encode the PRISM Aggregator Message from both the pam: and pim: namespaces; includes normative material.

The PRISM PAM Markup for Web Content Specification [PRISMPAMWMS]

Describes the XML elements and attributes used to encode the PRISM Aggregator Message for Web Content.  This Specification draws from both the pam: and pim: namespaces and includes normative material. PAMW is used to automate the harvesting of Web Content so that it may be sent to aggregators or stored in a publishers PAM-based content management system.

2.7    PRISM Inline Markup Specification

This module documents the PRISM Inline Markup Elements and Attributes for use with the PRISM Aggregator Message.  This set of documents includes:

Document

Description

The PRISM Inline Markup Specification [PRISMIMS]

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

2.8    PRISM Controlled Vocabulary Specifications

These modules are new with PRISM 3.0.  All controlled vocabularies and their terms are documented in this publication set. 

Document

Description

The PRISM Controlled Vocabulary Markup Specification [PRISMCVMS]

Describes the metadata fields in the PRISM Controlled Vocabulary Namespace that can be used to describe a controlled vocabulary.   Actual PRISM controlled vocabularies are now placed in the PRISM Controlled Vocabularies Specification [PRISMCVS]

The PRISM Controlled Vocabularies Specification [PRISMCVS]

The PRISM Controlled Vocabularies are now documented in this document.

 

2.9    Additional PRISM Documentation (Non-Normative Guides)

•       The Guide to the PRISM Aggregator Message [PAMGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.

•       The Guide to the PRISM Aggregator Message for Web Content [PAMWGUIDE] documents the PRISM Aggregator Message (PAM), an XML-based application of PRISM.

•       Guide to the PSV Aggregator/Distributor Message Package [PAMPGUIDE] documents how to use the PRISM metadata fields and pamP XML messaging tags to deliver content to content aggregators/distributors.  The Guide documents the pamP XML message structure and provides the pamP XSD and document samples.

•       The Guide to PRISM Contract Management [CONTRACTSGUIDE] documents an XML-based PRISM contract management model.  The Guide is accompanied by an XSD that can be used as the basis for developing a contract management system that interfaces with the PRISM Rights Summary to populate ODRL policy statements. Reference [ODRLRSGUIDE]

•       The Guide to PRISM Metadata for Images [IMAGEGUIDE] documents an XML-based PRISM Profile 1 application for the expression of the structure and use of PRISM Metadata for Images and can be used as the basis for developing an image management system based on PRISM Metadata for Images and for implementing PMI in XML.

•       The Guide to PRISM Recipe Metadata and XML Encoding [RECIPEGUIDE] documents the XML-based recipe model for developing a recipe database, for tagging a wide variety of recipes in XML and for tagging recipes within a PAM Message.

•       The Guide to PRISM Usage Rights [RIGHTSGUIDE] documents an XML-based PRISM application for the expression of PRISM Usage Rights.  The Guide is accompanied by an XSD that can be used as the basis for developing a digital rights management system based on PRISM Usage Rights.

•       PAM to PSV_Guide [PAMPSVGUIDE] documents mappings from PAM XML to PSV XML.

2.10 PRISM Source Vocabulary Specification

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.

2.11 PRISM Schemas

While PRISM is primarily a metadata specification, it also includes some XML schemas that define encoding of specific kinds of content for publication and interchange.  The PRISM schemas include:

•       Contracts_xsd.zip contains a schema that can be used to encode publication contracts.

•       Crafts_xsd.zip contains a schema that can be used to encode crafts.

•       Image_xsd.zip contains a schema that can be used to encode images.

•       PAM_xsd.zip contains a schema that can be used to encode a PRISM aggregator message.

•       pamW_xsd.zip contains a schema that can be used to encode a PRISM aggregator message for Web content.

•       pamP_xsd.zip contains a schema that can be used to encode a PRISM aggregator/distributor message package.

•       PSV_xsd.zip contains a schema that can be used to encode content in PRISM Source Vocabulary.

•       Recipe_xsd.zip contains a schema that can be used to encode recipes.

•       Rights_xsd.zip contains a schema that can be used to encode usage rights.

2.12 PRISM Controlled Vocabularies

PRISM has defined 38 controlled vocabularies using PRISM controlled vocabulary markup.  See The PRISM Controlled Vocabulary Specification [PRISMCVS].  All CVs are available in CVs.zip.

2.13 PRISM Namespaces

PRISM namespace declarations can be found in Namespaces.zip.  The following are the recommended Namespaces for PRISM metadata:

Usage Vocabulary

Namespace

PRISM Basic Metadata

basic:

PRISM Aggregator Message (PAM) Markup

pam:

PRISM Controlled Vocabulary Markup

pcv:

PRISM Source Vocabulary

psv”

PRISM Inline Markup

psm

Dublin Core metadatap

dc:

RDF

rdf:

PAM aggregator/distributor package

pamp:

PRISM Crafts metadata

pcm:

PRISM Contract Management metadata

pccm:

PRISM advertising metadata

prism-ad:

PRISM rights language metadata

prl:

PRISM recipe metadata

prm:

PRISM usage rights metadata

pur:

2.14 PSV Content Management Schema

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

Note: The PSV CM schema is not designed for tagging content.  It is provided simply to serve as a basis for the design of a content repository.  Metadata building blocks from this schema can be combined with HTML5 by publishers who wish to develop a hybrid PSV metadata and content tagging schema.

 

3     Introduction

3.1    Purpose and Scope

The purpose of this document is to describe the crafts metadata elements that the PRISM Working Group has defined and included in the pcm: namespace. 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 Crafts Metadata V.3.1. [CRAFTSGUIDE].

3.2    New in this Version

This is the first version of the PRISM Crafts Metadata Specification.

4     PRISM Element and Attribute Definitions

4.1    PRISM Crafts Metadata Namespace

The PRISM specification defines namespaces for each metadata module. The “pcm:”’ namespace (http://prismstandard.org/namespaces/crafts/3.1/) contains crafts elements suitable for a wide range of content publication, licensing, and reuse situations.

The recommended namespace for PRISM is:
xmlns:pcm=”http://prismstandard.org/namespaces/crafts/3.1 /

4.2    PRISM Element and Attribute Models

All three PRISM profiles are documented in this section. First Profile #1 is documented. The documentation for the XML only profile includes a field that indicates whether this element is included in the PRISM Aggregator Message. If the element is included in PAM, please refer to Appendix C for more detailed information about the use of the element in the context of the XML PAM message. The elements included in PAM are those elements that publishers plan to send to aggregators for the purpose of aggregation. Not all elements are included in PAM.

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

PRISM Profile #3 (XMP) is also documented in this section. The documentation concentrates on the property and container values for the XMP field to 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  pcm:craftCategory

Name

Craft Category

Identifier

pcm:craftCategory

Definition

Indicates an organizational category for a craft.  This is user defined and there is no formal controlled vocabulary for this field.

Comment

 

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

 

Example

<pcm:craftCategory>home décor</pcm:craftCategory>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

string

Attributes

 

Examples

Model #1

<pcm:craftCategory rdf:resource=“craftCategory.xml/#homeDecor” />

Model #2

<pcm:craftCategory>home décor</pcm:craftCategory>

Profile #3 (XMP)

 

Property Value

Text

4.2.2  pcm:craftSubcategory

Name

Craft Subcategory

Identifier

pcm:craftSubcategory

Definition

Indicates an organizational subcategory for a craft.  This is user defined and there is no formal controlled vocabulary for this field.

Comment

Note that a craft category is required if the craft subcategory is present

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

 

Example

<pcm:craftCategory>home décor</pcm:craftCategory>
<pcm:craftSubategory>pillows </pcm:craftSubcategory>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

String

Attributes

 

Examples

Model #1

<pcm:craftCategory rdf:resource=“craftCategory.xml/#homeDecor” />
<pcm:craftCategory rdf:resource=“craftSubcategory.xml/#pillows” />

Model #2

<pcm:craftCategory>home décor</pcm:craftCategory>
<pcm:craftSubategory>pillows </pcm:craftSubcategory>

Profile #3 (XMP)

 

Property Value

Text

4.2.3  pcm:craftTitle

Name

Craft Title

Identifier

pcm:title

Definition

Indicates the title for this craft.  May be used interchangeably with dc:title.

Comment

 

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

 

Example

<pcm:craftTitle>denim pillow</pcm:craftTitle>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

string

Attributes

 

Examples

Model #1

<pcm:craftTitle rdf:resource=“craftTitle.xml/#denimpillow”/>

 

Model #2

<pcm:craftTitle>denim pillow</pcm:craftTitle>

Profile #3 (XMP)

 

Property Value

Text

4.2.4  pcm:mainMaterial

Name

Craft Main Material

Identifier

pcm:mainMaterial

Definition

The primary material(s) from which this craft is made.

Comment

 Note that a PRISM CV for craft materials is provided for this purpose

Occurrence

Occurs 0 or many times

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated value, may be customized by each publisher

Attributes

 

Example

<pcm:mainMaterial>Household Item</pcm:mainMaterial>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated value, may be customized by each publisher

Attributes

 

Examples

Model #1

<pcm:mainMaterial rdf:resource=“pubCraftMaterial.xml/#householdItem”/>

 

Model #2

<pcm:mainMaterial>Household Item</pcm:mainMaterial>

Profile #3 (XMP)

 

Property Value

Open Choice

4.2.5  pcm:method

Name

Craft Method

Identifier

pcm:method

Definition

Specifies the method by which this craft is constructed.

Comment

A PRISM Controlled Vocabulary for crafting method is provided

Occurrence

Occurs 0 to many times

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Example

<pcm:method>quilting</pcm:method>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Examples

Model #1

<pcm:method rdf:resource=“craftmethod.xml/#quilting”/>

 

Model #2

<pcm:method>quilting</pcm:method>

Profile #3 (XMP)

 

Property Value

Open Choice

4.2.6  pcm:skillLevel

Name

Craft Skill Level

Identifier

pcm:skillLevel

Definition

Indicates the skill level required to prepare this craft

Comment

.  A craft “skill level” CV is provided for this purpose. Note that the craft skill level CV differs from the recipe skill level CV.

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.0)

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Example

 

<pcm:skillLevel>beginner</pcm:skillLevel>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated value

Attributes

 

Examples

Model #1

<pcm:skillLevel rdf:resource=“craftskillLevel.xml/#beginner”/>

 

Model #2

<pcm:skillLevel>beginner</pcm:skillLevel>

Profile #3 (XMP)

 

Property Value

Open Choice

4.2.7  pcm:sourceType

Name

Craft Source Type

Identifier

pcm:sourceType

Definition

Indicates the type of the craft source (indicated with dc:source). 

Comment

A PRISM CV is provided for craft source.

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Example

<pcm:sourceType >blog</pcm:sourceType>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Examples

Model #1

<pcm:sourceType rdf:resource=“craftSource.xml/#blog”/>

 

Model #2

<pcm:sourceType >blog</pcm:sourceType>

Profile #3 (XMP)

 

Property Value

Open Choice

4.2.8  pcm:specialEquipment

Name

Craft Special Equipment

Identifier

pcm:specialEquipment

Definition

Indicates any major equipment that is needed to prepare this craft such as a kiln or construction equipment. 

Comment

A PRISM CV is provided for this purpose. Example is kiln or pottery wheel.

Occurrence

Occurs 0 to many times

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Example

<pcm:specialEquipment>kiln</pcm:specialEquipment >

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Examples

Model #1

<pcm:specialEquipment rdf:resource=“craftEquipment.xml/#kiln”/>

 

Model #2

<pcm:specialEquipment>kiln</pcm:specialEquipment >

Profile #3 (XMP)

 

Property Value

Open Choice

4.2.9  pcm:specialOccasion

Name

Craft Special Occasion

Identifier

pcm:specialOccassion

Definition

Indicates a special occasion or event associated with this craft.

Comment

Note that the craft special occasion CV differs from the recipe special occasion CV.

Occurrence

Occurs 0 to many times

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Example

<pcm:specialOccasion>Valentines Day</pcm:specialOccasion>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

Enumerated values, may be customized by each publisher

Attributes

 

Examples

Model #1

<pcm:specialOccasion rdf:resource=“craftOccasion.xml/#Valentines”/>

 

Model #2

<pcm:specialOccasion>Valentine’s Day</pcm:specialOccasion>

Profile #3 (XMP)

 

Property Value

Open Choice

4.2.10            pcm:totalCost

Name

Craft Total Cost

Identifier

pcm:totalCost

Definition

Indicates the total cost of this craft.

Comment

Note that the cost of each material required for the craft may be contained within the materials element in the craft body. The unit of currency should be included in this field.

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

 

Example

<pcm:totalCost>$4.50</pcm:totalCost>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

string

Attributes

 

Examples

Model #1

<pcm:totalCost rdf:resource=“pillow31X.xml/#totalCost”/>

 

Model #2

<pcm:totalCost>$4.50</pcm:totalCost>

Profile #3 (XMP)

 

Property Value

Text

4.2.11            pcm:totalTime

Name

Craft Total Time

Identifier

pcm:totalTime

Definition

Indicates the total time it takes to complete this craft.

Comment

Note that detailed information about the time it takes to complete the craft may be contained within the <duration model in the craft body.  This field should contain the total time to complete the craft, including the unit of measure.  Example: totalTime=”23 minutes”

Occurrence

Occurs 0 or one time

Included in PAM?

Yes

Included in PSV?

Yes (V1.1)

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

 

Example

<pcm:totalTime>35 minutes</pcm:totalTime>

Profile #2 (RDF)

 

Model #1

 

Element Content

URI Reference (empty element)

Attributes

Authority Reference (rdf:resource)

Model #2

 

Element Content

string

Attributes

 

Examples

Model #1

<pcm:totalTime rdf:resource=“pillow42WK0.xml/#totalTime”/>

 

Model #2

<pcm:totalTime>35 minutes</pcm:totalTime>

Profile #3 (XMP)

 

Property Value

Text