A System of Organization

KANSAS CITY

Jim Powers, Elena Bonjour,Kelly Hangauer,

Lynn Winebrenner

Missouri Wine Trails - There are ten in the stateThis schema could be

used for any of the

Missouri Wine

Trails, or even to

organize wines in

any region in North

or South America.

What is the Kansas City Wine Trail?The Kansas City Wine Trail is a partnership between nine

wineries spanning from Kansas City to Waverly, Missouri (about 70 miles east of Kansas City.)

Amigoni Urban Winery

Arcadian Moon Vineyards & Winery

Albonee Country Inn & Winery

Stonehaus Farms

Odessa Country Winery

LaBella Vineyards & Winery

Fahrmeier Family Vineyards

Terre Beau Winery

Baltimore Bend Winery

Why do we need an organizational schema for wine?

?

What will an organizational schema for the Kansas City Wine Trail accomplish?

1. Make it easier for people who want to

drink local wines to find one that they like

2. Restaurants could use it to pair local

wines with the dishes they serve

3. The wineries in the Kansas City Wine Trail

could use it to promote their wines and

winery tours

Attributes of wine used as descriptorsColor (red, white, blush)

Style (Cab, Merlot, Chardonnay, Shiraz)

Sweetness (dry, off-dry, dessert)

Acidity (tart, crisp, soft)

Tannin (astringent, firm, soft)

Body (light, medium, full)

Flavor attributes (fruity, earthy, spicy, herbal, citrus, and many more...)

Other fruit used, if any

DU B

L I NC O R E

Dublin Core

Managed by the Dublin Core Metadata Initiative (DCMI), Dublin Core is international in scope:

The DCMI, Ltd is headquartered in Singapore. The DCMI website (dublincore.org) is hosted by the

National Library of Korea. The DC Metadata Registry is hosted by the Research Center for

Knowledge Communities at the University Of Tsukuba, Japan

Dublin Core (DC) is a

metadata schema for

description of digital and

physical resources:

books, maps, artwork,

and wine bottles.

Originally created for

describing electronic

resources, it now

encompasses the

description of electronic,

print, and conceptual

resources

Why Dublin Core?The purpose of Dublin Core is to make information on the Web searchable.

It uses simple vocabularies to find, identify, and use the resources.

ELEMENTS

Simple Dublin Core consists of 15 elements for describing resources:

Creator

Contributor

Publisher

Title

Date

Language

Format

Subject

Description

Identifier

Relation

Source

Type

Coverage

Rights

About The Elements...

All elements are optional and repeatable. There is no set order of the elements.

The elements can be organized by:

Content: Type, Title, Subject, Source, Description, Coverage, and Relation

Intellectual Property: Creator, Contributor, Publisher, and Rights

Application: Language, Format, Date, and Identifier

The Dublin Core standard works well with other schemas

Qualified Dublin core

added 3 more elements

● Audience

● Provenance

● RightsHolder

Extensibility

Dublin Core is designed to be small but extensible.

It can be used with a wide range of vocabularies (scheme=LCSH).

New elements can be added to suit a particular resource.

Element

Price $$

Coverage (type=spatial) (scheme=TGN)

Waverly (Lafayette County, Missouri, United States)

Flexibility Dublin core is highly flexible.

Each element in Dublin Core can be modified by a qualifier

Qualifiers either refine (type) or encode elements (scheme)

Relation (type=PartOf) (Identifier=URL) http://www.kcwineries.com/winetrail.html

Relation (type=hasPart) Norton grape

Coverage (type=spatial) (scheme=TGN) Waverly, Missouri

Interoperability

Dublin Core is a fundamental metadata schema, widely used with libraries, archives, and the Internet.

There are four

levels of

interoperability

to Dublin Core.

Our schema

coordinates with

Level 1 and Level 2.

Level 1: Shared language and definitions - standard vocabulary

Level 2: Properties and classes of Dublin Core Metadata Terms are used to coordinate with Linked Data on the web. Linked Data helps establish relationships between content on the Web and is used by major search engines.

Elements of Our Schema● Color● Title/Wine Name● Source/Winery● Creator/Winery OR Name of Wine Makers● Subject (scheme=LCSH)● Description● Date (type=created)/Date bottled● Format (type=medium● Sweetness● Price● Relation (type=isPartOf) (identifier = URL)● Relation (type=hasPart)/Specific grape varieties● Coverage (type=spatial) (scheme=TGN)● Acidity● Body● Flavor Attributes● Type (must use DCMI Type Vocabulary)

Sample of the Schema

Color Red White Red White

Title/Wine Name 2012 Norton Reserve 2014 Chardonel 2011 Rose Red Sauvignon Blanc

Source/Winery Baltimore Bend Vineyard Baltimore Bend Vineyard Stonehaus Farms Winery Amigoni Urban Winery

Creator/Winery OR Name of Wine Makers

Baltimore Bend Vineyard Baltimore Bend Vineyard Stonehaus Farms Winery Amigoni Urban Winery

Subject (scheme=LCSH) Wine, Wine and wine making--United States

Wine, Wine and wine making--United States

Wine, Wine and wine making--United States

Wine, Wine and wine making--United States

Description Aged in French oak, this full bodied red is made from Norton grapes that hung on the vine longer producing lower acids and higher sugars. Norton is the same grape as Cynthiana

Barrel fermented, sur lies style wine. Dry white. Aged on French oak for 8 months

Cold fermented and pairs well with fruit, sandwiches, cheeses and light pastas

Crisp and dry with hints of citrus nose.Starts with hint of grapefruit when tasted and finishes with pineapple taste. Light wine, great paired with food. Aged in oak barrell

Date (type=created)/Date bottled

2012 2014 2011 2015

Searching With The Schema...

Users can search for a specific element, among them:

● Color● Style● Sweetness

The schema will show wines that have that element.

The Kansas City Wine Trail makes nearly 100 varieties, too many to select from the list manually.

100 bottles of wine on the wall...

>100

Search one or more elements: color, body, sweetness, etc.

The ones you might like

Questions and concernsMore elements, such as flavor attributes, can be added, but too many is inadvisable. If you are too flexible the schema loses its interoperability.

REFERENCES

Baca, M., Harpring, P., Ward, J., & Beechcroft, A. (Eds.). (2014). Metadata standards crosswalk. [PDF document].

Retrieved from http://www.getty.edu/research/publications/electronic_publications/intrometadata/crosswalks.html

Boehmer, A. & Comet, R. (2009). Wine basics: A complete illustrated guide to understanding, selecting and enjoying

wine. Guilford, CT: Knack.

DCMI Metadata Basics. (n.d.) Retrieved on July 02, 2016 from http://dublincore.org/metadata-basics/

Dublin Core. (2005) Retrieved on July 24, 2016 from https://www.w3.org/wiki/DublinCore

Garcia- Penalvo, F. J., Merlo Vega, J. A., Ferreras- Fernandez, T., Casaus- Pena, A., Albas Aso, L., & Atienza

Diaz, M.L. (2010). Qualified Dublin Core metadata: Best practices for GREDOS. Journal of library

metadata, 10(1), 13-36 doi: 10.1080/19386380903546976

REFERENCES continuedHillmann, D. I. (2000). Using Dublin Core. Retrieved from http://dublincore.org/documents/2000/07/16/usageguide/

Hillmann, D.I. (2005). Using Dublin Core: The elements. Retrieved from

http://dublincore.org/documents/usageguide/elements.shtml

KC Wine Trail. Retrieved from http://kcwineries.com/

Lubas, R., Jackson, A., Schneider, I. (2013). The metadata manual: A practical workbook.

Oxford, UK: Chandos Publishing

McCarthy, E. & Ewing-Mulligan, M. (2003). Wine for dummies, 3rd edition. Hoboken, NJ: Wiley Publishing.

National Information Standards Organization. (2008). Building a metadata schema - where to start. Retrieved from

http://www.niso.org/apps/group_public/document.php?document_id=5271&wg_abbrev=tc46sc11interest