ADL Registry

(Plus a Little Technological Context)

Larry Lannom

Corporation for National Research Initiativeshttp://www.cnri.reston.va.us/

http://www.handle.net/

Corporation for National Research Initiatives

• Significant role in the evolution of network infrastructure– Technological– Organizational

• Current work in digital object architecture– Identifying and managing content objects

Why is CNRI Involved in This Project?

Corporation for National Research Initiatives

• Framework for managing Digital (Information) Objects

• Give it a name and talk to it– Don’t worry about where it is– Don’t worry about what it’s made of

• Rise above details of application versions and content formats

Digital Object Architecture - Goals

Corporation for National Research Initiatives

Digital Object Architecture

Client

Resource Discovery

•Search Engines•Metadata Databases•Catalogues, Guides, etc.

Resolution System

Repositories / Collections

Corporation for National Research Initiatives

Digital Object Architecture ComponentsHandle System

• Go from name to attributes

• Fundamental indirection system for Digital Object management on the net

• No free lunch– Added layer of infrastructure– Must be managed

Naming Resources on the Net

The Problem

Internet

chapter.pdfwww.acme.com

Naming Resources on the Net

The Problem

Internet

www.acme.com http://www.acme.com/chapter.pdf

Internet

Naming Resources on the Net

The Solution

Name = Value(s)10.123/xyz = http://www.acme.com/chapter.pdf

Naming Service

www.acme.com

Internet

Naming Resources on the Net

The Solution

Name = Value(s)10.123/xyz = http://www.newbusiness.com/chapter.pdf

http://www.newbusiness.com/chapter.pdf

Naming Service

www.newbusiness.com

www.acme.com http://www.acme.com/chapter.pdf

Corporation for National Research Initiatives

• Distributed, scalable, secure• Enforces unique names• Enables association of one or more typed values,

e.g., URL, with each name• Optimized for speed and reliability• Open, well-defined protocol and data model• Provides infrastructure for application domains,

e.g., digital libraries, electronic publishing ...

CNRI Handle System

Corporation for National Research Initiatives

Handle System Usage

• Library of Congress

• DTIC (Defense Technical Information Center)

• IDF (International DOI Foundation)– CrossRef (scholarly journal consortium)

– Enpia (Korean content management technology firm)

– CDI (U.S. content management technology firm)

– LON (U.S. learning object technology firm)

– CAL (Copyright Agency Ltd - Australia)

– TSO (U.K. publisher & info mgmt service provider)

– MEDRA (Multilingual European DOI Registration Agency)

– Nielsen BookData (bibliographic data - ISBN)

– R.R. Bowker (bibliographic data - ISBN)

– Office of Publications of the European Community

– German National Library of Science and Technology (applied)

• NTIS (National Technical Information Service)

• DSpace (MIT + HP)

• Coming on stream: ADL, Globus Alliance, NSDL

Corporation for National Research Initiatives

Handles Resolve to Typed Data

URL 2 http://a-books.com/….

DLS 9 acme/repository

HS_ADMIN 100 acme.admin/jsmith

XYZ 100111001111012

Handle dataHandle Data typeIndex

10.123/456 URL 1 http://acme.com/….

Handle Resolution

is a collection ofhandle services,each of which consists of one ormore replicated sites,

Site 1Site 1 Site 2Site 2

Site 1Site 1

Site 2Site 2

Site 3Site 3 …... Site nSite n

Client

The Handle System

LHS

LHS LHS

LHSGHR

each of which mayhave one or moreservers.

123.456/abc URL 4 http://www.acme.com/

http://www.ideal.com/8URL

#1#1 #2#2 #n#n#4#4#3#3

#1#1 #2#2

...

Handle Clients

LHS

LHS LHS LHS

LHS

LHS

LHS

LHSGHR

LHS

Handle System

Web ClientHandle Administration

Client

ResolveHandle

HTTP Redirect

Proxy/Web Server

HTTP Get

Handle Data

http://hdl.handle.net/123.456/abc

Handle Clients

LHS

LHS LHS LHS

LHS

LHS

LHS

LHSGHR

LHS

Handle System

ClientHandle Administration

Client

hdl:/123.456/abc

ClientPlug-In

Resolve HandleRequest

Handle Data

Handle Clients

LHS

LHS LHS LHS

LHS

LHS

LHS

LHSGHR

LHS

Handle System

WebHandle Administration

Client

Web Server

HTTP

Handle Admin API

Admin Forms

Handle Clients

LHS

LHS LHS LHS

LHS

LHS

LHS

LHSGHR

LHS

Handle System

WebHandle Administration

Client

CustomClient

Handle Clients

LHS

LHS LHS LHS

LHS

LHS

LHS

LHSGHR

LHS

Handle System

Handle Administrationembedded in another

process

Handle Administrationembedded in another

processWeb

Handle Clients

LHS

LHS LHS LHS

LHS

LHS

LHS

LHSGHR

LHS

Handle System

Handle Administrationembedded in another

process

Handle Administrationembedded in another

process

Handle Resolutionembedded in another

process

Handle Resolutionembedded in another

process

Corporation for National Research Initiatives

• Assigned Prefixes (Jan 05)– DOI - 1176– Other - 401

• Handles– DOI - 15.6 M– Other - Additional millions (total per prefix known only to

prefix manager)

• Global– Core: three service sites (added locations being considered)– 10.6 M resolutions

Handle System Usage

Corporation for National Research Initiatives

• Specification– RFC 3650: Overview

– RFC 3651: Namespace and Service Definition

– RFC 3652: Protocol

• HSAC - Handle System Advisory Committee– Now includes ADL representation

Handle System Management and Standards

Corporation for National Research Initiatives

• Technological and Organizational Infrastructure– Register the existence and access conditions for Learning Objects

relevant to the DoD ‘Enterprise’– Provide user interface to search the registry

• Integrates existing technologies– Handle System for identification and access– XML for object description and submission– LOM metadata– Repository for metadata object storage and access– Lucene search engine

• Running at CNRI in pilot phase

ADL Registry (ADL-R)

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

Marines

M1

M10

M20

ContentObjects

ADL-R Input

Collections Input Processing Registry

ParseAuthenticateValidateReturn

1N1

metadata

SearchEngine

MetadataObjects

ADL-R

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

ADL-R Input

Collections Input Processing Registry

ParseAuthenticateValidateReturn

N1

metadata

<xml><title>Course 1</title><org>J-School</org><hdl>123/4</hdl>........</xml>

SearchEngine

MetadataObjects

ADL-R

DTIC

LOC IDF NSDL

LHS

UWisc

LHS

ADL-RGHR

LHS

Handle System

NAVAIR has HandlePrefix 123 and names N1 hdl:123/4

Marines

M1

M10

M20

ContentObjects

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

ADL-R Input

Collections Input Processing Registry

ParseAuthenticateValidateReturn

2 ResultsLog

SearchEngine

MetadataObjects

ADL-R

Marines

M1

M10

M20

ContentObjects

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

ADL-R Input

Collections Input Processing Registry

ParseAuthenticateValidateReturn

SearchEngine

MetadataObjects

ADL-R

MetadataObject

matching ContentObject N1

hdl:abc/d

xml

DTIC

LOC IDF NSDL

LHS

UWisc

LHS

ADL-RGHR

LHS

Handle System

Input process createsMetadata Object forN1 named hdl:abc/d...

3

...and creates twohandles: hdl:abc/dfor the MetadataObject & hdl:123/4for the ContentObject.

4

Marines

M1

M10

M20

ContentObjects

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

Searching the Registry

SearchEngine

MetadataObjects

ADL-R

MetadataObject

matching ContentObject N1

hdl:abc/d

xml

Client

Client does a search. Resultspoint to Metadata Object abc/d.

1

DTIC

LOC IDF NSDL

LHS

UWisc

LHS

ADL-RGHR

LHS

Handle System

Marines

M1

M10

M20

ContentObjects

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

Searching the Registry

SearchEngine

MetadataObjects

ADL-R

MetadataObject

matching ContentObject N1

hdl:abc/d

xml

If desired, client gets Metadata Object abc/d to view full registrymetadata.

2

DTIC

LOC IDF NSDL

LHS

UWisc

LHS

ADL-RGHR

LHS

Handle System

Client does a search. Resultspoint to Metadata Object abc/d.

1

Marines

M1

M10

M20

ContentObjects

Client

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

Searching the Registry

SearchEngine

MetadataObjects

ADL-R

MetadataObject

matching ContentObject N1

hdl:abc/d

xml

Client decides to get ContentObject N1 and resolves handle123/4 to get its accesslocation and other conditions.

3

DTIC

LOC IDF NSDL

LHS

UWisc

LHS

ADL-RGHR

LHS

Handle System

Client does a search. Resultspoint to Metadata Object abc/d.

1

If desired, client gets Metadata Object abc/d to view full registrymetadata.

2

Marines

M1

M10

M20

ContentObjects

Client

ATSC

A3 A3 A2 A2

A1A1

ContentObjects

NAVAIR

N4N4

N3N3

N2N2

ContentObjects

N1

hdl:123/4

Searching the Registry

SearchEngine

MetadataObjects

ADL-R

MetadataObject

matching ContentObject N1

hdl:abc/d

xml

Client requests a copy ofContent Object N1 from NAVAIR.

4

Client decides to get ContentObject N1 and resolves handle123/4 to get its accesslocation and other conditions.

3

Client does a search. Resultspoint to Metadata Object abc/d.

1

If desired, client gets Metadata Object abc/d to view full registrymetadata.

2

DTIC

LOC IDF NSDL

LHS

UWisc

LHS

ADL-RGHR

LHS

Handle System

Marines

M1

M10

M20

ContentObjects

Client