Last Sync: 2025-06-06 21:33 (Mobile)

pages/PAPERS___DSL-FOR-IOT-TESTING.md

@@ -13,13 +13,11 @@ progress:: {{renderer : todomaster}}
 
 	- ## Meeting del [[06-06-2025]]
 	  type:: [[meeting]]
-	  collapsed:: true
 		- Si e' deciso di andare per IST
 			- 49 vs 85 linee di codici
 		- Pensare a come valutare la convenienza dell'uso del linguaggio.
 			-
 	- ## NOTES
-	  collapsed:: true
 		- Aapproach to detect possible faults that can occur when giving a time series to an input port of an IoT component and get output data from the corresponding output. The kinds of faults that we have carrently identified are the following:
 			- EARLY: output is provided too early
 			- LATE: output is provided too late
@@ -83,13 +81,11 @@ progress:: {{renderer : todomaster}}
 			- mutazioni a piacere
 	- ## MEETINGS
 	- ## READINGS
-	  collapsed:: true
 		- [[MAUDE-Manual]]
 	- ## TASKs
 	- ## QUESTIONS TO ANSWER
 	  {{query (and [[question]][[PAPERS/DSL-FOR-IOT-TESTING]])}}
 	- ## [[PAPERS/NOTES]]
-	  collapsed:: true
 		- MAUDE sembra essere un buon candidato come linguaggio target per dare semantica al DSL in fase di definizione.
 		- Come descritto [1 Introduction (uma.es)](https://maude.lcc.uma.es/maude321-manual-html/maude-manualch1.html#x4-140001.2)
 			- In the context of Maude, such property specifications can be given in a variety of ways: