This preview shows pages 1–2. Sign up to view the full content.
This preview has intentionally blurred sections. Sign up to view the full version.View Full Document
Unformatted text preview: A Semantic Wiki Approach to Cultural Heritage Data Management Ren´e Witte, Thomas Gitzinger, Thomas Kappler, Ralf Krestel Institut f¨ur Programmstrukturen und Datenorganisation (IPD) Universit¨at Karlsruhe (TH), Germany Abstract Providing access to cultural heritage data beyond book digitization and information retrieval projects is important for delivering advanced semantic support to end users, in order to address their specific needs. We introduce a separation of concerns for heritage data management by explicitly defining different user groups and analyzing their particular requirements. Based on this analysis, we developed a comprehensive system architecture for accessing, annotating, and querying textual historic data. Novel features are the deployment of a Wiki user interface, natural language processing services for end users, metadata generation in OWL ontology format, SPARQL queries on textual data, and the integration of external clients through Web Services. We illustrate these ideas with the management of a historic encyclopedia of architecture. 1. Introduction The amount of publicly available knowledge increases faster than we can imagine—hence the term “Information Ex- plosion” used by several authors ( Lyman and Varian, 2003 ; Sweeney, 2001 ). With the barrage of newly created content— news, blogs, web pages, research papers—existing, “analog” documents and their users often receive less attention than the quality of the content deserves. In this paper, we present the results from a project aimed at developing enhanced semantic support for users of textual cultural heritage data. A particular feature of our approach is the integration of different concerns into a single, cohesive system architecture that addresses requirements from end users, software engineering aspects, and knowledge discov- ery paradigms. The ideas were implemented and tested with a historic encyclopedia of architecture and a number of dif- ferent user groups, including building historians, architects, and NLP system developers. 2. User Groups and Requirements Nowadays, the baseline for cultural heritage data man- agement of book-type publications is the production of a scanned (digitized) version that can be viewed and dis- tributed online, typically with some kind of Web interface. Before we can deliver more advanced access methods, we have to be more precise about the targeted end users. Who needs access to heritage data, and for what purpose? 2.1. User Groups Within our project, we had to consider the requirements from four different user groups; each of them having a different background and expectations concerning the management of historic textual data....
View Full Document
- Spring '12
- Data Management