GEORGIA INSTITUTE OF TECHNOLOGY G. Agnew & J.Hudgins April 6, 2000 DIGITAL VIDEO METADATA Data or...

GEORGIA INSTITUTE OF TECHNOLOGY

G. Agnew & J.Hudgins

April 6, 2000

DIGITAL VIDEO METADATADIGITAL VIDEO METADATA

“Data or information which help us perform one or more of the following functions with respect to data and information resources:

Finding

Interpreting/evaluating

Accessing

Analyzing

Managing

Preserving”

Metadata Definition and Rationale:

Boyko, Ernie. “Statistical Metadata: A User Perspective.” Open Forum on Metadata Registries. January 20, 2000.

April 6, 2000

SIMPLIFIED METADATA REPOSITORY DESIGN:

Record

Design

Database

Design

Data Element

Registration

Database

Population

DISSEMINATION

TO USERS

DISSEMINATION TO OTHER

REPOSITORIES

April 6, 2000

METADATA MAY BE:

Intrinsic: Incorporated within information object

Extrinsic: Located in a separate metadatabase with fielded link to information object

April 6, 2000

Grace Agnew1/15/2000

Georgia Instituteof Technology

I nges t

Arc hival S tora ge

Da ta Mana geme ntDI

S IP Ac cess a nd

Dissemination

Requests

Other info

MODEL: Functional Component Model for an OAIS

CCSDS 650.0-R-1: Reference Model for an Open Archival Information System (OAIS). RedBook. Issue 1. May 1999. PDF.Available at: http://ssdoo.gsfc.nasa.gov/nost/isoas/overview.html

April 6, 2000

RECORD DESIGNRECORD DESIGN

April 6, 2000

A METADATA SCHEMA SHOULD:A METADATA SCHEMA SHOULD:

Precisely define the information object.

Find the right information

Be flexible, scalable, extensible

Continued viability, as new formats come along; as creators and users change; as repositories are redesigned.

April 6, 2000

• Interoperate with other metadata repositories

Enable Data Sharing

• Be Machine-interpretable; Machine-creatable.

For automatic metadata generation and automated data management

A METADATA SCHEMA A METADATA SCHEMA SHOULD:SHOULD:

April 6, 2000

METADATA SCHEMA INCLUDES:METADATA SCHEMA INCLUDES:

Three Types of Metadata (Digital Library Federation Architecture Committee)

Descriptive: Discovery and Identification of Information

Structural: Display and Navigation of Information.

Administrative: Management and Preservation of Information

April 6, 2000

WEBKEYWORDS

DIGITAL VIDEO RESPOSITORY

DIGITIZED LECTURES

KEYWORDS

LIBRARY:

Books, JournalsMARC Metadata Format

DESCRIPTIVEDESCRIPTIVE

April 6, 2000

WEBKEYWORDS

DIGITAL VIDEO RESPOSITORY

DIGITIZED LECTURES

KEYWORDS

LIBRARY:

Books, JournalsMARC Metadata Format

DUBLIN CORE

DESCRIPTIVEDESCRIPTIVE

FUTURE: MPEG7

April 6, 2000

Books, Articles, web sites by Jean Hudgins

Metadatabase - Dublin CoreRecord 1

DC.Creator Hudgins, Jean

Record 70

DC.Contributor. Hudgins, Jean.

Result Set:HUDGINS, JEAN…1999………………

HUDGINS, JEAN…1994……………...

SEARCH & RETRIEVALSEARCH & RETRIEVAL

April 6, 2000

BOOKS, ARTICLES, WEB SITES BY JEAN HUDGINS

DATABASE: Dublin Core

DC.Creator Hudgins, Jean.

DC.Contributor Hudgins, Jean

DATABASE: MARC

100 Hudgins, Jean.

700 Hudgins, Jean.

HARVESTED KEYWORD:

Jean Hudgins

April 6, 2000

DATA DISSEMINATIONDATA DISSEMINATION• Z39.50 - The End User

Information Retrieval (Z39.50): Application Service Definition and Protocol Specification: Client/Server - allows different databases and search engines to “talk”. Enabled for MARC, Dublin Core

• RDF - Resource Description Framework

Enables interoperability among metadata schemes, including the modular use of multiple schemes within a metadata record utilizing the XML namespace facility;

Adds machine-interpretable semantics to the encoding, exchange and reuse of structured metadata;

April 6, 2000

• XMI - End User or Repository Exchange

Open information interchange model for exchange of models and data over the Internet in a standardized manner. XML-based.

• CWMI - Repository Exchange

Common Warehouse Metadata Interchange -

Request for Proposal issued. OMG Document ad/98-09-02. Available from http://www.omg.org

Provide a generic mechanism that can be used to transfer warehouse metadata. Should be object-oriented (CORBA)

DATA DISSEMINATIONDATA DISSEMINATION

April 6, 2000

RECOMMENDATIONS:RECOMMENDATIONS:Dublin Core Descriptive Metadata Design

Follow recommendations of Dublin Core Working Groups;

Examine Usage of other Dublin Core communities:

CIMI, EdNA, CORC;

CrosswalkCrosswalk (map data elements) between Dublin Core and other metadata formats, esp. MARC & IMS

Adapt to descriptive needs of digital video and audio

April 6, 2000

RECOMMENDATIONS:RECOMMENDATIONS:

Display/Export Formats:

• Dublin Core

• Dublin Core / HTML

• Dublin Core /RDF

• MARC

• XML (create a DTD or DCD)

• IMS

Metadatabase Design

• ODBC

• CORBA

April 6, 2000

Content IntellectualProperty

Instantiation

Title Creator DateSubject Publisher TypeDescription Contributor FormatSource Rights IdentifierLanguageRelationCoverage

From “Description of Dublin Core Elements”http://purl.oclc.org/metadata/dublin_core_elements

April 6, 2000

GT DUBLIN CORE FOR AUDIO/VIDEO: GT DUBLIN CORE FOR AUDIO/VIDEO:

DESIGN STRATEGYDESIGN STRATEGY

• Support simple and qualified Dublin Core Fields

Ease of Application vs. Precision of Access

• Support Domain Interoperability

Crosswalk to MARC, EAD & IMS formats; Align with MPEG7; Incorporate available “best practices”

Use controlled (e.g. documented vocabularies)

April 6, 2000

BEYOND DUBLIN CORE:BEYOND DUBLIN CORE:

ADMINISTRATIVE METADATA:ADMINISTRATIVE METADATA:

• DIGITAL PERSISTENCE

• DIGITAL QUALITY EVALUATION

April 6, 2000

Digital Persistence:

technology emulation

recreate the technology needed to open and display

• migration path/backward compatibility

standards backward compatible one or more version to allow migration of data

• interpolation

technology interpolates to retrieve or enhance obsolete data

April 6, 2000

ADMINISTRATIVE METADATA

Can Include: Encoding Information

Encoding hardware:

Computer (make&model; processor and speed; RAM)

Video or Audio card

Encoding software/version

Editing software/version

April 6, 2000

ADMINISTRATIVE METADATA - SLIDE 2

Encoding Standard:

MPEG level of service

Vendor encoding profile

File-Specific Information:

Frame size (X x Y)

Frames per second

Color vs. Black & White

Color Pixel Depth (8-bit, 16-bit, 32-bit)

Data Rate

April 6, 2000

ADMINISTRATIVE METADATA - SLIDE 3

Audio channels (mono, stereo, Dolby, Surround Sound, etc.)

Audio bit depth (8 bit, 16-bit, etc. (could combine with channels)

Audio Rate (44 kHz, etc.)

Analog Creation hardware

Analog Input Device

Input Format

April 6, 2000

GT DUBLIN CORE FOR VIDEOGT DUBLIN CORE FOR VIDEO

SAMPLE RECORD:

Interview with Jimmy Carter, from the Georgia Tech Alumni Association’s Living History Collection--video interviews with prominent alumni.

Three non-consecutive video segments are merged using dissolve transitions into one QuickTime 4.0 digital video file

April 6, 2000

Dublin Core may be expressed in:

HTML (within META TAG)

XML/RDF (identifies source for controlled vocabularies)

April 6, 2000

TITLETITLE“A name by which the resource is formally known”

Simple: DC.Title

Qualified: DC.Title.Excerpt DC.Title.Sequence (Scene, Shot, Frame) D.C.Title.Main (GT will not use. DC.Title will be used for the main title) DC.Title.Alternative DC.Abbreviated DC.Title.Series DC.Title.Subtitle

April 6, 2000

CREATORCREATOR

“An entity primarily responsible for making the content of the resource”Simple: DC.Creator

Qualified: DC.Creator.Person DC.Creator.Organization DC.Creator.Event DC.Creator.Object

Optional Expanded Qualifiers: Controlled vocabularies to further define the Creator or Contributor role. MARC-Relator list preferred. AAT Agent Facets, in singular form, as secondary.

April 6, 2000

SUBJECTSUBJECT

“The topic of the resource”

Simple: DC.Subject (Keywords is the default--no need to use scheme)

Qualified: DC.Subject scheme =LCSH

DC.Subject scheme=Getty AAT

DC.Subject scheme=LCC

DC.Subject scheme=LCNAF

April 6, 2000

DESCRIPTIONDESCRIPTION“A textual description of the item and its contents”

Simple: DC.Description

Qualified: DC.Description.Content

DC.Description.Summary

April 6, 2000

PUBLISHERPUBLISHER“As entity responsible for making the resource available.”

Simple: DC.Publisher (name as it appears on the item)

Qualified: DC.Publisher.Place (place of publication (U.S. (city,state) Outside US: Country

April 6, 2000

DIGITAL VIDEO METADATADIGITAL VIDEO METADATACONTRIBUTORCONTRIBUTOR

““An entity responsible for making contributions to the content of the resource”

Simple: contributor

Qualified: contributor.person contributor.organization contributor.event contributor.object

Optional Expanded Qualifiers: Controlled vocabularies to further define the Creator or Contributor role. MARC-Relator list (1st choice) AAT Agent Facets, in singular (2nd)

April 6, 2000

DATEDATE

“A date associated with an event in the life cycle of the resource.”

Standard interpretation: date associated with creation or availability.

Format: ISO 8601 profile: http://www.w3.org/TR/NOTE-datetime YYYY-MM-DD

Simple: DC.Date

Qualified: DC.Date->Created DC.Date->Issued DC.Date->Accepted DC.Date->Acquired DC.Date->Available DC.Date->Valid DC.Date->DataGathered

April 6, 2000

Date - Slide 2Date - Slide 2

Date as used by GT conforms to the creation of the item (e.g. the digital file) in hand. Date is used in the DC.Coverage field to indicate date of the intellectual content, e.g. the date of the interview.

April 6, 2000

TYPETYPE

“The nature or genre of the content of the resource”

GT Practice: Image.Moving (recommended for MPEG7).

For videos with sound. If the sound has meaning independent of the visual image, a second field is used: Sound

Genre is added as an independent field since the concepts of “Nature” and “Genre” are independent.

Simple: DC.Type

April 6, 2000

FORMATFORMAT

“The physical or digital manifestation of the resource. Format may include the media-type or dimensions (size, duration) of the resource”

Simple: DC. Format

Media-type

Best practice - use MIME

GT will use separate fields for the independent concepts, “media-type” and “dimensions”. CIMI practice - use this field for any item that cannot be experienced without machine assistance. To be congruent with other DC implementations, GT will use DC.Format for media-type (MIME or MIME extension) and size/duration only. All other physical description information will appear in adminstrative metadata.

April 6, 2000

FORMAT - Slide 2FORMAT - Slide 2

Media-type

GT will use MIME, with the following extensions/extrapolations to MIME:

multipart/SMIL video/vnd.microsoft.avi video/vnd.quicktime video/mpeg1 video/mpeg2 video/mpeg4 video/vnd.miro.mjpeg video/vnd.real

Dimensions - size.

In bytes. Optional second field, in Mbytes or Kbytes

Dimensions - duration

hours:minutes:seconds

April 6, 2000

FORMAT - slide 3FORMAT - slide 3

“Format is used to identify the software and possibly hardware that might be needed to display or operate the resource”

Under Discussion to include in DC.Format fields:

frames per second

Data rate (Kbps/sec or Mbps/sec)<meta name = “DC.Format” scheme=“MIME” content=“video/vnd.quicktime”>

April 6, 2000

IDENTIFIERIDENTIFIER

“An unambiguous reference to the resource within a given context”

Best Practice: “string or number conforming to a formal identification system” (e.g. URI, PURL, URL)

Simple: DC.Identifier

GT Practice: URL. For excerpts, segments, sequences, scenes or shots, the URL will end with the start time code of the first element. If SMPTE is available, it will be used. Otherwise, the notation will be hh:mm:ss, as determined by the playback device (e.g. VTR) or editing software (e.g. Adobe Premiere).

April 6, 2000

SOURCESOURCE

“A reference to a resource from which the present resource is derived.”

Best Practice: “string or number conforming to a formal identification system” (e.g. URI, PURL, URL)

Simple: DC.Source

CIMI practice is to use source when there is a direct parent/child relationship. GT will use only for direct parent/child relationships, including one-to-one format correspondence. Since the entire Carter interview is not digitized, there is no exact “parent” so the field is not used. The VHS interview appears in the DC.Relation field instead

April 6, 2000

DIGITAL VIDEO METADATADIGITAL VIDEO METADATALANGUAGELANGUAGE

“A language of the intellectual content of the resource”

Best practice: use RFC1766--a two-digit language code (e.g. en) taken from the ISO 639 standard, followed optionally by the country (e.g. en-uk). GT will use the country extension, because speech indexing programs in the future may be pronunciation-based.

Simple: DC.Language

Qualified: DC.Language->Dubbed

DC.Language->Subtitled

(the above are proposed extensions by GT. No working group currently exists for implementation.)

April 6, 2000

RELATIONRELATION

“A reference to a related resource.” “An identifier of a second resource, and its relationship to the present resource.” Used to “reflect linkages” and “identify significant points in the hierarchy of surrogacy”

Best practice: “string or number conforming to a formal identification system” (e.g. URI, PURL, URL)

Simple: DC.Relation

April 6, 2000

DIGITAL VIDEO METADATADIGITAL VIDEO METADATARELATION - slide 2RELATION - slide 2

Qualified:

DC.Relation->IsPartOf DC.Relation->HasPart (physical or logical)

C.Relation->IsVersionOfDC.Relation->HasVersion

DC.Relation->IsFormatOf DC.Relation->HasFormat (“encoded version”)

DC.Relation->References DC.Relation->IsReferencedBy

DC.Relation->IsBasedOn DC.Relation->IsBasisFor

DC.Relation->Requires DC.Relation->IsRequiredBy

April 6, 2000

COVERAGECOVERAGE

“The extent or scope of the content of the resource.” Includes spatial location (e.g. country, geographic co-ordinates or time code) and temporal period (period label, date or date range) or jursidiction (e.g. a named administrative entity)

Best Practice: Use a controlled vocabulary or standard, such as Getty Thesaurus of Geographic Names. SMPTE time code SMPTE 12M-1995 is preferred, but hh:mm:ss as derived from the playback source (VTR, etc.) or video editing software is acceptable when SMPTE is not readily available. Document the coverage source.

April 6, 2000

COVERAGE - slide 2COVERAGE - slide 2

Simple: DC.Coverage

Qualified: DC.Coverage->periodName

DC.Coverage->placeName

DC.Coverage->x x.min x.max

DC.Coverage->y y.min y.max

DC.Coverage->z z.min z.max

DC.Coverage->polygon polygon.include polygon.exclude

DC.Coverage->line

DC.Coverage->3d 3d.exclude

April 6, 2000

COVERAGE - slide 3COVERAGE - slide 3

Qualified: DC.Coverage->t t.min t.max

April 6, 2000

RIGHTSRIGHTS

“Information about rights held in and over the resource. Typically, a Rights element will contain a rights management statement for the resource, or reference a service providing such information. Rights information often encompasses Intellectual Property Rights (IPR), Copyright, and various Property Rights.”

Best Practice: Use a pointer (typically URL or URN) to a rights statement containing “accessibility, reproduction constraints, copyright holder, and/or inclusion of credit line”May vary according to type of material and type of restriction (e.g. Archival material; web-based class lecture)

April 6, 2000

RIGHTS slide - 2RIGHTS slide - 2

Under Consideration: Use permanent file name/repository location, for DC.Identifer; Use an access page requiring password or digital certificate for DC.Rights.

Simple: DC.Rights

April 6, 2000

XML - Record - Format - Draft

<?xml version=“1.0”?><dc-record><title>

<excerpt>Jimmy Carter Interview </excerpt><series>Oral History Interviews of the GeorgiaInstitute of Technology Alumni Association OralHistory Project</series>

</title><creator>

<person><interviewee>Carter, Jimmy, 1924-</interviewee>

</person></creator><subject>

<LCNAF>Carter, Jimmy, 1924-</LCNAF><LCSH>United States. President (1977-1981:

Carter)</LCSH></subject>

April 6, 2000

<description><summary>Three segments from a videotaped(VHS) 1982 interview with former U.S. PresidentJimmy Carter, graduate of the class of 1946,conducted by Marilyn Somers, Director of theGeorgia Tech Living History Program.</summary>

</description>

<publisher><organization>Georgia Tech Alumni Association</organization>

<place>Atlanta, Ga.</place></publisher><contributor>

<person><interviewer>Somers, Marilyn<interviewer>

</person></contributor>

April 6, 2000

</date><type>

<nature>image.moving</nature><nature>sound</nature><genre>Interviews</genre>

</type><format>

<media-type> <MIME>video/vnd.quicktime”</MIME>

</media-type><size>

</size><duration>00:05:35</duration>

</format>

April 6, 2000

<identifier><URL>http://www.library.gatech.edu/livhist/27/00:10:32.htm</URL>

</identifier><language>en-us</language><relation>

<IsPartOf>T171 .G47 G57X AUDIO 27</IsPartOf><IsFormatOf> T171 .G47 G57X AUDIO27</IsFormatOf>

</relation><coverage>

<t.min><SMPTE>00:10:32;1</SMPTE><Adobe Premiere 5.1>00:10:32</Adobe

Premiere 5.1></t.min>

April 6, 2000

<t.max><SMPTE>00:12:07;7</SMPTE>

</t.max></coverage><rights>

<URL>http://www.library.gatech.edu/rights/gtarchives</URL>

April 6, 2000

NEXT STEPSNEXT STEPS

• Add Administrative Metadata

• Refine Extended Dublin Core for Video Model

• Crosswalk to MARC, EAD SIM, IMS

• Test with Alumni Association Video Collection and other samples

• Develop Brief and Full Record Templates

• Publish XML DTD

• Request Comments from Library and Video Community

• Publish “Best Practices for Digital Video” document

April 6, 2000

Hunter, Jane and Liz Armstrong. A Comparison of Schemas for Video Metadata Representation

http://www8.org/w8-papers/3c-hypermedia-video/comparison/comparison.html

Reggie http://metadata.net

Generates records in Dublin Core and RDF/Dublin Core. Provides a template for establishing a metadata registry.

MetaWeb: http://www.dstc.edu.au/RDU/MetaWeb/broker/search.html

Provides software for establishing a gateway to search distributed Dublin Core.

http://www.ukoln.ac.uk/metadata/interoperability/

Crosswalks between Formats:

MORE INFORMATIONMORE INFORMATION

April 6, 2000

CORC: OCLC Cooperative Online Resource Catalog Project. http://purl.oclc.org/corc

Information entered in a template is cross-cataloged in MARC, Dublin Core and RDF/Dublin Core. Membership to libraries of any description at no charge through July 1, 2000. Currently available for search and display to non-members. Use for MARC, Dublin Core and DC/RDF examples

DC.dot http://www.ukoln.ac.uk/metadata/dcdot/

Generates records in Dublin Core and RDF/Dublin Core

April 6, 2000

Dublin Core Record--Draft

April 6, 2000

April 6, 2000

</HEAD></HTML>

GEORGIA INSTITUTE OF TECHNOLOGY G. Agnew & J.Hudgins April 6, 2000 DIGITAL VIDEO METADATA Data or...

Documents

Transcript of GEORGIA INSTITUTE OF TECHNOLOGY G. Agnew & J.Hudgins April 6, 2000 DIGITAL VIDEO METADATA Data or...

Chad cotton agnew planning 10

No SQL Metadata Management - Dan McCreary · Metadata, or data that describes data, is fundamentally different than data itself. The management of metadata is becoming a strategic

SPOTL: Some Programs for Ocean-Tide Loadingagnew/Spotl/spotlman.pdf · 2012), (Agnew, 1997), a brief journal article. or the earlier version of this document (Agnew, 1996) – though

EXTERIORS - Agnew Building Supplies

Agnew - Toccata Tragica

Denise a. Agnew - Corazones Ocultos

Agnew Gold Mine · Agnew Gold Mine Technical Short Form Report Agnew Gold Mine represents a solid base for Gold Fields growth in the Region and is an important contributor to the

Isaac Agnew Autumn 14 Offers

Semantic Web 0 (2017) 1–0 IOS Press Evaluation of Metadata …pdfs.semanticscholar.org/3297/846f6c8b4878c6f12de6e569b... · 2018-03-26 · tic and/or semantic metadata or provenance

Agnew Sovereignty Regimes

Harold M. Agnew

1455 Agnew Street, Simi Valley, CA 93065

Présentation jonathan agnew

METADATA VALUE SPACE Almost all metadata standards require or recommend the use of controlled vocabularies for some elements.

Agnew, Dwifht Merle · Dwicht Agnew was born in Fredericktown, Chic, , n January 1, 1302, son of liuzray J. and Louise (Full in) Agnew, both now deceased. He attended Fredericktown

agnew jack - Naval History and Heritage Command · JACK AGNEW, SUPPLY CORPS, U. S. Jack Agnew was born in Bonham, Texas, on September 5, 1909, son of Mrs. Jenny Agnew (nee Mildred

GALINTEL MONO STRINGER - Agnew Building Supplies

3.6 IMPROVING STATISTICAL DATA AND METADATA ......It will develop or reuse services for metadata management and metadata discovery and will put in place an appropriate governance.

Agnew Territorial Trap

2009 agnew banks