CNI Fall Task Force Meeting 2003, Portland, OR Using MPEG-21 DIDL, the OAI-PMH, and the OpenURL as...

CNI Fall Task Force Meeting 2003, Portland, OR

Using MPEG-21 DIDL, the OAI-PMH, and the OpenURL as building blocks for storing & disseminating complex digital objects

Research Library, Los Alamos National LaboratoryRESEARCHLIBRARY

Using MPEG-21 DIDL, the OAI-PMH, and the OpenURL as building blocks for storing and disseminating

complex digital objects

Jeroen Bekaert, Patrick Hochstenbach and Herbert Van de Sompel

Research Library, Prototyping Team

Los Alamos National Laboratory




Context

• Uniform approach for storing and disseminating LANL data collections

• Interesting characteristics of the repository architecture:o Distributed by designo Use of MPEG-21 DIDL to represent complex objects ~ DIDso Multi-faceted use of OAI-PMH to access the repositoryo Use of NISO OpenURL to access the repository o Dynamic binding of behaviors to DIDso Use of XMLTape for storing collections of DIDs




Using MPEG-21 DIDL to represent complex digital objects






Motivation

• Potential impact of MPEG-21o MPEG: ISO/IEC Committeeo MPEG-1/MPEG-2/MPEG-4/MPEG-7/MPEG-21o Expected industry support

• MPEG-21 Vision: ‘MPEG-21 defines ‘a normative open framework for multimedia delivery and consumption for use by all the players in the delivery and consumption chain’

o Applicability to Digital Librarieso Ability to accomodate any media type and genre

• MPEG-21 is modular:o MPEG-21 Part 2: DIDL – representation of digital objectso MPEG-21 Part 3: DII – identification of digital objectso MPEG-21 Part 4: IPMP – enforcement of rights expressionso MPEG-21 Part 5: REL – declaration of rights expressionso MPEG-21 Part 7: DIA – transcoding based on contextual informationo MPEG-21 Part 10: DIP – association of behaviors




MPEG-21 DIDL - 1. Data Model

• Abstract Definitions + W3C XML Schema

• Entitieso a Container didl:Containero an Item didl:Itemo a Component didl:Componento a Resource didl:Resourceo a Descriptor didl:Descriptoro …

• Remarkso not a cookbooko further profiling is necessary (applications/communities)




Component<didl:Component>

Resource<didl:Resource>

Container<didl:Container>

<didl:Descriptor>

Item<didl:Item>

<didl:Descriptor> <didl:Descriptor>



Item<didl:Item>

Item<didl:Item>






MPEG-21 DIDL - 1. Data Model




MPEG-21 DIDL - 2. Descriptors

• Secondary information pertaining to Entitieso MPEG-21 defined uses

- identification information – MPEG-21 Part 3 : DII- rights information – MPEG-21 Part 5 : REL / Part 4 : IPMP- processing information – MPEG-21 Part 10 : DIP

o community/application specific uses- cf. LANL use




MPEG-21 DIDL - 2. Descriptors - Identifiers

<didl:Item> <didl:Descriptor> <didl:Statement mimeType="text/xml; charset=UTF-8"> <dii:Identifier xmlns:dii="urn:mpeg:mpeg21:2002:01-DII-NS"> urn:isbn:0-395-36341-1</dii:Identifier> </didl:Statement> </didl:Descriptor> …</didl:Item> MPEG-21 dii:Identifier

MPEG-21 DIDL - 2. Descriptors - rights

<didl:Item> … <didl:Descriptor> <didl:Statement mimeType="text/xml; charset=UTF-8"> <r:license xmlns:r="urn:mpeg:mpeg21:2003:01-REL-R-NS"> 

<r:otherInfo> <dc:rights xmlns:dc="http://purl.org/dc/elements/1.1/">

Copyright2003; American Physical Society</dc:rights> </r:otherInfo> </r:license> </didl:Statement> </didl:Descriptor> …</didl:Item> MPEG-21 r:license




MPEG-21 DIDL - 2. Descriptors - behaviors

<didl:Component> … <didl:Descriptor> <didl:Statement mimeType="text/xml; charset=UTF-8"> <dip:ObjectType xmlns:dip="urn:mpeg:mpeg21:2002:01-DIP-NS"> urn:foobar:Argument</dip:ObjectType> </didl:Statement> </didl:Descriptor> …</didl:Component> MPEG-21 dip:ObjectType

Content

<didl:Item> … <didl:Descriptor> <didl:Statement mimeType="text/xml; charset=UTF-8"> <dip:Argument xmlns:dip="urn:mpeg:mpeg21:2002:01-DIP-NS"> urn:foobar:Argument</dip:Argument> </didl:Statement> </didl:Descriptor> <didl:Resource> function PlayTrack() { } </didl:Resource> …</didl:Item> MPEG-21 dip:Argument

Processing Item




MPEG-21 DIDL at LANL

• 2 questions:o How to map datastreams of complex objects of the LANL repository to

the DIDL data model o How to use Descriptors to meet the design goals of the repository and

its associated applications

• LANL DID profile, explained by means of the following example:o A complex object consisting of

- LANL technical report

– 1 file: pdf

– id = info:lanl-tr/LA-9870- metadata record

– 2 versions: raw MARC record and derived MARCXML file

– id = info:lanl-opac/LANLb10012271




LANL DIDs grow in breadth, not in depth

Item<didl:Item>


<didl:Descriptor>



<didl:Descriptor>

<didl:Descriptor> <didl:Descriptor> <didl:Descriptor>

<didl:Descriptor>

Item<didl:Item>






Relationships expressed in RDF




All LANL data is created equal

Item<didl:Item>


<didl:Descriptor>



<didl:Descriptor>


<didl:Descriptor>

Item<didl:Item>






LANL technical report

MARC record

Relationships expressed in RDF




LANL DID Descriptors - relationships

Item<didl:Item>


<didl:Descriptor>



<didl:Descriptor>


<didl:Descriptor>

Item<didl:Item>






hasMetadata: Item[1]isPartOf: Collection A…

isTranslationOf: Object A

isMetadataOf: Item[2]


MARC record




LANL DID Descriptors - relationships

info:lanl-opac/LANLb10012271 info:lanl-tr/LA-9870

isDescriptiveMetadataOf

hasDescriptiveMetadata

info:sid/library.lanl.gov:lanl-opac

isPartOf

info:sid/library.lanl.gov:lanl-tr

isPartOf

http://library.lanl.gov/2003-11/STB-RL/#Collection

hasType hasType




LANL DID Descriptors - identifiers

• DID-identifier: Container-level

• Content-identifier: Item-levelo When a single datastream has an identifier, it must be treated as an

Item. (1.)o When multiple datastreams share an identifier, their combination must

be treated as an Item. (2.)o All Items must have an identifier. (3.)




LANL DID Descriptors - identifiers

Item<didl:Item>


<didl:Descriptor>



<didl:Descriptor>


<didl:Descriptor>

Item<didl:Item>






info:lanl-tr/LA-9870info:lanl-opac/LANLb10012271

urn:uuid:10ba6842-ec45-3b19-8kub-hy8ff58c58a8b


MARC record




LANL DID Descriptors - placeholder for behaviors

Item<didl:Item>


<didl:Descriptor>



<didl:Descriptor>


<didl:Descriptor>

Item<didl:Item>







MARC record

content-stream:text:structured-text:mark-up-lang:xml#application/marc+xml




LANL DID Descriptors - placeholder for behaviors

<didl:Item> … <didl:Descriptor> <didl:Statement mimeType="text/xml; charset=UTF-8"> <dip:Argument xmlns:dip="urn:mpeg:mpeg21:2002:01-DIP-NS"> urn:foobar:Argument</dip:Argument> </didl:Statement> </didl:Descriptor> <didl:Resource> function PlayTrack() { } </didl:Resource> …</didl:Item>

MPEG-21 dip:Argument

Processing Item

<didl:Item> … <didl:Descriptor> <didl:Statement mimeType="text/xml; charset=UTF-8"> <dip:ObjectType xmlns:dip="urn:mpeg:mpeg21:2002:01-DIP-NS"> urn:foobar:Argument</dip:ObjectType> </didl:Statement> </didl:Descriptor> …</didl:Item>

MPEG-21 dip:ObjectType

Content Item

Profile/BehaviorR

egistry…<didl:Descriptor> <didl:Statement> <dipr:Profile> content-stream:… </dipr:Profile> </didl:Statement></didl:Descriptor>…

stored DID disseminated DID

dynamic insertion of behaviors




Using the OAI-PMH and the OpenURL as building blocks for storing and disseminating DIDs






LANL

A&I publisher

publisher

ftp

ftp

Storing DIDs in OAI-PMH repositories

ftp

baseURL(1)

Ex

po

se

techReport

baseURL(2)

A&I

baseURL(3)

FTXT

Ing

es

t

techReport

A&I

FTXT

OAI-PMH identifier = DID-identifier

OAI-PMH datestamp = datetime of ingestion

OAI-PMH response = DIDs




XMLTape:

• XML wrapper for DIDs

• Zipped

• Zipped file is made accessible through OAI-PMH

• Index (DID-identifiers and datestamps) based on byte offset and byte count in zipped file

XMLTape: a special OAI-PMH repository

DID-identifierDatestamp of ingestion

XMLTape

DID

DID

DID

DID

DID

DID

DID

DID



…

…

…

…

…




Repo Index

Repository Index

baseURL(1) 2003-02-20

baseURL(2) 2003-01-15

baseURL(3) 2002-11-12

STEP 2: ListRecords (OAI-PMH)

List of DIDs

Repository Index: keeping track of OAI-PMH repositories

baseURL(index)

baseURL(1)

Ex

po

se

baseURL(2)

A&I

STEP 1: ListIdentifiers (OAI-PMH)

baseURL(1)

techReport




Identifier Resolver

monitors

DID-id or content-id

baseURL & DID-id

identifier resolver

identifier datestamp repository

DID-id 1 2003-02-20baseURL(1) &

DID-id 1

Content-id 1 2003-01-15baseURL(2) &

DID-id x

Content-id 2 2002-11-12baseURL(x) &

DID-id y

Repo IndexbaseURL(index)

Ex

po

se

baseURL(2)

A&I

techReport

Identifier Resolver: locating DIDs and Items

DID-id

Content-id

Content-id




OAI-PMH OAI-PMH

DID-level access

Ex

po

se

A&I

techReport

OAI-PMH access to DIDs across repositories

DID

DID, METS, SCORM, … MPEG-21

DIPEngine

Registry of trans-

formations

Profile/BehaviorR

egistry

DIDwith PI

FTXT

OA

I-PM

H F

ederato

r

set = baseURL(1)

set = baseURL(2)

set = baseURL(3)




Ex

po

se

A&I

techReport

OpenURL OAI-PMH

OpenURL access to Items across repositories

OpenURL

Requester

…

ServiceType

Referent

Op

en

UR

LOpenURL

Item-level and DID-level access

FTXT

Profile/BehaviorR

egistry

DIDwith PI

transformedcontent MPEG-21

DIPEngine

Registry of trans-

formations




Summary of repository access methods

DID-level Item-level

OAI-PMH – individual repositories

DIDL ---

OAI-PMH – FederatorDIDL, METS, SCORM, IMS,

ToC, …---

OpenURL GatewayDIDL, METS, SCORM, IMS,

ToC, …Transforms of content

OAIS: Dissemination Information Package(s)

OAIS: Result Set




Repo Index

OAI 1

OAI 4OAI 5

OAI-PMH Federator in a distributed architecture

Identifier Resolver

OAI 3OAI 2

OAI-PMH Federator 1 OAI-PMH Federator 2 OAI-PMH Federator 3

SP 1 SP 2 SP 3 SP 4 … SP x

DIDL METS




OAI 2

OAI 5

Repo Index

OAI 1

OAI 4

OpenURL gateway in a distributed architecture

Identifier Resolver

SP 1Institutional

Disseminator

OAI 3

OpenURL

Result Set




Overview of the LANL architecture

LANLftp

OpenURL

Ingest

Repo Index

A&I publisherftp

publisher

publisher

OAI-PMH

OpenURL

OAI PMH

Identifier Resolver

MPEG-21DIP

Engine

Registry of trans-formation

s

DID

Profile/BehaviorR

egistry

DIDwith PI

OAI PMH

ftp

ftp

FTXT

A&I

TechReport

OAI PMH

OA

I-PM

H F

ederator

FTXT




Acknowledgements

• This research is conducted by the Prototyping Team of the LANL Research Library: Luda Balakireva, Jeroen Bekaert, Patrick Hochstenbach, Henry Jerez, Xiaoming Liu, Thorsten Schwander and Herbert Van de Sompel

• The Prototyping Team of the LANL Research Library wishes to thanko Rick Luce at the LANL Research Library for making this research

possible and for his continued encouragement. o Miriam Blake and Beth Goldsmith from the Development Team of the

LANL Research Library for valuable feedback regarding the LANL DID.o Multimedia Lab of the Ghent Univeristy for sharing their MPEG-21

knowledge.

CNI Fall Task Force Meeting 2003, Portland, OR Using MPEG-21 DIDL, the OAI-PMH, and the OpenURL as...

Documents

Transcript of CNI Fall Task Force Meeting 2003, Portland, OR Using MPEG-21 DIDL, the OAI-PMH, and the OpenURL as...