Downloaden Sie, um offline zu lesen
Hochgeladen vonStefan Gradmann
20110505 linked openeuropeanalswt2011
Das Dokument beschreibt das Europeana Data Model (EDM) und seine Entwicklung, einschließlich der Integration von Linked Open Data (LOD) in die europäische digitale Bibliothek Europeana. Es hebt die Herausforderungen der semantischen Interoperabilität und die Notwendigkeit hervor, ursprüngliche Metadaten beizubehalten, während gleichzeitig die Nutzung von vernetzten Daten gefördert wird. Das EDM zielt darauf ab, verschiedene Wissensorganisationssysteme zu verbinden und eine reichhaltige, kontextualisierte Repräsentation von Objekten zu ermöglichen.
Weitere ähnliche Inhalte
20110505 linked openeuropeanalswt2011
- 1. Linked (Open) Europeana: Vernetzte Daten in der Europäischen Digitalen Bibliothek Prof. Dr. Stefan Gradmann Unter Rückgriff auf M. Doerr, S. Hennicke , A. Isaac, C. Meghini, G. Schreiber, H. Van de Sompel Und Arbeiten von Europeana V1.0 und EuropeanaConnect
- 2. Übersicht NICHT: wasist Europeana
- 3. NICHT: was istLinked Data
- 4. Nach dem Katalog:semantische Kontextualisierung in Europeana
- 5. Das Europeana DataModel (EDM) Grundlagen
- 6. Mona Lisa undmehr ...
- 7. Status Quo Über'Offenheit'
- 8.
- 9. Alte und neue Begriffe (thanks, Karen Coyle!) Katalog Bestand 'Record' Dokument Suche Bibliothek Information Aggregation Exploration Navigation Verbindung Kontext Wissen
- 10. Nach dem Katalog:Objekte und Semantischer Kontext in Europeana Kontextualisierte Objektrepräsentationen (-> Wissensgenerierung): Europeana verbindet Objekt- und Wissensorganisationssysteme!
- 11. Die Semantische DatenschichtÜberbrückt Informationsinseln und verbindet Objektrepräsentationen aus verschiedenen Gedächtnisdomänen. Bibliothek Archiv Museum
- 12. EDM und LinkedOpen Data Kontextoptionen DBpedia VIAF GND Geonames LCSH … Europeana-Objekte
- 13.
- 14. ESE “ EuropeanaSemantic Elements” (ESE) ad hoc für den ersten Prototyp (2008) kreiert
- 15. Interoperabilität: Bezug aufdas minimalistische und 'flache' Dublin-Core Modell
- 16. “ einfach undrobust” aber: Semantik der Original-Metadaten geht verloren
- 17. Keine Spezialisierung imSinne granularer Modelle möglich
- 18. Keine Verlinkungen unddamit auch keine Verbindungen zu externen Ressourcen
- 19. Wir hätten eswohl besser nicht „semantic“ genannt :)
- 20. EDM “ EuropeanaData Model” (EDM) wird ESE mit dem “Danube”-Release von Europeana (Mai 2011) ersetzen
- 21. ESE wird dannein “application profile” von EDM (Rückwärtskompatibilität!)
- 22. erhält die Semantikder Originaldaten ohne Verlust von Interoperabilität
- 23. ermöglicht eine Nutzungvon Europeana als Linked Open Data
- 24. ermöglicht eine Nutzungvon Linked Open Data in Europeana
- 25.
- 26. EDM: Anforderungen undDesignprinzipien Unterscheidung zwischen realem Objekt (Buch, Bild, Akte, mediale Aufzeichnung) und digitaler Repräsentation
- 27. Unterscheidung zwischen Objekt und beschreibenden Metadaten
- 28. Es müssen mehrere Sichten eines Objekts möglich sein, mit potentiell einander widersprechenden Aussagen
- 29. Unterstützung komplexer Kompositobjekte
- 30. Standard -Metadatenformat mit Spezialisierungsoption
- 31. Standard -Vokabularformat mit Spezialisierungsoption
- 32. Maximale Nachnutzung existierender Standards
- 33. EDM und andereStandards Simple Knowledge Organization System ( SKOS ) Modelliert die Wissensorgabnisationssysteme (KOS) in der semantischen Datenschicht von Europeana.
- 34. Ermöglicht Verbindungen zwischenKOSs. DCMI Metadata Terms ( DCTerms ) Basis für semantisch interoperable deskriptive Objekt-Metadaten
- 35. Stellen Rückwärtskompatibilität zuESE her Open Archives Initiative Object Reuse & Exchange ( OAI ORE ) Organisiert und modelliert Aggregationen von Web-Resourcen für die Objektrepräsentation
- 36. Provided Object :repräsentiert des gegebene (reale) Objekt
- 37. Digital Representation :eine digitale Sicht des Objektes
- 38. Proxy : Objektbeschreibungaus einer bestimmten Perspektive
- 39. Aggregation : gruppiertalle Teilinformationen
- 40.
- 41. Mona Lisa: Beschreibungder Direction des Musées de France ...
- 42. … undals Metadaten-Aggregation in EDM Proxy Digitale Repräsentationen Reales Objekt Aggregation
- 43.
- 44.
- 45.
- 46.
- 47. Ereignisbasierte Modellierung Erhaltund Nutzung der Originaldaten impliziert Kompatibilität der Beschreibungen jenseits der einfachen Objektsicht!
- 48. Komplexe Objekte undBeziehungen Teil-Ganzes für komplexe (hierarchische) Objekte
- 49.
- 50.
- 51. ESE in EDM<...xmlns:europeana="http://www.europeana.eu/schemas/ese/“ ... <!--National Library of Poland--> <record> <dc:identifier>urn:repox.bn.org.pl:polona:oai:www.polona.pl:4445</dc:identifier> <europeana:uri>http://www.europeana.eu/resolve/record/01406/18A8F5DFCAE75694A8AAD18E2791861FBE92589A</europeana:uri> <dc:title>[Ośmiu powstańców uzbrojonych w kosy] [Dokument ikonograficzny]</dc:title> <dc:subject>Powstanie 1863 r. styczniowe - ikonografia</dc:subject> <dc:date>[1863-1864]</dc:date> <dc:rights>Biblioteka Narodowa</dc:rights> <europeana:object>http://193.59.172.16/szzz/IsShownBy.do?id=6481</europeana:object> <europeana:isShownAt>http://193.59.172.16/szzz/ShowStart.do?id=6481</europeana:isShownAt> </record> Europeana Audiovisual Community Meeting20100409
- 52. ESE in EDM5.0 Europeana Audiovisual Community Meeting20100409
- 53. Les Fleurs duMal: UNIMARC http://catalogue.bnf.fr/ark:/12148/cb37367035f 000 nam 22 450 001FRBNF373670350000003 009http://catalogue.bnf.fr/ark:/12148/cb37367035f 039 $oGEA$a000288182 100 $a19920409d1857 m y0frey50 ba 1010 $afre 102 $aFR 105 $a||||z 00||| 106 $ar 2001 $aˆLes ‰fleurs du mal$bTexte imprimé$fpar Charles Baudelaire 210 $aParis$cPoulet-Malassis et De Broise$d1857 215 $a248 p.$d19 cm 676 $a841.8$v22 686 $a840$2Cadre de classement de la Bibliographie nationale française 700 |$311890582$aBaudelaire$bCharles$4070 801 0$aFR$bBNF$c19920409$gAFNOR$2intermrc
- 54. Les Fleurs duMal: Gallica http://gallica.bnf.fr/ark:/12148/bpt6k70861t
- 55. Les Fleurs duMal: Digitalisiert http://gallica.bnf.fr/ark:/12148/bpt6k70861t.textePage.f1
- 56. Les Fleurs duMal: EDM
- 57. Aggregationen … undFragen Wo beginnen resource aggregations ? Wo enden sie?
- 58.
- 59. Und welcher Knotenwar zum Zeitpunkt X mit welchem verknüpft??? A B C
- 60.
- 61. Gegenwärtiger Stand desEDM Machbarkeit in vier 'community workshops' bestätigt (Archive, Bibliotheken, audiovisuelle Sammlungen, Museen – und Systemanbieter!)
- 62. EDM ist Teilder Spezifikationen für den 'Danube'-Release der Europeana (Mai 2011).
- 63. Prototyperprobung istabgeschlossen.
- 64. Dokumentation : EDMSpezifikationen und Primer unter http://version1.europeana.eu/web/europeana-project/technicaldocuments/
- 65. Martin Doerr, StefanGradmann, Steffen Hennicke, Antoine Isaac, Carlo Meghini, Herbert van de Sompel: The Europeana Data Model. IFLA 2010 (Gothenburg). Session on „Libraries and the Semantic Web“. http://www.ifla.org/files/hq/papers/ifla76/149-doerr-en.pdf
- 66. Entwicklerdokumentation und OWL-Versionin EuropeanaLabs: http://europeanalabs.eu/
- 67. EDM: Weiterentwicklung undPerspektiven FRBRoo (Functional Requirements for Bibliographic Records) Die Entitäten der Gruppe 1 werden im Rahmen von Europeana 2.0 (ab 2011) unterstützt werden.
- 68. RDA (Resource Description andAccess) RDA-basierte Metadaten werden in EDM integrierbar sein, sobald die FRBR-Entitäten unterstützt werden.
- 69. Skalierbarkeit von RDF'triple stores' ist kein kritischer Faktor. Relationale Datenhaltung mit Tripel-Aufsätzen wie D2R-Prozessoren sind eine gangbare Alternative zu nativen 'triple stores'.
- 70. LOD (Linked OpenData) EDM erlaubt die technische Integration von Europeana in die Welt der Linked Open Data – ersetzt aber keinesfalls eine entsprechend angepasste Politik der Datenlieferanten!
- 71. LoD Pilot : Ab Ende Mai 2011 … und heute in Leipzig!
- 72.
- 73.
- 74. Europeana LoD Pilot(3) DEMO
- 75. Europeana LoD Pilot(6) Zahlen, Fakten und kurzfristige ToDos Momentan ca. 3,5 Millionen der 16 Millionen in Europeana repräsentierten Objekte – Koalition der Willigen
- 76. Freigabe ab EndeMai 2011
- 77. Integration von Kontextualisierungslinks(GeoNames, VIAF, DBPedia)
- 78. Implementierung von loadbalancing
- 79.
- 80. Credits to BernhardHaslhofer (U Wien), Antoine Isaac (Europeana Foundation), Cesare Concordia (CNR IST) und weitere ...
- 81.
- 82. Wie 'offen' müssenLinked Data sein? (1) “ Openness (allowing access) is separate question.” (TBL, http://www.w3.org/2008/Talks/0617-lod-tbl/#(22))
- 83. Funktioniert Linked Dataohne 'offen' zu sein? Rein technisch besehen durchaus (so etwa in der Pharmaindustrie oder bei biochemischen Daten oder auch im Bankensektor)
- 84. Aber der Ansatzwird dann extrem aufwändig und teuer …
- 85. … vielzu teuer wahrscheinlich: für Europeana nicht zu bezahlen! Sehr viel 'semantischer Charme' des offenen Ansatzes geht verloren – und zudem ist der geschlossene Ansatz recht parasitär.
- 86. Dem entsprechend zielenwir in Europeana explizit auf ein Open Linked Data (mehr in einem Statement der Europeana Foundation unter http://bit.ly/fe637P) und streben an, Europeana-Daten unter CC0 verfügbar zu machen!
- 87. Wie 'offen' müssenLinked Data sein? (2) Ein 'offener' Ansatz hat eine Reihe von Implikationen Verwendung der Daten ist nicht kontrollierbar.
- 88. Zugang zu denDaten und deren Verwendung entfällt als Einkommensquelle
- 89. Innovative und kommerziellattraktive Dienste können auf LoD basieren (multimediale Mehrwertdienste) -> Lizenzierung von Inhalten darf kommerzielle Nachnutzung nicht ausschließen. -> In den nun anstehenden Diskussionen nicht sämtliche Fehler der Diskussion um Open Access wiederholen!
- 90. -> Was istder (kommerzielle!) Wert semantischer Kontextualisierung?
- 91. Europeana v1.0 WP3EuropeanaConnect WP1 Prof. Dr. Stefan Gradmann Humboldt-Universität zu Berlin Institut für Bibliotheks- und Informationswissenschaft Unter den Linden 6 10099 Berlin Tel.: +49 30 2093-4481 e-mail: stefan.gradmann@ibi.hu-berlin.de Fragen ?
Hinweis der Redaktion
- #3 EDM re-uses three ontologies all of which are defined as a RDFS model. SKOS SKOS is an ontology to model KOS (vocabularies) in the Semantic Data Layer of Europeana. It specifically enables cross-vocabulary matching between concepts. Dublin Core Dublin Core is used to describe the core features of culture objects. ESE uses “old” Dublin Core Element Set. EDM uses “new” Dublin Core Metadata Terms which are specializations of the 15 “old” Dublin Core Elements. The use of DC Terms ensures backward compatibility to ESE. OAI ORE The typical record about an object provided to Europeana will included several information pieces: e.g. with descriptive metadata, views (thumbnails, video files, audio files, text documents etc.), links to landing pages etc. OAI ORE allows us to group and organize these information pieces: the abstract “provided object” (Object), the descriptive metadata (Proxy), any “view” of the provided object (Digital Representation).
- #5 The current data model of Europeana are the “Europeana Semantic Elements” (ESE). ESE addresses the issue of interoperability between the data from the different domains represented in Europeana by reducing the data to a “flat”, Dublin-Core like representation. This is a “simple and robust” approach but it has some drawbacks: The original metadata and information perspective are not visible anymore. And at the same time we can not specialize to finer-grained models or connect to external resources like LOD community. The EDM addresses exactly these shortcomings . It tries to transcend the different information perspectives which are represented in Europeana. It acts as a top-level ontology in order to make objects from different domains interoperable while still preserving the original data. The EDM is destined to replace ESE after the 2011 release of Europeana. The ESE will then be an „application profile“ of EDM. That means that all ESE data in Europeana will be still compatible with the new system.
- #6 First a few words about the envisioned information architecture of Europeana: This is how the information space of Europeana will be restructured : At the “bottom” we have the objects which are provided to Europeana. Above we have the “Semantic Data Layer” which is new. It contains various kinds of KOSs with knowledge about people, places, concepts, and so on. These concepts are linked to the objects below and thereby contextualize and enrich them.
- #7 The data provided to Europeana will come from many different kinds of domains like libraries, archives, or museums. They all will provide their specific collections and KOSs . That will naturally result in „isles of information“ . In order to make the data interoperable the concepts of the various KOSs in the Semantic Data Layer will be aligned , that means they will be connected via cross-vocabulary links . This technically enables applications to navigate through a semantic layer of concepts from different sources and to use it to access objects which are originally described by different but semantically related concepts.
- #8 Europeana intends to connect to the Linked Open Data community. In the Linked Open Data cloud we find many more knowledge sources like Dbpedia, Geonames, or Library of Congress Subject Headings. Europeana wants to use them to further contextualize and enrich the objects in its information space. At the same time Europeana wants to make its own data available to other communities. The EDM is crucial for realizing this vision. [ LOD cloud July 2009 ]
- #10 The current data model of Europeana are the “Europeana Semantic Elements” (ESE). ESE addresses the issue of interoperability between the data from the different domains represented in Europeana by reducing the data to a “flat”, Dublin-Core like representation. This is a “simple and robust” approach but it has some drawbacks: The original metadata and information perspective are not visible anymore. And at the same time we can not specialize to finer-grained models or connect to external resources like LOD community. The EDM addresses exactly these shortcomings . It tries to transcend the different information perspectives which are represented in Europeana. It acts as a top-level ontology in order to make objects from different domains interoperable while still preserving the original data. The EDM is destined to replace ESE after the 2011 release of Europeana. The ESE will then be an „application profile“ of EDM. That means that all ESE data in Europeana will be still compatible with the new system.
- #11 The current data model of Europeana are the “Europeana Semantic Elements” (ESE). ESE addresses the issue of interoperability between the data from the different domains represented in Europeana by reducing the data to a “flat”, Dublin-Core like representation. This is a “simple and robust” approach but it has some drawbacks: The original metadata and information perspective are not visible anymore. And at the same time we can not specialize to finer-grained models or connect to external resources like LOD community. The EDM addresses exactly these shortcomings . It tries to transcend the different information perspectives which are represented in Europeana. It acts as a top-level ontology in order to make objects from different domains interoperable while still preserving the original data. The EDM is destined to replace ESE after the 2011 release of Europeana. The ESE will then be an „application profile“ of EDM. That means that all ESE data in Europeana will be still compatible with the new system.
- #13 EDM re-uses three ontologies all of which are defined as a RDFS model. SKOS SKOS is an ontology to model KOS (vocabularies) in the Semantic Data Layer of Europeana. It specifically enables cross-vocabulary matching between concepts. Dublin Core Dublin Core is used to describe the core features of culture objects. ESE uses “old” Dublin Core Element Set. EDM uses “new” Dublin Core Metadata Terms which are specializations of the 15 “old” Dublin Core Elements. The use of DC Terms ensures backward compatibility to ESE. OAI ORE The typical record about an object provided to Europeana will included several information pieces: e.g. with descriptive metadata, views (thumbnails, video files, audio files, text documents etc.), links to landing pages etc. OAI ORE allows us to group and organize these information pieces: the abstract “provided object” (Object), the descriptive metadata (Proxy), any “view” of the provided object (Digital Representation).
- #14 In the physical world we create, use, and refer to aggregations of things all the time. We collect pictures in a photo album, read journals that are collections of articles, and burn CDs of our favorite songs. In this physical world these aggregations are frequently tangible - we can hold the photo album, journal, and CD. But, we also aggregate abstract entities – for instance on the WEb. OAI-ORE makes it possible to identify an aggregation .
- #15 Mona Lisa as described and depicted by the French ministry of culture (Directions des musees de France)
- #16 This is the metadata record of the French ministry of culture modeled in EDM. Each bubble represent a resource. In the bubble you have the class of the resource (its type) in italics and beneath the URI of the resource which identifies it. The arrows are the semantic links (the properties) between the resources. If there are two properties then the one below is the sub-property of the other one with a more specific meaning. First we have the Aggregation node which groups together all information pieces delivered by the Ministry. It aggregates the node representing the physical object “Mona Lisa”, the digital representations of the Mona Lisa, and the proxy node which is specific to a given provider, and is used to represent the description of the provided object, as seen from the perspective of that specific provider. This is how every metadata record provided to Europeana will look like in its basic form. Why manage central nodes for provided objects? The ORE model says so: an ORE proxy has to be proxy for some &quot;view- independent&quot; resource. Users are looking for (real world) objects (the painting Mona Lisa) and not for the specific view on it of Louvre, or Jaconde (of which they normally do not know anyway). So the approach is: Find the object first (PhysicalThing) and then proceed to the specific views on it. This is also the LOD approach.
- #17 Europeana wants to contextualize and enrich its objects by linking them to resources which contain additional knowledge. This enables richer functions, such as query expansion (e.g., using alternatives for a creator's name), recommendation of objects using semantic relations between them (objects created by connected artists), etc. This is the same Proxy from the slide before but now all the string values are converted to resources and typed. For example the subject of the painting Mona Lisa “femme” is now a resource typed as a concept and with the english and french spelling of the concept attached taken from a KOS in the Semantic Data Layer. And in the same KOS we could also properly find the broader term for this concept. Furthermore we could semantically align the concept femme with the concept femme in the Wikipedia (LOD cloud) and take all the information available there for this specific subject, including the many translations of the term itself. To increase the data value of its objects.
- #18 What we looked at so far can be understood as object-centric modeling. The second general modeling approach is event-centric which tries to tell a story about the object’s history. For this purpose EDM provides a simple “event-centric core” of one class and three properties: ens:Event: hub for event descriptions ens:wasPresentAt, holding between any resource and an event it is involved in; ens:happenedAt, holding between an event and a place; ens:occurredAt, holding between events and the time spans during which they occurred. This is to give you an impression of what is possible without going into details.
- #19 This is a (more or less fictional) example of three records about a translation of Edgar Allan Poe’s “ The Narrative of Arthur Gordon Pym of Nantucket ” to french: Record from BNF about an edition from 1868 Record from Gallica about an edition from 1868 (which offers a digital version of the book online: this the WebResource) Record from BNF with an edition from 2007 A few things I want to point out: Two records about the same thing and both point to the same object of interest, the 1868 edition. The user will look for this edition and not for the specific view of Gallica or BNF on this edition. So this node is the point of entry from which a user will proceed to a specific view on the object. It is also apparent now why Proxies for the descriptive metadata are helpful: Because this way we can keep the two views on the 1868 edition distinct. Finally the link „isDerivativeOf“ is an example of an inter-object link. So, for example, if a user found the 2007 edition he will be also hinted to the digital version of the 1868 edition in Gallica. With respect to FRBR one could start discussing now what and where is the work, expression, manifestation, and item here. Although the development of the EDM has been inspired by FRBR it is not implemented yet. That will happen after 2011.
- #28 EDM is still under development, and will continue to be refined until the end of 2010. It will be implemented during 2011, in the lead up to the Danube release of Europeana. Before, during and after the implementation of EDM, data that is compliant only with ESE will continue to be accepted. EDM is compatible with ESE and no data will need to be resubmitted. Europeana will make available a converter, and any provider who wishes to resubmit data, in order to increase its richness within Europeana, will be able to do so if they wish but will be under no obligation. How will EDM data be delivered to Europeana? Providers will have to create mapping to EDM and deliver it alongside their data which ideally are metadata records properly linked (IDs) to a vocabulary. The data has to be in XML or RDF. From this Europeana will create EDM data which includes enrichments and linking to external resources (vocabularies in the semantic data layer and/or the LOD cloud). Prototyping? At the end of the year we will start to produce first EDM data for the productive version of Europeana. This data will be taken from existing ESE data and from rich data delivered to Europeana by then.
- #35 Copied from the DoW
- #36 Copied from the DoW