10
EDM Cases: Polymath Virtual Library Xavier Agenjo Fundación Ignacio Larramendi [email protected]

EDM Cases: Polymath Virtual Library

  • Upload
    digibis

  • View
    1.222

  • Download
    1

Embed Size (px)

DESCRIPTION

The Polymath Virtual Library es el nombre que el W3C Incubator Group ha dado a la Biblioteca Virtual Ignacio Larramendi de Polígrafos de la Fundación Ignacio Larramendi tras seleccionarla como Case Study junto con otras diez de diversos lugares del mundo.

Citation preview

Page 1: EDM Cases: Polymath Virtual Library

EDM Cases: Polymath Virtual Library

Xavier Agenjo

Fundación Ignacio Larramendi

[email protected]

Page 2: EDM Cases: Polymath Virtual Library

Work done: Use URIs as names for things

http://www.larramendi.es/aut/FILA20120003101

Page 3: EDM Cases: Polymath Virtual Library

Work done: Use HTTP URIs so that these things can be referred to and looked up ("dereferenced") by people and user

agents

Page 4: EDM Cases: Polymath Virtual Library

Work done: Provide useful information about the thing when its URI is dereferenced, using standard formats such as RDF/

XML

Page 5: EDM Cases: Polymath Virtual Library

Work done: Include links to other, related URIs in the exposed data to improve discovery of other related

information on the Web

Page 6: EDM Cases: Polymath Virtual Library

influenced

dc:creator dc:subject

Escepticismo

is related to

dc:subject

sameAs

skos:closeMatch

influenced

influenced influenced

influenced

influenced

skos:closeMatch

sameAs influenced

is related to

is related to

is related to

is related to

influenced

Page 7: EDM Cases: Polymath Virtual Library

Some buts...• We need a stable EDM: its development is being long, with major changes and

not yet stable.

• For exchange and harvesting, we need an XSD schema stable and clearly versioned

• Phases doesn’t facilitate its application. Once it is decided to apply LOD, it’s difficult [and expensive] to be constrained by EDM implementation phases. How to proceed? Should we [CP] send all existing data and relationships? Or, should we send only data and relationships according to phases?

• Messages are not clear enough about who should apply EDM or when [Europeana Bussiness Plan 2012 – EDM Implementation Roadmap]

• What will be the benefits [for content providers and their users] of moving to EDM? What developments are foreseen to show this benefits.

Page 8: EDM Cases: Polymath Virtual Library

More important

• Provide useful information – Not any data in EDM is good enough (or useful); granularity matters

• Include links to other URIs so that they can discover more things – It is not about converting basic Dublin Core records to RDF, which

matters are relationship with other resources and vocabularies (VIAF, DBpedia, WGS84, etc.).

– What about local resources?

– Europeana can't do everything

• [Include EDM/LOD in your real cataloging process]– MARC 21 Records– Linking data through 024– New relationships (through $4)

Page 9: EDM Cases: Polymath Virtual Library

Authority records are the support of EDM

Cataloguing processes have to change to incorporate LOD

Facilitate the reuse of data: tools for searching and linking data to common external resouces

How to pass from MARC to LOD without losing any data?

Page 10: EDM Cases: Polymath Virtual Library

Thank You!