A Strategy Language for Graph Rewriting

Abstract

Abstract. We give a formal semantics for a graph-based programming language, where a program consists of a collection of graph rewriting rules, a user-defined strategy to control the application of rules, and an initial graph to be rewritten. The traditional operators found in strategy languages for term rewriting have been adapted to deal with the more general setting of graph rewriting, and some new constructs have been included in the language to deal with graph traversal and management of rewriting positions in the graph. This language is part of the graph transformation and visualisation environment PORGY.

Multilevel coupled model transformations for precise and reusable definition of model behaviour

“…About the next steps in our work, we plan to increase the tool support to both hierarchies and MCMTs specification, as well as test their feasibility in new scenarios. In addition, we plan to use, or adapt, strategy languages like [88,89] in order to coordinate the execution of MCMTs, allowing for even richer semantics for the execution of behavioural DSLs [61].…”

Strategic Port Graph Rewriting: An Interactive Modelling and Analysis Framework

“…The syntax presented here extends the one in [14] by including a language to define subgraphs of a given graph by selecting nodes that satisfy some simple properties (see Table 2).…”

“…PORGY and its strategy language were first presented in [1,14]. Unlike those papers, the notion of port graph considered in this paper includes attributes for nodes, ports and also edges, which are taken into account in the definition of port graph morphism.…”

PORGY: A Visual Graph Rewriting Environment for Complex Systems

“…Designing formal languages to specify rewriting strategies is beyond the scope of this paper and forms a whole chapter of port graph rewriting. More details on PORGY's rewriting strategy language developed by our partners may be found in [FKN12].…”

“…Choosing a rule is accomplished by dragging and dropping the involved rules onto the strategy panel and combining them with proper operators (A2). The development of the underlying formal language [FKN12] to describe strategies evolved as users (biologists and computer scientists) experimented with our environment. Several iterations were necessary, reasoning about the system and testing several different combinations of rules, to design adequate rulesets and strategies.…”