Download presentation
Presentation is loading. Please wait.
Published byHannah McPherson Modified over 10 years ago
1
ADL Registry (Plus a Little Technological Context) Larry Lannom Corporation for National Research Initiatives
2
Why is CNRI Involved in This Project?
Significant role in the evolution of network infrastructure Technological Organizational Current work in digital object architecture Identifying and managing content objects Corporation for National Research Initiatives
3
Digital Object Architecture - Goals
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 Corporation for National Research Initiatives
4
Repositories / Collections
Digital Object Architecture Repositories / Collections Client Resolution System Resource Discovery Search Engines Metadata Databases Catalogues, Guides, etc.
5
Digital Object Architecture Components Handle 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 Corporation for National Research Initiatives
6
Naming Resources on the Net
The Problem Internet chapter.pdf
7
Naming Resources on the Net
The Problem Internet
8
Naming Resources on the Net
The Solution Internet Name = Value(s) 10.123/xyz = Naming Service
9
Naming Resources on the Net
The Solution Internet Naming Service Name = Value(s) 10.123/xyz =
10
Corporation for National Research Initiatives
CNRI Handle System 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 ... Corporation for National Research Initiatives
11
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
12
Handles Resolve to Typed Data
Data type Index Handle data 10.123/456 URL 1 URL 2 DLS 9 acme/repository HS_ADMIN 100 acme.admin/jsmith XYZ 12 Corporation for National Research Initiatives
13
Handle Resolution The Handle System is a collection of
handle services, Client GHR LHS each of which consists of one or more replicated sites, Site 1 Site 2 Site 3 …... Site n each of which may have one or more servers. /abc URL 4 8 #1 #2 #n #4 #3 ...
14
Handle Administration
Handle Clients Web Client Handle Administration Client HTTP Redirect HTTP Get Proxy/ Web Server Handle Data Resolve Handle LHS GHR Handle System
15
Handle Administration
Handle Clients Client Handle Administration Client Client Plug-In Handle Data Resolve Handle Request hdl:/ /abc LHS GHR Handle System
16
Handle Administration
Handle Clients Web Handle Administration Client HTTP Admin Forms Web Server Handle Admin API LHS GHR Handle System
17
Handle Administration
Handle Clients Web Handle Administration Client Custom Client LHS GHR Handle System
18
Handle Administration
Handle Clients Handle Administration embedded in another process Web LHS GHR Handle System
19
Handle Administration
Handle Clients Handle Resolution embedded in another process Handle Administration embedded in another process LHS GHR Handle System
20
Corporation for National Research Initiatives
Handle System Usage Assigned Prefixes (Jan 05) DOI Other - 401 Handles DOI 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 Corporation for National Research Initiatives
21
Handle System Management and Standards
Specification RFC 3650: Overview RFC 3651: Namespace and Service Definition RFC 3652: Protocol HSAC - Handle System Advisory Committee Now includes ADL representation Corporation for National Research Initiatives
22
Corporation for National Research Initiatives
ADL Registry (ADL-R) 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 Corporation for National Research Initiatives
23
ADL-R Input Collections Input Processing Registry ADL-R A3 A2 A1 ATSC
Content Objects ADL-R Search Engine ATSC N4 N3 N2 Content Objects N1 hdl:123/4 Metadata Objects Parse Authenticate Validate Return 1 N1 metadata NAVAIR M1 M10 M20 Content Objects Marines
24
ADL-R Input Collections Input Processing Registry ADL-R A3 A2 A1 ATSC
Content Objects ADL-R Search Engine ATSC N4 N3 N2 Content Objects N1 hdl:123/4 Metadata Objects <xml> <title>Course 1</title> <org>J-School</org> <hdl>123/4</hdl> </xml> Parse Authenticate Validate Return N1 metadata NAVAIR M1 M10 M20 Content Objects NAVAIR has Handle Prefix 123 and names N1 hdl:123/4 DTIC LOC IDF NSDL LHS UWisc ADL-R GHR Marines Handle System
25
ADL-R Input Collections Input Processing Registry ADL-R A3 A2 A1 ATSC
Content Objects ADL-R Search Engine ATSC N4 N3 N2 Content Objects N1 hdl:123/4 Metadata Objects Parse Authenticate Validate Return 2 Results Log NAVAIR M1 M10 M20 Content Objects Marines
26
ADL-R Input Collections Input Processing Registry ADL-R A3 A2 A1 ATSC
Content Objects ADL-R Search Engine ATSC N4 N3 N2 Content Objects N1 hdl:123/4 Metadata Objects Parse Authenticate Validate Return ...and creates two handles: hdl:abc/d for the Metadata Object & hdl:123/4 for the Content Object. 4 Input process creates Metadata Object for N1 named hdl:abc/d... 3 NAVAIR M1 M10 M20 Content Objects hdl:abc/d Metadata Object matching Content Object N1 xml DTIC LOC IDF NSDL LHS UWisc ADL-R GHR Marines Handle System
27
Searching the Registry
ADL-R A3 A2 A1 Content Objects Client does a search. Results point to Metadata Object abc/d. 1 Client Search Engine Metadata Objects ATSC N4 N3 N2 Content Objects N1 hdl:123/4 hdl:abc/d Metadata Object matching Content Object N1 xml NAVAIR M1 M10 M20 Content Objects DTIC LOC IDF NSDL LHS UWisc ADL-R GHR Handle System Marines
28
Searching the Registry
ADL-R A3 A2 A1 Content Objects Client does a search. Results point to Metadata Object abc/d. 1 Client Search Engine Metadata Objects If desired, client gets Metadata Object abc/d to view full registry metadata. 2 ATSC N4 N3 N2 Content Objects N1 hdl:123/4 hdl:abc/d Metadata Object matching Content Object N1 xml NAVAIR M1 M10 M20 Content Objects DTIC LOC IDF NSDL LHS UWisc ADL-R GHR Handle System Marines
29
Searching the Registry
ADL-R A3 A2 A1 Content Objects Client does a search. Results point to Metadata Object abc/d. 1 Client Search Engine Metadata Objects If desired, client gets Metadata Object abc/d to view full registry metadata. 2 ATSC N4 N3 N2 Content Objects N1 hdl:123/4 hdl:abc/d Client decides to get Content Object N1 and resolves handle 123/4 to get its access location and other conditions. 3 Metadata Object matching Content Object N1 xml NAVAIR M1 M10 M20 Content Objects DTIC LOC IDF NSDL LHS UWisc ADL-R GHR Handle System Marines
30
Searching the Registry
ADL-R A3 A2 A1 Content Objects Client does a search. Results point to Metadata Object abc/d. 1 Client Search Engine Metadata Objects If desired, client gets Metadata Object abc/d to view full registry metadata. 2 ATSC N4 N3 N2 Content Objects N1 hdl:123/4 hdl:abc/d Client decides to get Content Object N1 and resolves handle 123/4 to get its access location and other conditions. 3 Metadata Object matching Content Object N1 xml NAVAIR M1 M10 M20 Content Objects Client requests a copy of Content Object N1 from NAVAIR. 4 DTIC LOC IDF NSDL LHS UWisc ADL-R GHR Handle System Marines
Similar presentations
© 2024 SlidePlayer.com. Inc.
All rights reserved.