Changes between Version 64 and Version 65 of ExDescLang

Timestamp:

Oct 20, 2010 3:59:37 PM (14 years ago)

Author:

sunshine

Comment:

--

ExDescLang

@@ -23 +23 @@
    * An action must happen vs may happen
    * Additional actions are allowed vs not allowed 
+   * An action can(not) be split into multiple smaller pieces that have the same effect
    * State changes in objects due to some action, at random, due to a timeout ... State changes that generate an action
    * Conditions that lead to state change or to an action
@@ -31 +32 @@
      a. those that deal with objects and their states ("cache must be poisoned")
      b. those that deal with events and their features ("traffic must flow from A to B for 5 minutes at 100Mbps")
+     
+     In general case invariants are defined in the logical topology and timeline of events. Additional invariants may be defined in this section but so far I had hard time coming up with those for a meta-description. Naturally when the user designs her experiment starting from the metadescription this will lead to more invariants being defined automatically and to some that a user can choose to define.
 
 '''Note that intentionally this is all pretty high-level and is orthogonal to any generator used to generate topologies, traffic, etc.''' There must be a mapping process that selects eligible generators for each dimension and takes their output and maps objects and events to it. More about this mapping process later.
 
+= Domain Knowledge =
+
+= Generator Descriptions = 
+
+= Mapping elements of metadescription to generators =
 
 = TODO =