Spatial Hypertext represents associations between chunks of information by spatial or visual attributes (such as proximity, color, shape etc.). This allows expressing information structures implicitly and in an intuitive way. However, automatic recognition of such informal, implicitly encoded structures by a machine (a so-called spatial parser) is still a challenge. One reason is, that conventional (non-adaptive) parsers are conceptually restricted by their underlying source of information (i. e., the spatial hypertext). Due to this limitation there are several types of structures that cannot be recognized properly. This inevitably limits both quality of parser output and parser performance. We claim that considering temporal aspects in addition to spatial and visual properties in spatial parser design will lead to significant increase in parsing accuracy, detection of richer structures and thus higher parser performance.

For the purpose of providing evidence, parsers for recognizing spatial, visual and temporal object relations have been implemented and tested in a series of user surveys. It turned out, that in none of the test cases pure spatial or visual parser could outperform the spatio-temporal parser. Instead, the spatiotemporal parser was able to compensate limitations of conventional parsers. Furthermore, differences in parsing accuracy were successfully tested for statistical significance. The results indicate a non-trivial effect that is recognizable by humans. We have shown that the addition of a temporal parser shifts machine detected structures significantly closer to what knowledge workers intend to express.

The capability to operate cloud-native applications can generate enormous business growth and value. But enterprise architects should be aware that cloud-native applications are vulnerable to vendor lock-in. We investigated cloud-native application design principles, public cloud service providers, and industrial cloud standards. All results indicate that most cloud service categories seem to foster vendor lock-in situations which might be especially problematic for enterprise architectures. This might sound disillusioning at first. However, we present a reference model for cloud-native applications that relies only on a small subset of well standardized IaaS services. The reference model can be used for codifying cloud technologies. It can guide technology identification, classification, adoption, research and development processes for cloud-native application and for vendor lock-in aware enterprise architecture engineering methodologies.

Technische Sicherheit erzeugt mehr Rechtssicherheit, wenn sie Haftung und Schäden vermindern oder zu vermeiden hilft. Bei Verstößen gegen Recht und Gesetz drohen erhebliche Bußgelder und ggf. ein Image- Verlust. IT-Compliance als Einhaltung von Recht und Gesetz von und durch IT ist vom technisch Machbaren und wirtschaftlich Vertretbaren abhängig. Technische Sicherheit kann dann mehr Rechtssicherheit erzeugen, wenn für Konzeption und Implementierung der technischen und organisatorischen Maßnahmen die gesetzli- chen Anforderungen berücksichtigt, Risiken eingeschätzt und diese beweisbar dokumentiert werden. Hierfür ist ein strukturierter und dauerhafter IT-Compliance Prozess erforderlich.

Background

Medical symptoms independent of body location burden individuals to varying degrees and may require care by more than one expert. Various paper and computer-based tools exist that aim to comprehensively capture data for optimal clinical management and research.

Methods

A web-based interdisciplinary symptom evaluation (WISE) was newly designed, constructed, and technically implemented. For worldwide applicability and to avoid copyright infringements, open source software tools and free validated questionnaires available in multiple languages were used. Highly secure data storage limits access strictly to those who use the tool for collecting, storing, and evaluating their data. Concept and implementation is illustrated by a WISE sample tailored for the requirements of a single center in Switzerland providing interdisciplinary care to orofacial pain and temporomandibular disorder patients.

Results

By combining a symptom- burden checklist with in-depth questionnaires serving as case-finding instruments, an algorithm was developed that assists in clarifying case complexity and need for targeted expert evaluation. This novel modular approach provides a personalized, response-tailored instrument for the time- and cost-effective collection of symptom-burden focused quantitative data. The tool includes body drawing options and instructional videos. It is applicable for biopsychosocial evaluation in a variety of clinical settings and offers direct feedback by a case report summary.

Conclusions

In clinical practice, the new instrument assists in clarifying case complexity and referral need, based on symptom burden and response –tailored case finding. It provides single-case summary reports from a biopsychosocial perspective and includes graphical symptom maps. Secure, centrally stored data collection of anonymous data is possible. The tool enables personalized medicine, facilitates interprofessional education and collaboration, and allows for multicenter patient-reported outcomes research.

Compliance, die Einhaltung von Recht und Gesetz und unternehmensinternen Normen, ist Teil der Good Corporate Governance und Bestandteil des Risikomanagements. Compliance ist damit eine rechtliche, organisatorische und Prozessherausforderung für jedes Krankenhaus. Einigkeit besteht mittlerweile darüber, dass jedes Unternehmen sich mit den Herausforderungen von Compliance beschäftigen sollte, auch wenn Rechtsgrundlagen und Umfang der erforderlichen Maßnahmen im Einzelnen noch ungeklärt sind. Compliance ist eine Aufgabe der Unternehmensleitung, die in der Umsetzung an einen entsprechend qualifizierten Compliance Officer delegiert werden kann. Die Letztverantwortung für Compliance im Krankenhaus verbleibt jedoch immer bei der Leitung selbst. Der Aufbau eines angemessenen Compliance Management Systems soll die Haftungsrisiken für das Unternehmen und seine Leitung mindern. Ob Compliance Zertifizierungen hierzu beitragen können, ist weder durch Gesetz noch die Rechtsprechung geklärt.

Spatial hypertext represents associations between chunks of information by spatial or visual attributes (such as proximity, color, shape, etc.). This supports expressing information structures implicitly and in an intuitive way. However, automatic recognition of such informal, implicitly encoded structures by a machine (a so-called spatial parser) is still a challenge. Conventional parsers are conceptually restricted by their underlying source of information. Due to this limitation there are various possible structures that cannot be recognized properly, as the machine has no means to detect them. This inevitably limits both the quality of parser output and hence parser performance. In this paper we show that considering temporal aspects in spatial parser design will lead to significant increase in parsing accuracy, detection of richer structures and thus higher parser performance. We call machines that consider such spatial and temporal information spatio-temporal parsers.

For the purpose of providing evidence, parsers for recognizing spatial, visual, and temporal object relations have been implemented and tested in a series of user surveys. One aim was to find out how "close" the machine interpretetation of structures get to human interpretation. It turned out that in none of the test cases pure spatial or visual parser could outperform the spatio-temporal parser. Instead, the spatio-temporal parser was able to compensate limitations of conventional parsers. Furthermore, we have statistically tested parsing accuracy. The results indicate a non-trivial effect that is recognizable by humans. This shows that spatio-temporal parsers produce output that is significantly closer to what knowledge workers intend to express compared to traditional spatial parsers.

The Semantic Web has matured from a vision and research area of a few AI specialists to an important technology being used in a large number of research and a few practice projects. Most building blocks of the Semantic Web stack are filled with concrete technologies and W3C standards, but there are still enough areas for research. However, even with existing technologies, the potential of semantic applications within corporations is not yet fully harnessed as the adoption of Semantic Web technologies lacks behind other technologies like NoSQL databases or Web 2.0 technologies. This paper reviews the state of the art of Semantic Web technologies, discusses important terms and developments as well as currently active research streams. It further analyses available tools and applications with a focus on corporate scenarios and open source software and concludes with the suggestion of an architecture for a corporate semantic intranet.

Docker provides a good basis to run composite applications in the cloud, especially if those are not cloud-aware, or cloud-native. However, Docker concentrates on managing containers on one host, but SaaS providers need a container management solution for multiple hosts. Therefore, a number of tools emerged that claim to solve the problem. This paper classifies the solutions, maps them to requirements from a case study and identifies gaps and integration requirements. We close some of these gaps with our own integration components and tool enhancements, resulting in the currently most complete management suite.

Der Hype um das Container-Werkzeug Docker ist auch drei Jahre nach seiner ersten Veröffentlichung ungebrochen. Docker
adressiert sowohl Entwickler, die einen einfachen Weg suchen, um ihre Anwendungen zu testen und anschließend in die
Produktivumgebung zu bringen, als auch Cloud-Betreiber, die durch die Verwendung von Containern statt Virtuellen Maschinen
(VMs) eine höhere Packungsdichte und Performance realisieren können. Während die Handhabung für Entwickler mit einzelnen
Docker-Containern recht einfach ist, setzen die „Googles“ und „Netflixe“ dieser Welt häufig selbstentwickelte Werkzeugketten
ein, um die Komplexität in großen Umgebungen durch Automatisierung beherrschbar zu machen. Dazwischen stehen mittel-
ständische Cloud-Anbieter oder Rechenzentren größerer Unternehmen, die sich keine Entwicklerschar für Docker-Tools leisten
können oder wollen, andererseits aber die Komplexität manuell nicht mehr handhaben können. Für diese gibt es eine schier
unüberschaubare Anzahl an Open-Source-Werkzeugen, die das eine oder andere Problem mildern, jedoch kaum eine um-
fassende Lösung aus einem Guss. Der vorliegende Artikel zeigt, welche Aufgaben zu erfüllen sind, welche Werkzeuge welche
Aspekte davon abdecken und welche Kombinationen von Werkzeugen miteinander harmonieren, um eine umfassende Lösung
zu erreichen.

Bei auf die Infrastruktur bezogenen Szenarien hat Open-Source-Software in den vergangenen Jahren ihre Tauglichkeit für den Firmeneinsatz bereits hinreichend unter Beweis gestellt.

Entgegen der landläufigen Meinung bietet freie Software auch im Bereich klassischer Enterprise-Applikationen durchaus ernstzunehmende Alternativen zu den proprietären Produkten.

Anwender sind bei Problemen aber nicht ausschließlich auf die Gnade der Community angewiesen; ein mittlerweile existierendes Dienstleistungsökosystem kann Service-Ansprüche auch von Unternehmen zufriedenstellen.

This paper proposes to make complex production machines more user-friendly. Improved machines help the operator in case of an error message or a process event by displaying recommendations, such as “in the last 10 occurences of this event the operators performed the following keystrokes”. The messages are generated from statistical data on former user- interaction and previous process-events. The data represents the knowledge of all the machine operators. The data is gathered by logging user-interaction and process-events during regular operation of the production machine. This approach allows to store the operators’ expert knowledge in the production machine without human intervention.

NoSQL and especially graph databases are constantly gaining popularity among developers as they promise to deliver superior performance when handling highly interconnected data compared to relational databases. Apache Shindig is the reference implementation for OpenSocial with a highly interconnected data model. However, it had a relational database as back-end. In this paper we describe our experiences with the graph database Neo4j as back-end and compare Cypher, Gremlin and Java as alternatives for querying data with MySQL. We consider performance as well as usability from a developer's perspective. Our results show that Cypher is a good query language in terms of code readability and has a moderate overhead for most queries (20–200%). However, it has to be supplemented with “stored procedures” to make up for some performance deficits in pattern matching queries (>1000%). The RESTful API is unusable slow, whereas our WebSocket connection performs significantly better (>650%).

Die digitale Transformation bringt ein viel diskutiertes Thema zurück auf die Agenda: IT-Compliance. Wie die Öffentliche Verwaltung davon betroffen ist, untersuchen das Institut für Informationssysteme (iisys) der Hochschule Hof und die Blue Eye Solutions GmbH. Erste Ergebnisse des laufenden Forschungsprojekts liegen nun vor.

In the present mobile climate, both companies as well as their consumers are able to execute various processes at any time in any location using a myriad of wireless technologies. Organizational trends demonstrate that mobile devices are being utilized exponentially more to solve problems from the strategic planning level to the operational level through various departments. This propensity was recently confirmed for Germany in a neoteric IDC study [1]. Utilizing that analysis, this article will evaluate and inspect the scope of such modeling. We will endeavor to define the term "mobile modeling", and our final desideratum will be to present results from an empirical investigation of its requirements and benefits. Finally, we will discuss the future technical implications and conclusions of the model.