Tutorial on Semantic Digital Libraries at ICSD'09

Hinweis der Redaktion

1. We need to introduce that Semantic Web is „a hype” – everyone is talking about – and say what it is Then we have to show that actually the Web was meant to be that way from the begining Finally tell what the „Semantic” means in all of that
2. OK – everyone says that he/she runs semantic web applications – but is that true? Where are we *really* in the the SW layer cake? Still far away – isn’t it ?
3. The semantic web will not emerge on its own We need to help it Explain the car example in more details
4. 1)OK – first step to deliver semantic web – is to provide semantic descriptions 2)In order to do that – we can use widely addopted RDF 3)What is RDF? What are the properties? 4)RDF is not XML – as RDF is based on graph model 5)How machines can process it ?
5. Now, RDF is a really nice – but what more can we do with it? First – obvious: objects/resources and relationsships Than – easy extend the model with new relantionships, types, etc Finally – we can easily integrate stuff But be aware – RDF support many points of view – if you want to be sure – you need to exend the knowledge with more sentences to know which „conflicting” statement is right for you
6. RDF alone is not enough – it just delivers a graph – but we need to provide some constraints, knowledge, etc Ontologies are the key concept to do so They are based on the social agreement There are several ways to express ontologies
7. The simplest ontology we can define is with RDF Schema RDFS defines a small vocabulary ... It can be easily used to define other vocabularies Like in our example ...
8. Another example is OWL (motice that the name does not match the abbreviation – but we know why :D) It is based on RDF/XML vocabulary It allows us to be more explicite in what we define – see example ... .. And DLs OWL as W3C recommendation
9. We cannot see SW unless we will look into applications There are two kinds: enabling technologies like e.g. End-user applications Today we will present the new emerging ones – Semantic Digital Libraries
10. What are SDL? They aim to integrate information coming from different sources SDLs provide interoperability mechnisms – and can act as an integration champions in heterogeneous networks of libraries But the **ultimate goal** is to provide better service for the end user – that is search and browsing features
11. One of the requirements was to support different metadata Although they are so different – they can be represented in RDF
12. One of the requirements was to support different metadata Although they are so different – they can be represented in RDF
13. One of the requirements was to support different metadata Although they are so different – they can be represented in RDF
14. One of the requirements was to support different metadata Although they are so different – they can be represented in RDF
15. The goal of this ontology is to provide means to mediate between heterogeneous database schemas and metadata structures. The central concept of CIDOC is that knowledge is attained by investigating relations between the facts. Therefore, the ontology concentrates on the definition of relationships between items rather then the terminology of a particular domain. The core ontology defines a set of very general classes (e.g. actor, event, period) and supplies a variety of relationship descriptions that can adjust the concepts understanding for a particular environment. Apart of the content preservation and summery CIDOC provides the concept of events, such as creation, publication, etc. Therefore, with regard to digital libraries, it is possible to utilize CIDOC to talk in detail about items content and their bibliographic description.
16. 1) Explain what do we mean by “simple solution” and “complex solution”
17. 3 major problems o libraries: They were build for librarians They were delivering information – not sharing knowledge DLs lost the human-part
18. Solutions: Make users involved in the process Allow users to share knowledge Provide better communication means witin and outside of communities
19. Ok, we know what we are missing – what is the solution? Web 2.0 – a community-aware web
20. What is the focus of Web 2.0 What are in **general** tools technologies that we can call Web 2.0
21. Roadmap to SSIS
22. Roadmap to SSIS
23. Roadmap to SSIS
24. Roadmap to SSIS
25. Roadmap to SSIS
26. Roadmap to SSIS
27. Comparing different technologies ... And there are social semantic digital libraries finally :D
28. 1)What is simile 2)Its relation to DSpace 3)Its goal
29. Main features of SIMILE: Enhanced end-user services Web-based architecture for digital assets dissimination
30. Now – lets see what SIMILE is Two categories of components – that we will describe in details later
31. Now – lets see what SIMILE is Two categories of components – that we will describe in details later
32. RDFizers -> in MarcOnt we would call them „adapters”
33. Solvent lets you easily integrate different sites into RDF -> e.g. For piggy bank
34. Now – lets see what SIMILE is Two categories of components – that we will describe in details later
35. Themes - use cases; JHU collaboration for data curation
36. Encyclopedia of Chicago: integration of newspapers, maps, GIS, images; UVa Collectus tool
37. Max Planck - e-research; medical imaging
38. Max Planck has extended ontology; and PLoS
39. UVa - silos for arch drawings and letters - integrated
40. Integration of data sets with articles - data curation scenario
41. Are using triplestore to record assertions of annotations at fine-grained level. Use separate external triplestore. Exploding key metadata as RDF. Also assertions about agents - moving toward access control model. Mulgara - Topaz needs complex queries
42. Different triplestore than PLoS
43. How do we actually use it - how do we build on all these capabilities?
44. EV has two interrelated goals: provide a community discussion/presentation forum; create context for science resources in the library
45. Here’s a current example: adding polar bears to the endangered species list due to climate change. Note the NSDL tagged resource.
46. Search shows both the post and referenced resources now in the NSDL.
47. Walk through an example using MediaWiki. Create a new article.
48. And identify resources to include in the wiki article
49. Referenced resources display with NSDL icon
50. Contribute the wiki article to the library, adding metadata about the new resource.
51. And potentially add any referenced resources not in the library or more information about those that do exist.
52. - present overview and motivation behind JeromeDL - describe ontologies and system architecture - sebastian will take over - after lunch you will have chance to get your hands on the newest version- let’s get started
53. - we’ve got phenomenal participation from users form all over the world and fantastic feedback - users create their own customizations and at the same time influence the the main line of development
54. - here are the most important features of the system- to start with
55. - from the beginning our goal was create a semantic digital library with the user in the center - we defined two questions in our research - thus we tried to find the best way to integrate ...- interconnect
56. - we defined 3 different groups of users with 3 sets of requirements - we can observe that those requirements are strongly based on the the legacy libraries
57. - in the quest of finding the answers to our question we knew that we need - motivations based on the use case scenarios
58. - this is a three-layer architecture of metadata management on top of a digital library system- each layer enriches basic information gathered in a library with semantic annotations, thus providing additional capabilities to searching and browsing- the bottom layer handles tasks required from a digital object repository, that is keeps track of pysical representation of resources their structure and provenance- the middle layer lifts up egacy bibliographic descriptions to a semantic level- the top layer utilizes benefits from engging community of users into annotatiog and filtering resources
59. From alexandria DL -> to 3 layers -> to 3 metadata layers
60. - dynamic collections
61. MarcOnt Initative aims to utilize existing metadata in MarcOnt ontology through MMS
62. MarcOnt Initative aims to utilize existing metadata in MarcOnt ontology through MMS
63. From alexandria DL -> to 3 layers -> to 3 metadata layers
64. The underlying concepts of social networks can be also represented by RDF with FOAF metadata
65. We use FOAFRealm system to manage securely FOAF information, deliver authentification module and ... SSCF module
66. Now, legacy metadata is not enough – since we want average people to use our library That is where SSCF comes into place
67. ... And this is how it looks like
68. - let’s not take a look at ontologies used in JeromeDL
69. - structure ontology is used to describe an electronic representation of the content itself- information object - abstract library resource -, e.g. book, chapter, page- hasPart, hasParts- Resource Aggregation Service as a way for dynamic content- the upcoming verion of JeromeDL will combine RAS with OAI-ORI datamodel
70. - simplified view of the bibliographic ontology- keywords: - domains:
71. - FOAFREalm ontoloy allows to capture user contribution to the resource descriptions - FOAFRealm extends FOAF vocabulary with the notion of friendship level properties - the community-aware ontology enables JeromeDL to describe social’s network information - library resource as a bookmark (SSCF) - common practice of bookmarking, - SSCF enables users to share their bookmarks with others, as well as annotate directories with keywords and domains- library resource as a Blog entry- users can comment a resource, thus providing new knowledge to the library
72. based on the tag ontology by Tom Gruber tagging connects taggera, with document, with termg community annotations for multimedia (currently in alpha stage) the goal is to allow tagging in any type of documents region of interest (ROI) tagging in photos time-tagging of video streams tags can contain descriptions, keywords, links and cross references
73. - when we will put all those ontologies together – this is what we got
74. What has Orang-utan from the Unseen University in Ankh-Morpork to do with semantic digital libraries? Well – he was the first librarian to develop a very complicated controlled vocabullary for describing resources. It consisted out of **one** word Ook – with various modifications like „Oook”, „gook”, „eek”, „eeek”.