PROSI © 2005 Guy Maréchal Prepared by: Guy Maréchal [email protected] Une introduction à AXIS An introduction to AXIS Une conférence organisée par l’ASBLdans

PROSI © 2005

Prepared by:Guy Maréchal Guy Maréchal [email protected]

Une introduction à AXIS

An introduction to AXIS

Une conférence organisée par l’ASBL dans le cadre de l’

Bruxelles les 17 et 18 novembre 2005

PROSI © 2005

Titan asbl :Titan asbl : http://www.titan.behttp://www.titan.be

Titan asblTitan asbl

ForumForum

ContactsContacts

GlossairesGlossaires

LaboratoireLaboratoire

ActualitésActualités

PhotothèquesPhotothèques

Titan, l’avenir par le numériqueTitan, l’avenir par le numérique

FR NL GB DFR NL GB D

PROSI © 2005

Présentation générale Présentation générale de l’architecture de l’architecture

d’AXISd’AXIS

General presentation of General presentation of the AXIS architecturethe AXIS architecture

AAcquisition, ecquisition, eXXchange, change, IIndexingndexing, , SStructurationtructuration

PROSI © 2005

1.1. Missions & RequirementsMissions & Requirements2.2. An architectural approachAn architectural approach3.3. The AXIS key featuresThe AXIS key features4.4. The “Open Licensing of AXIS” by TITANThe “Open Licensing of AXIS” by TITAN5.5. Conclusions & AcknowledgementsConclusions & Acknowledgements

Structure of the Structure of the presentationpresentation

PROSI © 2005


Structure of the presentationStructure of the presentation

PROSI © 2005 1.1. Missions & RequirementsMissions & Requirements

IT SystemNetwork

How should the ‘Management of the Archives’ organize the IT SystemHow should the ‘Management of the Archives’ organize the IT Systemto valorize the archives and to meet the requirements of the users ?to valorize the archives and to meet the requirements of the users ?

ManagementManagementof the archivesof the archives

Archives Archives (Digital)(Digital)

Archives Archives (Analog)(Analog)

Logistics

Life in evidenceLife in evidence Recording

UserUserof the archivesof the archives

Clone of the Clone of the Life in evidenceLife in evidence

PROSI © 2005

1.1. Missions & Requirements Missions & Requirements (Users)(Users)

The users want to find interesting media materialThe users want to find interesting media material• That they can listen toThat they can listen to

• With good quality of audio, video, image, text, … With good quality of audio, video, image, text, …

• Easy & cheap to accessEasy & cheap to access

• They can acquire rights to exploit, to enrich, to improve, …They can acquire rights to exploit, to enrich, to improve, …

• Through a large variety of network channelsThrough a large variety of network channels

• With large semantic annotationsWith large semantic annotations

• With association and synchronization of other contentWith association and synchronization of other content

• ……

UserUserof the archivesof the archives

Clone of the Clone of the Life in evidenceLife in evidence

PROSI © 2005

1.1. Missions & Requirements Missions & Requirements (Contents)(Contents)

The ‘Contents’ are those excerpts of the social live which The ‘Contents’ are those excerpts of the social live which have been selected for recording.have been selected for recording.

They are the ‘Original Information Packages’They are the ‘Original Information Packages’

They requireThey require• That they should be captured with the expected qualityThat they should be captured with the expected quality• That they should be recorded with preservation of their existence, That they should be recorded with preservation of their existence,

of their identity, of their authenticity, of their integrity, of their of their identity, of their authenticity, of their integrity, of their accessibility, of their availability…accessibility, of their availability…

• That they should be documented, indexed, ... in a fair, competent That they should be documented, indexed, ... in a fair, competent and ethic wayand ethic way

Life in evidenceLife in evidence

PROSI © 2005

1.1. Missions & Requirements Missions & Requirements (Archives)(Archives)

The Archives, as custodians of the social memory, requireThe Archives, as custodians of the social memory, require• That they could easily be accessed and exploitedThat they could easily be accessed and exploited

• That they will survive to the progressive physical degradation of their supportThat they will survive to the progressive physical degradation of their support

• That they will survive to the progressive evolution of the formats of That they will survive to the progressive evolution of the formats of representationrepresentation

• That they will survive to the changes of the industrial policies That they will survive to the changes of the industrial policies

• That they will be semantically understoodThat they will be semantically understood

• That the enrichments will be kept for further exploitationsThat the enrichments will be kept for further exploitations

• … …

Archives Archives (Digital)(Digital)

Archives Archives (Analog)(Analog)

PROSI © 2005

1.1. Missions & Requirements Missions & Requirements (Management)(Management)

The management team shouldThe management team should• Meet the expectations of the Meet the expectations of the User’sUser’s and the various and the various User’s communitiesUser’s communities

• Meet the expectations of the Social communities as custodians of the Meet the expectations of the Social communities as custodians of the archivesarchives

By ensuring By ensuring • The IT system for managing and exploiting the archivesThe IT system for managing and exploiting the archives

• The persistence of the archives at a reasonable costThe persistence of the archives at a reasonable cost

• A technology watchA technology watch

• …… ManagementManagementof the archivesof the archives

PROSI © 2005

1.1. Missions & Requirements Missions & Requirements (Management)(Management)

The management team should not any longer accept to The management team should not any longer accept to

• To become captive of “Proprietary Systems”To become captive of “Proprietary Systems”

• To pay the price of “Exclusive” suppliersTo pay the price of “Exclusive” suppliers

• To suffer the “barriers” and “obstacles” in the flows of their To suffer the “barriers” and “obstacles” in the flows of their processesprocesses

• ……

ManagementManagementof the archivesof the archives

PROSI © 2005


Structure of the presentationStructure of the presentation

PROSI © 2005

The conference is based on my involvement in many The conference is based on my involvement in many architectural works:architectural works:

• The frame project The frame project ARCADEARCADE sponsored by PHILIPS, a contribution to ISO TC-184 sponsored by PHILIPS, a contribution to ISO TC-184

• The frame project The frame project CIMOSACIMOSA ( (CComputer omputer IIntegrated ntegrated MManufacturing based on an anufacturing based on an OOpen pen SSystem ystem AArchitecture)rchitecture)

A consortium project sponsored by the Commission of the European UnionA consortium project sponsored by the Commission of the European Union having led having led to to ‘SAP’‘SAP’

• The frame project The frame project AXISAXIS ((AAcquisition, ecquisition, eXXchange, change, IIndexing & ndexing & SStructuration)tructuration) of the ‘ of the ‘Non Non Profit AssociationProfit Association’ ’ TITANTITAN

• The The PAXOS PAXOS project and the derived servicesproject and the derived services “Video & Audio Libraries” “Video & Audio Libraries”A collaboration of Belgavox, INNA, MEMNON, Lsi-e and Logon-SIA collaboration of Belgavox, INNA, MEMNON, Lsi-e and Logon-SI

• The The AIMEAIME project project« « AArchivagerchivage I Intelligent desntelligent des MMultimédia de manière ultimédia de manière ÉÉconomiqueconomique » »

A collaboration of TITAN with the CIRTEF, Belgavox, inOvo and MinotaurA collaboration of TITAN with the CIRTEF, Belgavox, inOvo and Minotaur

• The The RIMESRIMES project project« « RRushesushes I Indexingndexing MMultimedia ultimedia EExchange xchange SSystem »ystem »

A collaboration of TITAN with Skema, Panasonic, RTBF, the University of A collaboration of TITAN with Skema, Panasonic, RTBF, the University of CompiègneCompiègne, …, …

• The The AIDARAIDAR project project«« AAdressage &dressage & I Indexation de ndexation de DDocuments multimédia ocuments multimédia AAssistés ssistés par des techniques depar des techniques de RReconnaissance vocale »econnaissance vocale »

A collaboration of TITAN with Voice-Insight, the Brussels University, …A collaboration of TITAN with Voice-Insight, the Brussels University, …

• The The ADABLE ADABLE projectprojectThe Memnon project (en collaboration avec LSI-e) for the The Memnon project (en collaboration avec LSI-e) for the ASR project of the ASR project of the

« « British LibraryBritish Library » »

• The The ACE-Media ACE-Media project (project (AAutonomous utonomous CContent ontent EEntities- ntities- MediaMedia) ) A consortium project sponsored by the Commission of the European Union, under the A consortium project sponsored by the Commission of the European Union, under the

leading of Motorola leading of Motorola

PROSI © 2005 2.2. An architectural approach An architectural approach (The need of a ‘red line’)(The need of a ‘red line’)

The current Information Technologies become mature!The current Information Technologies become mature!The definition of ‘architectural directives’ becomes realistic!The definition of ‘architectural directives’ becomes realistic!

Each large organization should define its ownEach large organization should define its own ‘strict guidelines’‘strict guidelines’ and plan its concrete project having in sight:and plan its concrete project having in sight:

• The identification of the parts of the guide lines pertinent that The identification of the parts of the guide lines pertinent that specific concrete projectspecific concrete project

• The current situation and scenarios for a progressive convergenceThe current situation and scenarios for a progressive convergence• Several scenarios of evolution depending on constrains and plansSeveral scenarios of evolution depending on constrains and plans

PROSI © 2005 2.2. An architectural approach An architectural approach (The need of (The need of a ‘red line’)a ‘red line’)

Many large public and private organizations Many large public and private organizations

have defined their own have defined their own ‘strict guidelines’‘strict guidelines’ and derived explicit requirements for their and derived explicit requirements for their suppliers and own personal.suppliers and own personal.

The ‘Library of Congress’ of the USAThe ‘Library of Congress’ of the USAThe adoption of the METS, XML, … as technical standards The adoption of the METS, XML, … as technical standards The adoption of OAIS as reference model with as key entities The adoption of OAIS as reference model with as key entities

the “SIP, DIP, AIP”the “SIP, DIP, AIP”

The BBC The BBC The adoption of the MXF, AAF, XML, … as technical and The adoption of the MXF, AAF, XML, … as technical and

architectural standardsarchitectural standards

The CTO of the The CTO of the M. John Varney: M. John Varney: ““We will not use you as suppliers if youWe will not use you as suppliers if you don't embrace the standards, if don't embrace the standards, if you don't embrace MXF,”you don't embrace MXF,”

PROSI © 2005 Key part of the ‘Key part of the ‘strict guidelinesstrict guidelines’ of ’ of the BBC:the BBC:

The implementation schemaThe implementation schema

PROSI © 2005

2.2. An architectural approach An architectural approach (Ten (Ten recommendations)recommendations)

The The ‘strict guidelines’‘strict guidelines’ have to be expressed by: have to be expressed by:

““POLICIES”POLICIES”

““TECHNOLOGICAL SPECIFICATIONS”TECHNOLOGICAL SPECIFICATIONS”

““STRUCTURAL & MANAGERIAL STRUCTURAL & MANAGERIAL FACILITIES”FACILITIES”

PROSI © 2005


The The ‘strict guidelines’‘strict guidelines’ have to be expressed by: have to be expressed by:

““POLICIES”POLICIES”The POLICIES are strategic directives and requirements framing The POLICIES are strategic directives and requirements framing and guiding the projects within the organization. It is more than a and guiding the projects within the organization. It is more than a MODEL like the OAIS.MODEL like the OAIS.

““TECHNOLOGICAL SPECIFICATIONS”TECHNOLOGICAL SPECIFICATIONS”It is not enough to decide the adoption of policies. It is required to It is not enough to decide the adoption of policies. It is required to specify how to use METS, XML, SIP, DIP, AIP, OAIS, … together to specify how to use METS, XML, SIP, DIP, AIP, OAIS, … together to obtain consistent results.obtain consistent results.For examples: For examples: METS or MXF could be used in a METS or MXF could be used in a ‘CLOSED’‘CLOSED’ mode! It is mode! It is also not obvious to combine DCMI with RDF to obtain the expected results! also not obvious to combine DCMI with RDF to obtain the expected results! The definition of the rules for the identification of the assets is a complex The definition of the rules for the identification of the assets is a complex problem!problem!

““STRUCTURAL & MANAGERIAL FACILITIES”STRUCTURAL & MANAGERIAL FACILITIES”It is not enough to decide the adoption of policies and technological It is not enough to decide the adoption of policies and technological specifications. It is required to set facilities to empower the specifications. It is required to set facilities to empower the realizations and to ensure the implementation of those policies and realizations and to ensure the implementation of those policies and facilities.facilities.

PROSI © 2005


1.1. Use standards to have full control on the exchanges between Use standards to have full control on the exchanges between functional modulesfunctional modules

2.2. Adopt the SIP, DIP, AIP architecture of the OAIS modelAdopt the SIP, DIP, AIP architecture of the OAIS model

3.3. Construct ‘Logical Entities’ from ‘Physical Entities’ using Construct ‘Logical Entities’ from ‘Physical Entities’ using ‘Proxies’ & vice-versa‘Proxies’ & vice-versa

4.4. Plan the capacity to deliver the DIP through various channels Plan the capacity to deliver the DIP through various channels

5.5. Trace always the “Packages”Trace always the “Packages”

6.6. Create “Collection profiles” to enable “Autonomous Assets Create “Collection profiles” to enable “Autonomous Assets Entities”Entities”

7.7. Create the AIP’s as sets of “Autonomous Assets Entities”Create the AIP’s as sets of “Autonomous Assets Entities”

8.8. Manage the persistence of the AIP’sManage the persistence of the AIP’s

9.9. Manage the off-line conservation of the AIP’sManage the off-line conservation of the AIP’s

10.10.Adopt the previous recommendations for your “Functional Adopt the previous recommendations for your “Functional modules” and “AIP’s” modules” and “AIP’s”

I do suggest that you check your current I do suggest that you check your current ‘strict ‘strict guidelines’guidelines’ or construct / define them considering or construct / define them considering the following ten recommendations:the following ten recommendations:

PROSI © 2005

2.2. An architectural approachAn architectural approach: : Recommendation # 1 :Recommendation # 1 :

Use standards to have full Use standards to have full control on the exchanges control on the exchanges

between functional modulesbetween functional modules

PROSI © 2005

2.2. An architectural approachAn architectural approach: : Recommendation # 1 :Recommendation # 1 :Use standards to have full control on the exchanges between Use standards to have full control on the exchanges between functional modulesfunctional modules

Domain of the industrial proprietary Domain of the industrial proprietary technologiestechnologies

Domain under control of the local Domain under control of the local organizationorganization

Functional module

Environment

Control

Data Data according to according to

standardsstandards

Data Data according to according to

standardsstandards

Fu

ncti

on

al

modu

le

Fu

ncti

on

al

modu

le

PROSI © 2005 2.2. An architectural approach An architectural approach Recommendation # 1 :Recommendation # 1 :Use standards to have full control on the exchanges between Use standards to have full control on the exchanges between functional modulesfunctional modules

By standards it is meant:By standards it is meant:1.1. International standardsInternational standards (ISO, ETSI, …) (ISO, ETSI, …)

2.2. National standardsNational standards (DIN, AFNOR, ANSI, …) (DIN, AFNOR, ANSI, …)

3.3. Industrial & Community standardsIndustrial & Community standards(DVD-R, CD-R, RDF, Dublin Core, OAIS, METS, MXF, AAF, …):(DVD-R, CD-R, RDF, Dublin Core, OAIS, METS, MXF, AAF, …):They are standards backed by a large number of major actors of the domainThey are standards backed by a large number of major actors of the domain

4.4. Industrial standards backed by International or National Industrial standards backed by International or National StandardsStandards (DVB → ETSI) (DVB → ETSI)

5.5. Local standardsLocal standards: : They are standards valid in a specific environment They are standards valid in a specific environment (BLAP-S is a (BLAP-S is a local standard of the British Library for the creation of metadata in the Audio local standard of the British Library for the creation of metadata in the Audio sector; it is the definition of a Dublin Core Profile with possible MARC relators)sector; it is the definition of a Dublin Core Profile with possible MARC relators)

Remark: Remark: If ‘proprietary formats’ have to be included in the exchanges between modules, If ‘proprietary formats’ have to be included in the exchanges between modules,

they will be they will be encapsulated encapsulated and cloned by a and cloned by a proxy. proxy.

PROSI © 2005

The ISO MPEG group cares that each new MPEG standard is upward compatible and/or consistent with all previous MPEG standards:

MPEG 4 “understand" MPEG2 and MPEG1

MPEG 21 “manage” contents coded according to MPEG1, MPEG2 and MPEG4Future MPEG group activities

The ISO MPEG group cares that each new MPEG standard is backed by the main actors of the IT industry through the

PROSI © 2005

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation # 2 :Recommendation # 2 :

Adopt the SIP, DIP, AIP architectureAdopt the SIP, DIP, AIP architectureof the OAIS modelof the OAIS model

OAIS:OAIS: OOpenpen A Archivalrchival I Information nformation SSystemystemSIP: SIP: SSubmission ubmission IInformation nformation PPackageackageDIP: DIP: DDissemination issemination IInformation nformation PPackageackageAIP:AIP: AArchival rchival IInformation nformation PPackageackage

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation # 2 :Recommendation # 2 : Adopt the SIP, DIP, AIP architecture of the Adopt the SIP, DIP, AIP architecture of the OAIS modelOAIS model

SIPSIP DIPDIPMain Operations AMS

/ CMS / WEB/ …& Preservation

planning

Logistic of the archives

User /Custom

er

Creation &

Acquisition

AIPAIP

Management

OAISOAISmodelmodel


PROSI © 2005


Preservation

Description

Information

Content Informati

on

Package # nPackage # n

Packaging Information

InformationInformation PackagePackageConcepts & RelationshipsConcepts & Relationships

Descriptive

Information

aboutPackage

#n

AccessQueries

Descriptive

Information

aboutPackage

#n

Descriptive

Information

aboutPackage

#n

PROSI © 2005


The detailed OAIS functional modelThe detailed OAIS functional model

PROSI © 2005


PROSI © 2005

2.2.An architectural approach An architectural approach Recommendation # 3 :Recommendation # 3 :

Construct ‘Logical Entities’ from Construct ‘Logical Entities’ from ‘Physical Entities’ using ‘Proxies’‘Physical Entities’ using ‘Proxies’

& vice-versa& vice-versa

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation Recommendation # 3 :# 3 : Construct ‘Logical Entities’ from ‘Physical Entities’ using Construct ‘Logical Entities’ from ‘Physical Entities’ using ‘Proxies’ & vice-versa‘Proxies’ & vice-versa

‘‘Physical Entities’ Physical Entities’ are physical objects carrying ‘Logical are physical objects carrying ‘Logical Entities’ or part of them Entities’ or part of them

‘‘Logical Entities’Logical Entities’are semantic objects are semantic objects (usually called ‘OPUS’ or (usually called ‘OPUS’ or

‘Works’)‘Works’) modeled and represented modeled and represented independently of any “data carrier” independently of any “data carrier”

PROSI © 2005

For example:For example:• On a Microgroove disk On a Microgroove disk (Physical object)(Physical object)

could be recorded pieces of music could be recorded pieces of music composed by W. A. Mozart and by J.S. composed by W. A. Mozart and by J.S. Bach.Bach.Themselves, they could have two Themselves, they could have two movements on face and the last one on the movements on face and the last one on the other faceother faceThe Microgroove disk have its The Microgroove disk have its metadata metadata

printed on its containerprinted on its container• The “Toccata & fugue in d-moll of J.S. Bach The “Toccata & fugue in d-moll of J.S. Bach

is an ‘OPUS’ is an ‘OPUS’ (Logical object)(Logical object) with three with three movements. movements.


PROSI © 2005

• The most easy and general way to isolate, annotate The most easy and general way to isolate, annotate and structure the Logical Entities is to use ‘Proxies’.and structure the Logical Entities is to use ‘Proxies’.

• The Proxy represents the Physical Masters “one-to-The Proxy represents the Physical Masters “one-to-one”.one”.

• A ‘Clip Manager’ generate a file expressing the A ‘Clip Manager’ generate a file expressing the fusions, prunings, segmentations, punctuations, fusions, prunings, segmentations, punctuations, structuring, annotations, … structuring, annotations, …

• The AIP’s are structured according to the LOGICAL The AIP’s are structured according to the LOGICAL structure, i.e. each Package contains an integer structure, i.e. each Package contains an integer number of Logical entities number of Logical entities

Note:Note: In the AIDAR project, a two pass process In the AIDAR project, a two pass process assists the Clip Manager for restructuring by assists the Clip Manager for restructuring by ‘‘Computer Aided Sound and Voice Computer Aided Sound and Voice recognition’ recognition’


PROSI © 2005

DIPDIPUser /Customer

Logistic of the archives

AIPAIP

SIPSIPCreation

& Acquisiti

on

Management

Physical to & from Logical

OAISOAISmodelmodel



Main Operations AMS

/ CMS / WEB/ …& Preservation

planning

PROSI © 2005


Plan the capacity to deliver the Plan the capacity to deliver the DIP through various channelsDIP through various channels

PROSI © 20052.2. An architectural approach An architectural approach Recommendation # 4 :Recommendation # 4 : Plan the capacity to deliver the DIP through Plan the capacity to deliver the DIP through various channelsvarious channels

The core of the IT system should allow that the DIP The core of the IT system should allow that the DIP could be delivered in many different channels or could be delivered in many different channels or carriers.carriers.

This means ‘open-ended-ness’This means ‘open-ended-ness’

For example:For example:By Internet through WEB sitesBy Internet through WEB sitesBy Internet through FTPBy Internet through FTPBy BroadcastBy BroadcastOn nomadic carriers (DVD’s, CD-Audio, …)On nomadic carriers (DVD’s, CD-Audio, …)

If the AIP’s are structured according If the AIP’s are structured according to the ‘Logical Entities’, that to the ‘Logical Entities’, that flexibility is a ‘build-in’ !flexibility is a ‘build-in’ !

PROSI © 2005


Trace always the “Packages”Trace always the “Packages”

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation # 5 :Recommendation # 5 : Trace always the “Packages”Trace always the “Packages”

All ‘Packages’ imported or exported in or from the All ‘Packages’ imported or exported in or from the operational units should be traced for existence, operational units should be traced for existence, channels, carriers, property rights, usage rights, channels, carriers, property rights, usage rights, occurrences of use, … :occurrences of use, … :

Examples of concrete approaches:Examples of concrete approaches:The MPEG-21 standardThe MPEG-21 standardThe Certificates of TraceabilityThe Certificates of TraceabilityThe steganographic Water MarkingThe steganographic Water Marking

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation Recommendation # 6 :# 6 :

Create “Collection profiles” to Create “Collection profiles” to enable “Autonomous Assets enable “Autonomous Assets

Entities”Entities”

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation Recommendation # 6 :# 6 : Create “Collection profiles” to enable “Autonomous Create “Collection profiles” to enable “Autonomous Assets Entities”Assets Entities”

A ‘Collection Profile’ defines how to bundle several A ‘Collection Profile’ defines how to bundle several standards to construct representations of the standards to construct representations of the information having specific properties in mind.information having specific properties in mind.

The ‘The ‘AAutonomous utonomous AAssets ssets EEntities’ntities’ are instances of are instances of ‘Collection Profiles’ defined by standards ‘Collection Profiles’ defined by standards

Example of a concrete ‘Collection Profile’:Example of a concrete ‘Collection Profile’:The combination of the use ofThe combination of the use of

MPEG-4, RDF, Dublin Core, SMIL, ID3, XML, MPEG21, MPEG-4, RDF, Dublin Core, SMIL, ID3, XML, MPEG21, UDF, PDF … UDF, PDF …

The concept of AAE is the essential component of the The concept of AAE is the essential component of the management of the persistence and of the flexibility management of the persistence and of the flexibility in exploitation.in exploitation.

PROSI © 2005


Create the AIP’s as sets of Create the AIP’s as sets of “Autonomous Assets Entities”“Autonomous Assets Entities”

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation Recommendation # 7 :# 7 : Create the AIP’s as sets of Create the AIP’s as sets of ““AAutonomous utonomous AAssets ssets EEntities”ntities”

The ‘ARCHIVES’ are usually organized per type of The ‘ARCHIVES’ are usually organized per type of files or per proprietary ‘Back-up’ format and the files or per proprietary ‘Back-up’ format and the preservation plan is simply the conversion of preservation plan is simply the conversion of formats per type of file. formats per type of file.

The Assets Management System should organize The Assets Management System should organize or construct the ‘Aor construct the ‘Archivalrchival I Informationnformation P Packagesackages’ ’ as structured sets of ‘as structured sets of ‘AAutonomous utonomous AAssets ssets EEntities’ntities’..

The advantage is that the The advantage is that the PERSISTENCEPERSISTENCE construction can be enabled, immediately or construction can be enabled, immediately or later! This will be developed by the later! This will be developed by the recommendation # 8. recommendation # 8.

PROSI © 2005

2.2. An architectural approach An architectural approach Recommendation Recommendation # 7 :# 7 : Create the AIP’s as sets of Create the AIP’s as sets of ““AAutonomous utonomous AAssets ssets EEntities”ntities”

The ‘AIP’ is organized as a mini-module The ‘AIP’ is organized as a mini-module including all information pertinent for one or including all information pertinent for one or more OPUS’s:more OPUS’s:

• OPUSOPUS• ClipClip• PackagePackage• ProjectProject• ResourcesResources

• MEDIAMEDIA• REPOSITORYREPOSITORY

• ProfilesProfiles• ThesaurusThesaurus• Identification Identification

PROSI © 2005


Manage the persistence of the Manage the persistence of the AIP’sAIP’s

through the AAE’sthrough the AAE’s

PROSI © 2005


Manage the persistence of the AIP’s Manage the persistence of the AIP’s through the AAE’sthrough the AAE’s

The elaboration of the “Preservation planning” is not obvious!The elaboration of the “Preservation planning” is not obvious!

The ‘AThe ‘Archivalrchival I Informationnformation P Packagesackages’ are usually spread on a large ’ are usually spread on a large variety of carriers. The persistence requires re-bundling tools, to be variety of carriers. The persistence requires re-bundling tools, to be used when a need to access is expressed!used when a need to access is expressed!

An active An active technology watchtechnology watch based on based on “Collection Profiles”“Collection Profiles” is is far better! It preventsfar better! It prevents

• The obsolescence of the carriersThe obsolescence of the carriers• The obsolescence of the formatsThe obsolescence of the formats• The consequences of the changes of polices of the The consequences of the changes of polices of the

supplierssuppliers

The active technology watch based on such an The active technology watch based on such an approachapproach simplifies and automates simplifies and automates the the construction of the persistence!construction of the persistence!The theoretical grounds of that assurance are now well known: The theoretical grounds of that assurance are now well known: see references at the end see references at the end ((ISO/IEC ISP 35100 & ULB paper on layeringISO/IEC ISP 35100 & ULB paper on layering)). .

PROSI © 2005

AIP AIP (AAE)(AAE)(according to the(according to thetoday’s profiles)today’s profiles)

Creation &

Acquisition

SIPSIP Main

Operations

DIPDIP

The SIP – DIP – AIP flows of The SIP – DIP – AIP flows of

todaytoday

Logistics of the archives & Technology WatchLogistics of the archives & Technology Watch

Creation &

Acquisition

SIPSIP Main

Operations

DIPDIP

AIPAIP (AAE) (AAE)(according to the past’s profiles)(according to the past’s profiles)

The SIP – DIP – AIP flows of The SIP – DIP – AIP flows of

thethe pastpast

OAIS ModelOAIS Model

AIP AIP (AAE)(AAE)(according to the(according to the

past’s profiles)past’s profiles)

OAIS ModelOAIS Model

Check of the AIP Check of the AIP (AAE)(AAE) against past profiles against past profiles

Transcoding to the new profiles with zero, or better negative, entropy lossTranscoding to the new profiles with zero, or better negative, entropy loss


Manage the persistence of the AIP’s Manage the persistence of the AIP’s through the AAE’sthrough the AAE’s

PROSI © 2005

Hu

man

p

erc

ep

tion

Tra

nsd

uce

rS

cie

nce &

T

ech

niq

ues

Info

rmati

on

T

ech

nolo

gi

es

Hu

man

in

terp

reta

tio

n

Information

Evidence

Data

Carrier

Nature

Substance

OccurrencesOccurrences

ProcessesProcesses

Projects

Semiotics

Standards

Standards

Models

Culture

ConventionsConventions

Hu

man

p

erc

ep

tion

Tra

nsd

uce

rS

cie

nce &

T

ech

niq

ues

Info

rmati

on

T

ech

nolo

gi

es

Hu

man

in

terp

reta

tio

n

Information

Evidence

Data

Carrier

Substance

OccurrencesOccurrences

ProcessesProcesses

Projects

Semiotics

Standards

Standards

Models

Culture

ConventionsConventions

OrthogonalityOrthogonality

Substance Substance versus versus DataData

OrthogonalityOrthogonality

Data Data versus Carrierversus Carrier

OSI approach (ISO/IEC ISP 35100) adapted to the AIP being AAE’sOSI approach (ISO/IEC ISP 35100) adapted to the AIP being AAE’s

PROSI © 2005

2.2.An architectural approach An architectural approach Recommendation # Recommendation # 9 :9 :

Manage the off-line conservation of Manage the off-line conservation of the AIP’sthe AIP’s

PROSI © 2005


Manage the off-line conservation of the Manage the off-line conservation of the AIP’sAIP’s

The ‘AThe ‘Archivalrchival I Informationnformation P Packagesackages’ should be ’ should be generated in several nomadic copies (DVD’s, Tapes, generated in several nomadic copies (DVD’s, Tapes, …) for redundancy…) for redundancy

An Active Remote Center should manage ‘near-on-An Active Remote Center should manage ‘near-on-line’ archive service in area adapted for the correct line’ archive service in area adapted for the correct conservation of the carriers.conservation of the carriers.

The identification system of the AIP’s should be The identification system of the AIP’s should be based on three independent identifiers:based on three independent identifiers:

• Carrier identifierCarrier identifier• Contents identifierContents identifier• Location identifierLocation identifier

PROSI © 2005

2.2.An architectural approach An architectural approach Recommendation # Recommendation # 10 :10 :

Adopt the previous recommendations Adopt the previous recommendations for your “Functional modules” and for your “Functional modules” and

“AIP’s”“AIP’s”

PROSI © 2005

2.2.An architectural approach An architectural approach Recommendation # Recommendation # 10 :10 : Adopt the previous recommendations for your “Functional Adopt the previous recommendations for your “Functional modules” and “AIP’s” modules” and “AIP’s”

The key concept is to construct all the ‘Functional The key concept is to construct all the ‘Functional Modules’ as Autonomous Entities which manage as well Modules’ as Autonomous Entities which manage as well the the

• The ‘Autonomous Assets Entities’The ‘Autonomous Assets Entities’

• The ‘Packages’ andThe ‘Packages’ and

• The local Repository of the used standards (including The local Repository of the used standards (including the profiles)the profiles)

The ‘FThe ‘Functionalunctional M Modulesodules’ are ‘A’ are ‘Active ctive FFunctional unctional MModulesodules’, including ’, including the ‘Athe ‘Acquisitioncquisition’.’.

The ‘AThe ‘Archivalrchival I Informationnformation P Packagesackages’ are ‘P’ are ‘Passive assive FFunctional unctional MModulesodules’’

PROSI © 2005


Creation &

Acquisition

SIPSIP Main

Operations

DIPDIP

The SIP – DIP – AIP flows in the The SIP – DIP – AIP flows in the module module # n# n

OAIS* ModelOAIS* Model OAIS* ModelOAIS* Model


The SIP – DIP – AIP flows in oneThe SIP – DIP – AIP flows in one

modulemodule

What is applied for transfer from the “PAST” to What is applied for transfer from the “PAST” to “TODAY” in the recommendation 8, can be applied to “TODAY” in the recommendation 8, can be applied to the transfer between “MODULES” the transfer between “MODULES”

AIP AIP (AAE)(AAE)(according to the(according to thelocal profiles)local profiles)

Creation &

Acquisition

SIPSIP Main

Operations


local profiles)local profiles)

DIPDIP

The SIP – DIP – AIP flows in the The SIP – DIP – AIP flows in the module module # p# p


local profiles)local profiles)

PROSI © 2005



F.M. # s

AIP-Archive

DIPDIP

F.M. # r

AIP-Archive

DIPDIP

AIPAIP

OAIS*OAIS* OAIS*OAIS*

Functional

Module

# n

Original IPOriginal IP

SIPSIP

DIPDIP

Original IPOriginal IP

SIPSIP AIPAIPFunctional

Module

# p

Functional

Module

# q

AIPAIP

AIPAIP

Generalization : Handling of the Original Generalization : Handling of the Original IP’sIP’s

PROSI © 2005

1.1.Missions & RequirementsMissions & Requirements2.2.An architectural approachAn architectural approach3.3.The AXIS key featuresThe AXIS key features4.4.The “Open Licensing of AXIS” by The “Open Licensing of AXIS” by

TITANTITAN5.5.Conclusions & AcknowledgementsConclusions & Acknowledgements


PROSI © 2005

Présentation générale dePrésentation générale del’architecture d’AXISl’architecture d’AXISAAcquisition, ecquisition, eXXchange, change, IIndexingndexing, ,

SStructurationtructuration

PROSI © 2005

Application AApplication A InterchangeInterchange Application BApplication B

NormesNormesStandardsStandards

Personnalisations formaliséePersonnalisations formalisée

AXISAXIS

ValeurValeurajoutéeajoutée

ValeurValeurajoutéeajoutée

AXIS : AXIS : Une ‘interaction’ basée sur des définitions formellesUne ‘interaction’ basée sur des définitions formelles

PROSI © 2005

Acquisition & Enrichment Systems Acquisition & Enrichment Systems

X-AXIS X-AXIS (FFH)(FFH)

Mod

ule

/Op

us/

Med

ia/R

epos

itor

y in

FF

HM

odu

le/O

pu

s/M

edia

/Rep

osit

ory

in F

FH

AXIS PlatformAXIS Platform

X-AXIS X-AXIS ((Wrapped packageWrapped package))

ApplicationsApplications

AXIS ManagerAXIS Manager SDK-exportSDK-export

. mxf /. mxf /

. zip /. zip /

. mets /. mets / … …

DIPDIPAIPAIP

. mxf /. mxf /

. zip /. zip /


ExploitationsExploitations

DIPDIPSIPSIPAIPAIP

DAMDAMMAMMAMCMSCMS

……

SIPSIP

SDK-importSDK-import

MediaMediaacquisitionacquisition

Original Information PackageOriginal Information PackageDigital source Digital source (Camera, …)(Camera, …)

AnalogueAnalogue source source

OIPOIP

PROSI © 2005

Les « Les « EntitésEntités » d’AXIS » d’AXIS

Dans AXIS tout ce qui peut être considéré comme une Dans AXIS tout ce qui peut être considéré comme une ressource ressource (au sens du RDF)(au sens du RDF) est représenté sous forme est représenté sous forme d’une d’une ‘ENTITE’‘ENTITE’ : :•Chaque ‘unité’ de Chaque ‘unité’ de travailtravail ou d’ ou d’interchangeinterchange est une entité du type est une entité du type

:: MODULEMODULE•Chaque MODULE est accompagné des information de Chaque MODULE est accompagné des information de

compréhension, de persistance, des méta-méta définitions, … compréhension, de persistance, des méta-méta définitions, … pertinents pour ce MODULE dans une entité du type pertinents pour ce MODULE dans une entité du type ::

REPOSITORYREPOSITORY•Les ‘Les ‘représentation audio, vidéo, image, texte, modèle 3D, …représentation audio, vidéo, image, texte, modèle 3D, …’ est ’ est

une entité du type une entité du type ::

MEDIAMEDIA•Chaque ‘Chaque ‘représentation d’une intentionreprésentation d’une intention’ est une entité du type ’ est une entité du type ::

OPUSOPUS

PROSI © 2005

Les « Les « EntitésEntités » d’AXIS » d’AXIS

Chaque ‘Chaque ‘représentation d’une intentionreprésentation d’une intention’ est une entité du type ’ est une entité du type ::

OPUSOPUSLes OPUS peuvent être représentés par cinq aspects orthogonaux :Les OPUS peuvent être représentés par cinq aspects orthogonaux :•Une entité permettant d’identifier, définir, structurer, indexer, Une entité permettant d’identifier, définir, structurer, indexer,

synchroniser, … les processus prévus pour réaliser l’OPUS : synchroniser, … les processus prévus pour réaliser l’OPUS : Cette entité est du type Cette entité est du type :: PROJECTPROJECT

•Une (ou plusieurs) entité(s) permettant d’identifier, définir, Une (ou plusieurs) entité(s) permettant d’identifier, définir, structurer, indexer, synchroniser, … un ou plusieurs MEDIA : structurer, indexer, synchroniser, … un ou plusieurs MEDIA : Cette entité est du typeCette entité est du type:: CLIPCLIP

•Une (ou plusieurs) entité(s) permettant d’identifier, définir, Une (ou plusieurs) entité(s) permettant d’identifier, définir, structurer, indexer, synchroniser, … les moyens nécessaires à la structurer, indexer, synchroniser, … les moyens nécessaires à la réalisation de l’OPUS : réalisation de l’OPUS : RESOURCERESOURCE

•Une (ou plusieurs) entité(s) permettant de définir, protéger, Une (ou plusieurs) entité(s) permettant de définir, protéger, tracer,… les exports et imports du MODULE, exprimés comme tracer,… les exports et imports du MODULE, exprimés comme des projets en soi (la définition d’un AIP, d’un SIP ou d’un SIP, des projets en soi (la définition d’un AIP, d’un SIP ou d’un SIP, …) d’un OPUS (dans le cas des AEE, c’est l’OPUS cible) :…) d’un OPUS (dans le cas des AEE, c’est l’OPUS cible) :

PACKAGEPACKAGE•Une (ou plusieurs) entité(s) du type :Une (ou plusieurs) entité(s) du type :

OPUSOPUS

PROSI © 2005

Les « NORMES ARCHITECTURALES » Les « NORMES ARCHITECTURALES » d’AXISd’AXIS

Les normes de l’Les normes de l’ossatureossature d’AXIS sont les d’AXIS sont les suivantes:suivantes:1.1. OAIS OAIS

(ISO, CCSDS)(ISO, CCSDS)2.2. Dossiers, Fichiers, Hyperliens Dossiers, Fichiers, Hyperliens

(Normes ISO)(Normes ISO)3.3. XML / XSDXML / XSD

(ISO, W3C)(ISO, W3C)4.4. Dublin Core Metadata InitiativeDublin Core Metadata Initiative

(DCMI, W3C, JISC, …)(DCMI, W3C, JISC, …)5.5. RDF RDF

(W3C)(W3C)6.6. SMIL SMIL

(W3C)(W3C)7.7. MXF MXF

(SMPTE, ANSI, ISO)(SMPTE, ANSI, ISO)8.8. METS METS

(MARC Standards Office, W3C)(MARC Standards Office, W3C)9.9. ZIP ZIP (ADOBE / ANSI Standards )(ADOBE / ANSI Standards )

PROSI © 2005

Le concept de Le concept de ““ PLANEPLANE ” ” dans AXISdans AXIS

Dans une ‘ENTITE’, des data sets peuvent être Dans une ‘ENTITE’, des data sets peuvent être instanciés :instanciés :• En plusieurs langues (L)En plusieurs langues (L)• En plusieurs qualités de représentation (Q)En plusieurs qualités de représentation (Q)• En plusieurs formats (normes/standards) (F)En plusieurs formats (normes/standards) (F)

Chaque instance fait partie d’un ‘plane’ qui reçoit un Chaque instance fait partie d’un ‘plane’ qui reçoit un attribut LQF.attribut LQF.

Exemples : Exemples : La même information pourrait être disponible en La même information pourrait être disponible en français et en anglais ;français et en anglais ;

Le même son pourrait être disponible à divers Le même son pourrait être disponible à divers niveaux de qualité dans le même format ;niveaux de qualité dans le même format ;

Le même son pourrait être représenté dans divers Le même son pourrait être représenté dans divers formats.formats.

Le concept de ‘plane’ permet d’activer des ensembles Le concept de ‘plane’ permet d’activer des ensembles cohérents de données dans contexte des spécificités de cohérents de données dans contexte des spécificités de mise en œuvre de chaque projet.mise en œuvre de chaque projet.

PROSI © 2005

Le concept de Le concept de ““ PROFILPROFIL ” ” dans AXISdans AXISEn choisissant un ensemble de formats de En choisissant un ensemble de formats de

représentation, avec un choix de paramètres, l’on représentation, avec un choix de paramètres, l’on obtient la capacité de représenter l’information pour obtient la capacité de représenter l’information pour une classe d’applications; de nombreux usages sont une classe d’applications; de nombreux usages sont possibles. Ce choix s’appelle un ‘profil’.possibles. Ce choix s’appelle un ‘profil’.

Exemple du profil noyau d’AXIS :Exemple du profil noyau d’AXIS :

http://www.titan/axis/documents/axis-cap-fre-v00/http://www.titan/axis/documents/axis-cap-fre-v00/ Qui définit comment organiser d’assembler des contenus d’Qui définit comment organiser d’assembler des contenus d’Opus, Opus, desdes PackagesPackages et de et de RepositoryRepository dans un Module ainsi que les relations entre dans un Module ainsi que les relations entre les entités (aci) qui défini comment organiser de mettre ensemble dans les entités (aci) qui défini comment organiser de mettre ensemble dans un seul clip des fichiers et les indexer :un seul clip des fichiers et les indexer :

[.xml + .xsd + .wav [.xml + .xsd + .wav (+ chunck parameters)(+ chunck parameters) .mp4 + .jpg + .smil + .pdf ] + .mp4 + .jpg + .smil + .pdf ] + [ [ rulesrules & & semanticssemantics]]

PROSI © 2005 Le concept de Le concept de ““ PROFILPROFIL ” ” dans AXISdans AXIS

The 15 ‘elements’ of the Dublin CoreThe 15 ‘elements’ of the Dublin Core

1.1. TitleTitle2.2. Creator (or Author)Creator (or Author)3.3. Subject (and Keywords)Subject (and Keywords)4.4. Description Description 5.5. Publisher Publisher 6.6. Contributors Contributors (other)(other)7.7. DateDate8.8. Type Type (The category of the resource, such as homepage, (The category of the resource, such as homepage,

novel, poem,...)novel, poem,...)9.9. Format Format (The data representation of the resource)(The data representation of the resource)10.10.IdentifierIdentifier11.11.SourceSource12.12.LanguageLanguage13.13.RelationRelation14.14.CoverageCoverage15.15.RightsRights

PROSI © 2005

The ‘qualified elements’ of the Dublin-Core for the Axis-Core The ‘qualified elements’ of the Dublin-Core for the Axis-Core Dublin CoreDublin Core AXIS Core Application AXIS Core Application ProfileProfileElement-nameElement-name Element-nameElement-name

Comments / property / …Comments / property / …

TitleTitle titletitleMax 255 charactersMax 255 characters

titleShorttitleShortMax 30 charactersMax 30 characters

CreatorCreator authorauthorSubjectSubject subjectsubject

List of the applicable Textual & Sound Thesauri List of the applicable Textual & Sound Thesauri

DescriptionDescription descriptiondescriptionPublisher Publisher publisherpublisherContributorsContributors <see appending list><see appending list>DateDate creationDatecreationDateTypeType entityClassentityClass

Module, Repository, Opus, Package, Opus-Stream, Module, Repository, Opus, Package, Opus-Stream, Opus-Source Audio-Clip, Audio-Clip-Component, Audio-Opus-Source Audio-Clip, Audio-Clip-Component, Audio-Clip-Stream, … Clip-Stream, …

entityStatusentityStatusPreliminary, Temporary, … , validated, … Preliminary, Temporary, … , validated, …

Released Released FormatFormat formatformat

suffixsuffixqualityquality

IdentifierIdentifier moduleIdmoduleIdURI (W3C)URI (W3C)

creationModulecreationModulerootIdrootIdtagIdtagId

W3C-SMILW3C-SMILdomainIddomainIdversionversion

SourceSource sourcesource

LanguageLanguage languagelanguageISO639-3ACISO639-3AC

RelationRelation isPartOfisPartOfhasParthasPart<all RDF relations><all RDF relations>

W3C …W3C …CoverageCoverage country, place, locationcountry, place, location

ISO3166ISO3166timeCode, periodCodetimeCode, periodCode

W3CDTFW3CDTF

rootIndex, componentIdrootIndex, componentId<chaining-code> <chaining-code>

W3C-SMILW3C-SMILduplicationIndexduplicationIndexnaturalLanguagenaturalLanguage

RightsRights originalRightsOwneroriginalRightsOwnercurrentRightsOwnercurrentRightsOwner

PROSI © 2005 Définition formalisée ISO d’un ‘Définition formalisée ISO d’un ‘qualified termqualified term’’AXIS-CAP (Core Application Profile)AXIS-CAP (Core Application Profile)

Term Name: identifierTerm Name: identifierDublin Core entryDublin Core entry

Term URI: Term URI: http://purl.org/dc/elements/1.1/identifier http://purl.org/dc/elements/1.1/identifier Label: Label: Resource IdentifierResource IdentifierDefined by:Defined by: http://purl.org/dc/documents/dcmi-terms/http://purl.org/dc/documents/dcmi-terms/Source Definition: Source Definition: An unambiguous reference to the resource within a An unambiguous reference to the resource within a

given context.given context.Source Comment: Source Comment: Recommended best practice is to identify the resource Recommended best practice is to identify the resource

by means of a string or number conforming to a formal identification system. Example by means of a string or number conforming to a formal identification system. Example formal identification systems include the Uniform Resource Identifier (URI) (including formal identification systems include the Uniform Resource Identifier (URI) (including the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the the Uniform Resource Locator (URL)), the Digital Object Identifier (DOI) and the International Standard Book Number (ISBN).International Standard Book Number (ISBN).

Qualification in the ‘Namespace’ of the ‘Core Axis Profile” [xmlns:axis-Qualification in the ‘Namespace’ of the ‘Core Axis Profile” [xmlns:axis-cap]cap]

AXIS-CAP definition:AXIS-CAP definition: The resource identified according to the rules of The resource identified according to the rules of AXIS-CIF AXIS-CIF

AXIS-CAP comment:AXIS-CAP comment: The identification of the resources is structured The identification of the resources is structured according to the “Collection Based” approach. The context is given by the value of [axis-according to the “Collection Based” approach. The context is given by the value of [axis-cap:module]. Each “entity-class” has its own encoding scheme.cap:module]. Each “entity-class” has its own encoding scheme.

Type of Term: Type of Term: element element Refines:Refines: identifieridentifierRefined by:Refined by:Has encoding schemeHas encoding scheme http://www.titan.org/axis/documents/axis-cif/...http://www.titan.org/axis/documents/axis-cif/...Status: Status: Mandatory for the each instance of a “entity-class”. Mandatory for the each instance of a “entity-class”.

Recommended in the other cases.Recommended in the other cases.Date Issued: Date Issued: 2005-04272005-0427

PROSI © 2005 Définition formalisée ISO d’un ‘Définition formalisée ISO d’un ‘EncodingEncoding SchemeScheme’ ’ dans undans un

‘‘qualified termqualified term’ de ’ de AXIS-CAP (Core Application AXIS-CAP (Core Application Profile)Profile)Encoding SchemesEncoding Schemes

They are defined by reference to a ‘standard’, local definition or to a ‘thesaurus’ (list of They are defined by reference to a ‘standard’, local definition or to a ‘thesaurus’ (list of possible/suggested values or rule)possible/suggested values or rule)

Standards:Standards:

DCMI-Type: DCMI-Type: DC list of types used to characterize the nature or genre of DC list of types used to characterize the nature or genre of the content of the resourcethe content of the resource

http://purl.org/dc/dcmitype/URIhttp://purl.org/dc/dcmitype/URIOpen-URL:Open-URL: NISO…NISO…URIURI W3C …W3C …ISO3166ISO3166 Code for the representation of the names of the countriesCode for the representation of the names of the countriesISO639-3ACISO639-3AC Code for the representation of the names of the languagesCode for the representation of the names of the languagesW3CDTFW3CDTF Code for the representation of the dates, times and periodsCode for the representation of the dates, times and periodsISSNISSN International Standard Serial NumbersInternational Standard Serial NumbersXMLXML ISO 8859-1 ISO 8859-1 (à vérifier)(à vérifier)

…… <<International Thesaurus>International Thesaurus>

AXIS-CoreAXIS-CoreAXIS-Type:AXIS-Type: AXIS list of type codes used to characterize the nature, AXIS list of type codes used to characterize the nature, roles or genre of the content of the resourceroles or genre of the content of the resource

http://www.titan/axis/axistype/URIhttp://www.titan/axis/axistype/URIAXIS-ThesaurusAXIS-Thesaurus AXIS list of key-entries and valuesAXIS list of key-entries and values

http://www.titan/axis/axisthesaurus/URIhttp://www.titan/axis/axisthesaurus/URI

PROSI © 2005

Concepts fondamentaux des Concepts fondamentaux des documentsdocuments

Les documents sont représentés par des ensembles structurés de dossiers, fichiers et hyperliens.

Plusieurs représentations de la même ‘chose’ peuvent exister simultanément dans une instance d’un document :

par exemple, une représentation d’un clip audio peut être disponible en .bwf, .wav, .wma, .mp3, … et, chacune, à divers débits binaires

Un document couvre ce qui se rapporte à une réalité « spatiale, temporelle et spatiale, temporelle et sémantiquesémantique » UNIQUE

PROSI © 2005

Formats fondamentaux de représentation des Formats fondamentaux de représentation des DocumentsDocuments

Format source (normalisé, standardisé ou non)Formats normalisés ou standardisés utilisés dans les profils• .xml / .xsd /.xslt / … • .mpg4• .jpg• .pdf• .wav .bwf• .mp3• .mp4• …

• Dossiers• Fichiers• Hyperliens• Synchronisations via SMIL-2• Configuration, Play lists &

Edit lists via SMIL-2 ou implicite via les ‘index’

PROSI © 2005 Schéma général des data sets Schéma général des data sets en en FFHFFHMODULE

Opus REPOSITORY

……

.afp

.afp

OpusOPUS

.afp

Clip FolderClip Folder

.amp

.app

.afp

Project FolderProject Folder

.apm

…

.afp

Package FolderPackage Folder

.act

.avv

.afp

Resource FolderResource Folder

.arm

…

…

MEDIA

Folders per Media typesFolders per Media types

.mp4

.afp

.mp4.mp4.mp4.mp4

.mp3

.mp4.mp4.mp4.mp3

.wav

.mp4.mp4.mp4.wav

Media linkMedia link

Package linkPackage link

…

.afp

Id fountain

AXIS CoreApplication

Profile

Standards& Norms

.aopObject linkObject link

.aci

ContentContent

linklink

AXIS AIDARApplication

Profile

AXIS RIMESApplication

Profile

PROSI © 2005 Naming / Identifying Naming / Identifying RulesRules

creationModuleentityClass- rootId - rootIndex FormatcomponentId qualitynaturalLanguageVersion . Suffix

Naming of Files

URI of Files

<domain> <file name>/

URI of Package

<domain> root Id

URI of Folder

<domain> <folder name>

Naming of Folders

duplication

//

URI of Package-Component within a Package-StreamURI of Opus-Component within an Opus-Stream

<domain> rootId/ rootIndexcomponentId

duplication

duplicationentityClass

entityClass-

-

-

-

<Foreign file name>

Depends on the Class of the entity

Basic part for the ID fountain

Codage : • La longueur totale de l’identifieur / nom d’un fichier ou d’un dossier serait fixée à 128

caractères (séparateurs compris)• Chaque champ est nommé dans xmlns:axisCap• Le séparateur d’isolement du ‘root-id’ est le tiret « - »• Le séparateur d’isolement des autres champs est le ‘underscore’ « _ » ; il est mis pour tous

les champs prévus pour la « entity-class », même s’ils sont vides.

. Suffix

creationModuleentityClass- rootId - rootIndexcomponentId

PROSI © 2005

Concepts fondamentaux de Concepts fondamentaux de segmentation des flux dans les segmentation des flux dans les documents du type documents du type ClipClip : :

Les ClipsLes Clips : :Un Clip est un ensemble statique de données

représentant un flux d’essences (Audio, Vidéo) sur une durée de temps. Dans AXIS, ils sont représentés soit comme des ‘fichiers’, soit comme des ‘flux’. Par ces dispositions, le ‘clip’ peut représenter des ‘albums’ (de photos, par exemple).

Les PointsLes Points : : A n’importe quel moment du flux, il y possibilité de

placer une balisebalise de Point.

Les SegmentsLes Segments : :A n’importe quels moments (non confondus) du flux, il

y a possibilité de placer un couple de balisesbalises, une de début et une de fin ; ce couple de balises défini un Segment.

PROSI © 2005

L’ L’ ‘Axis Configuration & Indexing’‘Axis Configuration & Indexing’

• Sélection de clip(s)Sélection de clip(s)• SéquençageSéquençage• Offset d’OpusOffset d’Opus• Fusion de clipFusion de clip

• SegmentationSegmentation• SynchronisationSynchronisation• PonctuationPonctuation

• ÉlagageÉlagage

• PartitionPartition en en ‘Clip-Components’‘Clip-Components’

• Chaînage deChaînage de‘‘Clip-components’ →Clip-components’ → ‘Clip’‘Clip’

‘‘Clips’ → ‘Clip-Stream’Clips’ → ‘Clip-Stream’

• Annotation Annotation de ‘Segment’, de ‘Point, de ‘Clip-Stream’, de ‘Clip’, de de ‘Segment’, de ‘Point, de ‘Clip-Stream’, de ‘Clip’, de ‘Clip-Component’‘Clip-Component’

EDL #1EDL #1 EDL #2EDL #2

EDL #3EDL #3

PROSI © 2005


Mod

ule

/Op

us/

Med

ia/R

epos

itor

y in

FF

HM

odu

le/O

pu

s/M

edia

/Rep

osit

ory

in F

FH


AXIS PlatformAXIS Platform


SDK-exportSDK-export

. mxf /. mxf /

. zip /. zip /



DIPDIPSIPSIPAIPAIP

DAMDAMMAMMAMCMSCMS

……


. mxf /. mxf /

. zip /. zip /


X-AXIS X-AXIS ((Wrapped PackageWrapped Package))

Digital source Digital source (Camera, …)(Camera, …)


ApplicationsApplications

AXIS ManagerAXIS Manager

DIPDIPAIPAIP

SIPSIP

PROSI © 2005



OSIER OSIER (Outil de Segmentation, d’Indexation et d’Edition en Réseaux)(Outil de Segmentation, d’Indexation et d’Edition en Réseaux)


Mod

ule

/Op

us/

Med

ia/R

epos

itor

y in

FF

HM

odu

le/O

pu

s/M

edia

/Rep

osit

ory

in F

FH

Audio / Vidéo / Image / Text Audio / Vidéo / Image / Text

CLIP ManagerCLIP Manager SDK-importSDK-import


. mxf /. mxf /

. zip /. zip /



DIPDIPSIPSIPAIPAIP

DAMDAMMAMMAMCMSCMS

……


. mxf /. mxf /

. zip /. zip /


X-AXIS X-AXIS ((Wrapped PackageWrapped Package))



PROSI © 2005


AIDAR ENGINEAIDAR ENGINECoreCore

Mod

ule

/Op

us/

Med

ia/R

epos

itor

y in

FF

HM

odu

le/O

pu

s/M

edia

/Rep

osit

ory

in F

FH


Voice-InsightVoice-Insight TITANTITAN


ULBULB SkemaSkema

Image CLIP ManagerImage CLIP Manager

Project & Resource ManagerProject & Resource Manager

Audio CLIP ManagerAudio CLIP Manager

……

General Product ArchitectureGeneral Product Architecture

Textual CLIP ManagerTextual CLIP Manager

Video CLIP ManagerVideo CLIP Manager

Voi

ce A

ctiv

ated

Ser

ver

Voi

ce A

ctiv

ated

Ser

ver



. mxf /. mxf /

. zip /. zip /



DIPDIPSIPSIPAIPAIP

DAMDAMMAMMAMCMSCMS

……


. mxf /. mxf /

. zip /. zip /


X-AXIS X-AXIS ((Wrapped packageWrapped package))



PROSI © 2005

1.1.Missions & RequirementsMissions & Requirements2.2.An architectural approachAn architectural approach3.3.The AXIS key featuresThe AXIS key features4.4.The “Open Licensing of AXIS” by The “Open Licensing of AXIS” by

TITANTITAN5.5.Conclusions & AcknowledgementsConclusions & Acknowledgements


PROSI © 2005

L’intention de TITAN est de mettre à L’intention de TITAN est de mettre à disposition, sous licence ouverte, de :disposition, sous licence ouverte, de :• La spécification de l’architecture AXISLa spécification de l’architecture AXIS• La définition technique d’AXIS (statique La définition technique d’AXIS (statique et dynamique)et dynamique)• Le code source des SDK de Le code source des SDK de parsing parsing et et assemblage.assemblage.

Cette licence sera définie sur base de la licence Cette licence sera définie sur base de la licence générique rédigée par le Centre de Recherches en générique rédigée par le Centre de Recherches en Informatique et Droit (CRID) des Facultés Informatique et Droit (CRID) des Facultés Universitaires Notre-Dame de la Paix (FUND) à Universitaires Notre-Dame de la Paix (FUND) à Namur.Namur.

Cette licence implique un droit d’usage gratuit si Cette licence implique un droit d’usage gratuit si certaines conditions de modes d’exploitations sont certaines conditions de modes d’exploitations sont remplies. Toutes applications (industrielles ou remplies. Toutes applications (industrielles ou autres) sont couvertes. autres) sont couvertes.

PROSI © 2005



PROSI © 2005

THANKS & THANKS & ACKNOWLEDGMENTSACKNOWLEDGMENTS

I would like to express my thanks to all the persons I would like to express my thanks to all the persons having contributed directly or indirectly to my having contributed directly or indirectly to my contribution to this TITAN ACF conference.contribution to this TITAN ACF conference.

In particular, I address my thanks & acknowledgments In particular, I address my thanks & acknowledgments to:to:

TITAN, TITAN, in particular to M. Roger Robertsin particular to M. Roger Roberts

MEMNON, MEMNON, in particular to M. Michel Mertenin particular to M. Michel Merten

The BRITISH LIBRARY, The BRITISH LIBRARY, in particular to MM. Peter Findlay, Chris Clark in particular to MM. Peter Findlay, Chris Clark andand Crispin JewittCrispin Jewitt

The BBC, The BBC, in particular to Mrs. Sue Malden (past manager of the BBC in particular to Mrs. Sue Malden (past manager of the BBC archiving services)archiving services)

PROSI © 2005

CONCLUSIONSCONCLUSIONS““Good solutions are affordableGood solutions are affordable””

Realistic approaches can be found to meet the Realistic approaches can be found to meet the evolving requirements evolving requirements

of the USERS and/or CUSTOMERS of the archives;of the USERS and/or CUSTOMERS of the archives;

of the ARCHIVES, as custodian of the Social and of the ARCHIVES, as custodian of the Social and Cultural heritagesCultural heritages

Each large organization should construct its ownEach large organization should construct its own

‘‘strict guidelines’strict guidelines’• Fitting with its Missions & Constrains andFitting with its Missions & Constrains and• Having the OAIS model in sight.Having the OAIS model in sight.

PROSI © 2005

Your ‘Architectural guidelines’ can ensure thatYour ‘Architectural guidelines’ can ensure that

““Your ‘media assets’ will be listened or seen for Your ‘media assets’ will be listened or seen for centuries” centuries”

CONCLUSIONSCONCLUSIONS““Good solutions are effectivesGood solutions are effectives””

PROSI © 2005

The list below is a first contribution to the elaboration of a The list below is a first contribution to the elaboration of a proposal for enhancing and extending the OAIS model (V2 to proposal for enhancing and extending the OAIS model (V2 to be planned in 2006)be planned in 2006)

1.1. Adaptations to adhere to the ISO terminology and OSI extensions Adaptations to adhere to the ISO terminology and OSI extensions for persistencefor persistence

2.2. Coverage of the ‘Metadata’ for ‘Ontology and ‘Semantic’ Coverage of the ‘Metadata’ for ‘Ontology and ‘Semantic’ (Standards & (Standards & personalized)personalized)

3.3. Identification & LabelingIdentification & Labeling (ID fountain, ID schemes, …)(ID fountain, ID schemes, …)

4.4. Inclusion of the ‘acquisition’ functions: Inclusion of the ‘acquisition’ functions: OIPOIP (Original Information Package) (Original Information Package) 5.5. Information securityInformation security (Identity, Integrity, Authenticity, Confidentiality, …)(Identity, Integrity, Authenticity, Confidentiality, …)

6.6. Object and Data Structures ready for the construction of the Object and Data Structures ready for the construction of the automatic persistenceautomatic persistence

7.7. Separation of the physical IT objects, the logical IT objects and the Separation of the physical IT objects, the logical IT objects and the external objects external objects

8.8. Management of the “Profiles” for the “Autonomous Assets Entities”Management of the “Profiles” for the “Autonomous Assets Entities”9.9. Management of the “Profiles” for the encapsulation of the Management of the “Profiles” for the encapsulation of the

‘proprietary’ formats with their associated ‘proxies’‘proprietary’ formats with their associated ‘proxies’ (standard compliant)(standard compliant)10.10. Management of the “profiles” for ‘DIPs’ not targeted to a specific Management of the “profiles” for ‘DIPs’ not targeted to a specific

communitycommunity11.11. Chaining of OAISChaining of OAIS (Modules {Opus [Clip, Project, Resource, Package], Media, Repository})(Modules {Opus [Clip, Project, Resource, Package], Media, Repository})

12.12. Unstructured searchesUnstructured searches13.13. Certificates of traceabilityCertificates of traceability14.14. Management of the ‘multilingual’Management of the ‘multilingual’

Conclusions Conclusions :“:“The OAIS model should be extended and improvedThe OAIS model should be extended and improved””

PROSI © 2005

References and theoretical foundations for References and theoretical foundations for the persistencethe persistence

‘‘Content criticalContent critical’ ’ by by Gerry McGovern Gerry McGovern Target : Humanity lifetime !Target : Humanity lifetime ! [Prentice Hall ISBN 0-273-65604])[Prentice Hall ISBN 0-273-65604])

‘‘The OThe Openpen A Archivalrchival I Informationnformation S Systemystem’ (OAIS’ (OAIS Blue bookBlue book ))http://www.ccsds.org/documents/650x0b1.pdf

‘‘The Open System Interconnection’ of ISO and its profilesThe Open System Interconnection’ of ISO and its profilesISO/IEC standard ISP 35100ISO/IEC standard ISP 35100

‘‘The OSI model applied to the Archives’The OSI model applied to the Archives’ by Guy Maréchal by Guy MaréchalTo be published in 2006 (Brussels’s University [ULB])To be published in 2006 (Brussels’s University [ULB])

‘‘Persistence by combining OAIS and METS’ Persistence by combining OAIS and METS’ by Catherine Lupoviciby Catherine Lupovicihttp://ww.adbs.fr/uploads/journees/lupovici200503.html

‘‘Collection-Based Persistent ArchivesCollection-Based Persistent Archives’’ by by Rajasekar, A., Marciano, R., Moore, R.,Rajasekar, A., Marciano, R., Moore, R.,[Proceedings of the 16[Proceedings of the 16thth IEEE Symposium on Mass Storage Systems, March 1999] IEEE Symposium on Mass Storage Systems, March 1999]

Target : 300 years !Target : 300 years !• Collection based persistent data archives (part 1) inCollection based persistent data archives (part 1) in D-Lib Magazine April 2000 Volume 6 Number 3D-Lib Magazine April 2000 Volume 6 Number 3

ISSN 1082-9873ISSN 1082-9873 http://www.dlib.org/dlib/march00/moore/03moore-pt1.html• Collection based persistent data archives (part 2) inCollection based persistent data archives (part 2) in D-Lib Magazine April 2000 Volume 6 Number 4 D-Lib Magazine April 2000 Volume 6 Number 4

ISSN 1082-9873ISSN 1082-9873 http://www.dlib.org/dlib/april00/moore/04moore-http://www.dlib.org/dlib/april00/moore/04moore-pt2.htmlpt2.html

• Metadata Principles and PracticalitiesMetadata Principles and Practicalities The D-Lib Magazine April 2002 Volume 8 Number 4The D-Lib Magazine April 2002 Volume 8 Number 4

ISSN 1082-9873ISSN 1082-9873 http://www.dlib.org/dlib/april02/weibel/04weibel.htmlhttp://www.dlib.org/dlib/april02/weibel/04weibel.html

‘‘The KEO satellite project’The KEO satellite project’Target : 50 000 years !Target : 50 000 years !

PROSI © 2005

References and theoretical foundations for References and theoretical foundations for the ‘metadata’the ‘metadata’

‘‘RDF’ by W3CRDF’ by W3Chttp://www.w3.org/TR/rdf-primer/

‘‘Dublin Core’Dublin Core’http://dublincore.org/documents/

‘‘The MThe Metadataetadata E Encoding andncoding and T Transmissionransmission S Standardtandard’ (METS)’ (METS)http://www.loc.gov/standards/mets/

‘‘MPEG-7’MPEG-7’http://mpeg.tilab.comcselt.it

‘Cover Pages ‘METS’http://xml.coverpages.org/mets.html

PROSI © 2005

PROSI © 2005

Prepared by:Guy Maréchal Guy Maréchal [email protected]

Une introduction à AXIS

An introduction to AXIS

Une conférence organisée par l’ASBL dans le cadre de l’

Bruxelles les 17 et 18 novembre 2005