1 / 11

Content Working Group

Content Working Group . Paolo Manghi ISTI-CNR paolo.manghi@isti.cnr.it. WG Members. WG Leader. C.H.J.P. Kees Hendriks Dutch National Museum of Natural History. Donatella Castelli ISTI-CNR. Luc Moreau University of Southampton. Detlev Balzer Expert in data models EFG Project.

trung
Download Presentation

Content Working Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. WG Members WG Leader C.H.J.P. KeesHendriks Dutch National Museum of Natural History Donatella Castelli ISTI-CNR Luc Moreau University of Southampton DetlevBalzer Expert in data models EFG Project Stefan Gradman UniversityofBerlin Paolo Manghi ISTI-CNR Leonardo Candela ISTI-CNR 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… Knowledgemodelingand design: organization, end users, designers, developers Knowledge Interoperability Task Resource Relevantfactsabout the resource: structure, semantics,functionalities Conceptual Conceptual Realization Realization Data management systems: data model and language Knowledgerepresentation and provision: hardware, software, protocols Interface Interface Toolsfor remote interaction: data model and language System Interoperability Consumer Provider

  6. DL Resource patterns Provenance Format Information Object Context Attributes Identifier

  7. 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

  8. 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

  9. 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 systemcontent interoperability • e.g., transformators, mediators • Estimate of design and development cost

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

  11. Towards the Cookbook: EFG federation example • Federationofproviderswithfilm-oriented information • Non-bibliographicresources • One consumer withspecific XML schema requirements and OAI-PMH protocol Knowledge Interoperability Task Conceptual Conceptual Resource EFG Schema: films and persons Local Schema: films and persons Realization Realization D-NET Stores and Indices Localimplementation Interface Interface OAI-PMH harvester OAI-PMH with EFG XML Schema System Interoperability Consumer Provider

More Related