logseq/pages/LARC2025-278.md

type:: [[REVIEWS]]
tags:: 
year:: 2025
venue:: [[ICSA-LARC]]
full-title:: Streamlining the Engineering and Distribution of Graphical DSLs based on Recurring Patterns
date-start:: [[20-01-2025]] - 17:59
date-submitted::
external-links::
status:: [[DONE]] 
deadline-submission:: 
file:: [[@Streamlining the Engineering and Distribution of Graphical DSLs based on Recurring Patterns]] 
parent::
todoist:: https://app.todoist.com/app/task/l-arc-2025-submission-assignment-6X45crcww3pgQCF8

	- ### [[Highlights]]
	  collapsed:: true
		- # Annotazioni  
		  
		  (20/1/2025, 17:50:34)
		- “Abstract—In” ([Mitwalli et al., p. 4](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=1&annotation=29WPCJHZ)) #ffd400  
		  
		  *The abstract is not effective in presenting what are the problems in the focus of the paper in making a clear sttement of what is the proposed solution of the work.*
		- “LCNC” ([Mitwalli et al., p. 4](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=1&annotation=WBI2NN64)) #ffd400  
		  
		  *This is the first occurrence of this acronym and as a such it is necessary to put it here in the extended manner.*
		- “possibly” ([Mitwalli et al., p. 4](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=1&annotation=8R8JNJUY)) #ffd400
		- “key patterns” ([Mitwalli et al., p. 4](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=1&annotation=FWDN6XRH)) #ffd400  
		  
		  *what kind of patterns are you looking for? Patterns of what?*
		- “project 1” ([Mitwalli et al., p. 4](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=1&annotation=ALH7K6NW)) #ff6666
		- “In that sense, we will demonstrate the potential of Cinco Cloud in streamlining language engineering processes and discuss the future development of such repositories in the language engineering landscape.” ([Mitwalli et al., p. 4](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=1&annotation=Z7G5AEU8)) #5fb236
		- “Several metamodeling tools address this problem by generating dedicated IMEs from a high-level specification that are then tailored to a specific set of graphical DSLs such as Eclipse Sirius Web [2] 2, WebGME [10] 3 and others [11, 1, 9, 7].” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=S35BBAKX)) #ffd400
		- “[2] 2” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=669CLC2T)) #ff6666
		- “There, language engineers can specify graphical languages using two high-level textual specification languages:” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=T4IBWG4J)) #ffd400  
		  
		  *The novelty is not clarified.*
		- “Meta Graph Language (MGL)” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=8IL3TGEF)) #2ea8e5
		- “Meta Style Language (MSL)” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=WBKVHUUR)) #2ea8e5
		- “TypeScript” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=AJ7LNS87)) #5fb236
		- “By abstracting the complexities of IME development, Cinco Cloud allows users to focus on designing DSLs and deploying intuitive graphical modeling tools.” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=NSNFBMG9)) #ffd400  
		  
		  *Still not clear what are the limitations of existing approaches that authors aim at addressing, and thus what are the novelties of Cinco Cloud concerning the development of domain-specific modeling languages.*
		- “uploading the associated language to a central language repository.” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=RRHTRDSY)) #ffd400  
		  
		  *THis is potentially interesting even though it is not clear what are the provided reusability mechanisms.*
		- “A domain expert simply selects the language through a form and a dedicated IME is automatically deployed in the Cinco Cloud, ready to use. Under the hood, a general purpose IME is deployed, the selected language(s) fetched from the central language repository into the IME, and thereby the IME is configured for the language(s).” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=8NVTX9GE)) #ffd400  
		  
		  *What's new with what MetaEdit++ or other modeling platforms already provide?*
		- “These are provided automatically by Cinco Cloud 4” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=9ZSCMHT6)) #a28ae5
		- “abstract and concrete syntax of a graphical DSL” ([Mitwalli et al., p. 5](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=2&annotation=TJZFBLKL)) #5fb236
		- “Eclipse Layout Kernel (ELK)” ([Mitwalli et al., p. 6](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=3&annotation=LMVKJRV3)) #a28ae5
		- “. Dyamic Components and Functionalities” ([Mitwalli et al., p. 6](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=3&annotation=Z7FPI4J6)) #ffd400  
		  
		  *Over the last few years there has been a proliferation of low-code platforms that permit to develop applications by reusing components that embody recurring behaviours. It is necessary to compare the propose approach with such a line of research.*
		- “CertBot 8” ([Mitwalli et al., p. 7](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=4&annotation=AFY4FSG8)) #ffd400
		- “Langium-based 11 language server” ([Mitwalli et al., p. 7](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=4&annotation=CRDF253Y)) #ffd400
		- “easing the distribution and composition of languages, both from language-designer to language-designer, as well as from language-designer to domain-expert (a holistic approach)” ([Mitwalli et al., p. 8](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=5&annotation=7SCBUV9P)) #ffd400  
		  
		  *This concept of language composition is not clear. It is relevant, but it is not clear how the proposed approach has addressed such a problem.*
		- “Sprotty Client 13 and GLSP server” ([Mitwalli et al., p. 9](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=6&annotation=GFXSUR4L)) #a28ae5
		- “As mentioned before, our language repository currently only supports a single version of each language.” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=HMAI22B7)) #5fb236
		- “Although the current state of the central language repository is an independent microservice, it is not yet completely independent from the overall Cinco Cloud archetecture.” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=HUGPWSS6)) #5fb236
		- “archetecture” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=9JUWFFFY)) #ff6666
		- “an independently deployable service that can be integrated with other cloud-based archetectures for LCNC platforms, including a generalized API.” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=AQEAH325)) #ffd400  
		  
		  *I'm not sure I got the plan of the authors. The repository is supposed to store languages developed with the Cinco Cloud and to enable their reuse. What does it mean enabling the integration of the repository in other LCNC platforms? How to to ensure the their interoperability/compatibility?*
		- “common patterns” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=Y48NFW7Y)) #ffd400  
		  
		  *it is not clear in the paper what are the common patterns that have been identified with respect to already existing primitives that existing (meta)modeling platforms already implement.*
		- “recurring patterns” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=IVH77YQN)) #ffd400  
		  
		  *if the authors are referring to the content given in Section III, it is not clear what's their novelty.*
		- “the externalization of a centralized language repository.” ([Mitwalli et al., p. 10](zotero://select/library/items/8L6UM4C9)) ([pdf](zotero://open-pdf/library/items/AMAMTJKN?page=7&annotation=XJ8GECQT)) #ffd400  
		  
		  *I see this as potential novelty of the proposed approach and as a such I would restructure the paper and rebalance the content and focus in this direction, instead of pushing the recuccring patterns concepts, that instead are recurring functionalities that are expected by any modeling environments nowadays.*
	- ### [[Comments]]
		- **SUMMARY:** The paper introduces Cinco Cloud, a platform for supporting the development and deployment of domain-specific languages. DSLs are defined in terms of two different specifications defining the abstract and the concrete syntax of the language being developed. Cinco Cloud supports language reuse by relying on a centralized language repository.
		- **COMMENTS**: The topic of simplifying the development and reuse of DSLs is, of course, interesting, even though the paper struggles to effectively highlight the novelty of Cinco Cloud in comparison to existing solutions. I have several concerns about the paper that are related to the following issues:
			- The abstract fails to clearly articulate the problem and proposed solution. This reduces the initial impact of the paper.
			- The novelty of the proposed approach is not clearly stated. For instance:
				- The distinction between Cinco Cloud and existing tools like MetaEdit++ and other platforms is unclear.
				- The recurring patterns mentioned in the paper lack innovative elements compared to functionalities provided by existing (meta)modeling platforms.
				- The externalization of a centralized language repository is a potential novelty but is underexplored and should be given more focus.
			- The concept of "language composition" is introduced but not adequately explained. More clarity and examples are needed to illustrate how the approach addresses this challenge.
			- The reusability mechanisms of the central language repository are unclear. More details on these mechanisms and their interoperability with other LCNC platforms would strengthen the paper's contribution.
			- There is a lack of sufficient comparison with existing LCNC platforms and low-code tools that facilitate application development. Discussing how Cinco Cloud advances beyond these platforms is critical to establishing its significance.
			- The concept of recurring patterns is overemphasized, while the centralized language repository - a potentially novel feature - is not sufficiently detailed. Restructuring the paper to highlight this aspect would better align with its contributions.
			- LCNC, a key term in the paper, is used without prior expansion. For clarity, it should be introduced in complete form on the first occurrence.
		- Thus, the Cinco Cloud platform is interesting, even though the paper is not convincing about its novelty, strengths, and limitations. I suggest at least the following actions:
			- Rewrite the abstract to make the problem statement and proposed solution explicit.
			- Provide a comparison with existing tools, emphasizing the unique aspects of Cinco Cloud.
			- Focus on the centralized language repository as a key contribution and provide details on how it ensures reusability and interoperability.
			- Clarify technical concepts such as language composition with concrete examples.
	- ### YELLOW CONCERNS
	  background-color:: yellow
	  collapsed:: true
		- {{query (and [[ffd400]] [[LARC2025-278]] )}}