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 Advertising Metadata Specification describes the metadata elements contained in the PRISM Specification to describe advertising 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:
http://www.prismstandard.org/ specifications/3.0/PRISM_ad_materials_namespace_3.0.pdf
Version Number |
Release Date |
Editor |
Description |
3.0 Draft |
12/15/11 |
Kennedy |
Released for Public Comment |
3.0 Draft |
06/12/2012 |
Kennedy |
Final Draft, comments resolved |
3.0 Spec |
10/04/2012 |
Kennedy |
Final Specification, comments resolved |
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.
The purpose of this document is to describe the elements that PRISM includes for the description of Advertising Materials. All of section 4 of this document is normative.
Note: PRISM includes elements from existing element namespaces that describe advertising materials along with new elements from its own PRISM Advertising Namespace, prism-ad: These elements, developed by the eMedia21 Council, were originally in the idea-aio: namespace but were moved into the prism-ad: namespace with the publication of PRISM 3.0.
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.
This is the first version of the PRISM Ad Materials Metadata Specification.
The PRISM Specification defines numerous namespaces. The “prism-ad:” namespace (http://prismstandard.org/namespaces/prism-ad/3.0) describes the elements that are included within PRISM for the description of advertising metadata.
The recommended namespace for PRISM Advertising Metadata [PRISMADMS] is:
xmlns:prism-ad=”http://prismstandard.org/namespaces/prism-ad/3.0/
The PRISM Advertising Metadata Specification includes metadata elements for advertising that come from two established advertising specifications that are in common use today. These include the adsml-at: namespace developed by the AdsML Working Group and the gwg-at: Ghent Work Group at https://www.gwg.org.
A metadata element from the PRISM prism: Namespace is also recommended for use with advertisements. This element is prism:issueName. In the ADAM Specification either an issue name (in the case of magazines) or the first publication date (in the case of news papers) is required.
Reference the PRISM PRISM Namespace Specification V3.0 for the definition of the PRISM metadata fields used for advertising.
IDEAlliance has published a number of specifications that utilize the metadata fields documented in this specification. In addition, metadata fields from this specification are utilized by specifications developed by other associations.
Note: The documentation for PRISM advertising metadata includes a notation about whether each metadata field is included in IDEAlliance advertising specifications.
The Digital Ad Lab Ad Insertion Order Confirmation Specification documents the fields that are required for submission of a print or straight-from-print (SFP) ad to magazine print production so that the Booking can be verified and be married up with booking information held by the publisher in order to expedite invoicing against the Ad Insertion Order.
Version 2.0 of the AIOC Specification documents only the fields that are required to expedite invoicing and refers to this specification for documentation of those fields.
Note: The AIOC spec has been retired and fields consolidated with the ADAM Specification to provide one specification that can function both for the submission of ad materials to a publisher and to provide booking information so billing can be expedited.
The Digital Ad Lab Asset Delivery Advertising Metadata Specification documents standard required metadata fields to enable automation among ad portals. While there is a direct relationship and overlap with the AIOC Specification, there are some additional fields that are required to facilitate ad production on the publisher side.
Note: While ADAM is designed to support portal interfaces for print advertising, it also takes into account the ads that will be submitted one time but are delivered both in print and as SFP tablet ads.
The PRISM Aggregator Specification documents an XML tag set used to deliver messages containing metadata and article content to content aggregators. The PAM use case does not include the delivery advertising and does not utilize any PRISM advertising metadata.
The PRISM Source Vocabulary Specification documents a framework for encoding source content that it can be managed, aggregated, transformed and delivered to a wide variety of publishing platforms, including print. PSV use cases include enabling the packaging and delivery of ad materials along with publication content. PSV uses many fields from this specification.
The PRISM specification defines numerous namespaces. The “prism-ad:” namespace (http://prismstandard.org/namespaces/prism-ad/3.0) describes the elements that are included within PRISM for the description of advertising metadata.
The recommended namespace for PRISM Advertising Metadata [PRISMADMS] is:
xmlns:prism-ad=”http://prismstandard.org/namespaces/prism-ad/3.0/
All three PRISM profiles are documented in this section. First Profile #1 is documented.
Note: Since delivering image metadata to aggregators is not currently in the scope of PAM, all elements documented here have a “No” indication for PRISM Aggregator Message inclusion.
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 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.
Note: Fields have been added to this documentation to indicate mappings to adsml-at:, gwg-at, and ad-id: namespaces. In addition an indication whether each field is used in either the Digital Ad Lab AIOC and ADAM specifications. Wherever possible IDEAlliance reuses existing elements from these namespaces in the specified order of precedence.
This specification uses existing metadata fields whenever possible. However, sometimes multiple metadata fields exist in competing namespaces. To clarify how users may map to this specification, mappings to the other specifications have been provided in the documentation for each metadata field.
Name |
Ad Identifier System |
Identifier |
prism-ad:adIDSystem |
Definition |
Specifies the system that generated the ad identifier. This may be the Ad-ID system, an agency’s ad identifier system, a publisher’s ad identifier system or even a file name. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
One type of unique identifier is the Ad-ID. This is a code registered with Ad-ID.org and is built with a prefix of 4 alphabetic characters, followed by 8 digits (non-visual media), or followed by 7 digits and optional H for HD (visual media). |
adsML / GWG Property Mapping |
-- |
Ad-ID Mapping |
-- |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism-ad:adIDSystem>Ad-ID</prism-ad:adIDSystem> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
String |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Ad Position |
Identifier |
prism-ad:adPosition |
Description |
Identifies the position in the magazine in which the advertisement is to be placed. Does not apply for newspapers. |
Occurrence |
Occurs 0 to many times |
Content Model |
Enumerated values |
adsML / GWG Property Mapping |
--- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
Text (closed) IFC (inside front cover), IBC (inside back cover), OBC (outside back cover) , MB (main body) |
Attributes |
None |
Example |
<prism-ad:adPosition>IFC</prism-ad:adPosition> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <prism-ad:adPosition rdf:resource= ”http://www.idealliance.org/adPosition.xml/#IFC”/>
Model #2 <prism-ad:adPosition>IFC</prism-ad:adPosition> |
Profile #3 (XMP) |
|
Property Value |
Text (closed) IFC (inside front cover), IBC (inside back cover), OBC (outside back cover) , MB (main body) |
Name |
Advertised Brand |
Identifier |
prism-ad:advertisedBrand |
Definition |
Specifies the brand featured in the advertisement. Brand is often used to help identify an ad. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
In some cases, for example for submitting ads via ADAM compliant portals, both brand and product are required. If only brand is known, enter brand in both the brand and product fields. |
adsML / GWG Property Mapping |
-- |
Ad-ID Mapping |
brand |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
xml:lang = (optional) designed for identifying the human language used |
Example |
<prism-ad:advertisedBrand>Kraft</prism-ad:advertisedBrand> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
String |
Attributes |
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 |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Audience Type |
Identifier |
prism-ad:audienceType |
Definition |
Specifies the audience sector targeted for this ad. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
Audience type may be used to specify the audience sector for the audience specified using prism-ad:targetedAudience. Examples of Audience Types include gender, age range, age group, ethnicity, marital status, educational level, employment status, income range and interest or hobby. |
adsML / GWG Property Mapping |
-- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism-ad:audienceType>gender</prism-ad:audienceType> <prism-ad:targetedAudience>male</prism-ad:targetedAudience> |
Profile #2 (RDF) |
|
Element Content |
Plain Literal |
Attributes |
none |
Example |
<prism-ad:audienceType>gender</prism-ad:audienceType> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Publisher Materials ID |
Identifier |
prism-ad:publisherMaterialsID |
Definition |
Specifies the identifier used by a publisher for this ad. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
The publisher’s identifier for the ad materials (this is matched with the supplier ID and is used by the publisher’s billing system). |
adsML / GWG Property Mapping |
-- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism-ad:publisherMaterialsID>TI80912</prism-ad:publisherMaterialsID> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
String |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Seller Sales Representative Contact |
Identifier |
prism-ad:sellerSalesRepContact |
Description |
The seller’s sales representative name. This is only used for newspaper ads in the situation where copy-chasing still occurs. Use only if absolutely required. A separate field is provided for the contact email. |
Occurrence |
Occurs 0 to 1 time |
Comment |
|
Content Model |
String |
adsML / GWG Property Mapping |
--- |
Ad-ID Mapping |
--- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism-ad:sellerSalesRepContact>Joe Schmo</prism- ad:sellerSalesRepContact> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <prism-ad:sellerSalesRepContact rdf:resource= ”jschmo”/>
Model #2 <prism-ad:sellerSalesRepContact>Joe Schmo </prism- ad:sellerSalesRepContact> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Seller Sales Representative Email |
Identifier |
prism-ad:sellerSalesRepEmail |
Description |
The seller’s sales representative email information. This is only used for newspaper ads in the situation where copy-chasing still occurs. Use only if absolutely required. |
Occurrence |
Occurs 0 to 1 time |
Comment |
|
Content Model |
String |
adsML / GWG Property Mapping |
--- |
Ad-ID Mapping |
--- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism-ad:sellerSalesRepEmail>jschmo@adsales.com</prism- ad:sellerSalesRepEmail> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <prism-ad:sellerSalesRepEmail rdf:resource= ”jschmo@sales.com”/>
Model #2 <prism-ad:sellerSalesRepEmail>jschmo@adsales.com</prism- ad:sellerSalesRepEmail> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Targeted Ad Type |
Identifier |
prism-ad:tabletAdType |
Description |
Identifies the type of tablet Ad |
Occurrence |
Occurs 0 to many times |
Content Model |
String |
adsML / GWG Property Mapping |
--- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
Text (closed) SFP (straight-from-print), SPFplus, DFT (designed for tablet), EFT (enhanced for tablet) |
Attributes |
None |
Example |
<prism-ad:tabletAdType>SFP</prism-ad:tabletAdType> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <prism-ad:tabletAdType rdf:resource= ”http://www.idealliance.org/adType.xml/#SFP”/>
Model #2 <prism-ad:tabletAdType>SFP</prism-ad:tabletAdType> |
Profile #3 (XMP) |
|
Property Value |
Text (closed choice) SFP, SFPplus, DFT, EFT |
|
|
Name |
Targeted Audience |
Identifier |
prism-ad:targetedAudience |
Definition |
Specifies the audience within an audience sector targeted for this ad. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
Audience type should be used to specify the audience sector before the targeted audience is specified.. |
adsML / GWG Property Mapping |
-- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism-ad:audienceType>gender</prism-ad:audienceType> <prism-ad:targetedAudience>male</prism-ad:targetedAudience> |
Profile #2 (RDF) |
|
Element Content |
Plain Literal |
Attributes |
none |
Example |
<prism-ad:audienceType>gender</prism-ad:audienceType> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Web Target |
Identifier |
prism-ad:webTarget |
Description |
For print that will be used directly for tablet “straight from print” (SFP) digital edition advertising as well as for print, this field will provide production with the correct target URL for the link from the advertisement. |
Occurrence |
Occurs 0 or 1 time |
Content Model |
URI |
adsML / GWG Property Mapping |
--- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
URI |
Attributes |
None |
Example |
<prism-ad:webTarget>http://www.idealliance.org</prism-ad:webTarget> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <prism-ad:webTarget rdf:resource= ”http://www.idealliance.org”/>
Model #2 <prism-ad:webTarget>http://www.idealliance.org</prism-ad:webTarget> |
Profile #3 (XMP) |
|
Property Value |
URI |
The PRISM Metadata for Images Namespace Specification includes metadata elements for advertising that come from three established image specifications that are in common use today. These include the adsml-at: namespace developed by the AdsML Working Group (see [ADSML-AT] and the gwg-at: Ghent Work Group (see [GWG-AT] at https://www.gwg.org/).
Name |
Ad Title |
Identifier |
adsml-at:adDescription |
Definition |
The title, theme, creative campaign name or the wording of the caption in the advertisement. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:ProductDescription |
Ad-ID Mapping |
ad_title |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:adDescription>Mac & Cheese is for adults too!</adsml-at:adDescription> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:adDescription rdf:resource= ”http://www.kraft.com/bookingHM11KR124T.htm”/>
Model #2 <adsml-at:adDescription>Mac & Cheese is for adults too! </adsml-at:adDescription>
Model #3 <adsml-at:adDescription rdf:parseType=”Literal”>Mac & Cheese is for adults too!</adsml-at:adDescription> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Product or Brand |
Identifier |
adsml-at:AdvertisedProduct |
Definition |
The product, products or brands featured in the advertisement. |
Occurrence |
Occurs 0 or more times |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:AdvertisedProduct |
Ad-ID Mapping |
product |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:AdvertisedProduct> Mac & Cheese</adsml-at:AdvertisedProduct> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:AdvertisedProduct rdf:resource= ”http://www.kraft.com/macncheese.htm”/>
Model #2 <adsml-at:AdvertisedProduct> Mac & Cheese</adsml-at:AdvertisedProduct> |
Profile #3 (XMP) |
|
Property Value |
Text bag |
Name |
Advertiser |
Identifier |
adsml-at:AdvertiserName |
Definition |
The company name of the parent brand featured in the advertisement. |
Occurrence |
Occurs 0 or more times |
Comment: |
|
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
adsML / GWG Property Mapping |
adsml-at:AdvertiserName |
Ad-ID Mapping |
advertiser |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:AdvertiserName>Kraft</adsml-at:AdvertiserName> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:AdvertiserName rdf:resource= ”http://www.kraft.com/kraft12.htm”/>
Model #2 <adsml-at:AdvertiserName>Kraft</adsml-at:AdvertiserName> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Bleed |
Identifier |
adsml-at:Bleed |
Definition |
Requirement for printing that goes beyond the edge of the sheet after trimming. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No |
adsML / GWG Property Mapping |
adsml-at:Bleed |
Ad-ID Mapping |
bleed |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:Bleed>True</adsml-at:Bleed> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
Boolean (True, False) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Boolean |
Attributes |
none |
Examples |
Model #1 <adsml-at:Bleed rdf:resource= ”http://www.kraft.com/kraft12.htm”/>
Model #2 <adsml-at:Bleed>True</adsml-at:Bleed> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Buyer Name |
Identifier |
adsml-at:BuyerName |
Definition |
The company name of the media buyer for this advertisement. |
Comment |
|
Occurrence |
Occurs 0 or 1 time |
Content Model |
String |
adsML / GWG Property Mapping |
adsml-at:BuyerName |
Ad-ID Mapping |
buyer |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:MediaBuyer>Media Associates</adsml-at:MediaBuyer> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:MediaBuyer rdf:resource= ”http://www.kraft.com/bookingHM11KR124T.htm”/>
Model #2 <adsml-at:MediaBuyer>Media Associates</adsml-at:MediaBuyer> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Replacement |
Identifier |
adsml-at:change |
Definition |
Indicates that this advertisement should replace a previously delivered file |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
-- |
Ad-ID Mapping |
-- |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
Boolean |
Attributes |
None |
Example |
<adsml-at:change>yes</adsml-at:change> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
Boolean |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Boolean |
Name |
Color |
Identifier |
adsml-at:Color |
Definition |
Indicates the type of color to be used for the ad. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:Color |
Ad-ID Mapping |
Color type |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
Text (closed choice) |
Attributes |
None |
Example |
<adsml-at:Color>BW</adsml-at:Color> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
Text (closed choice) |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal: “BW” for black and white, “Color” for full color or “Spot’ for spot color |
Attributes |
none |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Text (closed choice) |
Name |
Spot Color Description |
Identifier |
adsml-at:ColorDescription |
Definition |
Indicates the type of spot color to be used for the ad. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
If spot color is used, describes the type of spot color. This must be a comma-separated list of the colorants to be used in the ad. Process colorants should also be included if used. In the case a spot color would have a comma in the name, add the \ character in front of the comma and use \\ for \ character |
adsML / GWG Property Mapping |
adsml-at:ColorDescription |
Ad-ID Mapping |
Color type |
Required by ADAM |
Yes, conditioned on spot color being specified |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
Text |
Attributes |
None |
Example |
<adsml-at:ColorDescription></adsml-at:ColorDescription> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
Text |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Creative or Agency |
Identifier |
adsml-at:CreatorName |
Definition |
The creative or agency delivering the advertisement to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
This may also identify a production services company. |
adsML / GWG Property Mapping |
The creative or agency delivering the advertisement to the publisher. |
Ad-ID Mapping |
agency |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:CreatorName>ABC Agency</adsml-at:CreatorName> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:CreatorName rdf:resource= ”http://www.abcAgency.com/abcagency.htm”/>
Model #2 <adsml-at:CreatorName>ABC Agency </ adsml-at:CreatorName> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
First Publication Date |
Identifier |
adsml-at:FirstPublication |
Definition |
The date of the first appearance of these ad materials in the specified placement. Supports matching artwork to its booking when a Placement ID is not specified. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
Either the Publication Date (2.1.2) or the Issue Name (2.1.3) must be specified in order to identify the destination for the advertisement. Publication Date is most likely to be used for daily publications, such as newspapers, where the appearance date is known. |
adsML / GWG Property Mapping |
adsml-at:FirstPublication |
Ad-ID Mapping |
-- |
PRISM Mapping |
prism:publicationDate |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:FirstPublication>04-22-2012</ adsml-at:FirstPublication> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
Date |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
<adsml-at:FirstPublication>04-22-2012</ adsml-at:FirstPublication> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Issue Name |
Identifier |
prism:issueName |
Definition |
The common name of the magazine the advertisement is ordered to run in. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
Either the Publication Date or the Issue Name must be specified in order to identify the destination for the advertisement. Issue Name is most likely to be used for non-daily publications, such as magazines, where the appearance date is not known. |
adsML / GWG Property Mapping |
adsml-at:issueName |
Ad-ID Mapping |
-- |
PRISM Mapping |
|
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<prism:issueName>October 2012</prism:issueName> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
String |
Attributes |
None |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
<prism:issueName>October 2012</prism:issueName> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Version |
Identifier |
Gwg-at:PartVersion |
Definition |
Description of the version, or geographic edition of a magazine for which the ad was booked, (e.g., the region or the city …). |
Occurrence |
Occurs 0 to many times |
Content Model |
String |
adsML / GWG Property Mapping |
gwg-at:PartVersion |
Ad-ID Mapping |
geography |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<gwg-at:PartVersion>North America</gwg-at:PartVersion> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <gwg-at:PartVersion rdf:resource= ”http://www.kraft.com/bookingHM11KR124T.htm”/>
Model #2 <gwg-at:PartVersion>North America</gwg-at:PartVersion> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Primary Materials ID |
Identifier |
adsml-at:PrimaryMaterialsID |
Definition |
The creative’s unique identifier for an advertising asset. |
Occurrence |
Occurs one time |
Comment: |
An alternative is to use Ad-ID. |
adsML / GWG Property Mapping |
adsml-at:PrimaryMaterialsID |
Ad-ID Mapping |
Ad-ID |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrimaryMaterialsID>ABCD1234000H</adsml-at:PrimaryMaterialsID> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:PrimaryMaterialsID rdf:resource= ”http://www.abcAgency.com/ ABCD1234000H.htm”/>
Model #2 <adsml-at:PrimaryMaterialsID>ABCD1234000H</adsml-at:PrimaryMaterialsID> |
Examples |
|
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Named Ad Unit |
Identifier |
adsml-at:PrintFixedArea |
Definition |
Indicates a generalized intended display area for the ad such as “full page”. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
Values for this field come from the Ad-ID specification and are documented in the PRISM Controlled Vocabulary Specification |
adsML / GWG Property Mapping |
adsml-at:PrintFixedArea |
Ad-ID Mapping |
print size |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrintFixedArea>Full Page</adsml-at:PrintFixedArea> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:PrintFixedArea rdf:resource= ”http://www.kraft.com/size.htm”/>
Model #2 <adsml-at:PrintFixedArea>Full Page</adsml-at:PrintFixArea> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Print Height Unit |
Identifier |
adsml-at:PrintHeightUnit |
Definition |
Indicates the unit of measure for the print height value. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PrintHeightUnit |
Ad-ID Mapping |
print size |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrintHeightUnit>pt</adsml-at:PrintHeightUnit> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:PrintHeightUnit rdf:resource= ”http://www.kraft.com/sizeunit.htm”/>
Model #2 <adsml-at:PrintHeightUnit>pt</adsml-at:PrintHeightUnit> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Print Height Value |
Identifier |
adsml-at:PrintHeightValue |
Definition |
Indicates the print height value in the unit of measure provided by the adsml-at:PrintHeightUnit field. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
The Print Height Unit is required to give meaning to this value. |
adsML / GWG Property Mapping |
adsml-at:PrintHeightValue |
Ad-ID Mapping |
print size |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrintHeightValue>1024</adsml-at:PrintHeightValue> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:PrintHeightValue rdf:resource= ”http://www.kraft.com/sizevalue.htm”/>
Model #2 <adsml-at:PrintHeightValue>1024</adsml-at:PrintHeightValue> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Print Width Unit |
Identifier |
adsml-at:PrintWidthUnit |
Definition |
Indicates the unit of measure for the print width value. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PrintWidthUnit |
Ad-ID Mapping |
print size |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrintWidthUnit>pt</adsml-at:PrintWidthUnit> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:PrintWidthUnit rdf:resource= ”http://www.kraft.com/sizeunit.htm”/>
Model #2 <adsml-at:PrintWidthUnit>pt</adsml-at:PrintWidthUnit> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Print Width Value |
Identifier |
adsml-at:PrintWidthValue |
Definition |
Indicates the print width value in the unit of measure provided by the adsml-at:PrintHeightUnit field. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
The Print Height Unit is required to give meaning to this value. |
adsML / GWG Property Mapping |
adsml-at:PrintHeightValue |
Ad-ID Mapping |
print size |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrintHeightValue>1024</adsml-at:PrintHeightValue> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:PrintHeightValue rdf:resource= ”http://www.kraft.com/sizevalue.htm”/>
Model #2 <adsml-at:PrintWidthValue>1024</adsml-at:PrintWidthValue> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Production Company Contact |
Identifier |
adsml-at:PrepressContact |
Definition |
The name of the creative, agency or production company contact person delivering the advertisement to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PrepressContact |
Ad-ID Mapping |
agency |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrepressContact>Joe Schmo</adsml-at:PrepressContact> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:PrepressContact rdf:resource= ”http://www.abcAgency.com/abcagency.xml/#schmo”/>
Model #2 <adsml-at:PrepressContact>Joe Schmo</adsml-at:PrepressContact> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Production Company Email |
Identifier |
adsml-at:PrepressEmail |
Definition |
The email of the agency or production company contact person delivering the advertisement to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PrepressEmail |
Ad-ID Mapping |
agency |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrepressEmail>JSchmo@abcagency.com</adsml-at:PrepressEmail> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:PrepressEmail rdf:resource= ”http://www.abcAgency.com/abcagency.htm/#mailto:schmo”/>
Model #2 <adsml-at:PrepressEmail>JSchmo@abcagency</adsml-at:CreatorEmail> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Production Company Fax |
Identifier |
adsml-at:PrepressFax |
Definition |
The fax number of the agency or production company contact person delivering the advertisement to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PrepressFax |
Ad-ID Mapping |
agency |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrepressFax>333-44-2345 </adsml-at:PrepressFax> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:PrepressFax rdf:resource= ”http://www.abcAgency.com/abcagency.htm/#fax:schmo”/>
Model #2 <adsml-at:PrepressFax>333-44-2345 </adsml-at:PrepressFax> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Production Company Name |
Identifier |
adsml-at:PrepressName |
Definition |
The company delivering the advertisement to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
This may also identify an agency, prepress or production services company. |
adsML / GWG Property Mapping |
adsml-at:PrepressName |
Ad-ID Mapping |
agency |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrepressName>ABC Agency</adsml-at:PrepressName> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:PrepressName rdf:resource= ”http://www.abcAgency.com/abcagency.htm”/>
Model #2 <adsml-at:PrepressName>ABC Agency </ adsml-at:PrepressName> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Production Telephone |
Identifier |
adsml-at:PrepressTelephone |
Definition |
The telephone number of the agency or production company contact person delivering the advertisement to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PrepressTelephone |
Ad-ID Mapping |
agency |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:PrepressTelephone>866-333-1212</adsml-at:PrepressTelephone> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:PrepressTelephone rdf:resource= ”http://www.abcAgency.com/abcagency.htm/#schmo”/>
Model #2 <adsml-at:PrepressTelephone>866-333-1212</adsml-at:PrepressTelephone> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Destination Publication Name |
Identifier |
adsml-at:Publication |
Definition |
The title of the publication in which this ad will be published. Mandatory. Supports matching artwork to its booking when a Placement ID is not specified. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
Note: In order to optimize the interoperability between systems, the publication name should be the one provided by the publisher in the media kit. In case you need to add the city or the state as a way to differentiate the publications, they should be added into brackets, separated by coma and space characters, with the city ordered as a first item. For the state, you should use the abbreviated code usually used in the country rather than the full name. For instance, in the USA: The Examiner (Colombus, OH) |
adsML / GWG Property Mapping |
adsml-at:Publication |
Ad-ID Mapping |
-- |
PRISM Mapping |
prism:publicationName |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No, prism:publicationName is used |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:Publication>Lucky</adsml-at:Publication> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at::Publication rdf:resource= ”http://www.LuckyMagazine.com/”/>
Model #2 <adsml-at:Publication>Lucky</adsml-at:Publication> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Publisher |
Identifier |
adsml-at:Publisher |
Definition |
The company name of the publisher where the ad has been booked. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
gwg-at:destination |
Ad-ID Mapping |
-- |
PRISM Mapping |
dc:publisher |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No, dc:publisher is used |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:Publication>Lucky</adsml-at:Publication> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at::Publication rdf:resource= ”http://www.LuckyMagazine.com/”/>
Model #2 <adsml-at:Publication>Lucky</adsml-at:Publication> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Publisher Country |
Identifier |
adsml-at:PublisherCountry |
Definition |
The code of the country in which the publisher is based. The value is recorded as an ISO 3166 two letter code. This is used to identify the publishing company and may be different to the country where the publication is distributed. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:PublisherCountry |
Ad-ID Mapping |
-- |
PRISM Mapping |
-- |
Required by ADAM |
Yes |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
Enumerated String (ISO 3166 two letter code) |
Attributes |
None |
Example |
<adsml-at:PublisherCountry>DE</adsml-at:PublisherCountry> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at::Publication rdf:resource= ”http://www.ISO.org/3166/#Germany/”/>
Model #2 <adsml-at:PublisherCountry>DE</adsml-at:PublisherCountry> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Remarks |
Identifier |
adsml-at:Remarks |
Description |
Additional, non-binding, information about the order. |
Occurrence |
Occurs 0 or 1 time |
Content Model |
String |
adsML / GWG Property Mapping |
adsml-at:Remarks |
Ad-ID Mapping |
remarks |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:Remarks>No changes expected.</adsml-at:Remarks> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:Remarks rdf:resource= ”http://www.kraft.com/bookingHM11KR124T.htm”/>
Model #2 <adsml-at:Remarks>No changes expected.</adsml-at:Remarks> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Publication Section |
Identifier |
adsml-at:Section |
Definition |
Name of the publication where the ad will appear. A section is a logical subdivision of a publication, which helps to identify the general target audience. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:Section |
Ad-ID Mapping |
-- |
PRISM Mapping |
prism:section |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
No, prism:section is used |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:Section>Fashion</adsml-at:Section> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
None |
Examples |
Model #1 <adsml-at:Section rdf:resource= ”http://www.LuckyMagazine.com/Fashion”/>
Model #2 <adsml-at:Section>Lucky</adsml-at:Section> |
Profile #3 (XMP) |
|
Property Value |
Text |
Name |
Booking ID |
Identifier |
adsml-at:SellerPlacementID |
Definition |
A unique reference number for the booking. This is not a required element as the booking identifier might not be known when the ad is delivered from the supplier to the publisher. |
Occurrence |
Occurs 0 or 1 time |
Comment: |
|
adsML / GWG Property Mapping |
adsml-at:SellerPlacementID |
Ad-ID Mapping |
Booking ID |
Required by ADAM |
No |
Included in PAM |
No |
Included in PSV |
Yes |
Profile #1 (XML) |
|
Element Content |
String |
Attributes |
None |
Example |
<adsml-at:SellerPlacementID>ABC88779</adsml-at:SellerPlacementID> |
Profile #2 (RDF) |
|
Model #1 |
|
Element Content |
URI Reference (empty element) |
Attributes |
Resource Reference (rdf:resource) |
Model #2 |
|
Element Content |
Plain Literal |
Attributes |
none |
Examples |
Model #1 <adsml-at:SellerPlacementID rdf:resource= ”http://www.kraft.com/bookingHM11KR124T.htm”/>
Model #2 <adsml-at:SellerPlacementID>HM11KR124T</adsml-at:SellerPlacementID> |
Profile #3 (XMP) |
|
Property Value |
Text |