W3C W3C Member Submission

PRISM Recipe 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/
Author:
Dianne Kennedy (Idealliance)

Abstract

This PRISM Recipe Specification defines metadata elements in the PRISM Specification to define content describing recipes; contains 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:

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/3.0/PRISM_Recipe_Metadata_3.0.pdf

or

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

1.3    Version History

Version Number

Release Date

Editor

Description

1.0 Draft A

06/21/2011

Kennedy

Recipe Metadata Namespace Specification

1.0 Draft B

07/06/2011

Kennedy

Recipe Metadata Namespace Specification

1.0 Draft C

10/19/2011

Kennedy

Recipe Metadata Namespace Specification

3.0 Draft

12/15/2011

Kennedy

PRISM Recipe Metadata Specification

3.0 Final

96/12/2012

Kennedy

PRISM Recipe Metadata 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.2    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.3    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.4    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.5    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.6    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.7    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.8    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] 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.9    PRISM Source Vocabulary Specifications

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.10 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.11 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.12 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.13 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.14 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.


3    Introduction

3.1    Purpose and Scope

The purpose of this document, the PRISM Recipe Metadata Specification [PRISMRMS], is to describe the basic metadata elements that the PRISM Working Group has defined and included in the PRISM Recipe Metadata Namespace. All sections of this document are normative.

3.2    New in this Version

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

3.3    Related Documentation

3.3.1           Guide to PRISM Recipe Metadata and XML Encoding

This guideline document, Guide to PRISM Recipe Metadata and XML Encoding [RECIPEGUIDE], describes how to apply the full range of metadata fields to recipes to facilitate the management of the recipes from creation to use, to archive, aggregation and reuse of recipes.

3.3.2           Controlled Vocabularies for Recipe Metadata Fields

Recipe metadata fields are documented in this specification.  Values for the recipe metadata fields are documented in the The PRISM Controlled Vocabularies Specification [PRISMCVS] Version 3.0.

4    PRISM Recipe Metadata

4.1    prm: Namespace

The PRISM specification defines numerous namespaces. The “prm:” namespace (http://prismstandard.org/namespaces/prm/3.0) describes the elements that are included within PRISM for the description of recipes including nutritional information.  The recipe metadata fields for the prm: namespace are documented in Section 5 of this document.

The recommended namespace for PRISM Recipe Metadata is:
xmlns:prm=”http://prismstandard.org/namespaces/prm/3.0/

4.2    Related Specifications

The PRISM Recipe Metadata Namespace Specification includes metadata elements and class semantics for recipes that have equivalents in the hRecipe microformat (http://microformats.org/wiki/hrecipe).  Note that the PRISM Recipe use cases are quite different from the use case for hRecipes. However, where possible, PRISM has adopted the hRecipe field and class names so that semantic connections can be made when PRISM recipes are posted on the Web.  The mapping to hRecipe is documented in the The Guide to PRISM Recipes [RECIPEGUIDE].

4.3    Additional Recipe Metadata Elements

Additional metadata elements from PRISM, Dublin Core and PRISM Usage Rights namespaces are also recommended for use with recipes.  The full metadata models recommended for images are documented in The Guide to Recipe Metadata and XML Encoding [RECIPEGUIDE].

5    PRISM Recipe Metadata Elements and Attribute Definitions

5.1    PRISM Element and Attribute Documentation Model

All three PRISM profiles are documented in this section. First Profile #1 is documented.

Note: Since delivering recipe metadata to aggregators is currently targeted to be within the scope of PAM, a “Yes” will be indicated for these elements.

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.

5.2    Element and Attribute Definitions

5.2.1           prm:cookingEquipment

Name

Cooking Equipment

Identifier

prm:cookingEquipment

Definition

Specifies the primary equipment used to prepare a recipe

Comment

This is an “open choice” field.  PRISM provides a starter “cooking equipment” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:cookingEquipment>Wok</prm:cookingEquipement>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain literal

Attributes

 

Examples

<prm:cookingEquipment>Wok</prm:cookingEquipement>

Profile #3 (XMP)

 

Property Value

open choice text; enumerations = Blender, Bread Machine, Broiler, Convection Oven, Deep Fryer, Fondue Pot, Food Processor, Freezer, Barbecue Grill, Grill Pan, Ice Cream Maker, Microwave Oven, Oven, Pressure Cooker, Rice Cooker, Sandwich Press / Panini Press, Slow Cooker, Waffle Maker , Wok

5.2.2           prm:cookingMethod

Name

Cooking Method

Identifier

prm:cookingMethod

Definition

Specifies the primary method by which this dish was prepared.

Comment

This is an “open choice” field.  PRISM provides a starter “cooking method” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:cookingMethod>Grill</prm:cookingMethod>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain literal

Attributes

 

Examples

<prm:cookingMethod>Grill</prm:cookingMethod>

Profile #3 (XMP)

 

Property Value

open choice text; enumerations = Can, Bake, Blend, Boil, Braise, Broil, Deep Fry, Fondue, Freeze, Fry, Grill/Barbecue, Marinate, Microwave, No-Cook, Roast, Press, Saute, Slow Cook, Steam, Stir-Fry

5.2.3           prm:course

Name

Course

Identifier

prm:course

Definition

A course is a part of a meal served at one time; does not include names of individual foods or dish types.

Comment

This is an “open choice” field.  PRISM provides a starter “course” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:course>Appetizer</prm:course >

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:course>Appetizer</prm:course >

Profile #3 (XMP)

 

Property Value

open choice text; enumerations = Appetizer, Salad Course, Main Course, Beverage, Side, Dessert

5.2.4           prm:cuisine

Name

Cuisine

Identifier

prm:cuisine

Definition

A characteristic style of cooking often associated with a culture or geographic region influenced by locally available ingredients, cultural traditions or religious food laws.

Comment

This is an “open choice” field.  PRISM provides a starter “cusine” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:cuisine>Asian</prm:cuisine>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:cuisine>Asian</prm:cuisine>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations= African, American, Asian, Austrian, Brazilian, British/Irish, Cajun/Creole, California, Caribbean, Central/South American, Chinese, Cuban, Eastern European, French, German, Greek, Hungarian, Halal, Indian, Italian, Japanese, Jewish/Kosher, Korean, Lebanese, Mediterranean, Mexican, Middle Eastern, Moroccan, Native American, New England, Pacific Northwest, Pacific Rim, Peruvian, Polish, Scandinavian, Southern, Southwest, Spanish, Swiss, Thai, Vegan, Vegetarian, Vietnamese

5.2.5           prm:dietaryNeeds

Name

Dietary Needs

Identifier

prm:dietaryNeeds

Definition

Specific dietary restrictions or requirements (medically, religiously or personally indicated or preferred) associated with a recipe.

Comment

This is an “open choice” field.  PRISM provides a starter “dietary needs” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:dietaryNeeds>High Fiber</prm:dietaryNeeds>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:dietaryNeeds>High Fiber</prm:dietaryNeeds>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations = Appetizer, Babyfood, Bean/Pea/Legume, Beverage Alcoholic, Beverage Non-alcoholic, Bread, Cake/Cupcakes, Candy, Casserole, Cheese, Cookie, Dairy, Dip/Spread, Egg, Fish/Shellfish, Food Gift, Frosting, Fruit, Gravy, Grill, Ice Cream/Sherbet, Jelly/Jam/Preserves, Marinade/Rub, Meat/Game, Muffin/Quick Bread, Nuts, Pasta, Pizza, Pickles/Relishes, Pies/Tarts/Pastries, Poultry, Puddings/Custards, Salad/Salad Dressing, Sandwich, Sauce/Condiment, Seafood, Smoothie, Spice/Herbs/Seasoning, Soup/Stew, Stir-Fry, Stuffing/Dressing, Vegetable

5.2.6           prm:dishType

Name

Dish Type

Identifier

prm:dishType

Definition

Indicates the type of dish represented by this recipe.

Comment

This is an “open choice” field.  PRISM provides a starter “dish type” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:dishType>Meat/Game</prm:dishType>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:dishType>Meat/Game</prm:dishType>

Profile #3 (XMP)

 

Property Value

open choice text; enumerations = appetizer, babyfood, beanPeaLegume, beverageAlcoholic, beverageNonalcoholic, bread, cakeOrCupcakes, candy, casserole, cheese, cookie, dairy, dipOrSpread, egg, fishShellfish, foodGift, frosting, fruit, gravy, grill, iceCreamOrSherbet, jellyJamPreserves, marinadeOrRub, meatOrGame, muffinQuickBread, nuts, pasta, pizza, picklesOrRelishes, piesTartsPastries, poultry, puddingsOrCustards, saladOrSaladDressing, sandwich, sauceOrCondiment, seafood, smoothie, spiceHerbsSeasonings, soupOrStew, stirFry, stuffingOrDressing, vegetable

5.2.7           prm:duration

Name

Duration

Identifier

prm:duration

Definition

Specifies the total time / duration required to prepare and serve a recipe.  Includes prep time, cooking time and any additional time that may be required.

Comment

This maps to duration in the hRecipe microformat

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

enumerations; horizontal, vertical

Attributes

None

Example

<prm:duration>60 minutes</prm:duration>

Profile #2 (RDF)

 

Model #1

 

Element Content

String

Attributes

 

Examples

<prm:duration>60 minutes</prm:duration>

Profile #3 (XMP)

 

Property Value

Text

5.2.8           prm:ingredientExclusion

Name

Ingredient Exclusion

Identifier

prm:ingredientExclusion

Definition

Indication of ingredients that have specifically been excluded from this recipe.  Relates to Dietary Needs.

Comment

This is an “open choice” field.  PRISM provides a starter “ingredient exclusion” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:ingredientExclusion>salt</prm:ingredientExclusion>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:ingredientExclusion>salt</prm:ingredientExclusion>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations = Alcohol, Dairy, Eggs, Fish, Meat, Nuts/Peanuts, Pork, Salt, Shellfish, Soy, Sugar, Wheat/Gluten

5.2.9           prm:mainIngredient

Name

Main Ingredient

Identifier

prm:mainIngredient

Definition

Specifies the main ingredient of the recipe.

Comment

This is an open text field and has no recommended CV

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:mainIngredient>Eggplant</prm:mainIngredient>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

<prm:mainIngredient>Eggplant</prm:mainIngredient>

Profile #3 (XMP)

 

Property Value

Text

5.2.10         prm:meal

Name

Meal

Identifier

prm:meal

Definition

Specifies the meal for which this recipe is prepared. A meal is an instance of eating, specifically one that takes place at a certain time.

Comment

This is an “open choice” field.  PRISM provides a starter “ingredient exclusion” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

Yes

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:meal>Lunch</prm:meal>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

None

Examples

Model #1

<prm:meal>Lunch</prm:meal>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations = Hors d’Oeuvres, Breakfast, Brunch, Buffet, Dinner, Lunch, Supper, Snack

5.2.11         prm:recipeEndingPage

Name

Recipe Ending Page

Identifier

prm:recipeEndingPage

Definition

Specifies the last page on which the recipe appeared in a print source document

Comment

 

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:recipeEndingPage>104</prm:recipeEndingPage>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

None

Examples

Model #1

<prm:recipeEndingPage>104</prm:recipeEndingPage>

Profile #3 (XMP)

 

Property Value

Text

5.2.12         prm:recipePageRange

Name

Recipe Page Range

Identifier

prm:recipePageRange

Definition

Specifies the page range on which the recipe appeared in a print source document

Comment

Page range is a string. Sequential pages are to be separated with a dash. Nonsequential pages are to be separated with a comma.

Occurrence

Occurs 0 or 1 time

PAM

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:recipePageRange>102-104</prm:recipePageRange>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:recipePageRange>102-104</prm:recipePageRange>

Profile #3 (XMP)

 

Property Value

Text

5.2.13         prm:recipeSource

Name

Recipe Source

Identifier

prm:recipeSource

Definition

Specifies the original source for this recipe.

Comment

This is an “open choice” field.  PRISM provides a starter “recipe source” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:recipeSource>Magazine</prm:recipeSource>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:recipeSource>Magazine</prm:recipeSource>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations = TV Show, Chef, Restaurant, Magazine, Sponsors, Test Kitchen, Contest, Reader Submitted, Book, Online / Website, Client (a brand like Nestle or Kraft), Amateur, Celebrity

5.2.14         prm:recipeStartingingPage

Name

Recipe Startinging Page

Identifier

prm:recipeStartingPage

Definition

Specifies the first page on which the recipe appeared in a print source document

Comment

 

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:recipeStartingPage>102</prm:recipeStartingPage>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

None

Examples

Model #1

<prm:recipeStartingPage>102</prm:recipeStartingPage>

Profile #3 (XMP)

 

Property Value

Text

5.2.15         prm:recipeTitle

Name

Recipe Title

Identifier

prm:recipeTitle

Definition

Provides a formal title for the recipe

Comment

This element is a requirement for each recipe and serves as a primary identification for the recipe

This element maps to “fn” in hRecipe microformat

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:recipeTitle>Curried Butternut Squash</prm: recipeTitle>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:recipeTitle>Curried Butternut Squash</prm: recipeTitle>

Profile #3 (XMP)

 

Property Value

Text

5.2.16         prm:servingSize

Name

Serving Size

Identifier

prm:servingSize

Definition

Specifies the serving size for the recipe.

Comment

This field is required to help describe the yield of a recipe

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:servingSize>1 Cup</prm:servingSize >

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

None

Examples

Model #1

<prm:servingSize>1 Cup</prm:servingSize >

Profile #3 (XMP)

 

Property Value

Text

5.2.17         prm:skillLevel

Name

Skill Level

Identifier

prm:skillLeval

Definition

Specifies the skill level required to prepare the recipe

Comment

This is an “open choice” field.  PRISM provides a starter “skill level” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 or 1 time

PAM

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:skillLevel>Expert</prm: skillLevel>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:objectSubtype>coupe</prm:objectSubtype>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations= Children, Easy, Moderate, Expert

5.2.18         prm:specialOccasion

Name

Special Occasion

Identifier

prm:specialOccasion

Definition

Indicates a special occasion or event associated with this recipe.

Comment

This is an “open choice” field.  PRISM provides a starter “special occasion” controlled vocabulary.   The users may add their own values to this list.

Occurrence

Occurs 0 to many times

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:specialOccasion>car</prm:specialOccasion>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:objectType>car</prm:objectType>

Profile #3 (XMP)

 

Property Value

Open choice text; enumerations = Anniversary, Baby Shower, Barbeque, Bar Mitzvah / Bas Mitzvah, Birthday (Adult), Birthday (Child), Bridal Shower, Chinese New Year, Christmas Day, Christmas Eve, Cinco de Mayo, Cocktail Party, Cookie Swap, Dinner Party, Easter, Father's Day, Fondue Party, Fourth of July, Funeral/Wake, Graduation, Halloween, Hanukkah, Kwanzaa, Labor Day, Mardi Gras, Memorial Day, New Years' Day, New Years’ Eve, Oscars, Passover, Picnic/Cookout, Pot-Luck, Ramadan, Rosh Hashanah, St. Patrick's Day, Super Bowl, Tailgating, Thanksgiving, Valentine's Day, Yom Kippur, Wedding, Winter Holiday Party

5.2.19         prm:yield

Name

Yield

Identifier

prm:yield

Definition

Specifies the yield of the recipe in terms of servings as indicated by serving size

Comment

This maps to yield in the hRecipe microformat

Occurrence

Occurs 0 or 1 time

Included in PAM?

No

Included in PSV?

Yes

Profile #1 (XML)

 

Model #1

 

Element Content

String

Attributes

None

Example

<prm:yield>4 servings</prm:yield>

Profile #2 (RDF)

 

Model #1

 

Element Content

Plain Literal

Attributes

 

Examples

Model #1

<prm:yield>4 servings</prm:yield>

Profile #3 (XMP)

 

Property Value

Text