Presentation is loading. Please wait.

Presentation is loading. Please wait.

Content Working Group Paolo Manghi ISTI-CNR

Similar presentations


Presentation on theme: "Content Working Group Paolo Manghi ISTI-CNR"— Presentation transcript:

1 Content Working Group Paolo Manghi ISTI-CNR

2 WG Members Donatella Castelli ISTI-CNR Luc Moreau University of Southampton Leonardo Candela ISTI-CNR Paolo Manghi ISTI-CNR Stefan Gradman University of Berlin C.H.J.P. Kees Hendriks Dutch National Museum of Natural History Detlev Balzer Expert in data models EFG Project WG Leader Rapporteur

3 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

4 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)

5 An Content Interoperability Framework… Knowledge modeling and design: organization, end users, designers, developers Knowledge representation and provision: hardware, software, protocols Data management systems: data model and language Tools for remote interaction: data model and language ConsumerProvider Conceptual Realization Interface Conceptual Realization Interface Task Relevant facts about the resource: structure, semantics,functionalities Resource Knowledge Interoperability System Interoperability

6 Content Interoperability Knowledge modeling – Essential to motivate the reasons of an interaction between the provider and the consumer – The provider manages a resource that conceptually satisfies the task of the consumer System Interfaces – Essential to operate the communication between two systems satisfying knowledge interoperability – The consumer’s interface performs the consumer’s task by manipulating the provider’s resource as exposed by the provider’s interface

7 DL Resource patterns 7 Provenance Context Identifier Attributes Format Information Object

8 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

9 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

10 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

11 Towards the Cookbook: Real-case scenarios Consumer’s perspective: a provider satisfying knowledge interoperability offers a given scenario, the consumer wants to consume it and needs to system interoperate with it Provider’s perspective: a consumer satisfying knowledge interoperability offers a given scenario, the providers wants to be consumed and needs to system interoperate with it

12 Towards the Cookbook: Standards example… Conceptual Realization Interface CERIF, MARC, Dublin Core CERIF XML, MARC XML, OAI-PMH, OAI-ORE Reference Data models Access Protocols Reference data models: data model Access protocols: data model and language at the conceptual or interface level

13 Towards the Cookbook: EFG federation example ConsumerProvider Conceptual Realization Interface Conceptual Realization Interface Resource Knowledge Interoperability System Interoperability Local Schema: films and persons OAI-PMH with EFG XML Schema OAI-PMH harvester D-NET Stores and Indices 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


Download ppt "Content Working Group Paolo Manghi ISTI-CNR"

Similar presentations


Ads by Google