prism_specification

 

 

 

PRISM:

Publishing Requirements for Industry Standard Metadata

 

 

Version 2.2

 

 

The PRISM/PAM Inline Markup Specification

 

 

October 4, 2012

 

 

 

 

idealliancelogo_cymk


Copyright and Legal Notices

© 2001 – 2012 International Digital Enterprise Alliance, Inc.  All Rights Reserved.

PRISM® and nextPub® are registered trademarks of the International Digital Enterprise Alliance, Inc. (IDEAlliance).

This document may be downloaded and copied provided that the above copyright notice and this Notice are included on all such copies.  This document itself may not be modified in any way, except as needed for the purpose of developing International Digital Enterprise Alliance, Inc. (“IDEAlliance”) specifications.  Use of the specification or standard set forth in this document shall not create for the user any rights in or to such specification or standard or this document, which rights are exclusively reserved to IDEAlliance or its licensors or contributors.

Use of this document and any specification or standard contained herein is voluntary.  By making use of this document or any specification or standard contained herein, the user assumes all risks and waives all claims against IDEAlliance, its licensors and contributors.  By making this document available, IDEAlliance is not providing any professional services or advice to any person or entity.  Any person or entity utilizing this document or any specification or standard contained herein should rely upon the advice of a competent professional before using any such information. 

NO WARRANTY, EXPRESSED OR IMPLIED, IS MADE REGARDING THE ACCURACY, ADEQUACY, COMPLETENESS, LEGALITY, RELIABILITY OR USEFULNESS OF ANY INFORMATION CONTAINED IN THIS DOCUMENT OR IN ANY SPECIFICATION OR STANDARD OR OTHER PRODUCT MADE AVAILABLE BY IDEALLIANCE. THIS DOCUMENT AND THE INFORMATION CONTAINED HEREIN AND INCLUDED IN ANY SPECIFICATION OR STANDARD OR OTHER PRODUCT OR SERVICE OF IDEALLIANCE IS PROVIDED ON AN "AS IS" BASIS. IDEALLIANCE DISCLAIMS ALL WARRANTIES OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO, ANY ACTUAL OR ASSERTED WARRANTY OF NON-INFRINGEMENT OF PROPRIETARY RIGHTS, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

IN NO EVENT SHALL IDEALLIANCE, ITS LICENSEES, CONTRIBUTORS OR THEIR RESPECTIVE OFFICERS, DIRECTORS, EMPLOYEES, AGENTS, REPRESENTATIVES, SUPPLIERS OR CONTENT OR SERVICE PROVIDERS BE LIABLE FOR DAMAGES OF ANY KIND, INCLUDING WITHOUT LIMITATION, DIRECT, INDIRECT, COMPENSATORY, SPECIAL, INCIDENTAL, PUNITIVE OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION DAMAGES FROM DATA LOSS OR BUSINESS INTERRUPTION) EVEN IF MADE AWARE OF THE POSSIBILITY OF SUCH DAMAGES, WHETHER IN AN ACTION UNDER CONTRACT, TORT OR ANY OTHER THEORY, ARISING OUT OF OR IN CONNECTION WITH THE USE, INABILITY TO USE OR PERFORMANCE OF THIS DOCUMENT, THE SPECIFICATION OR STANDARD CONTAINED HEREIN, OR ANY OTHER DOCUMENT OR SPECIFICATION OR STANDARD MADE AVAILABLE BY IDEALLIANCE. 

Some states do not allow the disclaimer or limitation of damages, so the disclaimers set forth above apply to the maximum extent permitted under applicable law.

IDEAlliance takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed or implicated with respect to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available.  IDEAlliance does not represent that it has made any effort to identify any such rights. Information on IDEAlliance's procedures with respect to rights in IDEAlliance specifications can be found at the IDEAlliance website at www.idealliance.org.  Copies of third-party claims of rights, assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification, can be obtained from the President of IDEAlliance at patent-disclosure@idealliance.org.

IDEAlliance requests interested parties to disclose any copyrights, trademarks, service marks, patents, patent applications, or other proprietary or intellectual property rights which may cover technology that may be required to implement this specification. Please address the information to the President of IDEAlliance at patent-disclosure@idealliance.org.

 


Table of Contents

1     Status. 1

1.1         Document Status. 1

1.2         Document Location.. 1

1.3         Version History. 1

2     PRISM Documentation Structure. 3

2.1         Normative and Non-normative Sections. 3

2.1.1      Requirement Wording Note. 3

2.2         The PRISM Documentation Package. 3

2.2.1      General Documents. 3

2.2.2      PRISM Metadata Specifications. 4

2.2.3      PRISM Aggregator Message Markup Specification.. 4

2.2.4      PRISM Inline Markup Specification.. 5

2.2.5      PRISM Controlled Vocabulary Specifications. 5

2.2.6      Additional PRISM Documentation.. 5

2.2.7      Access to PRISM Documentation.. 6

2.2.8      Access to PAM Schemas. 6

2.2.9      PRISM Source Vocabulary Documentation Set. 6

2.3         PSV Content Management Schema. 7

2.4         Other PSV Schemas. 7

3     Introduction. 9

3.1         Purpose and Scope. 9

3.2         New in this Version.. 9

4     Element Definitions: The PRISM Inline Markup. 11

4.1         PRISM Inline Markup.. 11

4.1.1      pim:academicField.. 11

4.1.2      pim:event. 11

4.1.3      pim:industry. 12

4.1.4      pim:keyword.. 12

4.1.5      pim:link. 12

4.1.6      pim:location.. 13

4.1.7      pim:object. 13

4.1.8      pim:organization.. 13

4.1.9      pim:person.. 13

4.1.10        pim:profession.. 14

4.1.11        pim:quote. 14

4.1.12        pim:sport. 14

4.1.13        pim:ticker. 15

4.1.14        pim:timePeriod.. 15


1      Status

1.1      Document Status

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

1.2      Document Location

The location of this document is:

http://www.prismstandard.org/specifications/2.2/PRISM_Inline_Markup_Namespace_3.0.pdf

or

http://www.prismstandard.org/specifications/2.2/PRISM_Inline_Markup_Namespace_3.0.htm

1.3      Version History

Version Number

Release Date

Editor

Description

1.2

1/26/05

McConnell

Converted from unmodularized PRISM spec v 1.2

2.0 Release

2/19/08

Kennedy

Final for Release

2.1 Final

05/15/09

Kennedy

Final Spec with Comments Resolved

3.0 Draft

12/15/11

Kennedy

Released for Public Comment

3.0 Final Draft

06/12/2012

Kennedy

Final Draft w Comments Resolved

3.0 Final

10/04/2012

Kennedy

Final Specification


2      PRISM Documentation Structure

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

2.1      Normative and Non-normative Sections

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.1.1    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.1.2    General Documents

This is a set of general or overview documents that apply to PRISM.

Document

Description

PRISM Introduction [PRISMINT]
http://www.prismstandard.org/specifications/3.0/
PRISM_introduction_3.0.pdf

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

Overview, background, purpose and scope of PRISM; examples; contains no normative material.

PRISM Compliance [PRISMCOMP]
http://www.prismstandard.org/specifications/3.0/
PRISM_compliance_3.0.pdf

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

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

2.1.3    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

The PRISM Basic Metadata Specification [PRISMBMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Basic_Metadata_3.0.pdf

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

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

PRISM Advertising Metadata Specification [PRISMADMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Advertising_Metadata_3.0.pdf

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

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

The PRISM Subset of Dublin Core Metadata Specification [PRISMDCMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Dublin_Core_Metadata_3.0.pdf

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

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

The PRISM Image Metadata Specification [PRISMIMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Image_Metadata_Specification_3.0.pdf

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

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

The PRISM Recipe Metadata Specification [PRISMRMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Recipe_Metadata_3.0.pdf

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

Describes the metadata elements contained in the PRISM Recipe Metadata Namespace, includes normative material

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

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

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

2.1.4    PRISM Aggregator Message Markup Specification

This module documents the PRISM Markup Elements and Attributes for use with the PRISM Aggregator Message.  At the time of the publication of the Introduction to PRISM, the PAM Message remains at version 2.1.   This set of documents includes:

Document

Description

The PRISM PAM Markup Specification [PRISMPAMMS]
http://www.prismstandard.org/specifications/2.1/
PRISM_PAM_Markup_2.1.pdf

or
http://www.prismstandard.org/specifications/2.1/
PRISM_PAM_Markup_2.1.htm

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

2.1.5    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]
http://www.prismstandard.org/specifications/2.1/
PRISM_PIM_Markup_Specification 3.0.pdf

or
http://www.prismstandard.org/specifications/2.1/
PRISM_PIM_Markup_Specification 3.0.htm

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

2.1.6    PRISM Controlled Vocabulary Specifications

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

Document

Description

The PRISM Controlled Vocabulary Markup Specification [PRISMCVMS]
http://www.prismstandard.org/specifications/3.0/
PRISM_Controlled_Vocabulary_Markup_3.0.pdf

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

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

The PRISM Controlled Vocabularies Specification [PRISMCVS]
http://www.prismstandard.org/specifications/3.0/
PRISM_CV_Spec_3.0.pdf

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

The PRISM Controlled Vocabularies are now documented in this document.

2.1.7    Additional PRISM Documentation

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

The PRISM Cookbook [PRISMCB] documents implementation strategies for PRISM Profile 1 applications.

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.

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 PRISM Profiles for the encoding of recipes for:

·        Establish a Recipe Database

·        Establish a tagging scheme to code a wide variety of recipes in XML

·        Tag recipes within the PAM message

·        Tag recipes in nextPub XML Content Source

2.1.8    Access to PRISM Documentation

The PRISM documentation package, the PAM guide (see above), the PAM DTD, the PAM XSD and a range of other information concerning PRISM are all publicly and freely available on the PRISM website, www.prismstandard.org.

2.1.9    Access to PAM Schemas

Standard URLs have been established to access PRISM/PAM XSDs and DTDs as well as the XSD for the new PRISM Usage Rights Model.

To access PAM XSDs and DTDs:

http://www.prismstandard.org/schemas/pam/2.1/
http://www.prismstandard.org/schemas/pam/2.1/pam.xsd
http://www.prismstandard.org/schemas/pam/2.1/pam-dc.xsd
http://www.prismstandard.org/schemas/pam/2.1/pam-prism.xsd

To access PRISM Rights Model XSD

http://www.prismstandard.org/schemas/rights/3.0/rightsmodel.xsd

To access PRISM Recipe Tagging and Recipe Database XSD

http://www.prismstandard.org/schemas/recipe/3.0/recipemodel.xsd

2.1.10                    nextPub PRISM Source Vocabulary Documentation Set

nextPub has developed a series of specifications collectively known as the PRISM Source Vocabulary.  The use case for PSV is to encode semantically rich content for transformation and delivery to any platform. This Specification is made up of a modular documentation package that builds on PRISM 3.0 and HTML5.  Over time new modules may be added to the documentation package.  The documentation package for the nextPub PRISM Source Vocabulary Specification Version 1.0 consists of:

Document

Description

PRISM Source Vocabulary Specification Overview [PSVSO]

http://www.prismstandard.org/specifications/psv/1.0/PSV_overview.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PSV_overview.htm

The Introduction to the PRISM Source Vocabulary provides an introduction and a non-technical overview of the PRISM Source Vocabulary.

PRISM Source Vocabulary Specification [PSVS]

http://www.prismstandard.org/specifications/psv/1.0/PSV.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PSV.htm

The PRISM Source Vocabulary Specification defines semantically rich for source metadata and content markup that can be transformed and served to a wide variety of output devices including eReaders, mobile tablet devices, smart phones and print.

PRISM Source Vocabulary Markup Specification [PSVMS]

http://www.prismstandard.org/specifications/psv/1.0/PSV_markkup.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PSV_markup.htm

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

PAM to PSV_Guide [PAMPSVGUIDE]

http://www.prismstandard.org/specifications/psv/1.0/PAM_PSV.pdf
or
http://www.prismstandard.org/specifications/psv/1.0/PAM_PSV.htm

This Guide documents mappings from PAM XML to PSV XML.  It is normative only.

2.2      PSV Content Management Schema

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.

2.3      Other PSV Schemas

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.  These PSV sample schemas will be available from the nextPub website (http://www.nextpub.org) and documented in the nextPub PSV Implementation Guide that will be published following the publication of this specification.


3      Introduction

3.1      Purpose and Scope

The purpose of this document is to describe the basic metadata elements that the PRISM Working Group has defined and included in the PRISM Inline Markup 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: PRISM Inline Markup is XML markup used with the PAM article tagging schema. It does not follow the rules of RDF/XML, even for profile 2 PRISM Compliance (that documents encoding content using the PRISM Profile of RDF). PRISM Inline Markup is never expressed using XMP [XMP] markup. PRISM Inline Markup is not used for PSV content encoding.  See the nextPub PRISM Source Vocabulary Specification for details about how to encode inline markup using PSV.

3.2      New in this Version

Changes in this document include:

·        The addition of a new metadata elements pim:academicField, pim:link, pim:profession, pim:sport.

·        Fields to indicate whether an element is used in the PAM XML tag set or the nextPub XML tag set or both.



4      Element Definitions: The PRISM Inline Markup

All of the content models used in this section describing the PRISM inline Markup follow a model we will call %content.mix; This model is a mix of elements for representing content, such as #PCDATA, <p>, <bold>, <quote>, etc. The details of the parameter entity will depend on the context in which the PRISM namespace is being used.

The recommended namespace for PRISM Inline Markup is:
xmlns:pim=”http://prismstandard.org/namespaces/pim/2.2/”

4.1      PRISM Inline Markup

Metadata is typically considered as out-of-line information. Fields such as Author, Title, and Subject are stereotypical examples of information that is descriptive of the whole of a resource and is frequently held separately from it. However, the publisher members of the PRISM Working Group consistently identified a need for inline markup of organizations, locations, product names, personal names, quotations, etc. Therefore, the PRISM Specification defines a namespace of XML elements and attributes for inline metadata. Such inline metadata was needed for a number of applications and is made use of in the PRISM Aggregator Message Guide [PAMGUIDE].

Developers of XML specifications for the publishing industry can use the following DTD fragment to incorporate PRISM's inline markup elements into their DTDs. The fragment assumes that the basic textual content markup is described in another parameter entity known as %content.mix; Content mix is made up of ***

4.1.1    pim:academicField

Name

Academic Field

Identifier

pim:academicField

Definition

Used to tag mentions of an academic field of study such as archeology or paleontology within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>He studied <pim:academicField>Health Economics<.pim:academicField> before completing his Masters of Science. </p>

4.1.2    pim:event

Name

Event

Identifier

pim:event

Definition

Used to tag mentions of events within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>During the <pim:event>Toronto Film Festival</pim:event>, films from 17 countries were shown.</p>

 

<p>Recent conflicts in the region include the <pim:event>Iran-Iraq War</pim:event>, the <pim:event>First Gulf War</pim:event>, and the <pim:event>Second Gulf War</pim:event>.</p>

4.1.3    pim:industry

Name

Industry

Identifier

pim:industry

Definition

Used to tag mentions of industry sectors within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>The <pim:industry>records industry</pim:industry> attributes the recent slump in CD sales to rampant piracy of their intellectual content.</p>

 

<p><pim:industry>Forestry</pim:industry>, pardon the pun, is the new growth industry.</p>

4.1.4    pim:keyword

Name

Keyword

Identifier

pim:keyword

Definition

Used to tag keywords within the text of an article that are likely to be used in search queries.

Comment

Be sure to differentiate between tagging a keyword and tagging an event, industry, location, object, organization or person that is the subject of an article. Keywords are specifically used to aid search.

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>The <pim:keyword>avian flu</pim:keyword> outbreak in <pim:location>Asia</pim:location> is constantly being monitored.</p>

4.1.5    pim:link

Name

Link

Identifier

pim:link

Definition

Used to tag a link to other information such as a URL, email or twitter hash tag.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>You can learn more at <pim:link>#xmlconference</pim:link></p>

4.1.6    pim:location

Name

Location

Identifier

pim:location

Definition

Used to tag mentions of geographic locations such as “New York City”, “Georgetown”, or “Canada” within the content of an article.

Comment

Even at the simplest level, the location element helps to distinguish, for example, the Scottish city “Paisley” from the fabric design, or the country “China” from the tableware.

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>He spoke on the history of the<pim:location>Great Lakes basin</pim:location> at the Royal Ontario Museum in <pim:location>Toronto</pim:location>.</p>

 

<p>China patterns were selected before their honeymoon in <pim:location href= ”http://prismstandard.org/vocabs/ISO-3166/CN”>China</pim:location>.</p>

4.1.7    pim:object

Name

Object

Identifier

pim:object

Definition

Used to tag mentions of a physical object such as a book, a horse, or a house within the content of an article.

Comment

Use for both living and non-living objects. Should not be used for concepts, diseases, sports, or other concepts that are not truly physical objects.

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference to a controlled vocabulary)

Model

(%content.mix;)

Example

<p>Some analysts compared the recent events to the film <pim:object>Wag the Dog</pim:object>.</p>

4.1.8    pim:organization

Name

Organization

Identifier

pim:organization

Definition

Used to tag the name of any organization, such as a government, department, ministry, corporation, charity, private company, or club within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference to a controlled vocabulary)

Model

(%content.mix;)

Example

<p><pim:organization href=”http://prismstandard.org/vocabs/NYSE:NT”>Nortel Networks</pim:organization> saw its stock fall in the face of the Brazilian devaluation.</p>

4.1.9    pim:person

Name

Person

Identifier

pim:person

Definition

Used to tag the name of a human individual (real or imaginary) in the text of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference to a controlled vocabulary)

Model

(%content.mix;)

Example

<p>Prime Minister <pim:person>Tony Blair</pim:person> will meet with the other <pim:organization>EU</pim:organization> leaders to discuss agricultural policy.</p>

 

<p>Catch-22 is <pim:person href=”http://lc.gov/catdir/LC-NAF? Heller,+Joseph”>Joseph Heller</pim:person>’s best-known work.</p>

4.1.10pim:profession

Name

Profession

Identifier

pim:profession

Definition

Used to tag mentions of a profession such as educator or physician within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>He studied to be an <pim:profession>educator</pim:educator> before completing his Masters of Science. p>

4.1.11pim:quote

Name

Quote

Identifier

pim:quote

Definition

Marks the words attributed to a specific person in the text.

Comment

Note that quotes may contain other quotes.

Included in PAM?

Yes

Included in PSV?

No

Attributes

 

Model

(%content.mix;)

Example

<pim:quote speakerRef=”USPres#JFK” placeRef=”city/Berlin” occasion=”Address to West Berlin” xml:lang=”de”>Ich bin ein Berliner</pim:quote>

4.1.12pim:sport

Name

Sport

Identifier

pim:sport

Definition

Used to tag mentions of a sport such as soccer or baseball within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>The Stanley Cup <pim:sport>Hockey</pim:sport> playoff games were broadcast in late April.

4.1.13pim:ticker

Name

Ticker Symbol

Identifier

pim:ticker

Definition

Marks the appearance of stock ticker symbols in the text.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

 href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<pim:ticker>TWX</pim:ticker>

4.1.14pim:timePeriod

Name

Time Period

Identifier

pim:timePeriod

Definition

Used to tag mentions of a temporal time frame such as “Dark Ages”, “Roaring Twenties”, or “Golden Age” within the content of an article.

Comment

 

Included in PAM?

Yes

Included in PSV?

No

Attributes

href – (for an authority file reference for a controlled vocabulary)

Model

(%content.mix;)

Example

<p>Flappers were the rage during the <pim:timePeriod>Roaring Twenties</pim:timePeriod></p>