11
Content Working Group Paolo Manghi ISTI-CNR [email protected]

Content Working Group Paolo Manghi ISTI-CNR [email protected]

Embed Size (px)

Citation preview

Page 1: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

Content Working Group Paolo Manghi

[email protected]

Page 2: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

WG Members

Donatella CastelliISTI-CNR

Luc Moreau University of Southampton

Leonardo CandelaISTI-CNR

Paolo ManghiISTI-CNR

Stefan GradmanUniversity of Berlin

C.H.J.P. Kees HendriksDutch National Museum of Natural History

Detlev BalzerExpert in data modelsEFG Project

WG Leader

Rapporteur

Page 3: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

Expectations

• Identifying interoperability issues from the perspective of Digital Library content

• Discussing possible approaches to mitigate/resolve the issues identified

• Cookbook: proposing effective patterns towards their resolution

• Feedback to the Digital Library Reference Model

Page 4: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

Strategy

• Identification of a “content interoperability” framework– Provider of a resource and consumer in the need of

performing a task• The Cookbook: identifying the solutions

– Identification of common patterns for Digital Library resources

– Identification of common patterns of content interoperability scenarios

– Description of existing solutions (and real-case experiences)

Page 5: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

An Content Interoperability Framework…

Knowledge modeling and

design: organization,

end users, designers,

developers

Knowledge representatio

n

and provision:

hardware, software,

protocols

Data management systems: data model and language

Tools for remote interaction:data model and language

Consumer Provider

Conceptual

Realization

Interface

Conceptual

Realization

Interface

Task Relevant facts about the resource: structure, semantics,functionalities

Resource

Knowledge Interoperability

SystemInteroperability

Page 6: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

DL Resource patterns

7

Provenance

Context

Identifier

Attributes

Format

InformationObject

Page 7: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

DL Resource patterns

• Information Object Format – “Data type”: formal and intensional characterization of the

Information Objects– Consumer can safely and/or efficiently execute operations over an

Information Object based on the structural “assumptions” of the Information Object Format

• Information Object Attributes – Metadata enriching the information object– Granularity and quality of metadata strongly characterize the pool

of services that can be built by exploiting them– The wider is the understanding of metadata the consumer has,

the richer is the functionality it will be able to realize by exploiting it

Page 8: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

DL Resource patterns• Information Object Context

– Metadata characterizing the circumstances that form the setting for the Information Object

– Examples: relations with other entities like persons, places, moments in time or abstract ideas that complement the object semantics

• Information Object Provenance– Metadata describing the process that led an Information Object to be in

its current state– Example: information context and time -specific, both in the aspects

captured, their representation, and in term of the objects and processes referred

• Information Object Identifier – The Identifier is a token bound to the Information Object distinguishing it

from the others within a certain scope

Page 9: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

Content Interoperability Solutions

• Solutions categorization– By “real-case scenario patterns” - to be discussed

• e.g., given consumer, given provider, providers federation, (non-)cooperative interlocutor

– By “resource patterns” - others?– By “adoption of standards” - which ones?

• Solutions characterization– Changes required to achieve knowledge or/and system

content interoperability• e.g., transformators, mediators

– Estimate of design and development cost

Page 10: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

Towards the Cookbook: Standards example…

Conceptual

Realization

Interface

CERIF, MARC, Dublin Core

CERIF XML, MARC XML,

OAI-PMH, OAI-ORE

ReferenceData models

Access Protocols

Reference data models: data modelAccess protocols: data model and language at the conceptual or interface level

Page 11: Content Working Group Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it

Towards the Cookbook: EFG federation example

Consumer Provider

Conceptual

Realization

Interface

Conceptual

Realization

Interface

Resource

Knowledge Interoperability

SystemInteroperability

Local Schema:films and persons

OAI-PMHwith EFG XML Schema

OAI-PMHharvester

D-NET Stores andIndices

EFG Schema:films and persons

Task

Local implementation

• Federation of providers with film-oriented information• Non-bibliographic resources• One consumer with specific XML schema requirements and OAI-PMH protocol