type:: [[REVIEWS]]
full-title:: Asymmetric and Directed Bidirectional Transformation for Container Orchestrations
venue:: [[TTC]]
year:: 2023
date-start:: [[21-04-2023]] - 13:16
date-submitted:: [[21-04-2023]]
external-links:: ![TTC_2023_paper_3.pdf](../assets/TTC_2023_paper_3_1682076037575_0.pdf)
status:: [[DONE]]

	- [[Highlights]]
	- [[Comments]]
		- *Is the motivation of the case clear? Why does the problem matter?*
			- The author has done an excellent job presenting and motivating the case. I concur with the author's assertion that demonstrating the use of state-of-the-art bx tools on this case "could prove to be an interesting application niche." As outlined in the paper, it is currently common to encounter inconsistent model-based and corresponding textual-based docker compose specifications at an early stage of development.
		- *Is the description of the problem clear? Would you know roughly how to approach the problem in your favourite transformation tool?*
			- The problem is clearly articulated, and practitioners familiar with developing model transformations have ample material to devise a solution for this case.
		- *Are appropriate resources made available? Would you have access to appropriate models, test cases, etc. for constructing a solution to the case?*
			- The material described in Section 3.2 seems to be appropriate for developing solutions for the given case.
		- *Are the evaluation criteria reasonable and interesting? Would you feel that your solution to the problem was being judged fairly and that we might learn something from the comparison?*
			- Consistent with a previous analogous case, the evaluation criteria presented are sensible and intriguing. It might be beneficial to include a roster of change cases (pertaining to both the model and the docker-compose specification) that competing solutions are expected to accommodate.