Demo Data from VLDB 2026 / reviewers in the wild / expert
Benjamin Brandl
dblp:37/10082
· DBLP profile ↗
1ranked-venue papers
0as first author
0since 2021 · last 2011
—ORCID · none
Domains — the database's venue-derived domains; a paper can count in several
Software engineering, systems software and programming languages · 1
Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.
| Software engineering, system software, and programming languages
1 paper |
Software maintenance and evolution · 87% Empirical software engineering · 13% |
Topics — the 3 heaviest of 3, each with the papers that count most for it
| Topic | Weight | Papers | Last | Evidence papers |
|---|---|---|---|---|
Software maintenance and evolution › software merging
merge conflict resolution |
0.1 | 1 | 2011 | Semistructured merge: rethinking merge in revision control systems · SIGSOFT FSE 2011 |
Software maintenance and evolution › software configuration management
version control |
0.1 | 1 | 2011 | Semistructured merge: rethinking merge in revision control systems · SIGSOFT FSE 2011 |
Empirical software engineering
mining software repositories |
0.0 | 1 | 2011 | Semistructured merge: rethinking merge in revision control systems · SIGSOFT FSE 2011 |
Methods — techniques the papers use, named apart from their topics
empirical study · 0.1annotated grammars · 0.1
| Year | Publication | Venue | Position |
|---|---|---|---|
| 2011 | Semistructured merge: rethinking merge in revision control systemsabstractAn ongoing problem in revision control systems is how to resolve conflicts in a merge of independently developed revisions. Unstructured revision control systems are purely text-based and solve conflicts based on textual similarity. Structured revision control systems are tailored to specific languages and use language-specific knowledge for conflict resolution. We propose semistructured revision control systems that inherit the strengths of both: the generality of unstructured systems and the expressiveness of structured systems. The idea is to provide structural information of the underlying software artifacts --- declaratively, in the form of annotated grammars. This way, a wide variety of languages can be supported and the information provided can assist in the automatic resolution of two classes of conflicts: ordering conflicts and semantic conflicts. The former can be resolved independently of the language and the latter using specific conflict handlers. We have been developing a tool that supports semistructured merge and conducted an empirical study on 24 software projects developed in Java, C#, and Python comprising 180 merge scenarios. We found that semistructured merge reduces the number of conflicts in 60% of the sample merge scenarios by, on average, 34%, compared to unstructured merge. We found also that renaming is challenging in that it can increase the number of conflicts during semistructured merge, and that a combination of unstructured and semistructured merge is a pragmatic way to go. Sven Apel, Jörg Liebig, Benjamin Brandl, Christian Lengauer, Christian Kästner |
SIGSOFT FSE | 3 |