Recovered after rebase

2025-06-22 20:36:12 +02:00
parent f27d0bc951
commit 33f6de7df9
25 changed files with 844 additions and 422 deletions
@@ -2978,9 +2978,9 @@ This paper investigates the conceptual and technical feasibility of a new softwa
 \par
 8E5M8QKA\{"readingTime":\{"page":12,"data":\{"0":530,"1":1430,"2":1400,"3":1140,"4":450,"5":240,"6":330,"7":210,"8":250,"9":50\}\}\}
 \par
-9F5F2G9D\{"readingTime":\{"page":8,"data":\{"0":50\}\}\}
+9F5F2G9D\{"readingTime":\{"page":8,"data":\{"0":760,"1":680,"2":850,"3":120,"4":50,"5":50,"6":70,"7":70\}\}\}
 \par
-9G4B4RYG\{"readingTime":\{"page":477,"data":\{"0":20,"2":10,"3":20,"4":10,"7":20,"14":10,"17":140,"18":40,"19":10,"20":40,"21":30,"22":10,"25":220,"26":180,"27":140,"28":110,"29":40,"30":40,"31":340,"32":250,"33":90,"34":300,"35":340,"36":490,"37":220,"38":400,"39":230,"40":80,"399":10,"400":20\}\}\}
+9G4B4RYG\{"readingTime":\{"page":477,"data":\{"0":30,"2":10,"3":20,"4":10,"7":20,"14":10,"17":140,"18":40,"19":10,"20":40,"21":30,"22":10,"25":220,"26":180,"27":140,"28":110,"29":40,"30":40,"31":340,"32":250,"33":90,"34":300,"35":340,"36":490,"37":220,"38":410,"39":230,"40":80,"399":10,"400":20\}\}\}
 \par
 9QF9CWEH\{"readingTime":\{"page":44,"data":\{"0":30\}\}\}
 \par
@@ -2988,7 +2988,7 @@ This paper investigates the conceptual and technical feasibility of a new softwa
 \par
 9VTMURYV\{"readingTime":\{"page":9,"data":\{"3":10\}\}\}
 \par
-66AQQ5ZI\{"readingTime":\{"page":4,"data":\{"0":430,"1":680,"2":780,"3":490\}\}\}
+66AQQ5ZI\{"readingTime":\{"page":4,"data":\{"0":560,"1":730,"2":830,"3":500\}\}\}
 \par
 78JSCZMI\{"readingTime":\{"page":12,"data":\{"0":810,"1":1060,"2":440,"3":610,"4":430,"5":520,"6":760,"7":220,"8":430,"9":500,"10":200\}\}\}
 \par
@@ -34297,114 +34297,116 @@ And then add a Detailed Comments section to report the notets that contain issue
  author = {Muctadir, Hossain Muhammad and Liao, Yanyifan and Cleophas, Loek},
  abstract = {Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services. VEs are typically model-based software systems that incorporate a variety of multi-domain, multi-tool models that are essential throughout the DT’s lifecycle. Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT. In this paper, we present a case study on consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production.},
  langid = {english},
-  note = {\section{Annotazioni\\
+  note = {I'm reviewing a research paper and I took the following notes:
 \par
 \section{Annotazioni\\
 (16/6/2025, 23:22:43)}
 \par
- “Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services.” (Muctadir et al., p. 1) \#5fb236\\
+- “Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services.” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT.” (Muctadir et al., p. 1) \#5fb236\\
+- “Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT.” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production” (Muctadir et al., p. 1) \#a28ae5\\
+- “consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production” (Muctadir et al., p. 1) \#a28ae5
-\mkbibemph{ }
+
 \par
- “model inconsistencies during the DT lifecycle are frequent and have a major impact on DT functionality” (Muctadir et al., p. 1) \#e56eee\\
+- “model inconsistencies during the DT lifecycle are frequent and have a major impact on DT functionality” (Muctadir et al., p. 1) \#e56eee
-\mkbibemph{ }
+
 \par
- “effective consistency management method for DT models.” (Muctadir et al., p. 1) \#a28ae5\\
+- “effective consistency management method for DT models.” (Muctadir et al., p. 1) \#a28ae5
-\mkbibemph{ }
+
 \par
- “conceptual framework to address the challenges of consistency management for DT models.” (Muctadir et al., p. 1) \#5fb236\\
+- “conceptual framework to address the challenges of consistency management for DT models.” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “In this paper, we further evaluate the framework with a DT from the bio-chemical domain.” (Muctadir et al., p. 1) \#a28ae5\\
+- “In this paper, we further evaluate the framework with a DT from the bio-chemical domain.” (Muctadir et al., p. 1) \#a28ae5
-\mkbibemph{ }
+
 \par
- “We manage the consistency of the VE comprising four models, which are essential for delivering two services associated with predicting and controlling alcohol production.” (Muctadir et al., p. 1) \#e56eee\\
+- “We manage the consistency of the VE comprising four models, which are essential for delivering two services associated with predicting and controlling alcohol production.” (Muctadir et al., p. 1) \#e56eee
-\mkbibemph{ }
+
 \par
- “Section II reviews research on model consistency management” (Muctadir et al., p. 1) \#5fb236\\
+- “Section II reviews research on model consistency management” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “microbrewery” (Muctadir et al., p. 1) \#5fb236\\
+- “microbrewery” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “consistency management approaches into three categories” (Muctadir et al., p. 1) \#5fb236\\
+- “consistency management approaches into three categories” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “proof-theorybased” (Muctadir et al., p. 1) \#2ea8e5\\
+- “proof-theorybased” (Muctadir et al., p. 1) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “synchronization-based” (Muctadir et al., p. 1) \#2ea8e5\\
+- “synchronization-based” (Muctadir et al., p. 1) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “rule-based” (Muctadir et al., p. 1) \#2ea8e5\\
+- “rule-based” (Muctadir et al., p. 1) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “derivation of consistency from axioms and theorems.” (Muctadir et al., p. 1) \#5fb236\\
+- “derivation of consistency from axioms and theorems.” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “extensive manual definition of transformation rules and become increasingly difficult to manage in heterogeneous or large-scale system” (Muctadir et al., p. 1) \#5fb236\\
+- “extensive manual definition of transformation rules and become increasingly difficult to manage in heterogeneous or large-scale system” (Muctadir et al., p. 1) \#5fb236
-\mkbibemph{ }
+
 \par
- “entities and their relationships required to facilitate the development of systems that can effectively maintain model consistency by addressing specific requirements.” (Muctadir et al., p. 2) \#5fb236\\
+- “entities and their relationships required to facilitate the development of systems that can effectively maintain model consistency by addressing specific requirements.” (Muctadir et al., p. 2) \#5fb236
-\mkbibemph{ }
+
 \par
- “5D DT architecture proposed by Tao et al. [24].” (Muctadir et al., p. 2) \#5fb236\\
+- “5D DT architecture proposed by Tao et al. [24].” (Muctadir et al., p. 2) \#5fb236
-\mkbibemph{ }
+
 \par
- “(1) Physical Entity (PE)” (Muctadir et al., p. 2) \#2ea8e5\\
+- “(1) Physical Entity (PE)” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “(2) Virtual Entity (VE)” (Muctadir et al., p. 2) \#2ea8e5\\
+- “(2) Virtual Entity (VE)” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “chemical kinetics model” (Muctadir et al., p. 2) \#2ea8e5\\
+- “chemical kinetics model” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “thermal dynamics model” (Muctadir et al., p. 2) \#2ea8e5\\
+- “thermal dynamics model” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “heat transfer model” (Muctadir et al., p. 2) \#2ea8e5\\
+- “heat transfer model” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “control model” (Muctadir et al., p. 2) \#2ea8e5\\
+- “control model” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “Services” (Muctadir et al., p. 2) \#2ea8e5\\
+- “Services” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “Production prediction” (Muctadir et al., p. 2) \#2ea8e5\\
+- “Production prediction” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “production control” (Muctadir et al., p. 2) \#2ea8e5\\
+- “production control” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “PE sends monitoring data and receives control signals, beer flavor and physical attributes dictate VE model parameters, and the remaining VE data are model states” (Muctadir et al., p. 2) \#5fb236\\
+- “PE sends monitoring data and receives control signals, beer flavor and physical attributes dictate VE model parameters, and the remaining VE data are model states” (Muctadir et al., p. 2) \#5fb236
-\mkbibemph{ }
+
 \par
- “a) Read and extract model data:” (Muctadir et al., p. 2) \#2ea8e5\\
+- “a) Read and extract model data:” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “b) Store the extracted data:” (Muctadir et al., p. 2) \#2ea8e5\\
+- “b) Store the extracted data:” (Muctadir et al., p. 2) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “ConsistencyRules” (Muctadir et al., p. 2) \#5fb236\\
+- “ConsistencyRules” (Muctadir et al., p. 2) \#5fb236
-\mkbibemph{ }
+
 \par
- “c) Evaluate consistency rules:” (Muctadir et al., p. 3) \#2ea8e5\\
+- “c) Evaluate consistency rules:” (Muctadir et al., p. 3) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “d) Manage consistency rule relevancy” (Muctadir et al., p. 3) \#2ea8e5\\
+- “d) Manage consistency rule relevancy” (Muctadir et al., p. 3) \#2ea8e5
-\mkbibemph{ }
+
 \par
- “VE of the brewery DT” (Muctadir et al., p. 3) \#5fb236\\
+- “VE of the brewery DT” (Muctadir et al., p. 3) \#5fb236
-\mkbibemph{ }
+
 \par
- “CommonModelStructure” (Muctadir et al., p. 3) \#5fb236\\
+- “CommonModelStructure” (Muctadir et al., p. 3) \#5fb236
-\mkbibemph{ }
+
 \par
 - “the second ensures correct connectivity with the thermal dynamics model.” (Muctadir et al., p. 3) \#ffd400\\
 \mkbibemph{What does it mean "ensures". How connectivity is ensured?}
@@ -34412,14 +34414,14 @@ And then add a Detailed Comments section to report the notets that contain issue
 - “If a rule’s condition is violated, the associated error message is shown.” (Muctadir et al., p. 3) \#ffd400\\
 \mkbibemph{ANd then? WHo is the main intended user of the approach. What are the conditions to use the consistency management? What's the supported development of runtime environments that are required to enable the usage of the consistency management system?}
 \par
- “The checker mentioned previously enables us to preserve this structure” (Muctadir et al., p. 3) \#5fb236\\
+- “The checker mentioned previously enables us to preserve this structure” (Muctadir et al., p. 3) \#5fb236
-\mkbibemph{ }
+
 \par
 - “Discussion on results” (Muctadir et al., p. 4) \#ffd400\\
 \mkbibemph{What results? I undertand it's a short paper, however the paper is not effective in stressing the novelties of the proposed approach. What's the novelty? Is it the consistency language? is it the engine? Authors should distill what are the main ingredientes of the proposed approach. The paper presents an overview of the consistency mangenent systems consisting of different classes and interfaces. The presentation of the consistency managemtn rule is not effective in stressing what are the cases that existing approaches cannot support and that instead the proposed approach can do.}
 \par
- “In the case study presented in Section IV-B, we demonstrate the practical implementation and advantages of the consistency management framework (cf. Section IV-A) for the microbrewery DT.” (Muctadir et al., p. 4) \#ffd400\\
+- “In the case study presented in Section IV-B, we demonstrate the practical implementation and advantages of the consistency management framework (cf. Section IV-A) for the microbrewery DT.” (Muctadir et al., p. 4) \#ffd400
-\mkbibemph{ }
+
 \par
 - “Furthermore, it supports the structured management of consistency rules, with integrated checkers to ensure that these rules remain well organized and continuously aligned with the evolving DT models.” (Muctadir et al., p. 4) \#ffd400\\
 \mkbibemph{The paper presents some ideas, by sketching essentially a class diagram of the consistency management system. What's the novel aspects of the proposed system?}
@@ -34427,17 +34429,19 @@ And then add a Detailed Comments section to report the notets that contain issue
 - “b) Future work: Similar to the case studies presented in [3] implementing the consistency management framework,” (Muctadir et al., p. 4) \#ffd400\\
 \mkbibemph{WHat's the difference of the consistency management presented in this paper and that of [3]?}
 \par
- “[3]” (Muctadir et al., p. 4) \#ffd400\\
+- “[3]” (Muctadir et al., p. 4) \#ffd400
-\mkbibemph{ }
+
 \par
- “the framework’s relevance, practicality, and usability for a more complex system continue to be an area for further research.” (Muctadir et al., p. 4) \#ffd400\\
+- “the framework’s relevance, practicality, and usability for a more complex system continue to be an area for further research.” (Muctadir et al., p. 4) \#ffd400
-\mkbibemph{ }
+
 \par
 - “For this purpose, we implement a consistency management framework designed specifically to manage the consistency of DT models.” (Muctadir et al., p. 4) \#ffd400\\
 \mkbibemph{The strenghts and the limitations of the framework are not clearly stated.}
 \par
- “This provides a strong indication of the usefulness and applicability of the framework for DTs developed within the biochemical domain.” (Muctadir et al., p. 4) \#5fb236\\
+- “This provides a strong indication of the usefulness and applicability of the framework for DTs developed within the biochemical domain.” (Muctadir et al., p. 4) \#5fb236
-\mkbibemph{ }}
+
 \par
 COnsider that those that are tagget with \#5fb236 are just highlights, those that are tagged with \#e56eee and \#a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with \#ffd400. Those that are tagged with \#ff6666 are typos or errors. Could you please draft a review by organizing it as follows: SUMMARY: Just a few sentence to summarize the work COMMENTS: Organize the notes especially those that contain issues or typos.}
 }
@incollection{mullerAutonomicComputingNow2009,
@@ -38065,7 +38069,188 @@ Google's monolithic repository provides a common source of truth for tens of tho
  title = {An Agent Design Pattern Catalogue for the Entanglement of {{Digital Twins}}},
  author = {Pretel, Elena and Navarro, Elena and López-Jaquero, Víctor and González, Pascual and Dustdar, Schahram},
  abstract = {The entanglement property is an essential property of Digital Twins (DTs), enabling seamless interaction between the physical twin and its DT. Despite the increasing adoption of MultiAgent Systems (MAS) in DT development, there is a lack of structured guidance on how agent design can support different levels of entanglement. This paper addresses this gap by proposing a catalogue of agent design patterns tailored to support weak, simple, and strong entanglement in DTs. Each pattern is aligned with established design patterns in MAS literature. A decision model is also introduced to guide practitioners in selecting appropriate patterns based on the essential aspects of entanglement: connectivity, promptness, and association. The proposed patterns and model were applied in a real-world case study involving the design of a DT to manage study sessions for children with ADHD, demonstrating their effectiveness and practical value. The results support the feasibility and utility of our catalogue of design patterns for the entanglement of the DT.},
-  langid = {english}
+  langid = {english},
  note = {I'm reviewing a research paper and I took the following notes:
 \par
 \section{Annotazioni\\
 (22/6/2025, 09:59:46)}
 \par
 - “entanglement of Digital Twins” (Pretel et al., p. 1) \#5fb236
 \par
 - “entanglement property is an essential property of Digital Twins (DTs), enabling seamless interaction between the physical twin and its DT” (Pretel et al., p. 1) \#5fb236
 \par
 - “lack of structured guidance on how agent design can support different levels of entanglement.” (Pretel et al., p. 1) \#5fb236
 \par
 - “catalogue of agent design patterns” (Pretel et al., p. 1) \#5fb236
 \par
 - “decision model is also introduced to guide practitioners in selecting appropriate patterns” (Pretel et al., p. 1) \#5fb236
 \par
 - “connectivity, promptness, and association” (Pretel et al., p. 1) \#5fb236
 \par
 - “demonstrating their effectiveness and practical value.” (Pretel et al., p. 1) \#5fb236
 \par
 - “sharing real-time data and synchronizing the cyber and physical worlds” (Pretel et al., p. 1) \#5fb236
 \par
 - “physical and cybernetic convergence is called entanglemen” (Pretel et al., p. 1) \#e56eee
 \par
 - “constant and as far as possible, real-time flow of information, whereby the DT accurately reflects the state of the physical twin.” (Pretel et al., p. 1) \#a28ae5
 \par
 - “Connectivity (C)” (Pretel et al., p. 1) \#2ea8e5
 \par
 - “between the physical and digital twin” (Pretel et al., p. 1) \#5fb236
 \par
 - “Association (A)” (Pretel et al., p. 1) \#2ea8e5
 \par
 - “Promptness (P):” (Pretel et al., p. 1) \#2ea8e5
 \par
 - “critical applications, such as medical or industrial, near realtime synchronisation is required, however, in other cases, periodical or event-driven updates may be sufficient.” (Pretel et al., p. 1) \#5fb236
 \par
 - “Weak entanglement” (Pretel et al., p. 1) \#2ea8e5
 \par
 - “Simple entanglement” (Pretel et al., p. 1) \#2ea8e5
 \par
 - “Strong entanglement means” (Pretel et al., p. 1) \#2ea8e5
 \par
 - “The properties of MAS for modelling entities that perceive and act on an environment are naturally aligned with the properties of DTs” (Pretel et al., p. 2) \#5fb236
 \par
 - “Agents can represent DTs, providing them with autonomous, proactive, reactive and sociability properties.” (Pretel et al., p. 2) \#a28ae5
 \par
 - “This enables the development of DTs that not only reflect the state of their physical twin, but can also reason, learn, and interact with others to achieve complex goals” (Pretel et al., p. 2) \#a28ae5
 \par
 - “a gap still exists on how agents can be designed to adapt to different levels of entanglement.” (Pretel et al., p. 2) \#ffd400\\
 \mkbibemph{What does it mean exactly? Can you give some illustrative examples to explain and also to highlights the limitations of existing technologies concerning the aspects you are referring to?}
 \par
 - “There are no proposals that provide a catalogue of agent design patterns related to the entanglement aspects of DTs” (Pretel et al., p. 2) \#5fb236
 \par
 - “investigate the design of agents, focusing on how they support and manage the entanglement between the physical and digital twin.” (Pretel et al., p. 2) \#a28ae5
 \par
 - “RQ1: Which agent design patterns can be used to support the development of the entanglement property of DT?” (Pretel et al., p. 2) \#e56eee
 \par
 - “RQ2: How can software architects be guided in the selection of design patterns to achieve different degrees of entanglement of the DT?” (Pretel et al., p. 2) \#e56eee
 \par
 - “study on MAS for DT, applying two research methods, Systematic Literature Review (SLR) and Grounded Theory (GT), in order to detect patterns in the literature for defining a catalogue of design patterns that guide the development of the entanglement DT property” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “decision model that guides architects toward which agents they need to include in their architecture to support the DT entanglement expected” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “we evaluate the level of detail and completeness of the catalogue of design patterns by implementing a case study demonstrating that our pattern catalogue offers valuable insights for agent-based DT development” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “related work.” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “research methods applied in this study” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “e catalogue of agent design patterns” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “decision model for pattern selection based on the DT entanglement aspects” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “Section VI shows the practical application of the catalogue of design patterns proposed, the discussion and the threats to the validity of our study” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “Section VII summarises the conclusions and future wor” (Pretel et al., p. 2) \#2ea8e5
 \par
 - “Design patterns are typical solutions to common problems in software design [7].” (Pretel et al., p. 2) \#5fb236
 \par
 - “patterns address common problems in software design” (Pretel et al., p. 2) \#5fb236
 \par
 - “extensions and adaptations of these patterns have been proposed to address new emerging challenges, such as the design of patterns for distributed systems [9] and realtime systems [10].” (Pretel et al., p. 2) \#5fb236
 \par
 - “interest in design patterns for agent-based systems has also grown” (Pretel et al., p. 2) \#5fb236
 \par
 - “no prior work has systematically formalized a catalogue of agent design patterns explicitly oriented toward supporting the entanglement property.” (Pretel et al., p. 2) \#5fb236
 \par
 - “This research aims to fill this gap by proposing a catalogue of agent design patterns specifically developed to address the different levels of entanglement: weak, simple, and strong.” (Pretel et al., p. 2) \#a28ae5
 \par
 - “Systematic Literature Review (SLR) and Grounded Theory (GT).” (Pretel et al., p. 2) \#5fb236
 \par
 - “we conducted a Systematic Literature Review (SLR) on DT and MAS [5] following the guidelines proposed by Kitchenham et al. [17].” (Pretel et al., p. 3) \#5fb236
 \par
 - “Then, in order to further enrich the information gathered to define patterns, in this paper we extended our research approach by including a Grounded Theory (GT) [18].” (Pretel et al., p. 3) \#ffd400\\
 \mkbibemph{So, the Grounded Theory is the main focus of this paper and the main novelty compared with the already published SLRs. Isn't it:}
 \par
 - “This combination allowed us to complement the SLR results with additional findings derived from a process of inductive and iterative analysis.” (Pretel et al., p. 3) \#5fb236
 \par
 - “additional searches focusing on MAS design pattern works that were not captured in the initial SLR” (Pretel et al., p. 3) \#ffd400\\
 \mkbibemph{In what sense the SLR was not complete? What are the dimensions/aspects that were not covered? Why were not covered?}
 \par
 - “design patterns related to the entanglement propert” (Pretel et al., p. 3) \#ffd400
 \par
 - “selective coding was applied to create a catalogue of design patterns related to the entanglement property of the DT.” (Pretel et al., p. 3) \#5fb236
 \par
 - “This research methodology combining SLR and GT provided a richer understanding of the design principles and architectural patterns used to develop the entanglement of the DT. By combining the results of both research methods, we ensured that the identified patterns are based on empirical findings and, at the same time, are theoretically grounded. This analysis provides the basis for the next section of this article, in which the derived design patterns are presented.” (Pretel et al., p. 3) \#ffd400\\
 \mkbibemph{I'm still asking why authors have not covered the entanglement aspect in the previous SLR.}
 \par
 - “AGENT DESIGN PATTERN CATALOGUE FOR THE ENTANGLEMENT” (Pretel et al., p. 3) \#ffd400\\
 \mkbibemph{I still don't get what's the novelty of this paper in terms of the specificities of the proposed patterns with respect o t what already exists.~ Obesrver, publish-subscribers, and event dispatcher are existing patterns and this paper discuss their possible adoption while developing DTs. THis is something done, thus what's the strenghts / novelty of this work?}
 \par
 - “A. Indirect Observation Patter” (Pretel et al., p. 3) \#2ea8e5
 \par
 - “For example, the state of physical twin can be monitored by a camera, extracting some relevant information and transmitting it to the DT” (Pretel et al., p. 3) \#5fb236
 \par
 - “Problem: How to synchronize the DT when there is no direct connection with its physical twin?” (Pretel et al., p. 3) \#5fb236
 \par
 - “Real-Time Direct Data Dispatcher Pattern” (Pretel et al., p. 3) \#2ea8e5
 \par
 - “strong entanglement supporting the direct real-time link from the physical twin to the D” (Pretel et al., p. 3) \#2ea8e5
 \par
 - “V. DECISION MODEL FOR SELECTION OF DESING PATTERNS” (Pretel et al., p. 5) \#ffd400\\
 \mkbibemph{I appreciate the idea even though it is not clear how this can be used and work in practice. Who is the main stakeholder of the decision model? How this can be actually used when dealing with real and complex digital twins?}
 \par
 - “Each pattern proposed reflects established design patterns for MAS and has been adapted to the context of DTs.” (Pretel et al., p. 7) \#ffd400\\
 \mkbibemph{What does it mean? What's the kind of adaptations done?}
 \par
 - “11th Asia-Pacific Software Engineering Conference,” (Pretel et al., p. 8) \#5fb236
 \par
 COnsider that those that are tagget with \#5fb236 are just highlights, those that are tagged with \#e56eee and \#a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with \#ffd400. Those that are tagged with \#ff6666 are typos or errors. Could you please draft a review by organizing it as follows: SUMMARY: Just a few sentence to summarize the work COMMENTS: Organize the notes especially those that contain issues or typos.}
 }
@inproceedings{Pretschner05,
@@ -42136,6 +42321,16 @@ A MDE-based reverse engineering approach for inferring the schema of aggregate-o
  keywords = {machine learning}
 }
@online{shahHowBuildSimple2025,
  title = {How to {{Build}} a {{Simple MCP Server}}?},
  author = {Shah, Khushbu},
  date = {2025-05-06T16:16:55},
  url = {https://medium.com/projectpro/how-to-build-a-simple-mcp-server-0659672bc52d},
  urldate = {2025-06-21},
  abstract = {Have you ever wondered how AI systems can access real time data and perform dynamic tasks without manual intervention? Picture an AI that…},
  organization = {ProjectPro}
 }
@article{shahrivarBusinessModelCommercial2018,
  title = {A Business Model for Commercial Open Source Software: {{A}} Systematic Literature Review},
  shorttitle = {A Business Model for Commercial Open Source Software},
@@ -1,162 +0,0 @@
 icon:: ⚽
 progress:: {{renderer :todomaster}}
 - #.tabular
 	- [[P1]]
 		- {{query (and (task TODO) (priority A))}}
 		  query-table:: true
 		  query-properties:: [:block :todoist-desc :todoist-id]
 	- [[P2]]
 		- {{query (and (task TODO) (priority B))}}
 		  query-table:: true
 		  query-properties:: [:block :todoist-desc]
 -
 - TODO Fare timesheets
 - TODO [[PAPERS/ILIRIAN-COLLABORATION]]
 - TODO [[EditoringChairing/SOSYM-AI-MDE-SpecialIssue]]
 - TODO Literature review on adversarial ML for SE
  todoist-id:: [6841676473](https://todoist.com/app/task/6841676473)
  todoist-desc:: [Literature Review - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/643e68c8a424e0027e19fc5d)
 - TODO Finalizzazione questione documentale
 - TODO [#B] [[PAPERS/DSL-FOR-IOT-TESTING]]
 - TODO [[PAPERS/SSTD-LLMS]]
 - TODO [[PAPERS/JSS-2024-PERFORMANCE-TEST-COVERAGE]]
 - TODO [[PAPERS/SOSYM-EXPERT-VOICE-2024-ML-EVOLUTION]]
 - DONE Visita Riccardo
  todoist-desc:: ✉: http://s.diruscio.org/u9fPP
  todoist-id:: [7602643924](https://app.todoist.com/app/task/7602643924)
 - TODO [[PAPERS/2024-ONTOLOGY-AI]]
  todoist-id:: [7658261760](https://todoist.com/app/task/7658261760)
 - TODO NIER paper on how our two-level agent architecture
 - TODO [#C] [[PAPERS/2024-BiasInRSSEwithLLM]]
  todoist-id:: [7688827022](https://todoist.com/app/task/7688827022)
  todoist-desc:: [https://github.com/MDEGroup/BiasInRSSEwithLLM](https://github.com/MDEGroup/BiasInRSSEwithLLM)
 - TODO [#B] [FRINGE] Collaborazione su Fairness Mutation/Metamorphic Testing?
 - DONE [[EditoringChairing/2024-MODELS-WS-LOWCODE]]
  id:: 6832257a-cbb8-4881-ab20-bebcda629999
 - TODO [[PAPERS/2024-TESORO]]
 - DONE [[PAPERS/TOSEM-2024-0258]]
  id:: 6832257a-eea4-45f9-ab9f-98dbc36328cf
 - TODO [[PAPERS/AML4SE]]
  todoist-id:: [8113443070](https://todoist.com/app/task/8113443070)
  todoist-desc:: [AMLinRSSE - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/66683cbaf1ed22bc12efee72)
 - DONE [#B] popup UnivAQ Street Science 2024
  todoist-desc:: ✉: http://s.diruscio.org/eTBkR
  todoist-id:: [8117885918](https://app.todoist.com/app/task/8117885918)
  :LOGBOOK:
  CLOCK: [2025-05-10 Sat 22:52:25]--[2025-05-10 Sat 22:52:27] =>  00:00:02
  :END:
 - TODO [[PAPERS/BADGES-IMPACT]]
 - TODO [#C] Convenzione Erasmus Nazionale
 - DONE [#A] [[PAPERS/JSS-SATD]]
  todoist-desc:: ✉: http://s.diruscio.org/bWUfi
  todoist-id:: [8230073873](https://app.todoist.com/app/task/8230073873)
 - TODO [[PAPERS/EMELIOT-EXPERIMENT]]
 - DONE Career Day 24
  todoist-desc:: ✉: http://s.diruscio.org/Y20BN
  todoist-id:: [8359671703](https://app.todoist.com/app/task/8359671703)
 - TODO Panel Invitation (MODELS 2024)
 - TODO [[PAPERS/FSE2024-UserStories]]
  todoist-id:: [8407326252](https://todoist.com/app/task/8407326252)
  todoist-desc:: ✉: http://s.diruscio.org/fcx9l
 - DONE [#A] [ICSE 2025, Research Track] Review Assignment and Instructions (Half Review Deadline: *Aug 30*)
  todoist-desc:: ✉: [http://s.diruscio.org/vMkXT](http://s.diruscio.org/vMkXT)
  todoist-id:: [8286706547](https://app.todoist.com/app/task/8286706547)
 - DONE [#A] Progressione Phuong ad Associato
  todoist-desc:: ✉: http://s.diruscio.org/hJoCt
  todoist-id:: [8419941589](https://app.todoist.com/app/task/8419941589)
 - DONE [#A] Notifica nomina commissione RTD/A S.S.D INFO-01/A (Progetto MATTERS, Allegato A del Bando di  selezione)
  todoist-desc:: ✉: http://s.diruscio.org/Z3tSx
  todoist-id:: [8424508957](https://app.todoist.com/app/task/8424508957)
 - TODO Orientamento 2026 PNRR - Anno 24/25
 - DONE [#B] Progressione seconda fascia Phuong Nguyen
  todoist-desc:: ✉: http://s.diruscio.org/MjM5n
  todoist-id:: [8427313493](https://app.todoist.com/app/task/8427313493)
  SCHEDULED: <2025-01-10 Fri>
 - DONE [#A] Conscorso RTD/a MATTERS
  todoist-desc:: ✉: http://s.diruscio.org/ouj19
  todoist-id:: [8434113580](https://app.todoist.com/app/task/8434113580)
  SCHEDULED: <2024-11-08 Fri 11:10>
 - TODO Ridefinizione Piano Formativo e regole di riconoscimento CFU
 - TODO [#B] [[PAPERS/2024-AMLinRSSE]]
  id:: 6832257a-6e4b-4f1f-9d7b-1f520b8197ca
  SCHEDULED: <2025-05-26 Mon>
 - DONE [Lavoro Davide Sciarra e Giovanni Sicchio](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAHeU%2BoMgAA&exvsurl=1&viewmodel=ReadMessageItem)
  todoist-id:: [8558858426](https://app.todoist.com/app/task/8558858426)
 - DONE [#A] [[PAPERS/TOSEM-FAIRNESS]]
  todoist-desc:: [[TOSEM] Towards Early Detection of Algorithmic Bias from Dataset's Bias Symptoms: An Empirical Study - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/65b7d77455b46f44b87e2331)
  todoist-id:: [8565953885](https://app.todoist.com/app/task/8565953885)
  SCHEDULED: <2025-01-14 Tue 12:00>
 - TODO [[PAPERS/SANER2025-FAIRNESS]]
 - TODO [[PAPERS/SANER-2025-Popbias-LLM]]
 - DONE [[PAPERS/MSR-2025-CodeXHug-dataset]]
  id:: 6832257a-7e7e-4ed8-abf8-dd88c6643863
  :LOGBOOK:
  CLOCK: [2025-05-25 Sun 19:29:04]--[2025-05-25 Sun 19:29:05] =>  00:00:01
  :END:
 - TODO Nuova edizione del PinKamp
  todoist-id:: [8644892780](https://app.todoist.com/app/task/8644892780)
  todoist-desc:: From: giuseppe.dellapenna@univaq.it
 - TODO ICSE 2026 Program Committee
 - TODO [[PAPERS/Experience-Report-to-EMSE]]
 - DONE [[PAPERS/FSE2025-NIER]]
 id:: 68362092-aafa-44b6-83b2-8f4a163dd2a0
 - TODO [#C] Dottorato industriale riservato a dipendenti
 - TODO Esplorare e approfondire gli aspetti fondamentali e pratici dei large language models
 - TODO [#C] [[PAPERS/JOURNAL-LLMS4Edelta]]
 - TODO Richiesta afferenza al Collegio di Mauro Cappelli, ricercatore all’Enea
 - TODO [#C] Vedere per compenso per la De Masi
 - TODO [#B] [[PAPERS/Journal-Green-Paper]]
 - TODO [#A] Rivedere Composizione Collegio
  todoist-id:: [8750396305](https://app.todoist.com/app/task/8750396305)
 - TODO [#C] [[PAPERS/ABSTRACT-ENGINEERING]]
 - TODO [#C] [[PAPERS/TOSEM2025-TESORO]]
 - TODO [#B] [R: Scheda XLI ciclo e richieste di afferenza al Collegio](https://outlook.office365.com/owa/?ItemID=AAkALgAAAAAAHYQDEapmEc2byACqAC%2FEWg0AjoVpQvBez0Ss5ZY2WGWEJgAHueDXAQAA&exvsurl=1&viewmodel=ReadMessageItem)
 - TODO [#B] Informiamo che entro e non oltre il ciascun Coordinatore dovrà caricare sulla piattaforma telematica dedicata: - il verbale del collegio dei docenti con esplicita ammissione all’esame finale; - la copia della tesi finale del dottorando; - il verbale della commissione dell’esame finale.
  SCHEDULED: <2025-07-31 Thu>
 - TODO [#B] MODELS Journal-First-track + 1 more
  id:: 6832257a-2676-4bf1-8958-81797e5c7003
  SCHEDULED: <2025-05-26 Mon>
 - DONE Revision of manuscript #EMSE-D-25-00044
  id:: 6832257a-85cb-46bd-9018-855f59070a41
 - TODO [#B] [[PAPERS/MAS-4-POPULARITY-BIAS]]
 - TODO [#B] [ICSE 2026, Research Track] Review Assignment and Instructions (Half Review Deadline: *Apr 18*; All reviews deadline: May 16)
  todoist-desc:: From: noreply-icse2026@hotcrp.com
  todoist-id:: [9001461730](https://app.todoist.com/app/task/9001461730)
 - TODO Dottorato industriale
  todoist-id:: [9006116046](https://app.todoist.com/app/task/9006116046)
  id:: 6823acce-6cc8-4da4-9a2c-5ffacf92e168
  SCHEDULED: <2025-05-22 Thu>
 - DONE [#B] Models Conference 2025
  id:: 682ecc99-b356-4086-9ff8-4e4736018009
  SCHEDULED✔️ <2025-05-26 Mon>
  :LOGBOOK:
  CLOCK: [2025-05-24 Sat 22:02:34]--[2025-05-24 Sat 22:02:35] =>  00:00:01
  CLOCK: [2025-05-24 Sat 22:02:52]--[2025-05-24 Sat 22:02:52] =>  00:00:00
  :END:
 - DONE Review MODELS 2025 conference submissions
  id:: 6832257a-4373-4560-a7e2-79fba9f4c9e6
  :LOGBOOK:
  CLOCK: [2025-05-24 Sat 22:02:27]--[2025-05-24 Sat 22:02:28] =>  00:00:01
  :END:
 - DONE [#B] [[PAPERS/2025-SEAA-CodeXHug]]
  id:: 6832257a-f98d-4f5e-850c-ddf8ffd0b5fb
  :LOGBOOK:
  CLOCK: [2025-05-25 Sun 19:26:07]--[2025-05-25 Sun 19:26:08] =>  00:00:01
  :END:
 - DONE [[PAPERS/2025-Survey-MOSAICO]]
  id:: 6832257a-63a4-4c89-8353-25f0e94caa51
 - TODO [#B] Migliorare situazione economica dottorandi
 - TODO [#B] Sinergia con GSSI
 - TODO [#A] [[PAPERS/MOSAICO-Technical-Report]]
  todoist-id:: [9187744429](https://app.todoist.com/app/task/9187744429)
  SCHEDULED: <2025-05-31 Sat>
 - TODO [#A] SLIDES DI PRESENTAZIONE
  todoist-desc:: Con HOWTO etc.
  todoist-id:: [9193848277](https://app.todoist.com/app/task/9193848277)
 - TODO [[MODELS Journal-First-track + 1 more]]
  todoist-desc:: From: noreply@researchr.org
  todoist-id:: [8933176944](https://app.todoist.com/app/task/8933176944)
  SCHEDULED: <2025-05-30 Fri>
 - DONE [[PAPERS/2025-SEAA-CodeXHug]] 
  todoist-id:: [9123770472](https://app.todoist.com/app/task/9123770472)
@@ -1,131 +0,0 @@
 template:: JOURNAL-TEMPLATE
 	- #.tabular
 		- ### 🗒️Notes
 			-
 		- ### 📜Reviews
 			- {{query (and [[REVIEWS]] (or (property :date-end <%today%>) (property :date-start <%today%>) (property :date-submitted <%today%>)))}}
 			  query-table:: true
 			  query-properties:: [:file :year :venue :deadline]
 		- ### ⤴️Omnivore readings
 			- {{query (and (property :source [[Omnivore]]) (or (property :deadline <%today%>) (property :date-saved <%today%>) (property :date-archived <%today%>)))}}
 			  query-table:: true
 			  query-properties:: [:labels :state :full-title]
 -
 - type:: [[JournalPaper]], [[conferencepaper]], [[WorkshopPaper]], [[Bookchapter]]
  template:: PAPERS
  date:: <%today%> - <%time%>
  full-title::
  external-links::
  todoist::
  year::
  date-start::
  status:: [[DOING]], [[DONE]], [[SUBMITTED]], [[REJECTED]] [[UNDER-REVISION]] 
  venue::
  priority:: [[P1]] [[P2]] [[P3]] [[P4]]
  parent:: 
  leader:: 
  todoist:: 
  progress:: {{renderer :todomaster}}
 	- #.tabular
 		- ## MEETINGS
 			- {{query (and <%current page%> (block-property :type [[meeting]]) (not (page <%current page%>)))}}
 			- query-table:: true
 		- ## READINGS
 			- #+BEGIN_QUERY
 			    {:title "Related readings in Omnivore"
 			  :query [:find (pull ?b [*] )
 			        :in $ ?current-page
 			  	  :where
 			  		    [?b :block/page ?p]
 			              [?p :block/name ?p-name]
 			  		    [?b :block/content ?c]
 			  		    [(clojure.string/includes? ?c ?current-page)]
 			              [(clojure.string/includes? ?p-name "omnivore")]
 			  		  ]
 			         :inputs [:current-page]}
 			  #+END_QUERY
 			-
 		- ## TASKs
 			-
 			- ## ❓️ QUESTIONS TO ANSWER
 			  {{query (and [[question]]<%current page%>)}}
 		- ## [[PAPERS/NOTES]]
 			-
 - type:: [[weblink]]
  template:: WEBLINK
  source::
  tags:: [[readingnotes]]
  date:: <%today%> - <%time%>
 - type:: [[CAD]]
  template:: CAD
  corso:: [[Ingegneria Informatica]], [[Informatica]], [[TEACHING/DSU-S3S]], [[TEACHING/DSU-S3F]]
  date:: <%today%> - <%time%>
 - type:: [[REVIEWS]]
  tags:: 
  year::
  venue:: 
  template:: REVIEW
  full-title::
  date-start:: <%today%> - <%time%>
  date-submitted::
  external-links::
  status:: [[DOING]]
  deadline-submission:: 
  file::
  parent::
  todoist::
 	- ### [[Highlights]]
 	- ### [[Comments]]
 	- ### [[REVIEWS/Notes]]
 	- ### YELLOW CONCERNS
 	  background-color:: yellow
 		- {{query (and [[ffd400]] <%current page%> )}}
 		  collapsed:: true
 	- ### ❓️Questions
 		- {{query (and [[question]] <%current page%> )[[question]]}}
 		  query-table:: true
 		  query-properties:: [:block]
 - type:: [[Contact]] 
  page-type:: [[people]]
  date:: <%today%> - <%time%>
  template:: CONTACT
  name:: 
  struttura::  
  email::
 - type:: [[meeting]]
  template:: ConsiglioDisim
  external-links:: 
  tags:: [[SERVICES/ConsiglioDisim]]  [[Convocazioni]] 
  date:: <%today%> - <%time%>
  duration-min::
  file-brogliaccio::
  file-odg::
 - type::  [[meeting]]
  template:: MEETING
  external-links::  
  tags:: 
  people:: 
  date:: <%today%> - <%time%>
  duration::
 - template:: VENUE
  date:: <%today%> - <%time%>
  full-title:: 
  link:: 
  type:: [[JOURNAL]] [[CONFERENCE]] [[WORKSHOP]] 
  ranking-link::
 - template:: QUERY-QUESTIONS
  template-including-parent:: false
 	- ### Questions
 		- {{query (and [[question]] <%current page%> )[[question]]}}
 - template:: QUERY-IDEAS
  template-including-parent:: false
 	- ### Ideas
 		- {{query (and [[Ideas]] <%current page%>)}}
 - template:: QUERY-TASKS
  template-including-parent:: false
 	- ### TASKS
 		- {{query (and <%current page%> (task TODO DOING) (not [[GOALS-TODOIST]]))}}
 - template:: BOOX-TODAY-NOTES
 	- ![BOOX Notes - <%today%>](../assets/../../onyx/TabUltraCPro/Notepad/<%today%>.pdf)
@@ -0,0 +1,143 @@
 tags:: [[#zotero]]
 title:: @An agent design pattern catalogue for the entanglement of Digital Twins
 item-type:: [[journalArticle]]
 original-title:: An agent design pattern catalogue for the entanglement of Digital Twins
 language:: en
 authors:: [[Elena Pretel]], [[Elena Navarro]], [[Víctor López-Jaquero]], [[Pascual González]], [[Schahram Dustdar]]
 library-catalog:: Zotero
 links:: [Local library](zotero://select/library/items/9F5F2G9D), [Web library](https://www.zotero.org/users/1039502/items/9F5F2G9D)
 - [[Abstract]]
 	- The entanglement property is an essential property of Digital Twins (DTs), enabling seamless interaction between the physical twin and its DT. Despite the increasing adoption of MultiAgent Systems (MAS) in DT development, there is a lack of structured guidance on how agent design can support different levels of entanglement. This paper addresses this gap by proposing a catalogue of agent design patterns tailored to support weak, simple, and strong entanglement in DTs. Each pattern is aligned with established design patterns in MAS literature. A decision model is also introduced to guide practitioners in selecting appropriate patterns based on the essential aspects of entanglement: connectivity, promptness, and association. The proposed patterns and model were applied in a real-world case study involving the design of a DT to manage study sessions for children with ADHD, demonstrating their effectiveness and practical value. The results support the feasibility and utility of our catalogue of design patterns for the entanglement of the DT.
 - ### Attachments
 	- [PDF](zotero://select/library/items/ZPPV46KF) {{zotero-imported-file ZPPV46KF, "Pretel et al. - An agent design pattern catalogue for the entanglement of Digital Twins.pdf"}}
 - ### Notes
 	- I'm reviewing a research paper and I took the following notes:
 	  # Annotazioni 
 	   (22/6/2025, 09:59:46)
 	  - “entanglement of Digital Twins” (Pretel et al., p. 1) #5fb236
 	  - “entanglement property is an essential property of Digital Twins (DTs), enabling seamless interaction between the physical twin and its DT” (Pretel et al., p. 1) #5fb236
 	  - “lack of structured guidance on how agent design can support different levels of entanglement.” (Pretel et al., p. 1) #5fb236
 	  - “catalogue of agent design patterns” (Pretel et al., p. 1) #5fb236
 	  - “decision model is also introduced to guide practitioners in selecting appropriate patterns” (Pretel et al., p. 1) #5fb236
 	  - “connectivity, promptness, and association” (Pretel et al., p. 1) #5fb236
 	  - “demonstrating their effectiveness and practical value.” (Pretel et al., p. 1) #5fb236
 	  - “sharing real-time data and synchronizing the cyber and physical worlds” (Pretel et al., p. 1) #5fb236
 	  - “physical and cybernetic convergence is called entanglemen” (Pretel et al., p. 1) #e56eee
 	  - “constant and as far as possible, real-time flow of information, whereby the DT accurately reflects the state of the physical twin.” (Pretel et al., p. 1) #a28ae5
 	  - “Connectivity (C)” (Pretel et al., p. 1) #2ea8e5
 	  - “between the physical and digital twin” (Pretel et al., p. 1) #5fb236
 	  - “Association (A)” (Pretel et al., p. 1) #2ea8e5
 	  - “Promptness (P):” (Pretel et al., p. 1) #2ea8e5
 	  - “critical applications, such as medical or industrial, near realtime synchronisation is required, however, in other cases, periodical or event-driven updates may be sufficient.” (Pretel et al., p. 1) #5fb236
 	  - “Weak entanglement” (Pretel et al., p. 1) #2ea8e5
 	  - “Simple entanglement” (Pretel et al., p. 1) #2ea8e5
 	  - “Strong entanglement means” (Pretel et al., p. 1) #2ea8e5
 	  - “The properties of MAS for modelling entities that perceive and act on an environment are naturally aligned with the properties of DTs” (Pretel et al., p. 2) #5fb236
 	  - “Agents can represent DTs, providing them with autonomous, proactive, reactive and sociability properties.” (Pretel et al., p. 2) #a28ae5
 	  - “This enables the development of DTs that not only reflect the state of their physical twin, but can also reason, learn, and interact with others to achieve complex goals” (Pretel et al., p. 2) #a28ae5
 	  - “a gap still exists on how agents can be designed to adapt to different levels of entanglement.” (Pretel et al., p. 2) #ffd400
 	  *What does it mean exactly? Can you give some illustrative examples to explain and also to highlights the limitations of existing technologies concerning the aspects you are referring to?*
 	  - “There are no proposals that provide a catalogue of agent design patterns related to the entanglement aspects of DTs” (Pretel et al., p. 2) #5fb236
 	  - “investigate the design of agents, focusing on how they support and manage the entanglement between the physical and digital twin.” (Pretel et al., p. 2) #a28ae5
 	  - “RQ1: Which agent design patterns can be used to support the development of the entanglement property of DT?” (Pretel et al., p. 2) #e56eee
 	  - “RQ2: How can software architects be guided in the selection of design patterns to achieve different degrees of entanglement of the DT?” (Pretel et al., p. 2) #e56eee
 	  - “study on MAS for DT, applying two research methods, Systematic Literature Review (SLR) and Grounded Theory (GT), in order to detect patterns in the literature for defining a catalogue of design patterns that guide the development of the entanglement DT property” (Pretel et al., p. 2) #2ea8e5
 	  - “decision model that guides architects toward which agents they need to include in their architecture to support the DT entanglement expected” (Pretel et al., p. 2) #2ea8e5
 	  - “we evaluate the level of detail and completeness of the catalogue of design patterns by implementing a case study demonstrating that our pattern catalogue offers valuable insights for agent-based DT development” (Pretel et al., p. 2) #2ea8e5
 	  - “related work.” (Pretel et al., p. 2) #2ea8e5
 	  - “research methods applied in this study” (Pretel et al., p. 2) #2ea8e5
 	  - “e catalogue of agent design patterns” (Pretel et al., p. 2) #2ea8e5
 	  - “decision model for pattern selection based on the DT entanglement aspects” (Pretel et al., p. 2) #2ea8e5
 	  - “Section VI shows the practical application of the catalogue of design patterns proposed, the discussion and the threats to the validity of our study” (Pretel et al., p. 2) #2ea8e5
 	  - “Section VII summarises the conclusions and future wor” (Pretel et al., p. 2) #2ea8e5
 	  - “Design patterns are typical solutions to common problems in software design [7].” (Pretel et al., p. 2) #5fb236
 	  - “patterns address common problems in software design” (Pretel et al., p. 2) #5fb236
 	  - “extensions and adaptations of these patterns have been proposed to address new emerging challenges, such as the design of patterns for distributed systems [9] and realtime systems [10].” (Pretel et al., p. 2) #5fb236
 	  - “interest in design patterns for agent-based systems has also grown” (Pretel et al., p. 2) #5fb236
 	  - “no prior work has systematically formalized a catalogue of agent design patterns explicitly oriented toward supporting the entanglement property.” (Pretel et al., p. 2) #5fb236
 	  - “This research aims to fill this gap by proposing a catalogue of agent design patterns specifically developed to address the different levels of entanglement: weak, simple, and strong.” (Pretel et al., p. 2) #a28ae5
 	  - “Systematic Literature Review (SLR) and Grounded Theory (GT).” (Pretel et al., p. 2) #5fb236
 	  - “we conducted a Systematic Literature Review (SLR) on DT and MAS [5] following the guidelines proposed by Kitchenham et al. [17].” (Pretel et al., p. 3) #5fb236
 	  - “Then, in order to further enrich the information gathered to define patterns, in this paper we extended our research approach by including a Grounded Theory (GT) [18].” (Pretel et al., p. 3) #ffd400
 	  *So, the Grounded Theory is the main focus of this paper and the main novelty compared with the already published SLRs. Isn't it:*
 	  - “This combination allowed us to complement the SLR results with additional findings derived from a process of inductive and iterative analysis.” (Pretel et al., p. 3) #5fb236
 	  - “additional searches focusing on MAS design pattern works that were not captured in the initial SLR” (Pretel et al., p. 3) #ffd400
 	  *In what sense the SLR was not complete? What are the dimensions/aspects that were not covered? Why were not covered?*
 	  - “design patterns related to the entanglement propert” (Pretel et al., p. 3) #ffd400
 	  - “selective coding was applied to create a catalogue of design patterns related to the entanglement property of the DT.” (Pretel et al., p. 3) #5fb236
 	  - “This research methodology combining SLR and GT provided a richer understanding of the design principles and architectural patterns used to develop the entanglement of the DT. By combining the results of both research methods, we ensured that the identified patterns are based on empirical findings and, at the same time, are theoretically grounded. This analysis provides the basis for the next section of this article, in which the derived design patterns are presented.” (Pretel et al., p. 3) #ffd400
 	  *I'm still asking why authors have not covered the entanglement aspect in the previous SLR.*
 	  - “AGENT DESIGN PATTERN CATALOGUE FOR THE ENTANGLEMENT” (Pretel et al., p. 3) #ffd400
 	  *I still don't get what's the novelty of this paper in terms of the specificities of the proposed patterns with respect o t what already exists.  Obesrver, publish-subscribers, and event dispatcher are existing patterns and this paper discuss their possible adoption while developing DTs. THis is something done, thus what's the strenghts / novelty of this work?*
 	  - “A. Indirect Observation Patter” (Pretel et al., p. 3) #2ea8e5
 	  - “For example, the state of physical twin can be monitored by a camera, extracting some relevant information and transmitting it to the DT” (Pretel et al., p. 3) #5fb236
 	  - “Problem: How to synchronize the DT when there is no direct connection with its physical twin?” (Pretel et al., p. 3) #5fb236
 	  - “Real-Time Direct Data Dispatcher Pattern” (Pretel et al., p. 3) #2ea8e5
 	  - “strong entanglement supporting the direct real-time link from the physical twin to the D” (Pretel et al., p. 3) #2ea8e5
 	  - “V. DECISION MODEL FOR SELECTION OF DESING PATTERNS” (Pretel et al., p. 5) #ffd400
 	  *I appreciate the idea even though it is not clear how this can be used and work in practice. Who is the main stakeholder of the decision model? How this can be actually used when dealing with real and complex digital twins?*
 	  - “Each pattern proposed reflects established design patterns for MAS and has been adapted to the context of DTs.” (Pretel et al., p. 7) #ffd400
 	  *What does it mean? What's the kind of adaptations done?*
 	  - “11th Asia-Pacific Software Engineering Conference,” (Pretel et al., p. 8) #5fb236
 	  COnsider that those that are tagget with #5fb236 are just highlights, those that are tagged with #e56eee and #a28ae5 are imporant sentences. Please pay attention instead to the notes that are tagged with #ffd400. Those that are tagged with #ff6666 are typos or errors. Could you please draft a review by organizing it as follows: SUMMARY: Just a few sentence to summarize the work COMMENTS: Organize the notes especially those that contain issues or typos.
@@ -0,0 +1,244 @@
 tags:: [[#zotero]]
 title:: @Model Consistency Management of a Brewery Digital Twin
 item-type:: [[journalArticle]]
 original-title:: Model Consistency Management of a Brewery Digital Twin
 language:: en
 authors:: [[Hossain Muhammad Muctadir]], [[Yanyifan Liao]], [[Loek Cleophas]]
 library-catalog:: Zotero
 links:: [Local library](zotero://select/library/items/66AQQ5ZI), [Web library](https://www.zotero.org/users/1039502/items/66AQQ5ZI)
 - [[Abstract]]
 	- Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services. VEs are typically model-based software systems that incorporate a variety of multi-domain, multi-tool models that are essential throughout the DT’s lifecycle. Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT. In this paper, we present a case study on consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production.
 - ### Attachments
 	- [PDF](zotero://select/library/items/UWR8TM35) {{zotero-imported-file UWR8TM35, "Muctadir et al. - Model Consistency Management of a Brewery Digital Twin.pdf"}}
 - ### Notes
 	- # Annotazioni 
 	   (16/6/2025, 23:22:43)
 	  - “Digital Twins (DTs) are often defined as a pairing of a physical entity (PE) and one or more virtual entities (VEs) where the latter mimics certain behaviors of the former to provide specific services.” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “Any inconsistency among these models directly affects the performance, reliability, and effectiveness of a DT.” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “consistency management of VE models contained within a DT of a microbrewery, which encapsulates the fermentation process to optimize beer production” (Muctadir et al., p. 1) #a28ae5
 	  * *
 	  - “model inconsistencies during the DT lifecycle are frequent and have a major impact on DT functionality” (Muctadir et al., p. 1) #e56eee
 	  * *
 	  - “effective consistency management method for DT models.” (Muctadir et al., p. 1) #a28ae5
 	  * *
 	  - “conceptual framework to address the challenges of consistency management for DT models.” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “In this paper, we further evaluate the framework with a DT from the bio-chemical domain.” (Muctadir et al., p. 1) #a28ae5
 	  * *
 	  - “We manage the consistency of the VE comprising four models, which are essential for delivering two services associated with predicting and controlling alcohol production.” (Muctadir et al., p. 1) #e56eee
 	  * *
 	  - “Section II reviews research on model consistency management” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “microbrewery” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “consistency management approaches into three categories” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “proof-theorybased” (Muctadir et al., p. 1) #2ea8e5
 	  * *
 	  - “synchronization-based” (Muctadir et al., p. 1) #2ea8e5
 	  * *
 	  - “rule-based” (Muctadir et al., p. 1) #2ea8e5
 	  * *
 	  - “derivation of consistency from axioms and theorems.” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “extensive manual definition of transformation rules and become increasingly difficult to manage in heterogeneous or large-scale system” (Muctadir et al., p. 1) #5fb236
 	  * *
 	  - “entities and their relationships required to facilitate the development of systems that can effectively maintain model consistency by addressing specific requirements.” (Muctadir et al., p. 2) #5fb236
 	  * *
 	  - “5D DT architecture proposed by Tao et al. [24].” (Muctadir et al., p. 2) #5fb236
 	  * *
 	  - “(1) Physical Entity (PE)” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “(2) Virtual Entity (VE)” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “chemical kinetics model” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “thermal dynamics model” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “heat transfer model” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “control model” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “Services” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “Production prediction” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “production control” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “PE sends monitoring data and receives control signals, beer flavor and physical attributes dictate VE model parameters, and the remaining VE data are model states” (Muctadir et al., p. 2) #5fb236
 	  * *
 	  - “a) Read and extract model data:” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “b) Store the extracted data:” (Muctadir et al., p. 2) #2ea8e5
 	  * *
 	  - “ConsistencyRules” (Muctadir et al., p. 2) #5fb236
 	  * *
 	  - “c) Evaluate consistency rules:” (Muctadir et al., p. 3) #2ea8e5
 	  * *
 	  - “d) Manage consistency rule relevancy” (Muctadir et al., p. 3) #2ea8e5
 	  * *
 	  - “VE of the brewery DT” (Muctadir et al., p. 3) #5fb236
 	  * *
 	  - “CommonModelStructure” (Muctadir et al., p. 3) #5fb236
 	  * *
 	  - “the second ensures correct connectivity with the thermal dynamics model.” (Muctadir et al., p. 3) #ffd400
 	  *What does it mean "ensures". How connectivity is ensured? *
 	  - “If a rule’s condition is violated, the associated error message is shown.” (Muctadir et al., p. 3) #ffd400
 	  *ANd then? WHo is the main intended user of the approach. What are the conditions to use the consistency management? What's the supported development of runtime environments that are required to enable the usage of the consistency management system? *
 	  - “The checker mentioned previously enables us to preserve this structure” (Muctadir et al., p. 3) #5fb236
 	  * *
 	  - “Discussion on results” (Muctadir et al., p. 4) #ffd400
 	  *What results? I undertand it's a short paper, however the paper is not effective in stressing the novelties of the proposed approach. What's the novelty? Is it the consistency language? is it the engine? Authors should distill what are the main ingredientes of the proposed approach. The paper presents an overview of the consistency mangenent systems consisting of different classes and interfaces. The presentation of the consistency managemtn rule is not effective in stressing what are the cases that existing approaches cannot support and that instead the proposed approach can do. *
 	  - “In the case study presented in Section IV-B, we demonstrate the practical implementation and advantages of the consistency management framework (cf. Section IV-A) for the microbrewery DT.” (Muctadir et al., p. 4) #ffd400
 	  * *
 	  - “Furthermore, it supports the structured management of consistency rules, with integrated checkers to ensure that these rules remain well organized and continuously aligned with the evolving DT models.” (Muctadir et al., p. 4) #ffd400
 	  *The paper presents some ideas, by sketching essentially a class diagram of the consistency management system. What's the novel aspects of the proposed system? *
 	  - “b) Future work: Similar to the case studies presented in [3] implementing the consistency management framework,” (Muctadir et al., p. 4) #ffd400
 	  *WHat's the difference of the consistency management presented in this paper and that of [3]? *
 	  - “[3]” (Muctadir et al., p. 4) #ffd400
 	  * *
 	  - “the framework’s relevance, practicality, and usability for a more complex system continue to be an area for further research.” (Muctadir et al., p. 4) #ffd400
 	  * *
 	  - “For this purpose, we implement a consistency management framework designed specifically to manage the consistency of DT models.” (Muctadir et al., p. 4) #ffd400
 	  *The strenghts and the limitations of the framework are not clearly stated. *
 	  - “This provides a strong indication of the usefulness and applicability of the framework for DTs developed within the biochemical domain.” (Muctadir et al., p. 4) #5fb236
 	  * *
@@ -13,6 +13,7 @@
 			- `python -m ipykernel install --user --name=todoist-env --display-name "Python (todoist-env)`
 		- Once crated the virtual environment, you have to install the required dependencies with
 			- `pip install -r requirements.txt`
 	- `uvicorn simple_service:app --reload`
 - ## Structure of the project
 	- todoist-insight/
 	  ├── notebooks/
@@ -1,11 +1,13 @@
 icon:: 🧠
 - ***Agentic AI***: Systems that can *plan*, *reason*, and *take action* to *accomplish tasks* with  *minimal human intervention*.
-	- AI agents extend the capabilities of LLMs with respect to the following dimensions:
+	- Certainly! Here's the revised text with grammatical corrections:
-		- *Integrating memory*, to retain and recall information across interactions
+	- ***Agentic AI***: Systems that can *plan*, *reason*, and *take action* to *accomplish tasks* with *minimal human intervention*.
-		- *Tool use*, to utilize external tools, APIs, and databases
+		- - AI agents extend the capabilities of LLMs in the following dimensions:
-		- *Decision-making*, to plan and execute multi-step workflows
+		- - *Integrating memory* to retain and recall information across interactions
-		- AI agents will continue to refine the ability to *reason*, *plan*, and *act*.
+		- - *Tool use* to utilize external tools, APIs, and databases
 		- - *Decision-making* to plan and execute multi-step workflows
 		- - AI agents will continue to refine their ability to *reason*, *plan*, and *act*.
 - The **development of agentic-based AI** is a natural progression from *statistical modeling* to *deep learning* and now to *reasoning-based systems*
 	- This evolution marks a shift from predictive models to autonomous systems capable of dynamic decision-making.
 - The **main challenges with raw LLMs** are the following:
@@ -116,3 +116,10 @@ icon:: ✅
 		- ✔️ [[19-06-2025]]  *15:51* ((68540a72-f93d-4413-9b74-79d3e5716758))
 		- ✔️ [[19-06-2025]]  *16:46* ((6853f169-1d30-4e3e-8bd6-d795d2f01914))
 		- ✔️ [[19-06-2025]]  *18:57* ((d4b795f4-21e9-408f-a6c2-3aadc10c3468))
 		- ✔️ [[20-06-2025]]  *11:45* ((6855230d-2cce-40a9-87b4-d99207252a6b))
 		- ✔️ [[20-06-2025]]  *11:45* ((68552317-3e34-4889-8d03-7671dd9239d7))
 		- ✔️ [[20-06-2025]]  *11:55* ((6855232a-08da-43da-9147-2012a583dc21))
 		- ✔️ [[20-06-2025]]  *11:57* ((93ba52d0-ca92-4181-84c3-f85f7ad67810))
 		- ✔️ [[20-06-2025]]  *12:29* ((68553095-9110-4f54-a545-dd186fa92e2d))
 		- ✔️ [[21-06-2025]]  *11:11* ((68435168-0fca-49d3-b735-8363d04c92ff))
 		- ✔️ [[21-06-2025]]  *22:12* ((e7272b30-e96e-4b85-918e-20c89e27647b))
@@ -123,7 +123,7 @@ progress:: {{renderer :todomaster}}
 - DONE Revision of manuscript #EMSE-D-25-00044
  id:: 6832257a-85cb-46bd-9018-855f59070a41
 - TODO [#B] [[PAPERS/MAS-4-POPULARITY-BIAS]]
- TODO [#B] [ICSE 2026, Research Track] Review Assignment and Instructions (Half Review Deadline: *Apr 18*; All reviews deadline: May 16)
+- DONE [#B] [ICSE 2026, Research Track] Review Assignment and Instructions (Half Review Deadline: *Apr 18*; All reviews deadline: May 16)
  todoist-desc:: From: noreply-icse2026@hotcrp.com
  todoist-id:: [9001461730](https://app.todoist.com/app/task/9001461730)
 - TODO Dottorato industriale
@@ -1,5 +1,15 @@
 tags:: #todoist-task [[ADMIN/MISSIONI]] 
 progress:: {{renderer :todomaster}}
 external-link:: [Program - FSE 2025](https://conf.researchr.org/program/fse-2025/program-fse-2025/)
- Preparazione slides per [[PAPERS/FSE2025-NIER]]
+	- ### Tasks
 		- DONE Preparazione slides per [[PAPERS/FSE2025-NIER]]
 id:: 68435168-0fca-49d3-b735-8363d04c92ff
 		  :LOGBOOK:
 		  CLOCK: [2025-06-21 Sat 11:11:22]--[2025-06-21 Sat 11:11:23] =>  00:00:01
 		  :END:
 	- ### Notes
 		- #### Slides preparation
 			- "Teamwork makes the dream work: LLMs-Based Agents for GitHub README.MD Summarization", has been accepted for presentation in the Ideas, Visions, and Reflections track at FSE 2025
 			- Instructions to upload / send the slides ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgNERPBAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
 		-
@@ -1,4 +1,4 @@
-type:: [[JournalPaper]], [[conferencepaper]], [[WorkshopPaper]], [[Bookchapter]]
+type:: [[JournalPaper]], 
 date:: [[30-05-2025]] - 16:25
 full-title::
 external-links::
@@ -6,7 +6,7 @@ year:: 2025
 date-start::
 status:: [[DOING]]
 venue:: [[AUSE]]
-priority:: [[P1]] [[P2]] [[P3]] [[P4]]
+priority:: [[P1]] 
 parent:: 
 leader:: 
 todoist:: 
@@ -2,4 +2,12 @@ tags:: #todoist-task, [[SERVICES/PHDICT]]
 date:: [[16-06-2025]] - 16:49
 progress:: {{renderer :todomaster}}
- ![image.png](../assets/image_1750085408113_0.png){:height 244, :width 1010}
+- ![image.png](../assets/image_1750085408113_0.png){:height 242, :width 1003}
 - ### Tasks
 	- TODO Chiedere cosa si intende per prodotti nell'anno precedente
 	- TODO Recuperare dati per Prima sezione
 	- TODO Scrivere commenti prima sezione
 	- TODO Finalizzare dati terza sezione
 	- TODO Scrivere commenti terza sezione
 	- TODO Condividere scheda per il 1 - 2 Luglio
 	- TODO Ricevere commenti per il 10 - 11 luglio
@@ -0,0 +1,44 @@
 collapsed:: true
 type:: [[REVIEWS]]
 tags:: 
 year:: 2025
 venue:: [[SEAA]] 
 full-title:: An agent design pattern catalogue for the entanglement of Digital Twins
 date-start:: [[21-06-2025]] - 15:23
 date-submitted::
 external-links::
 status:: [[DONE]] 
 deadline-submission:: 
 file:: [[@Model Consistency Management of a Brewery Digital Twin]] 
 parent::
 todoist:: https://app.todoist.com/app/task/134-hossain-muhammad-muctadir-yanyifan-liao-and-loek-cleophas-model-consistency-6c9VMX6jhRWr4f76
 	- ### [[Highlights]]
 	- ### [[Comments]]
 		- SUMMARY:  This paper proposes an approach for managing the consistency management of Digital Twin (DT) models. The approach is discussed by considering a microbrewery use case, which consists of different components, including a checker component, rule-based consistency management, and additional elements for monitoring and controlling aspects such as alcohol production.
 		- COMMENTS: The paper is about a relevant problem. Managing the consistency of different models is a significant problem, and considering this problem in the digital twin setting is even more critical. However, the paper requires some improvements to address different issues, as discussed below.
 			- The statement "ensures correct connectivity with the thermal dynamics model" lacks details. How is connectivity ensured? Is it verified syntactically, semantically, or through simulation? Clarification is needed on the nature of this assurance.
 			- The phrase "If a rule's condition is violated, the associated error message is shown" is insufficient. What happens after the violation? Is there a mechanism for resolving inconsistencies? Who is expected to act on these errors ()a developer, system administrator, or automated agent)? What runtime environment is assumed or supported?
 			- There is no clear description of the expected user of the framework or the technological assumptions required for integration into existing DT platforms. Is the framework designed for software engineers, domain experts, or system operators?
 			- The "Discussion on results" section is vague. What concrete results are presented? The paper would benefit from a concise summary of what has been evaluated and how. More importantly, the novelty is not effectively articulated:
 				- Is it the consistency checking mechanism?
 				- The rule organization structure?
 				- The integration with the DT lifecycle?
 				- The application of the considered approach in the microbrewery domain?
 			- Authors should clarify which components are novel compared to prior work. In particular, the reference to [3] in the future work section raises questions about how this approach differs from previously published ones. What is the added value beyond [3]?
 			- The paper mostly sketches a system architecture and a class diagram but does not elaborate on its unique contributions. What consistency challenges are solved by this framework that are not addressed by proof-theory-based, synchronization-based, or rule-based approaches alone?
 		- ---
 			- <h2>SUMMARY</h2>
 			  This paper proposes an approach for managing the consistency management of Digital Twin (DT) models. The approach is discussed by considering a microbrewery use case, which consists of different components, including a checker component, rule-based consistency management, and additional elements for monitoring and controlling aspects such as alcohol production.
 			  <h3>COMMENTS</h3>
 			  The paper is about a relevant problem. Managing the consistency of different models is a significant problem, and considering this problem in the digital twin setting is even more critical. However, the paper requires some improvements to address different issues, as discussed below.
 			  * The statement "ensures correct connectivity with the thermal dynamics model" lacks details. How is connectivity ensured? Is it verified syntactically, semantically, or through simulation? Clarification is needed on the nature of this assurance.
 			  * The phrase "If a rule's condition is violated, the associated error message is shown" is insufficient. What happens after the violation? Is there a mechanism for resolving inconsistencies? Who is expected to act on these errors (a developer, system administrator, or automated agent)? What runtime environment is assumed or supported?
 			  * There is no clear description of the expected user of the framework or the technological assumptions required for integration into existing DT platforms. Is the framework designed for software engineers, domain experts, or system operators?
 			  * The "Discussion on results" section is vague. What concrete results are presented? The paper would benefit from a concise summary of what has been evaluated and how. More importantly, the novelty is not effectively articulated:
 			  * Is it the consistency checking mechanism?
 			  * The rule organization structure?
 			  * The integration with the DT lifecycle?
 			  * The application of the considered approach in the microbrewery domain?
 			  * Authors should clarify which components are novel compared to prior work. In particular, the reference to [3] in the future work section raises questions about how this approach differs from previously published ones. What is the added value beyond [3]?
 			  * The paper mostly sketches a system architecture and a class diagram but does not elaborate on its unique contributions. What consistency challenges are solved by this framework that are not addressed by proof-theory-based, synchronization-based, or rule-based approaches alone?
@@ -175,8 +175,9 @@ progress:: {{renderer :todomaster}}
 	  id:: 6659d0ed-b485-4423-9c75-a8f5d715b31f
 		- Questo e' un anti-pattern -> ![ASAD-Report - Year II _CY (MA).pdf](../assets/ASAD-Report_-_Year_II_CY_(MA)_1712172077031_0.pdf)
 - ## FAQs
-	- [[Frammenti di verbale riusabili]]
+	- ### **[[Frammenti di verbale riusabili]]**
-	- ###  ==Templates emails==
+	- ###  Templates emails
 	  collapsed:: true
 		- **INVIO TESI AI REVISORI** (esempio subject Asad's PhD thesis review)
 		  collapsed:: true
 			- Dear Bart and Paolo,
@@ -264,8 +265,10 @@ progress:: {{renderer :todomaster}}
 			- All the best
 			- Davide
 	- ### **PUBLIC**
 	  collapsed:: true
 		- [FAQs (notion.so)](https://www.notion.so/phd-ict-univaq/FAQs-ef2849e8affc4c21ab1999e32b5eb009)
 	- ### **PRIVATE**
 	  collapsed:: true
 		- #### Incremento borsa dottorato per periodo all'estero
 		  collapsed:: true
 			- Ciao Giordano,
@@ -289,7 +292,8 @@ progress:: {{renderer :todomaster}}
 		- ![Immagine WhatsApp 2025-03-07 ore 20.40.26_e61fad42.jpg](../assets/Immagine_WhatsApp_2025-03-07_ore_20.40.26_e61fad42_1741376476900_0.jpg)
 		- Circa 95'000 Euro incluso 10% per fondi di ricerca e 50% di maggiorazione per 6 mesi all'estero. Senza periodo all'estero siamo sui 65'000
 			- Vedi Art 12 del [Regolamento](https://www.univaq.it/include/utilities/blob.php?table=regolamento&id=64&item=file)
-	-
+	- ### **Incremento importi borse PNRR 38 e 39 Ciclo**
 		- ![image.png](../assets/image_1750427081840_0.png)
 - ## 2025/2026 #XLI ciclo
 	- CALENDARIO
 		- ![Bando Dottorato di Ricerca XLI ciclo_Comunicazione.pdf](../assets/Bando_Dottorato_di_Ricerca_XLI_ciclo_Comunicazione_1750159552604_0.pdf)
@@ -0,0 +1,5 @@
 icon:: 🔨
 - ### Meetings
 	- {{query (and [[meeting]] [[SoftwareMiningGroup]])}}
 	  query-table:: true
@@ -25,7 +25,7 @@ progress:: {{renderer :todomaster}}
  todoist-desc:: logseq://graph/Logseq?page=Progettazione%20Offerta%20Formativa
  todoist-id:: [9205819498](https://app.todoist.com/app/task/9205819498)
  SCHEDULED: <2025-06-23 Mon>
- TODO [#A] [[Missione STAF 2025]]
+- DONE [#A] [[Missione STAF 2025]]
  todoist-id:: [9135141990](https://app.todoist.com/app/task/9135141990)
  SCHEDULED: <2025-06-19 Thu>
  :LOGBOOK:
@@ -41,37 +41,42 @@ progress:: {{renderer :todomaster}}
 - TODO [#C] [[PAPERS/SOSYM-EXPERT-VOICE-2024-ML-EVOLUTION]]
  todoist-desc:: [Sosym Expert voice: Co-evo in the era of Low code - Online LaTeX Editor Overleaf](https://www.overleaf.com/project/680d243a75547ff8d273e791)
  todoist-id:: [7584640828](https://app.todoist.com/app/task/7584640828)
- TODO [#C] [[PAPERS/AUSE-Metagente]]
+- DOING [#C] [[PAPERS/AUSE-Metagente]]
  todoist-desc:: [MDEGroup/AUSE-Metagente: A paper to be submitted to a special issue of the Automated Software Engineering journal](https://github.com/MDEGroup/AUSE-Metagente)
  todoist-id:: [9213097648](https://app.todoist.com/app/task/9213097648)
  :LOGBOOK:
  CLOCK: [2025-06-20 Fri 22:58:39]
  :END:
 - TODO [#B] [[Call per posizioni MOSAICO]]
  todoist-desc:: logseq://graph/Logseq?page=Call%20per%20posizioni%20MOSAICO
  todoist-id:: [8663268357](https://app.todoist.com/app/task/8663268357)
-  SCHEDULED: <2025-06-20 Fri>
+  SCHEDULED: <2025-06-24 Tue>
  :LOGBOOK:
  CLOCK: [2025-06-14 Sat 11:21:37]--[2025-06-14 Sat 21:27:23] =>  10:05:46
  :END:
- TODO [#C] [[Missione FSE 2025]]
+- TODO [#A] [[Missione FSE 2025]]
  todoist-id:: [9074935545](https://app.todoist.com/app/task/9074935545)
  todoist-desc:: [FSE 2025](https://conf.researchr.org/home/fse-2025)
- TODO [#B] [[PAPERS/MOSAICO-Technical-Report]]
+  todoist-id:: [9074935545](https://app.todoist.com/app/task/9074935545)
  SCHEDULED: <2025-06-22 Sun>
 - DOING [#B] [[PAPERS/MOSAICO-Technical-Report]]
  SCHEDULED: <2025-06-25 Wed>
  todoist-desc:: logseq://graph/Logseq?page=PAPERS%2FMOSAICO-Technical-Report
  todoist-id:: [9187744429](https://app.todoist.com/app/task/9187744429)
  SCHEDULED: <2025-06-20 Fri>
  :LOGBOOK:
  CLOCK: [2025-06-07 Sat 13:49:10]--[2025-06-08 Sun 21:19:31] =>  31:30:21
  CLOCK: [2025-06-13 Fri 12:00:06]--[2025-06-14 Sat 09:56:22] =>  21:56:16
  CLOCK: [2025-06-20 Fri 22:58:10]
  :END:
 - DONE [#A] [[Preparazione Intervento PINKAMP]]
  todoist-id:: [9179967916](https://app.todoist.com/app/task/9179967916)
  SCHEDULED: <2025-06-19 Thu>
 - TODO [#B] [[Aggiornamento uso fondi progetti]]
  todoist-id:: [9143259271](https://app.todoist.com/app/task/9143259271)
-  SCHEDULED: <2025-06-20 Fri>
+  SCHEDULED: <2025-06-22 Sun>
 - TODO [#A] [[[mosaico-all] MOSAICO meetings in Rome July 2025]]
  todoist-desc:: From: zhanna.zhussupova@imt-atlantique.fr
  todoist-id:: [9224183665](https://app.todoist.com/app/task/9224183665)
-  SCHEDULED: <2025-06-21 Sat>
+  SCHEDULED: <2025-06-24 Tue>
 - TODO [[Invited talk at LLMA4SE Summer School website]]
  todoist-id:: [9201031612](https://app.todoist.com/app/task/9201031612)
  todoist-desc:: From: chemacm@unex.es
@@ -79,35 +84,38 @@ progress:: {{renderer :todomaster}}
 - TODO [#B] [[Missione Emeliot Salerno - Luglio 2025]]
  todoist-desc:: From: leonardo.mariani@unimib.it
  todoist-id:: [9161916557](https://app.todoist.com/app/task/9161916557)
-  SCHEDULED: <2025-06-23 Mon>
+  SCHEDULED: <2025-06-22 Sun>
 - TODO [#A] [[I: ELSEVIER IST: Your Submission - INFSOF-D-25-00112 - Major Revision]]
  todoist-desc:: From: [giordano.daloisio@univaq.it](mailto:giordano.daloisio@univaq.it)
  todoist-id:: [9223518427](https://app.todoist.com/app/task/9223518427)
- TODO [#B] [[Linee guida afferenza Collegio dottorato ICT]]
+- TODO [#A] [[Linee guida afferenza Collegio dottorato ICT]]
  todoist-desc:: [Linee guida per la valutazione richieste afferenza dottorato ICT.docx](https://univaq-my.sharepoint.com/:w:/g/personal/davide_diruscio_univaq_it/EbLmq-bFlvZDpxTZLeHiQFgBBlAIxRR_3aoAZsNBUHFyXw?e=cXOsS3)
  todoist-id:: [8912715542](https://app.todoist.com/app/task/8912715542)
-  SCHEDULED: <2025-06-20 Fri>
+  SCHEDULED: <2025-06-22 Sun>
  :LOGBOOK:
  CLOCK: [2025-06-13 Fri 11:59:57]--[2025-06-14 Sat 09:56:22] =>  21:56:25
  :END:
- DOING [#A] [[Presentazione dei documenti di monitoraggio]]
+- TODO [#A] [[Presentazione dei documenti di monitoraggio]]
  SCHEDULED: <2025-06-19 Thu>
  todoist-desc:: From: [antonio.mecozzi@univaq.it](mailto:antonio.mecozzi@univaq.it)
  todoist-id:: [9223534564](https://app.todoist.com/app/task/9223534564)
  SCHEDULED: <2025-06-22 Sun>
  :LOGBOOK:
-  CLOCK: [2025-06-19 Thu 19:33:26]
+  CLOCK: [2025-06-19 Thu 19:33:26]--[2025-06-19 Thu 22:24:30] =>  02:51:04
  :END:
- TODO [#A] [[🗓 TIASSISTO24 - MEETING BANDO REGIONE ABRUZZO 1.1.1.2]]
+- DOING [#A] [[🗓 TIASSISTO24 - MEETING BANDO REGIONE ABRUZZO 1.1.1.2]]
  SCHEDULED: <2025-06-25 Wed 09:30>
  todoist-desc:: From: executiveassistant@e.read.ai
  todoist-id:: [9248741876](https://app.todoist.com/app/task/9248741876)
-  SCHEDULED: <2025-06-19 Thu>
+  :LOGBOOK:
  CLOCK: [2025-06-20 Fri 16:29:44]
  :END:
 - TODO [#A] [[PRIN 2020 - scadenza rendicontazione finale]]
  todoist-desc:: From: proget@strutture.univaq.it
  todoist-id:: [9134866367](https://app.todoist.com/app/task/9134866367)
-  SCHEDULED: <2025-06-20 Fri>
+  SCHEDULED: <2025-06-22 Sun>
- TODO [#C] [[Missione ROMA Mosaico]]
+- TODO [#B] [[Missione ROMA Mosaico]]
  todoist-id:: [9204561368](https://app.todoist.com/app/task/9204561368)
-  SCHEDULED: <2025-06-20 Fri>
+  SCHEDULED: <2025-06-23 Mon>
 - DONE [#B] [[MODELS: 10 years most infuential paper selection committee]]
  todoist-desc:: From: manuel.wimmer@jku.at
  todoist-id:: [9153069465](https://app.todoist.com/app/task/9153069465)
@@ -144,9 +144,15 @@ template:: JOURNAL-TEMPLATE-OLD
  tags:: #todoist-task
  date:: <%today%> - <%time%>
  progress:: {{renderer :todomaster}}
 	- ### Tasks
 		-
 	- ### Notes
 		-
 - template:: JOURNAL-TEMPLATE
  progress:: {{renderer :todomaster}}
  icon:: 📅
  boox-notes:: ![BOOX Notes](../assets/../../onyx/TabUltraCPro/Notepad/JOURNALING.pdf)
-	- ## Tasks
+	- ### Tasks
-	- ## Notes
+		-
 	- ### Notes
 		-
@@ -1,5 +1,43 @@
 tags:: #todoist-task, [[PROJECTS]] 
 date:: [[19-06-2025]] - 13:11
 progress:: {{renderer :todomaster}}
 link:: [1.1) Documenti tecnici in preparazione - Google Drive](https://drive.google.com/drive/folders/1IVvT90ZYi7kyHTC7YCz9a5vQPTaX4KyK), ✉: [Link a WBS AGGIORNATA](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgOxNs1AAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
 - ### Tasks
 	- TODO Dare input su **Acronimo** e **Titolo progetto**
 	- TODO Descrizione sintetica **dell’oggetto** della proposta progettuale
 		- Rivedere quanto specificato nel documento ((685521de-7d0e-431f-801a-a3f836d10c8b))
 	- TODO Ruolo nel progetto-> **nominativo proponente**
 		- Rivedere quanto specificato nel documento ((685521de-7d0e-431f-801a-a3f836d10c8b))
 	- DOING WBS ed Obiettivi progettuali di ciascun partner, necessari anche per la costituzione dell'ATS.
 	  :LOGBOOK:
 	  CLOCK: [2025-06-20 Fri 11:14:14]
 	  :END:
 		- DONE Si allega WBS ( ((685521a4-f80f-4839-bf96-1dc0ff06ce4e))) discussa oggi. Si prega ciascun partner di fornire un contributo di 5 righe in cui descrive l’attività che svolge in quel task, in qualità di lead o contributor.
 id:: 6855230d-2cce-40a9-87b4-d99207252a6b
 		  :LOGBOOK:
 		  CLOCK: [2025-06-20 Fri 11:45:26]--[2025-06-20 Fri 11:45:26] =>  00:00:00
 		  :END:
 		- DONE Per ciascun task occorre identificare in maniera univoca l’output associato e la relativa tipologia (es. relazione tecnica, SW, DEMO, ecc).
 id:: 68552317-3e34-4889-8d03-7671dd9239d7
 		- Sulla base di queste informazioni si richiede un provisional **budget** che poi sarà discusso e concordato insieme al lead e alle esigenze di progetto a stretto giro.
 		- DONE Queste info appena descritte insieme al background di ciascun partner saranno inserite nell’ATS. In allegato le pagine dell’ATS in cui inserire quanto sopra ripotato.
 id:: 6855232a-08da-43da-9147-2012a583dc21
 			- [Allegato ATS.doc](../assets/Allegato_ATS_1750410047925_0.doc)
 	- TODO **Piano di ampia diffusione dei risultati**, necessario per incrementare % intensità dell'agevolazione
 		- Attività in capo al Polo di innovazione Inoltra. Sarà un costo di consulenza che, insieme all’attività in corso e quelle che svolgeremo a supporto della implementazione del progetto, potrà essere rendicontata da tutte le aziende. Le università non sono coinvolte nel contratto di collaborazione. Per i termini dell’accordo abbiamo già discusso con Michele, ma possiamo sentirci quando volete. A breve riceverete dal Polo la proposta economica mandato.
 	- TODO **RICHIESTA DOCUMENTAZIONE - BANDO REGIONE ABRUZZO 1.1.1.2**
 	  email:: ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgKbCesAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
 		- [[question]] questo non credo serva piu a valle della costituzione dell'ATS, giusto?
 -
 - ### Followup riunione del [[12-06-2025]] alla quale io non ho partecipato 
  email:: ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgKbCcvAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
 	- Progetto: [PROGETTO TIASSISTO24020625.xlsx](../assets/PROGETTO_TIASSISTO24020625_1750409693309_0.xlsx)
 	  id:: 685521a4-f80f-4839-bf96-1dc0ff06ce4e
 	- [FLUSSO DI LAVORO PROGETTO TIASSISTO24 rev1.docx](../assets/FLUSSO_DI_LAVORO_PROGETTO_TIASSISTO24_rev1_1750409715752_0.docx)
 	  id:: 685521de-7d0e-431f-801a-a3f836d10c8b
 	-
 - ### Completamento ATS - **ATTO COSTITUTIVO DI ASSOCIAZIONE TEMPORANEA DI SCOPO**
 	- ✉: [Web Link](https://outlook.office365.com/owa/?ItemID=AAMkADM1NGNiNjk0LTY0ZGUtNDgzOC04MDM5LWNhODNkYWNjNjU4YwBGAAAAAACT6qp78kRgRKuUMBdWEga%2FBwCOhWlC8F7PRKzlljZYZYQmAAAAAAEMAACOhWlC8F7PRKzlljZYZYQmAAgOxNsyAAA%3D&exvsurl=1&viewmodel=ReadMessageItem)
 	- [Atto Costitutivo ATS_18.06.25.doc](../assets/Atto_Costitutivo_ATS_18.06.25_1750409430902_0.doc)
 	- [Atto Costitutivo ATS_TIASSISTO24.doc - Google Docs](https://docs.google.com/document/d/1eMKA-KCGDFDfBl7wCDU1BQspqLiA9Ms6/edit)