scispace - formally typeset
Open AccessPosted Content

Guided Grammar Convergence.

Reads0
Chats0
TLDR
This paper investigates several milestones between those two extremes between language equivalence and grammar identity, and proposes a methodology for inconsistency management in grammar engineering.
Abstract
Relating formal grammars is a hard problem that balances between language equivalence (which is known to be undecidable) and grammar identity (which is trivial). In this paper, we investigate several milestones between those two extremes and propose a methodology for inconsistency management in grammar engineering. While conventional grammar convergence is a practical approach relying on human experts to encode differences as transformation steps, guided grammar convergence is a more narrowly applicable technique that infers such transformation steps automatically by normalising the grammars and establishing a structural equivalence relation between them. This allows us to perform a case study with automatically inferring bidirectional transformations between 11 grammars (in a broad sense) of the same artificial functional language: parser specifications with different combinator libraries, definite clause grammars, concrete syntax definitions, algebraic data types, metamodels, XML schemata, object models.

read more

Citations
More filters
Journal ArticleDOI

Grammar Zoo

TL;DR: This paper describes composition of a corpus of grammars in a broad sense in order to enable reuse of knowledge accumulated in the field of grammarware engineering and describes in detail the technology that is used to build and extend such a corpus.
Proceedings ArticleDOI

Renarrating linguistic architecture: a case study

TL;DR: This paper addresses the possibility of using one megamodel to tell several related stories --- that is, to renarrate it, and presents the renarration method with the case study of a software language engineering technique of guided grammar convergence, and MegaL as a metamegamodel.
Journal ArticleDOI

Software Language Engineering by Intentional Rewriting

TL;DR: A disciplined process of engineering a language for grammar mutations capable of applying uniform intentional transformations in the scope of a big grammar or a corpus of grammars by systematic reuse of semantic components of another existing software language is described.
Proceedings ArticleDOI

Negotiated grammar transformation

TL;DR: A different model of processing unidirectional programmable grammar transformation commands, that makes them more adaptable, and explains two kinds of different adaptability of transformation (through tolerance and through adjustment).

The Grammar Hammer of 2012

Vadim Zaytsev
TL;DR: In this article, personal research results of the year 2012 are documented in a form primarily intended for assessment of their scientific merit as a foundation for future work, not for quantitative assessment of the resulting publication record.
References
More filters
Journal ArticleDOI

A survey of approaches to automatic schema matching

TL;DR: A taxonomy is presented that distinguishes between schema-level and instance-level, element- level and structure- level, and language-based and constraint-based matchers and is intended to be useful when comparing different approaches to schema matching, when developing a new match algorithm, and when implementing a schema matching component.
Journal ArticleDOI

Definite clause grammars for language analysis—A survey of the formalism and a comparison with augmented transition networks

TL;DR: It is argued that DCGs can be at least as efficient as ATNs, whilst the DCG formalism is clearer, more concise and in practice more powerful.
Proceedings ArticleDOI

Parsing expression grammars: a recognition-based syntactic foundation

TL;DR: PEGs address frequently felt expressiveness limitations of CFGs and REs, simplifying syntax definitions and making it unnecessary to separate their lexical and hierarchical components, and are here proven equivalent in effective recognition power.
Journal Article

Differential Testing for Software.

TL;DR: Quality is not a question of correctness, but rather of how many bugs are fixed and how few are introduced in the ongoing development process, if the bug count is increasing, the software is deteriorating.
Journal ArticleDOI

Bidirectional model transformations in QVT: semantic issues and open questions

TL;DR: It is shown that any transformation language sufficient to the needs of model-driven development would have to be able to express non-bijective transformations.
Related Papers (5)