This document summarizes a presentation about the CASPAR Web Desktop. It discusses the key components of CASPAR including CASPAR & OAIS, the CASPAR infrastructure, and the CASPAR approach. It provides examples of how CASPAR deals with knowledge bases and modules/dependencies for scientific data, performing arts data, and cultural data. It also discusses CASPAR's approach to intellegibility and preservation over time as well as its use of a publish/subscribe system for notifications.

1. DEMO: CASPAR Web Desktop
Using The CASPAR Key Components
through Web Browser
Luigi Briguglio
Engineering R&D Laboratory – Rome (Italy)
3rd Annual WePreserve Conference in Nice (France)

2. Presentation Planning
• CASPAR & OAIS
• CASPAR Infrastructure
• CASPAR Approach
• CASPAR Demo

3. CASPAR & OAIS
Information Descriptive
Primary focus of Package Information
archival preservation
Needed for discovery
Preservation Needed for long-term
Content
Description preservation
Information
Information
Designated Community
Knowledge Base
interpreted
Data interpreted using using
Representation
Object
Information

4. CASPAR Infrastructure
Facade Layer
Information
Communication Information
Package
Mngt Access
Mngt
Designated Community
Security
& Knowledge
Mngt
Mngt
The CASPAR Foundation
KeyComponents Framework Platform

5. CASPAR Foundation
KeyComponents
GapManager DataAccess&Security RepInfoToolbox
The CASPAR Foundation
SemanticWeb Orchestration Registry
Packaging DigitalRights FindingAids
DataStores Authenticity Virtualisation
CASPAR Service Factory
Framework
Application Server: Tomcat, Glassfish, WASCE
Development Framework: Java, C++, XML, GWT, Ant
Development Management: Hudson and JTrac
DBMS: H2, Postgres
Platform
Java Platform
Operating System: Linux, Unix, Windows, Mac

6. Approach:
Dealing with Knowledge Base
• According to OAIS:
– “Data about data” are distinguished to various categories.
– One very important is that of Representation Information
(RepInfo)
– RepInfo allows interpretation of data object
– Interpretation is depending from the “Community” and its own KB
• Knowledge Base of Designated Community
– Each actor or community can be characterized by a profile that
contains those RI modules that are assumed to be
available/known.
– Those RI modules allow interpretation of digital objects

7. Approach:
Dealing with Knowledge Base
User has a  DCProfile contains  RIModules interpret  InfoObject
RIModules[A] ObjectA
101001010101
010101010010
101010101010
DCProfileA 100101101001
001011001010
UserA 010101010010
101001010101
010101010101
UserB DCProfileB
101001010101
010101010010
RIModules[B] 101010101010
100101101001
001011001010
010101010010
101001010101
ObjectB 010101010101

8. Modules and Dependencies:
Scientific Data Example
FITS FILE
FITS FITS
STANDARD DICTIONARY
DICTIONARY
PDF FITS SPECIFICATION
STANDARD JAVA s/w
XML
SPECIFICATION
PDF
JAVA VM
s/w
UNICODE
SPECIFICATION

9. Modules and Dependencies:
Performing Arts Data Example
3D motion Motion
data Analysis
and
Recognition
Motions Motion
Capture and
Processing Motion-
Mapping
Multimedia
Parameters
Mapping
Strategy
GUI (For
Multimedia Multimedi
monitor &
Generation a output
control)
MULTIMEDIA
PERFORMANCE DATA
C3D DirectX MAX/MSP
3D motion 3D scene motion to music
data files data files mapping strategy

10. Modules and Dependencies:
Cultural Data Example
Metadata
Record
CIDOC CRM
CORE
CIDOC CRM CRM CORE
STANDARD XML Schema
RDF XML
STANDARD SPECIFICATION

11. Approach
Intellegibility and Preservation
PRESENT
PAST FUTURE
time
DC knoledge base
Preservation is a “Process”
and it’s important to monitor
and notify about “event
change” within the Digital
Preservation Archive

12. Approach:
Dealing with Notifications
Publish/Subscribe System
publish subscribe
topic
topic expertise

13. http://developers.casparpreserves.eu:8080

14. …and Stay tuned on
http://developers.casparpreserves.eu:8080