Stop the war!

Остановите войну!

for scientists:

default search action

combined dblp search
author search
venue search
publication search

ask others

Timo Sztyler

Name: dblp XML data dump
Creator: Schloss Dagstuhl - Leibniz Center for Informatics
Published: 1993
License: https://creativecommons.org/publicdomain/zero/1.0/
Keywords: dblp, XML, computer science, scholarly publications, metadata

◀ ▶ joint publications with Christian Bikar

> Home > Persons > Timo Sztyler

Publications

2015
[c5]
- view
  authority control:
- export record
  dblp key:
  - conf/mum/OpitzSJKBPS15
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/mum/OpitzSJKBPS15
Bernd Opitz, Timo Sztyler, Michael Jess, Florian Knip, Christian Bikar, Bernd Pfister, Ansgar Scherp:
On-the-fly entity resolution from distributed social media sources for mobile search and exploration. MUM 2015: 14-24
2014
[c4]
- view
  - electronic edition @ ceur-ws.org (open access)
  - no references & citations available
- export record
  dblp key:
  - conf/esws/OpitzSJKBPS14
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/esws/OpitzSJKBPS14
Bernd Opitz, Timo Sztyler, Michael Jess, Florian Knip, Christian Bikar, Bernd Pfister, Ansgar Scherp:
An Approach for Incremental Entity Resolution at the Example of Social Media Data. AIMashup@ESWC 2014
[c2]
- view
  authority control:
- export record
  dblp key:
  - conf/mum/KnipBPOSJS14
- ask others
- share record
  persistent URL:
  - https://dblp.org/rec/conf/mum/KnipBPOSJS14
Florian Knip, Christian Bikar, Bernd Pfister, Bernd Opitz, Timo Sztyler, Michael Jess, Ansgar Scherp:
A field study on the usability of a nearby search app for finding and exploring places and events. MUM 2014: 123-132

a service of

manage site settings

To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.