0% found this document useful (0 votes)

18 views310 pages

Ms A Powerpoint

Uploaded by

Miguel Alvarado

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

18 views310 pages

Ms A Powerpoint

Uploaded by

Miguel Alvarado

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PPT, PDF, TXT or read online on Scribd

You are on page 1/ 310

Metadata Standards and

Applications
Introduction:
Background, Goals,
and Course Outline
Version 2.1, February 2009

2
Cataloging for the 21st
Century
Background for this course:
 The first of five courses developed as part
of:
 Bibliographic Control of Web Resources: A
Library of Congress Action Plan
 Action Item 5.3: Continuing Education (CE)
 Continuing Education Implementation Group
(CEIG)
 See course Bibliography for citations

3
Cataloging for the 21st Century:
The five CE course components
 1. Rules and Tools for Cataloging Internet
resources
 2. Metadata Standards and Applications
 3. Principles of Controlled Vocabulary and
Thesaurus Design
 4. Metadata and Digital Library Development
 5. Digital Project Planning and Management
Basics

4
Cataloging for the 21st Century:
CE Course Series Objectives
 To equip catalogers to deal with new types of resources and
to recognize their unique characteristics
 To equip catalogers to evaluate competing approaches to and
standards for providing access to resources
 To equip catalogers to think creatively and work
collaboratively with others inside and outside their home
institutions
 To ensure that catalogers have a broad enough understanding
of the current environment to be able to make their local
efforts compatible and interoperable with other efforts
 To prepare catalogers to be comfortable with ambiguity and
being less than perfect
 To enable practicing catalogers to put themselves into the
emerging digital information environment and to continue to
play a significant role in shaping library services
5
Goals for this Course

 Understand similarities and differences between

traditional and digital libraries
 Explore different types and functions of metadata
(administrative, descriptive, technical, etc.)
 Understand metadata standards: schemas, data content
standards, and data value standards
 Learn how various metadata standards are applied in
digital projects, including use of application profiles
 Understand how different controlled vocabularies are
used in digital libraries
 Approaches to metadata creation, storage and retrieval
 Learn about metadata interoperability and quality issues

6
Course objectives
 Increase catalogers’ understanding of metadata for
digital resources
 Evaluate competing approaches and standards for
managing and providing access to resources
 Enable catalogers to think creatively and work
collaboratively
 Increase understanding of current environment to
allow for compatibility among applications
 Increase flexibility in utilizing different kinds of
metadata standards
 Allow catalogers to use expertise to contribute to
the emerging digital information environment

7
Outline of this course
 Session 1. Introduction to Digital Libraries
and Metadata

 Session 2. Descriptive Metadata

Standards
 Data content standards, data value
standards, data structure standards
 Specific descriptive metadata formats
 Relationship models

8
Outline of this course cont.
 Session 3. Technical and Administrative
Metadata Standards

 Session 4. Metadata Syntaxes and

Containers

 Session 5. Application Profiles and how

they are used in digital libraries

9
Outline of this course cont.
 Session 6. Controlled Vocabularies

 Session 7. Metadata Creation, Storage

and Retrieval

 Session 8. Metadata Interoperability and

Quality Issues

10
1. Introduction to Digital
Libraries and Metadata

Metadata Standards and

Applications Workshop
Goals of Session

 Understand similarities and

differences between traditional and
digital libraries focusing on
metadata

 Explore different types and functions

of metadata (descriptive,
administrative, structural, etc.)

2
Traditional vs. Digital
Libraries

Traditional library characteristics

Digital library characteristics?

3
What is a digital library?

 a library in which collections are

stored in digital formats and
accessed by computers. The digital
content may be stored locally, or
accessed remotely via computer
networks.
 a type of information retrieval
system.
4
Digital Library Federation
(DLF)
 “Digital libraries are organizations that
provide the resources, including the
specialized staff, to select, structure, offer
intellectual access to, interpret, distribute,
preserve the integrity of, and ensure the
persistence over time of collections of
digital works so that they are readily and
economically available for use by a defined
community or set of communities.”
 http://www.diglib.org/

5
http://www.worlddigitallibrary.org/project/english/index.html
How does the environment
affect the creation of
metadata?

8
Traditional Libraries

 Firm commitment to standards

 Specifications for metadata content (e.g.,
AACR2)
 Specifications for metadata encoding (e.g.,
MARC)
 A variety of syntaxes can be used
 Agreements on quality expectations
 Tradition of sharing, facilitated by bibliographic
utilities
 Available documentation and training
9
Digital Libraries
 No dominant content standard
 A variety of “formats” (or “schemas” or “element
sets”)
 Some emerging “federated” agreements, mostly
in the world of digital libraries attached to
traditional libraries
 Variable quality expectations
 Emerging basis for sharing (OAI-PMH)
 Some documentation and training is becoming
available
10
Environmental Factors

 Differences:
 Players: New world of metadata not
necessarily led by librarians
 Goals: Competition for users critical for
sustainability
 Resources: No real basis for understanding
non-technical needs (including metadata
creation and maintenance)
 Many levels of content responsibility (or none)
11
Environmental Factors

 Similarities
 It’s about discovery (and access, and use and
meeting user needs)
 Pressure for fast, cheap and “good enough”
(also rich, scalable, and re-usable--is that a
contradiction?)
 Wide variety of materials and services
 Maintenance needs often overlooked

12
What IS Metadata?

 Some possibilities:
 Data about data (or data about resources)
 Structured information that describes,
explains, locates, and otherwise makes it
easier to retrieve and use an information
resource.”
 A management tool
 Computer-processible, human-interpretable
information about digital and non-digital
objects

13
“In moving from dispersed digital collections to
interoperable digital libraries, the most important
activity we need to focus on is standards… most
important is the wide variety of metadata standards
[including] descriptive metadata… administrative
metadata…, structural metadata, and terms and
conditions metadata…”
Howard Besser, NYU

14
Metadata standards in digital
libraries
 Interoperability and object exchange requires the use of
established standards
 Many digital objects are complex and are comprised of
multiple files
 XML is the de-facto standard syntax for metadata descriptions
on the Internet
 Complex digital objects require many more forms of metadata
than analog for their management and use
 Descriptive
 Administrative
 Technical
 Digital provenance/events
 Rights/Terms and conditions
 Structural

15
Functions of Metadata

Discover Manage Control IP

resources documents Rights

Identify Certify Indicate

versions authenticity status

Mark content Situate Describe

structure geospatially processes

16
Types of metadata

 Descriptive
 Administrative
 Technical
 Digital provenance
 Rights/Access
 Preservation
 Structural
 Meta-metadata
 Other?

17
Cataloging and Metadata

 Cataloging early form of descriptive

metadata
 Underlying models for cataloging based on
AACR2 and MARC 21
 Some new metadata models are emerging
(e.g, DC Abstract Model and RDA in
development)
 Most metadata models roughly based on
attribute/value pairs:
 <property> = <value>

18
Some differences between
traditional and digital libraries
 Metadata only vs. actual object
 Need to understand Web technologies
 Types of media
 Granularity
 User needs
 Web services
 Digitized vs. born digital
Slide by Brian Surratt
19
One BIG Difference ...

 Catalogers most often are attempting to fit new

items into an already existing world of
materials--
 The structure already exists, as do the rules for
describing

 Metadata practitioners are generally working

with aggregated “stuff,” attempting to find a
way to make it accessible
 Involves broad understanding, ability to work
with others to make decisions that work for whole
projects or domains
20
*Thanks to Marty Kurth for these insights
Questions to ask when selecting
metadata standards
 What type of material will be digitized?
 How rich does the metadata need to be?
 Is there information already available?
 Is there a Community of practice developed for this
resource type(s)?
 What is the purpose of digital project?
 Who will be the audience and how will they use the content?
 Are there pre-existing digital projects with which this one
needs to function? Is there a need to interact with any
existing records?
 What tools or systems options are available?

21
Exercise

 Examine the digital library sites below, and be

prepared to discuss differences in user
approach and experience. Look for how
metadata is used.
 Alsos: Digital Library for Nuclear Issues (http://
alsos.wlu.edu/default.aspx)
 CSUN Oviatt Library: Digital Collections (http://
library.csun.edu/Collections/SCA/digicoll.html)
 Birdsource (http://www.birdsource.org/)

22
2. Specific metadata
standards: descriptive
Metadata Standards and
Applications Workshop
Session 2 Objectives

 Understand the categories of descriptive

metadata standards (e.g., data content
standards vs. data value standards)
 Learn about the various descriptive
metadata standards and the community
that developed and use them
 Learn about some relationship models
used in descriptive metadata standards

2
Outline of Session 2:
descriptive metadata
 Types of descriptive metadata standards
(e.g. element sets, content standards)

 Specific descriptive metadata standards

(e.g. MARC, DC, MODS, EAD…)

 Relationship models

3
Descriptive metadata

 Most standardized and well understood

type of metadata
 Major focus of library catalog
 Increased number of descriptive
metadata standards for different needs
and communities
 Importance for resource discovery
 May support various user tasks

4
Aspects of descriptive
metadata
 Data content standards (e.g., rules: AACR2R/RDA,
CCO)
 Data value standards (e.g., values/controlled
vocabularies: LCNAF, LCSH, MeSH, AAT)
 Data structure standards (e.g., formats/schemes:
DC, MODS, MARC 21)
 Set of semantic properties, in this context used to
describe resource
 Data exchange/syntax standards (e.g. MARC 21
(ISO 2709), MARCXML, DC/RDF or DC/XML)
 The structural wrapping around the semantics
 Relationship models

5
Content Standards: Rules

 AACR2 functions as the content standard for traditional

cataloging
 RDA (Resource Description and Access) is the
successor to AACR2 that aspires to be independent of a
particular syntax
 DACS (Describing Archives: a Content Standard)
 CCO (Cataloging Cultural Objects) new standard
developed by visual arts and cultural heritage
community
 CSDGM (Content Standards for Digital Geospatial
Metadata)
 Best practices, Guidelines, policies-- less formal content
standards

6
Content Standards: Value
Standards/Controlled
Vocabularies
 Examples of thesauri
 Library of Congress Subject Headings
 Art and Architecture Thesaurus
 Thesaurus of Geographical Names

 Examples of value lists

 ISO 639-2 Language codes
 MARC Geographic Area codes
 Other enumerated lists (e.g. MARC/008 lists)
 Dublin Core Resource Types

7
Data structure standards
(element sets and formats)
 Facilitates database creation and record retrieval
 Flexibility because not tied to a particular syntax
 May provide a minimum of agreed upon
elements that facilitate record sharing and
minimal consistency
 Different user communities develop their own
standard data element sets
 May differ in complexity and granularity of fields
 Some data element sets become
formats/schemes by adding rules such as
repeatability, controlled vocabularies used, etc.

8
Data Structure Standards:
Examples

 MARC 21 (http://www.loc.gov/marc/)
/marc/

 Dublin Core (http://dublincore.org)

dublincore.org

 MODS (www.loc.gov/standards/mods/)
 IEEE-LOM (http://ltsc.ieee.org/wg12/)
http://ltsc.ieee.org/wg12/

 ONIX (http://www.editeur.org/onix.html)
 EAD (http://www.loc.gov/ead/)
9
Data Structure Standards:
Examples, cont.

 VRA Core (
http://www.vraweb.org/projects/vracore4/)

 PBCore (http://www.pbcore.org/)

 TEI (http://www.tei-c.org/index.xml)

10
What is MARC 21?

 A syntax defined by an international standard and

was developed in the late 60s
 As a syntax it has 2 expressions:
 Classic MARC (MARC 2709)
 MARCXML
 A data element set defined by content designation
and semantics
 Institutions do not store “MARC 21”, as it is a
communications format
 Many data elements are defined by external
content rules; a common misperception is that it is
tied to AACR2

11
02158cam 2200349Ia
450000100130000000300060001300500170001900600190003600600190005500700150007400800
41000890400020001300200015001500430021001650490009001862450119001952460025
003142600065003395380030004045060038004345360153004725200764006255050094013895000
086014836000049015696500040016186510039016586510023016977000026017208560050017469
94001201796ocm56835268 OCoLC20060118051017.0m d szx w s 0 2cr mn---------
041028m20049999vau st 000 0 eng d aVA@cVA@dOCLCQ a0813922917 an-us---an-us-va
aVA@@04aThe Dolley Madison digital editionh[electronic resource] :bletters 1788-June 1836 /
cedited by Holly C. Shulman. 1iAlso known as:aDMDE aCharlottesville, Va. :bUniversity of Virginia
Press,c2004- aMode of access: Internet. aSubscription required for access. aRotunda editions are
made possible by generous grants from the Andrew W. Mellon Foundation and the President's Office
of the University of Virginia. aDolley Payne Madison was the most important First Lady of the
nineteenth century. The DMDE will be the first-ever complete edition of all of her known
correspondence, gathered in an XML-based archive. It will ultimately include close to 2,500 letters.
From the scattered correspondence were gathered letters that have never been previously published.
The range and scope of the collection makes this edition an important scholarly contribution to the
literature of the early republic, women's history, and the institution of the First Lady. These letters
present Dolley Madison's trials and triumphs and make it possible to gain admittance to her mind and
her private emotions and to understand the importance of her role as the national capital's First
Lady.0 aGeneral introduction -- Biographical introduction -- Introduction to the digital edition. aTitle
from the opening screen; description based on the display of Oct. 21, 2004.10aMadison,
Dolley,d1768-1849vCorrespondence. 0aPresidents' spouseszUnited States. 0aUnited
StatesxHistoryy1801-1809. 0aVirginiaxHistory.1 aShulman, Holly Cowan.40
uhttp://rotunda.upress.virginia.edu:8100/dmde/ aC0bVA@

12
MARC 21 Scope
 Bibliographic Data
 books, serials, computer files, maps, music, visual
materials, mixed material
 Authority Data
 names, titles, name/title combinations, subjects, series
 Holdings Data
 physical holdings, digital access, location
 Classification Data
 classification numbers, associated captions, hierarchies
 Community Information
 events, programs, services, people, organizations

13
MARC 21 implementation
 National formats were once common and there
were different flavors of MARC
 Now most have harmonized with MARC 21 (e.g.
CANMARC, UKMARC, MAB)
 Billions of records world wide
 Integrated library systems that support MARC
bibliographic, authority and holdings format
 Wide sharing of records for 30+ years
 OCLC is a major source of MARC records

14
Streamlining MARC 21
into the future
 Take advantage of XML
 Establish standard MARC 21 in an XML structure
 Take advantage of freely available XML tools
 Develop simpler (but compatible) alternatives
 MODS
 Allow for interoperability with different XML
metadata schemas
 Assemble coordinated set of tools
 Provide continuity with current data
 Provide flexible transition options

15
MARC 21 evolution to XML

16
MARC 21 in XML – MARCXML

 MARCXML record
 XML exact equivalent of MARC (2709) record
 Lossless/roundtrip conversion to/from MARC
21 record
 Simple flexible XML schema, no need to
change when MARC 21 changes
 Presentations using XML stylesheets
 LC provides converters (open source)
 http://www.loc.gov/standards/marcxml

17
Example: MARC and
MARCXML

 Music record in MARC

 Music record in MARCXML

18
What is MODS?

 Metadata Object Description Schema

 An XML descriptive metadata standard
 A derivative of MARC
 Uses language based tags
 Contains a subset of MARC data elements
 Repackages elements to eliminate redundancies
 MODS does not assume the use of any specific
rules for description
 Element set is particularly applicable to digital
resources
19
MODS high-level elements
 Title Info  Note
 Name  Subject
 Type of resource  Classification
 Genre  Related item
 Origin Info  Identifier
 Language  Location
 Physical description  Access conditions
 Abstract  Part
 Table of contents  Extension
 Target audience  Record Info

20
Advantages of MODS

 Element set is compatible with existing

descriptions in large library databases
 Element set is richer than Dublin Core but
simpler than full MARC
 Language tags are more user-friendly than
MARC numeric tags
 Hierarchy allows for rich description, especially
of complex digital objects
 Rich description that works well with hierarchical
METS objects

21
Uses of MODS
 Extension schema to METS
 Rich description works well with hierarchical METS
objects
 To represent metadata for harvesting (OAI)
 Language based tags are more user friendly
 As a specified XML format for SRU
 As a core element set for convergence
between MARC and non-MARC XML
descriptions
 For original resource description in XML syntax
that is simpler than full MARC

22
Example: MODS

 Music record in MODS

23
Status of MODS

 Open listserv collaboration of possible

implementers, LC coordinated (1st half 2002)
 First comment and use period: 2nd half 2002
 Now in MODS version 3.3
 Companion for authority metadata (MADS) in
version 1.0
 Endorsed as METS extension schema for descMD
 Many expose records as MODS in OAI
 MODS Editorial Committee being formed

24
A selection of MODS projects
 LC uses of MODS
 LC web archives
 Digital library METS projects
 University of Chicago Library
 Chopin early editions
 Finding aid discovery
 Digital Library Federation Aquifer initiative
 National Library of Australia
 MusicAustralia: MODS as exchange format between National
Library of Australia and ScreenSoundAustralia
 Australian national bibliographic database metadata project
 See: MODS Implementation registry
http://www.loc.gov/mods/registry.php

25
What is MADS?

 Metadata Authority Description Schema

 A companion to MODS for authority data using
XML
 Defines a subset of MARC authority elements
using language-based tags
 Elements have same definitions as equivalent
MODS
 Metadata about people, organizations, events,
subjects, time periods, genres, geographics,
occupations

26
MADS elements
 authority  note
 name  affiliation
 titleInfo
 url
 topic
 temporal
 identifier
 genre  fieldOfActivity
 geographic  extension
 hierarchicalGeographic
 recordInfo
 occupation
 related
 same subelements
 variant
 same subelements

27
Uses of MADS
 As an XML format for information about people,
organizations, titles, events, places, concepts
 To expose library metadata in authority files
 To allow for linking to an authoritative form
and fuller description of the entity from a
MODS record
 For a simpler authority record than full MARC 21
authorities
 To integrate bibliographic/authority information
for presentation

28
Example: MADS Name Record
<mads xsi:schemaLocation="http://www.loc.gov/mads/ http://www.loc.gov/mads/mads.xsd">
<authority>
<name type=“personal”>
<namePart>Smith,John</namePart>
<namePart type="date">1995-</namePart>
</name>
</authority>
<variant type="other">
<name>
<namePart>Smith, J</namePart>
</name>
</variant>
<variant type="other">
<name>
<namePart>Smith, John J</namePart>
</name>
</variant>
<note type="history">Biographical note about John Smith.</note>
<affiliation>
<organization>Lawrence Livermore Laboratory</organization>
<dateValid>1987</dateValid>
</affiliation>
</mads>

29
Example: MADS Organization Record

<mads xsi:schemaLocation="http://www.loc.gov/mads/
http://www.loc.gov/mads/mads.xsd">
<authority>
<name type=“corporate”>
<namePart>Unesco</namePart>
</name>
</authority>
<related type="parentOrg">
<name>
<namePart>United Nations</namePart>
</name>
</related>
<variant type="expansion">
<name>
<namePart>United Nations Educational, Cultural, and Scientific
Organization</namePart>
</name>
</variant>
</mads>

30
Some MADS implementations

 Irish Virtual Research Library and Ar

chive Repository Prototype
 Perseus Digital Library (Tufts)
 Mark Twain Papers (University of
California)
 Library of Congress/National Library
of Egypt

31
Dublin Core: Simple

 Simple to use
 All elements are optional/repeatable
 No order of elements prescribed
 Interdisciplinary/International
 Promotes semantic interoperability
 Controlled vocabulary values may be expressed,
but not the sources of the values

32
Dublin Core Elements

Fifteen elements in Simple DC

Title Creator Date

Description Contributor Coverage

Subject Publisher Identifier

Relation Rights Format

Source Coverage Type

33
“Qualified” Dublin Core

 Includes 15 terms of the original DC Metadata

Element Set, plus:
 Additional properties and sub-properties
 Examples: abstract, accessRights, audience,
instructionalMethod, rightsHolder, provenance
 Provides:
 A fuller set of properties with specific requirements for
content
 A namespace that includes all properties
 Explicit value vocabularies can be specified

34
DC Structure

 Property/element refinements are used at the

element level in DC/XML
 Relationships between properties and sub-properties
explicit in the formal representation
 Does not use XML “nesting” to express those
relationships
 Encoding schemes (Syntax & Vocabulary)
 Syntax ES: Essentially a datatype that communicates
the format or structure of a string
 Vocabulary ES: Includes values from an identified
controlled vocabulary or list

35
Advantages: Dublin Core

 International and cross-domain

 Developed via an open review process
 Increased efficiency of the discovery/retrieval of
digital objects
 Rich element set (qualified DC) provides a
framework of elements which will aid the
management of information
 Ease of mapping to other metadata standards
promotes collaboration of cultural/educational
information

36
Uses of Dublin Core

Minimal standard for OAI-PMH

Core element set in some other
schemas
Switching vocabulary for more
complex schemas

37
Ex.: Simple Dublin Core

<metadata>
<dc:title>3 Viennese arias: for soprano, obbligato clarinet in B flat, and
piano.</dc:title>
<dc:contributor>Lawson, Colin (Colin James)</dc:contributor>
<dc:contributor>Bononcini, Giovanni, 1670-1747.</dc:contributor>
<dc:contributor>Joseph I, Holy Roman Emperor, 1678-1711.</dc:contributor>
<dc:subject>Operas--Excerpts, Arranged--Scores and parts</dc:subject>
<dc:subject>Songs (High voice) with instrumental ensemble--Scores and
parts</dc:subject>
<dc:subject>M1506 .A14 1984</dc:subject>
<dc:subject></dc:subject>
<dc:subject></dc:subject>
<dc:date>1984</dc:date>
<dc:format>1 score (12 p.) + 2 parts ; 31 cm.</dc:format>
<dc:type>text</dc:type>
<dc:identifier>85753651</dc:identifier>
<dc:language>it</dc:language>
<dc:language>en</dc:language>
<dc:publisher>Nova Music</dc:publisher></metadata>
38
Ex.: Qualified Dublin Core

<metadata>
<dc:title xml:lang="en">3 Viennese arias: for soprano, obbligato clarinet in B flat,
and piano.</dc:title>
<dc:contributor>Lawson, Colin (Colin James)</dc:contributor>
<dc:contributor>Bononcini, Giovanni, 1670-1747.</dc:contributor>
<dc:contributor>Joseph I, Holy Roman Emperor, 1678-1711.</dc:contributor>
<dc:subject xsitype="LCSH">Operas--Excerpts, Arranged--Scores and
parts</dc:subject>
<dc:subject xsitype="LCSH">Songs (High voice) with instrumental ensemble--
Scores and parts</dc:subject>
<dc:subject xsitype="LCC">M1506 .A14 1984</dc:subject>
<dc:date xsitype="W3CDTF">1984</dc:date>
<dcterms:extent>1 score (12 p.) + 2 parts ; 31 cm.</dcterms:extent>
<dc:type xsitype="DCMIType">Sound</dc:type>
<dc:identifier>85753651</dc:identifier>
<dc:language xsitype="RFC3066">it</dc:language>
<dc:language xsitype="RFC3066">en</dc:language>
<dc:publisher>Nova Music</dc:publisher>
</metadata>
39
Status of DC

 Dublin Core Metadata Element Set version 1.1

 ISO Standard 15836-2003; ANSI/NISO Standard
Z39.85-2007; IETF RFC 5013
 Updated encoding guidelines
 Proposed recommendation for expressing DC
description sets using XML (Sept. 2008)
 Final recommendation for expressing DC metadata
using HTML/XHTML (Aug. 2008)

40
A selection of DC projects
 National Science Digital Library http://nsdl.org/
Aggregates a wide variety of source collections using
Dublin Core
 Kentuckiana Digital Library http://kdl.kyvl.org/
 For item level metadata, on DLXS software

 Gathering the Jewels http://www.gtj.org.uk/

 Website for Welsh cultural history using DC standards

 MusicBrainz http://musicbrainz.org/
 User-maintained community music recording
database; extension of DC

41
Encoded Archival
Description (EAD)
 Standard for electronic encoding of finding
aids for archival and manuscript collections
 Expressed as an SGML/XML DTD
 Supports archival descriptive practices and
standards
 Supports discovery, exchange and use of
data
 Developed and maintained by Society of
American Archivists; LC hosts the website

42
EAD, continued

 Based on the needs of the archival

community
 Good at describing blocks of information,
poor at providing granular information
 Some uptake by museum community
 Not a content standard
 EAC is a companion for information about
creators of archival material
 Example:
http://purl.dlib.indiana.edu/iudl/findingaids/
lilly/InU-Li-VAA1292
43
Benefits of an EAD finding aid

 Documents the interrelated descriptive

information of an archival finding aid
 Preserves the hierarchical relationships
existing between levels of description
 Represents descriptive information that is
inherited by one hierarchical level from
another
 Supports element-specific indexing and
retrieval of descriptive information

44
Text Encoding Initiative (TEI)
 Consortium of institutions and research
projects which collectively maintains and
develops guidelines for the representation of
texts in digital form.
 Includes representation of title pages,
chapter breaks, tables of contents, as well
as poetry, plays, charts, etc.
 The TEI file contains a “header” that holds
metadata about the digital file & about the
original source.
45
TEI
<fileDesc>
<titleStmt>
<title type="main">A chronicle of the conquest of
Granada</title>
<author>
<name type="last">Irving</name>
<name type="first">Washington</name>
<dateRange from="1783"
to="1859">1783-1859</dateRange>
</author>
</titleStmt>
<extent>455 kilobytes</extent>
<publicationStmt>
<publisher>University of Virginia Library</publisher>
<pubPlace>Charlottesville, Virginia</pubPlace>
<date value="2006">2006</date>
</publicationStmt>
<availability status="public">
<p n="copyright">Copyright © 2006 by the Rector and
Visitors of the University of Virginia</p>
<p n="access">Publicly accessible</p>
</availability> 46
MORE TEI
<sourceDesc>
<titleStmt>
<title type="main”>A chronicle of the conquest of
Granada</title>
<author>
<name type="last">Irving</name>
<name type="first">Washington</name>
<dateRange from="1783"
to="1859">1783-1859</dateRange>
</author>
</titleStmt>
<extent>345 p. ; 21 cm.</extent>
<publicationStmt>
<publisher>Carey, Lea & Carey</publisher>
<pubPlace>Philadelphia</pubPlace>
<date value="1829">1829</date>
<idno type="LC call number">DP122 .I7 1829a</idno>
<idno type="UVa Title Control Number">a1599744</idno>
</publicationStmt>
</sourceDesc> 47
Selection of TEI projects

 American Memory (uses a TEI-conformant DTD

 http://memory.loc.gov/ammem/index.html
 Early Canada Online
 http://www.canadiana.org/
 Victorian Women Writers Project
 http://www.indiana.edu/~letrs/vwwp/index.html
 Oxford Text Archive
 http://ota.ahds.ac.uk/

48
VRA Core
 Maintained by the Visual Resources Association.
Version 4 is currently in beta release.

 A categorical organization for the description of works

of visual culture
as well as the images
that document them.

 Consists of a metadata
element set and an
initial blueprint for
how those elements
can be hierarchically
structured.

credit: K. Edward Lay

49
Work, Collection or Image

 work, collection or  relation

image  rights
 agent  source
 culturalContext  stateEdition
 date  stylePeriod
 description  subject
 inscription  technique
 location  textRef
 Material  title
 Measurements  workType

50
Advantages of VRA

 Allows description of original and

digital object
 Level of granularity greater than
Dublin Core, less than MARC and
supports specific discipline
 Now content rules have been
developed (CCO)

51
VRA Core
<work>
<titleSet>
<title pref="true” source=“LC NAF”>Rotunda</title>
</titleSet>
<agentSet><agent>
<name type="personal“ vocab=“LC NAF” refid= “n 79089957”>
Jefferson, Thomas</name>
<dates type="life">
<earliestDate>1743</earliestDate><latestDate>1826</latestDate>
</dates>
<role>architect</role>
<culture>American</culture>
</agent></agentSet>
<agentSet><agent>
<name type="personal“ vocab=“LC NAF” refid= “n 50020242”>
White, Stanford</name>
<dates type="life">
<earliestDate>1853</earliestDate><latestDate>1906</latestDate>
</dates>
<role>architect</role>
<culture>American</culture>
<notes>Architect of 1896-1897 renovation</notes>
</agent></agentSet>
52
<dateSet>
More VRA Core
<date type="construction">
<earliestDate>1822</earliestDate><latestDate>1826</latestDate>
</date>
<notes>Construction begun October, 1822, completed September, 1826.<notes>
</dateSet>
<dateSet>
<date type=“destruction">
<earliestDate>1895</earliestDate>
</date>
<notes>Burned October 27, 1895.</notes>
</dateSet>
<dateSet>
<date type=“renovation">
<earliestDate>1896</earliestDate><latestDate>1897</latestDate>
</date>
<notes>Rebuilt to designs of Stanford White, 1896-1897.</notes>
</dateSet>
<locationSet><location type="site">
<name type="geographic" vocab="TGN" refid="2002201">
Charlottesville, Virginia</name>
</location></locationSet>
</work>
53
More VRA Core
<image>
<titleSet>
<title type="descriptive">general view</title>
</titleSet>
<agentSet><agent>
<name type="personal“ vocab=“LC NAF”
refid=“n 82111472”>Lay, K. Edward</name>
<culture>American</culture>
<role>photographer</role>
</agent></agentSet>
<dateSet><date type=“creation">
<earliestDate>1990</earliestDate> credit: K. Edward Lay
<latestDate>2000</latestDate>
</date></dateSet>
<locationSet><location type="repository">
<name type="corporate">University of Virginia Library</name>
<name type="geographic" vocab="TGN" refid="2002201">
Charlottesville</name>
</location></locationSet>
<rightsSet>
<rights type=“credit”>K. Edward Lay</rights>
<rights type=“access”>Publicly accessible</rights>
</rightsSet>
</image> 54
More VRA Core
<image>
<titleSet>
<title type="descriptive">View from gymnasia</title>
</titleSet>
<agentSet><agent>
<name type="personal“ vocab=“LC NAF”
refid=“n 82111472”>Lay, K. Edward</name>
<culture>American</culture>
<role>photographer</role>
</agent></agentSet>
<dateSet><date type=“creation">
<earliestDate>1995</earliestDate>
<latestDate>2000</latestDate>
</date></dateSet> credit: K. Edward Lay

<locationSet><location type="repository">
<name type="corporate">University of Virginia Library</name>
<name type="geographic" vocab="TGN" refid="2002201">
Charlottesville</name>
</location></locationSet>
<rightsSet>
<rights type=“credit”>K. Edward Lay</rights>
<rights type=“access”>Publicly accessible</rights>
</rightsSet>
</image> 55
A Selection of VRA Core
Projects
 Luna Imaging
 http://www.lunaimaging.com/index.html
 ARTstor
 http://www.artstor.org/
 Visual Information Access (VIA), Harvard
University Libraries
 http://via.lib.harvard.edu/via/

56
Learning Object Metadata (LOM)

 An array of related standards for description of

‘learning objects’ or ‘learning resources’
 Most based on efforts of the IEEE LTSC
(Institute of Electrical and Electronics Engineers
Learning Technology Standards Committee) and
the IMS Global Learning Consortium, inc.
 Tends to be very complex with few
implementations outside of government and
industry
 One well-documented implementation is
CanCore
57
Uses of IEEE-LOM

 Describe and share information about

learning objects individually or as a group
 Export as LOM in XML or RDF
 Most descriptive elements mapped to
Dublin Core
 Can be used with the IMS VDEX
(Vocabulary Definition Exchange)

58
A Selection of IEEE-LOM
Projects
 CanCore
 http://www.cancore.ca/
 LearnAlberta.ca
 http://www.learnalberta.ca/
 Grades K-12
 Learning Object Repository Network
 http://lorn.flexiblelearning.net.au/Home.aspx

59
What is ONIX for Books?

 Originally devised to simplify the provision of

book product information to online retailers
(name stood for ONline Information eXchange)
 First version flat XML, second version included
hierarchy and elements repeated within
‘composites’
 Maintained by Editeur, with the the Book
Industry Study Group (New York) and Book
Industry Communication (London)
 Includes marketing and shipping oriented
information: book jacket blurb and photos, full
size and weight info, etc.

60
Advantages of ONIX

 Provides publisher information in a widely used

standard format
 Promotes exchange of information with
publishers, vendors, book sellers, libraries
 “Value-added” information (ex., book jacket
images, reviews) benefits book sellers (online
commercial sites) and libraries (online catalogs)
 More [information], faster [transmission],
cheaper? better?

61
A selection of ONIX projects

 http://www.editeur.org/onix.html
 ONIX Administrators
 EDItEUR (European & international)
 Book Industry Communication (BIC) (European and
international)
 Book Industry Study Group, Inc. (BISG) (U.S.)
 Amazon.com
 Association of American Publishers
 Baker & Taylor
 Barnes & Noble
 Google
 McGraw-Hill Companies

62
PBCore

 Public Broadcasting Core element

set
 http://www.pbcore.org/
 Built on Dublin Core (but does not
comply with the Abstract Model)
 Provides a shared descriptive
language for public broadcasters
 Used for television, radio, Web
activities
63
PBCore Elements

 53 elements arranged in 15 containers

and 3 sub-containers
 Four classes:
 Intellectual Content (title, subject, description,
audienceLevel …)
 Intellectual Property (creator, contributor, publisher,
rightsSummary)
 Instantiation (dateCreated, formatFileSize,
formatDuration, formatTracks, language)
 Extensions

64
Uses of PBCore

 Shared descriptive language for public

broadcasters
 Useful for both public search and viewing,
and internal asset management
 Facilitates production collaborations
 Ability to parse programs into short
segments for Web distribution, niche
community needs

65
Selection of PBCore
projects
 Wisconsin Public Television (WPT)
Media Library Online
http://wptmedialibrary.wpt.org/
 Kentucky Educational Television
(KET) http://www.ket.org/
 New Jersey Network (NJN)
http://www.njn.net/

66
Modeling metadata: why
use models?
 To understand what entities you are
dealing with
 To understand what metadata are
relevant to which entities
 To understand relationships between
different entities
 To organize your metadata to make
it more predictable (and be able to
use automated tools)
67
Descriptive metadata
models
 Conceptual models for bibliographic and authority
data
 Functional Requirements for Bibliographic Records
(FRBR)
 Functional Requirement for Authority Data (FRAD)
 Dublin Core Abstract Model (DCAM)
 Some other models:
 CIDOC Conceptual Reference Model (emerged from museum
community)
 INDECS (for intellectual property rights)
 There are many conceptual models intended for
different purposes

68
Bibliographic relationships
(pre-FRBR)
 Tillett’s Taxonomy (1987)
 Equivalence

 Derivative

 Descriptive

 Whole-part

 Accompanying

 Sequential

 Shared-characteristic

69
Bibliographic relationships in
MARC/MODS
 MARC Linking entry fields
 MARC relationships by specific
encoding format
 Authority vs bibliographic vs holdings
 MODS relationships
 relatedItem types
 Relationship to METS document

70
FRBR (1996)

 IFLA Study Group on the Functional

Requirements for Bibliographic Records
 Focused on the bibliographic record rather
than the catalog
 Used an entity relationship model, rather
than descriptive analysis without a
structural model
 Broader in scope than previous studies

71
FRBR Entities

 Bibliographic entities: works,

expressions, manifestations, items
 Responsible parties: persons,
corporate bodies
 Subject entities: concepts, objects,
events, places

72
Group 1 Entities and Relationships

An Expression Work A Work

“realizes”
A Work “Is realized through”
An Expression

Expression An Expression
A Manifestation
“embodies” “Is embodied in”
An Expression A Manifestation

Manifestation
An Item
“exemplifies” A Manifestation
A Manifestation “Is exemplified by”
An Item
Item

[Thanks to Sherry Vellucci for this slide.] 73

DC Abstract Model
 Reaffirms the One-to-One Principle
 Defines ‘statement’ as the atomic level
 Distinguishes between “description” and
“description set”:
 Description: “A description is made up of one or
more statements about one, and only one,
resource.”
 Description Set: “A description set is a set of one
or more descriptions about one or more resources.”
 RDA vocabularies being developed to use the
DC Abstract Model

74
is instantiated record
as

is grouped
into
description A record consists of descriptions,
set
using properties and values.
description
description
description A value can be a string or a pointer
to another description.
has one statement
or more statement
statement
has one property

has one value string

value is a
OR
is represented
by one or more representation
representation rich value
representation
is a OR

is a related
description
75
Basic model: Resource with properties

A Play has the title “Antony and Cleopatra,” was written in 1606
by William Shakespeare, and is about “Roman history”
76
… related to other Resources

77
An Exercise

Each group will be given a printout of

a digital object
Create a brief metadata record based
on the standard assigned to your
group
Take notes about the issues and
decisions made
Appoint a spokesperson to present
the metadata record created & the
issues involved (5-10 minutes)
78
3. Technical and
administrative metadata
standards
Metadata Standards and
Applications Workshop
Goals of session

 To understand the different types of

administrative metadata standards
 To learn what types of metadata are
needed for digital preservation
 To learn the importance of technical,
structural and rights metadata in
digital libraries

2
Types of administrative
metadata
 Provides information to help manage a resource
 Preservation metadata

 Technical characteristics
 Information about actions on an object
 Structural metadata may be considered
administrative; indicates how compound
objects are put together
 Rights metadata

 Access rights and restrictions

 Preservation rights and restrictions

3
PREMIS: introduction

 Preservation metadata that includes

subcategories:
 Technical metadata
 Relationships (structural and
derivative)
 Digital provenance (what actions
performed on objects)
 Rights

4
Preservation metadata
includes: Preservation
Metadata
 Provenance:
 Who has had custody/ownership of the
Content
digital object?

 Authenticity:
10 years on
 Is the digital object what it purports to be?

 Preservation Activity: 50 years on

 What has been done to preserve it?

Forever!
 Technical Environment:
 What is needed to render and use it?

 Rights Management:
 What IPR must be observed?

 Makes digital objects self-documenting across time

5
PREMIS Data Dictionary

 May 2005:
Data Dictionary for Preservation Metadata:
Final Report of the PREMIS Working Group
 237-page report includes:
 PREMIS Data Dictionary 1.0
 Accompanying report
 Special topics, glossary, usage examples
 Data Dictionary: comprehensive, practical resource for
implementing preservation metadata in digital archiving systems
 Used Framework as starting point
 Detailed description of metadata elements
 Guidelines to support implementation, use, management
 Based on deep pool of institutional experiences in setting up and
managing operational capacity for digital preservation
 Set of XML schema developed to support use of Data Dictionary
6
Scope of data dictionary

 Implementation independent
 Descriptive metadata out of scope
 Technical metadata applying to all or
most format types
 Media or hardware details are limited
 Business rules are essential for working
repositories, but not covered
 Rights information for preservation
actions, not access

7
What PREMIS is and is not
 What PREMIS is:
 Common data model for organizing/thinking about
preservation metadata
 Guidance for local implementations
 Standard for exchanging information packages between
repositories
 What PREMIS is not:
 Out-of-the-box solution: need to instantiate as metadata
elements in repository system
 All needed metadata: excludes business rules, format-
specific technical metadata, descriptive metadata for
access, non-core preservation metadata
 Lifecycle management of objects outside repository
 Rights management: limited to permissions regarding
actions taken within repository 8
PREMIS Data Model

Intellectual
Entities
Rights
Statements

Objects Agents

Events

9
Types of information covered in
PREMIS (by entity type)
 Object  Event
 Event ID
 Object ID  Event type
 Preservation level
 Event date/time
 Object characteristics  Event outcomes
(format, size, etc.)  Linking identifiers
 Storage  Agent
 Environment
 Agent ID
 Agent name
 Digital signatures
 Rights
 Relationships  Rights statement
 Linking identifiers  Granting agent
 Permission granted

10
PREMIS Maintenance Activity

Permanent Web presence,

hosted by Library of Congress

Centralized destination for

information, announcements,
and other PREMIS-related
resources

Discussion list for PREMIS

implementers (PIG list)

Coordinate future revisions of Data Dictionary and XML schema

Editorial committee guides development and revisions

http://www.loc.gov/standards/premis/ 11
Current activities
 PREMIS Implementers’ Registry
 http://www.loc.gov/standards/premis/premis-registry.htm
l
 Revision of data dictionary and schemas (March
2008)
 Guidelines for use of PREMIS within METS have
been developed
 PREMIS tutorials
 One or one and a half day tutorials have been
given in several locations: Glasgow, Boston,
Stockholm, Albuquerque, Washington, San Diego, Berlin
 Training materials available from LC
12
Why is PREMIS important to
catalogers?
 As we take responsibility for more digital
materials, we need to ensure that they can be
used in the future
 Most preservation metadata will be generated
from the object, but catalogers may need to
verify its accuracy
 Catalogers may need to play a role in assessing
and organizing digital materials
 Understanding the structure of complex digital objects
 Determining significant properties that need to be
preserved

13
Technical metadata for
images
 NISO Z39.87 and MIX
 Adobe and XMP
 Exif
 IPTC (International Press
Telecommunications Council)/XMP
 Some of these deal with embedded
metadata in images

14
Metadata For Images in
XML (MIX)
 An XML Schema designed for expressing
technical metadata for digital still images
 Based on the NISO Z39.87 Data
Dictionary – Technical Metadata for
Digital Still Images
 Can be used standalone or as an
extension schema with METS/PREMIS

15
Using MIX
 Includes
 Characteristics that apply to all or most object types,
e.g. size, format (elements also in PREMIS)
 Format specific metadata for images
 Some examples of format specific metadata
elements in MIX:
 Image width
 Color space, color profile
 Scanner metadata
 Digital camera settings
 Most well developed of format specific technical
metadata standards

16
Technical metadata for
textual objects
 textMD is an XML Schema designed for
expressing technical metadata for textual
objects
 Developed at New York University;
maintenance transferred to LC
 Includes format specific technical
metadata for text, e.g.
 byte order
 character set encoding
 font script

17
Technical metadata for
audio and video
 Not as well developed as other technical metadata
 Complexities of file formats requires expertise to
develop these
 LC developed XML technical metadata schemas in
2003/2004 for LC Audiovisual Prototype Project
used with METS; these were widely implemented
because of the lack of other schemas
 Audio and video technical metadata schemas under
development by expert organizations
 Moving Image Catalog (MIC) project is also
experimenting with these

18
Technical metadata for
multimedia (MPEG-7)
 A multimedia content description standard,
associated with the content itself
 Intended to allow fast and efficient searching
 Formally called Multimedia Content
Description Interface
 Does not deal with the actual encoding of
moving pictures and audio (as MPEG-1, MPEG-2
and MPEG-4 do)
 intended to provide complementary functionality
to the previous MPEG standards

19
Structural metadata

 Supports the intended presentation and use and

navigation of an object
 Binds the parts together; expresses relationships
between parts of a multipart object
 Examples of structural metadata expressions:
 METS structMap
 PREMIS relationship elements
 EAD hierarchical structure

20
Rights metadata

 Rights schemas with limited scope

 Rights Expression Languages (REL) for
managing intellectual property rights,
particularly by rights owners
 Rights information is not well understood
 Different laws in different jurisdictions
 Machine actionable vs. human understandable
 Rights take different forms
 legal statutes, e.g. copyright
 contractual rights, e.g. licenses

21
Rights schemas with limited
scope
 METS Rights
 Access rights for use with METS objects
 Rights declarations
 Rights holder
 Context
 CDL copyright schema
 Specifically copyrights, not other intellectual property
rights
 Information you need to know to assess copyright
status (e.g. creators, rights holders, dates, jurisdiction)
 Note that a new field 542 has been added to MARC 21
with information about copyright to help the cataloger
assess the status of the item (based on the CDL work)

22
Rights schemas with limited
scope cont.
 PREMIS Rights
 Focused on rights for preservation rather than access
 Revision of PREMIS data dictionary expanded this area
 Allows for extensibility, i.e. inserting another rights
schema
 Creative commons
 Allows creators to choose a license for their work
 Simple rights statements that fit a lot of situations
 http://creativecommons.org/
 An example: MIC catalog

23
Rights metadata for specific
object types
 PLUS for images
 MPEG-21 REL for moving images,
etc.
 ONIX for licensing terms
 Full Rights Expression Languages
 XRML/MPEG 21
 ODRL

24
Exercise

 Provide administrative/technical
metadata for the object used in the
descriptive metadata exercise

25
4. Metadata syntaxes and
containers
Metadata Standards and
Applications Workshop
Goals of session

 Understand syntaxes used for

encoding information, including
HTML, XML and RDF
 Discover how container formats are
used for managing digital resources
and their metadata

2
Overview of Syntaxes

 HTML, XHTML: Hypertext Markup

Language; eXtensible Hypertext
Markup Language
 XML: Extensible Markup Language
 RDF/XML: Resource Description
Framework

3
HTML

 HyperText Markup Language

 HTML 4 is the current standard
 HTML is an SGML (Standard Generalized Markup
Language) application conforming to
International Standard ISO 8879
 Widely regarded as the standard publishing
language of the World Wide Web
 HTML addressed the problem of SGML
complexity by specifying a small set of structural
and semantic tags suitable for authoring
relatively simple documents
4
XHTML

 XML-ized version of HTML 4.0, tightens up

HTML to match XML syntax
 Requires ending tags, quoted attributes, lower
case, etc., to conform to XML requirements

 XHTML is a W3C specification, redefining HTML

as an XML implementation, rather than an
SGML implementation
 Imposes requirements that are intended to lead
to more well-formed, valid XML, easier for
browsers to handle
5
<link rel="schema.DC" href="http://purl.org/dc/elements/1.1/" /> An XHTML
<link rel="schema.DCTERMS" href="http://purl.org/dc/terms/" /> Example
<meta name="DC.title" content="Using Dublin Core" />
<meta name="DC.creator" content="Diane Hillmann" />
<meta name="DC.subject" content="documents; Bibliography; Model; meta; Glossary; mark; matching;
refinements; XHTML; Controlled; Qualifiers; Hillmann; mixing; encoding; Diane; Issues; Appendix; elements;
Simple; Special; element; trademark/service; DCMI; Dublin; pages; Section; Resource; Grammatical; Qualified;
XML; Using; Principles; Documents; licensing; OCLC; formal; Usageguide; Roles; Implementing; Contents;
Guidelines; Expressing; Table; Syntax; Content; Element; DC.dot; Home; document; Metadata; RDF/XML;
Website; metadata; privacy; schemes; liability; profiles; Elements; Copyright; Localization; schemas;
HTML/XHTML; Core; Guide; registry; Research; contact; Scope; Projects; languages; Maintenance; Application;
available; Internationalization; HTML; Recommended; link; Purpose; Abstract; AskDCMI; Vocabularies; software;
Storage; Introduction" />
<meta name="DC.description" content="This document is intended as an entry point for users of Dublin Core. For
non-specialists, it will assist them in creating simple descriptive records for information resources (for example,
electronic documents). Specialists may find the document a useful point of reference to the documentation of
Dublin Core, as it changes and grows." />
<meta name="DC.publisher" content="Dublin Core Metadata Initiative" />
<meta name="DC.type" scheme="DCTERMS.DCMIType" content="Text" />
<meta name="DC.format" content="text/html" />
<meta name="DC.format" content="31250 bytes" />
<meta name="DC.identifier" scheme="DCTERMS.URI" content="http://dublincore.org/documents/usageguide/" />

6
XML

 Extensible Markup Language

 A ‘metamarkup’ language: has no fixed
tags or elements
 Strict grammar imposes structure
designed to be read by machines
 Two levels of conformance:
 well-formed--conforms to general grammar rules
 valid--conforms to particular XML schema or DTD
(document type definition)

7
XML: Extensible Markup
Language
 A technical approach to convey meaning with data
 Not a natural language, although uses natural languages
 < 姓名 >Louis Armstrong</ 姓名 >
 <name>Louis Armstrong</name>
 Not a programming language
 Language in the sense of:
 A limited set of tags defines the elements that can be
used to markup data
 The set of tags and their relationships need to be
explicitly defined (e.g., in XML schema)
 We can build software that uses XML as input and
processes them in a meaningful way
 You can define your own markups and schemas
8
XML is the lingua franca of
the Web
 Web pages increasingly use at least XHTML
 Business use for data exchange/ messaging
 Family of technologies can be leveraged
 XML Schema, XSLT, XPath, and XQuery

 Software tools widely available (open source)

 Storage, editing, parsing, validating,
transforming and publishing XML
 Microsoft Office 2003 supports XML as document
format (WordML and ExcelML)
 Web 2.0 applications based on XML (AJAX,
Semantic Web, Web Services, etc.) 9
An XML Schema may
define:
 What elements may be used
 Of which types
 Any attributes
 In which order
 Optional or compulsory
 Repeatability
 Subelements
 Logic

10
Anatomy of an XML Record

 XML declaration--prepares the processor to work

with the document and states the XML version
 Namespaces (uses xmlns:prefix and a URI to attach
a prefix to each element and attribute)
 Distinguishes between elements and attributes from
different vocabularies that might share a name (but
not necessarily a definition) using association with
URIs
 Groups all related elements from an application so
software can deal with them
 The URIs are the standardized bit, not the prefix, and
they don’t necessarily lead anywhere useful, even if
they look like URLs
11
XML Namespaces

XML Namespace Namespace Identifier

xmlns:dc=”http://purl.org/dc/elements/1.1/”

Namespace Prefix

12
XML Anatomy Lesson

Name Attribute Content

<mods:genre authority=“marcgt”>bibliography /</mods:genre>

Start Tag End Tag

13
XML Validation

XML Instance Valid

Validator

Invalid
XML Schema

14
XML Schema Example
<xs:element name="software" minOccurs="0"
maxOccurs="unbounded">
<xs:complexType>
<xs:sequence>
<xs:element name="swName" minOccurs="1"
maxOccurs="1" type="xs:string"></xs:element>
<xs:element name="swVersion" minOccurs="0"
maxOccurs="1" type="xs:string"></xs:element>
<xs:element name="swType" minOccurs="1"
maxOccurs="1" type="xs:string"></xs:element>
<xs:element name="swOtherInformation"
minOccurs="0" maxOccurs="unbounded" type="xs:string">
</xs:element>
<xs:element name="swDependency"
minOccurs="0" maxOccurs="unbounded" type="xs:string">
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
15
Will the following XML
instance validate?
<software>
<swName>Windows</swName>
<swVersion>2000</swVersion>
<swType>Operating System</swType>
</software>

How about this?

16
Resource Description
Framework
 A language for describing resources on the Web
 Structure based on “triples”
 Designed to be read by computers, not humans
 An ontology language to support semantic interoperability
—understanding meanings
 Considered an essential part of the Semantic Web
 Can be expressed using XML
Predicate
Subject Object

http://www.w3.org/RDF

17
Some RDF Concepts

 A Resource is anything you want to

describe
 A Class is a category; it is a set that
comprises individuals
 A Property is a Resource that has a
name, such as "creator" or "homepage"
 A Property value is the value of a
Property, such as “Barack Obama" or
"http://dublincore.org" (note that a
property value can be another resource)
18
RDF Statements

 The combination of a Resource, a Property,

and a Property value forms a Statement
(known also as the subject, predicate and object
of a Statement), also known as “triples”
 An example Statement: "The editor of
http://dublincore.org/documents/usageguide/ is
Diane Hillmann"
http://dublincore.org/documents/usageguide/
The subject of the statement above is:

 The predicate is: editor

 The object is: Diane Hillmann
19
RDF and OWL

 RDF does not have the language to

specify all relationships
 Web Ontology Language (OWL) can
specify richer relationships, such as
equivalence, inverse, unique
 RDF and OWL may be used together
 RDFS: a syntax for expressing
relationships between elements

20
An RDF/XML Example

<rdf:RDF
xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
xmlns:dc="http://purl.org/dc/elements/1.1/">
<rdf:Description rdf:about="http://www.dlib.org">
<dc:title>D-Lib Program - Research in Digital Libraries</dc:title>
<dc:description>The D-Lib program supports the community of people
with research interests in digital libraries and electronic
publishing.</dc:description>
<dc:publisher>Corporation For National Research Initiatives</dc:publisher>
<dc:date>1995-01-07</dc:date>
<dc:subject>
Note
<rdf:Bag> unordered list
<rdf:li>Research; statistical methods</rdf:li>
<rdf:li>Education, research, related topics</rdf:li>
<rdf:li>Library use Studies</rdf:li>
</rdf:Bag>
</dc:subject>
<dc:type>World Wide Web Home Page</dc:type>
<dc:format>text/html</dc:format>
<dc:language>en</dc:language>
</rdf:Description>
</rdf:RDF>

21
Overview of container formats

 A container format is needed to package

together all forms of metadata and digital
content
 Use of a container is compatible with and an
implementation of the OAIS information
package concept
 METS: packages metadata with objects or
links to objects and defines structural
relationships
 MPEG 21 DID: represents digital objects using
a flexible and expressive model
22
Metadata Encoding &
Transmission Standard (METS)

 Developed by the Digital Library Federation,

maintained by the Library of Congress
 “... an XML document format for encoding metadata
necessary for both management of digital library
objects within a repository and exchange of such
objects between repositories (or between repositories
and their users).”
 Records the (possibly hierarchical) structure of digital
objects, the names and locations of the files that
comprise those objects, and the associated metadata

http://www.loc.gov/standards/mets/

23
METS Usage

 To package metadata with digital object in

XML syntax
 For retrieving, storing, preserving, serving
resource
 For interchange of digital objects with
metadata
 As information package in a digital
repository (may be a unit of storage or a
transmission format)

24
Characteristics of METS

 Open non-proprietary standard

 Extensible
 Modular
 Developed by the digital library
community

25
METS Sections

Defined in METS schema for navigation & browsing

1. Header (XML Namespaces)
2. File inventory,
3. Structural Map & Links
4. Descriptive Metadata (not part of METS but uses
an externally developed descriptive metadata
standard, e.g. MODS)
5. Administrative Metadata (points to external
schemas):
1. Technical, Source
2. Digital Provenance
3. Rights

26
The structure of a METS file

METS
fileSec file inventory