TAMI - Recent changes [en]

PML Based AIR Justification

Ankesh — Mon, 16 Nov 2009 04:02:54 GMT

←Older revision		Revision as of 04:02, 16 November 2009
Line 44:		Line 44:
	## air:rule		## air:rule
	# pmlj:variableMappingList (is pmlj:variableMappingList an owl:ObjectProperty)		# pmlj:variableMappingList (is pmlj:variableMappingList an owl:ObjectProperty)
-	## airj:inputVariableMappingList (rdfs:subPropertyOf pmll:variableMappingList)	+	## #airj:inputVariableMappingList (rdfs:subPropertyOf pmll:variableMappingList)
	## airj:outputVariableMappingList (rdfs:subPropertyOf pmll:variableMappingList)		## airj:outputVariableMappingList (rdfs:subPropertyOf pmll:variableMappingList)
	### airj:outputVariableMappingListOf (inverse of airj:outputVariableMappingList)		### airj:outputVariableMappingListOf (inverse of airj:outputVariableMappingList)
Line 75:		Line 75:
	The ''RuleApplication'' event captures the step where a rule is applied. It is linked to the rule through the ''air:rule'' property. One of the main functions of the ''airj:RuleApplication'' event is to find bindings for variables in the rule. Some of the variables may be bound already in one of the ancestor rules (parent rule, parent rule of parent rule , ...). In order to find the variable bindings, the known graph (input graph + inferred triples) must contain a sub-graph that matches the pattern in the ''air:if'' condition of the rule and confirms to the bindings of the variables that are bound already. If such sub-graphs (matched graph) exist then the variables are mapped to the constants at the corresponding positions in the the sub-graph, for each sub-graph. Once the mappings are determined, the ''air:then'' actions (air:Action) are effected. When no such matching graphs are found and the world is closed, i.e. it is assumed that all triples not in the known graph are not believed, the ''air:else'' actions are effected. The effected ''air:Action'' is either the triggering of one of the child-rules or the addition of inferred triples to the known graph. <br><br>		The ''RuleApplication'' event captures the step where a rule is applied. It is linked to the rule through the ''air:rule'' property. One of the main functions of the ''airj:RuleApplication'' event is to find bindings for variables in the rule. Some of the variables may be bound already in one of the ancestor rules (parent rule, parent rule of parent rule , ...). In order to find the variable bindings, the known graph (input graph + inferred triples) must contain a sub-graph that matches the pattern in the ''air:if'' condition of the rule and confirms to the bindings of the variables that are bound already. If such sub-graphs (matched graph) exist then the variables are mapped to the constants at the corresponding positions in the the sub-graph, for each sub-graph. Once the mappings are determined, the ''air:then'' actions (air:Action) are effected. When no such matching graphs are found and the world is closed, i.e. it is assumed that all triples not in the known graph are not believed, the ''air:else'' actions are effected. The effected ''air:Action'' is either the triggering of one of the child-rules or the addition of inferred triples to the known graph. <br><br>
	[[Image:RuleApplication.jpg\|550px\|thumb\|right\|''RuleApplication'' ''Event'']]		[[Image:RuleApplication.jpg\|550px\|thumb\|right\|''RuleApplication'' ''Event'']]
-	The mappings for already bound variables is described through the ''airj:inputVariableMappingList'' property, and the ''airj:outputVariableMappingList'' property is used to describe the variable mappings after the rule has been applied. The output variable mappings is the union of input variable mappings and the new variable bindings. The branch taken depending on whether a matching sub-graph exists, is declared using ''airj:branch'' property. The range of ''airj:branch'' property is one of {''air:then'', ''air:else''}. The triples that are added to the known graph are linked by the ''airj:outputdata'' property. When some ''air:description'' is attached with the ''air:Action'' of the rule, defined in the policy document, then the current event is annotated with it using the same ''air:description'' property.<br><br>	+	The mappings for already bound variables is described through the ''#airj:inputVariableMappingList'' property, and the ''airj:outputVariableMappingList'' property is used to describe the variable mappings after the rule has been applied. The output variable mappings is the union of input variable mappings and the new variable bindings. The branch taken depending on whether a matching sub-graph exists, is declared using ''airj:branch'' property. The range of ''airj:branch'' property is one of {''air:then'', ''air:else''}. The triples that are added to the known graph are linked by the ''airj:outputdata'' property. When some ''air:description'' is attached with the ''air:Action'' of the rule, defined in the policy document, then the current event is annotated with it using the same ''air:description'' property.<br><br>
	A ''airj:RuleApplication'' event has two kinds of dependencies - flow control and data- on other events. When the rule of the current ''airj:RuleApplication'' event is a child rule of another rule, the event has a flow control dependency over some ''RuleApplication'' event of the parent rule. The input variable bindings for the current event are the output of this event. When the current event has a matched graph, the sub graphs of the matched graph could come from either the original (input) graph or from the inferred triples. The current event has data dependency in the former case over an ''airj:Extraction'' event where the input graph is extracted (parsed) from the input data log, and on the ''airj:RuleApplication'' event where the triples were added to the known graph in the latter. If the current event doesn't have a matched graph, i.e. the ''air:else'' actions are effected, then data dependency is used to describe all the sources of data for the known graph, none of whose sub-graphs matched the pattern in the ''air:if'' condition. As mentioned earlier, the effecting of actions depend on some ''airj:ClosingTheWorld'' event. The current event has data dependency, and also flow control dependency, over the same ''airj:ClosingTheWorld'' event, which has data dependencies on all prior events where triples are outputted. The flow control and data dependencies are described through the ''airj:flowDependency'' and ''airj:dataDependency'' properties, respectively.<br><br>		A ''airj:RuleApplication'' event has two kinds of dependencies - flow control and data- on other events. When the rule of the current ''airj:RuleApplication'' event is a child rule of another rule, the event has a flow control dependency over some ''RuleApplication'' event of the parent rule. The input variable bindings for the current event are the output of this event. When the current event has a matched graph, the sub graphs of the matched graph could come from either the original (input) graph or from the inferred triples. The current event has data dependency in the former case over an ''airj:Extraction'' event where the input graph is extracted (parsed) from the input data log, and on the ''airj:RuleApplication'' event where the triples were added to the known graph in the latter. If the current event doesn't have a matched graph, i.e. the ''air:else'' actions are effected, then data dependency is used to describe all the sources of data for the known graph, none of whose sub-graphs matched the pattern in the ''air:if'' condition. As mentioned earlier, the effecting of actions depend on some ''airj:ClosingTheWorld'' event. The current event has data dependency, and also flow control dependency, over the same ''airj:ClosingTheWorld'' event, which has data dependencies on all prior events where triples are outputted. The flow control and data dependencies are described through the ''airj:flowDependency'' and ''airj:dataDependency'' properties, respectively.<br><br>

Line 165:		Line 165:

	pr:extractInputGraph a airj:Extraction;		pr:extractInputGraph a airj:Extraction;
-	~~pmll:inputdata pr:inputLog;~~
	pmll:outputdata pr:inputLog.		pmll:outputdata pr:inputLog.

Line 187:		Line 186:
	airj:outputVariableMappingList (pr:MappingFVar1_1);		airj:outputVariableMappingList (pr:MappingFVar1_1);
	air:rule :Rule21;		air:rule :Rule21;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
	airj:branch air:then;		airj:branch air:then;
Line 200:		Line 199:
	airj:outputVariableMappingList (pr:MappingFVar1_2);		airj:outputVariableMappingList (pr:MappingFVar1_2);
	air:rule :Rule21;		air:rule :Rule21;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
	airj:branch air:then;		airj:branch air:then;
Line 210:		Line 209:
	pmll:outputdata {:s1 air:compliant-with :ExamplePolicy . };		pmll:outputdata {:s1 air:compliant-with :ExamplePolicy . };
	air:rule :Rule211;		air:rule :Rule211;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];
	airj:flowDependency pr:Event3_1;		airj:flowDependency pr:Event3_1;
	airj:branch air:then;		airj:branch air:then;
Line 223:		Line 222:
	pmll:outputdata { :s2 air:non-compliant-with :ExamplePolicy . };		pmll:outputdata { :s2 air:non-compliant-with :ExamplePolicy . };
	air:rule :Rule211;		air:rule :Rule211;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];
	airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;		airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;
	airj:branch air:else;		airj:branch air:else;
Line 237:		Line 236:
	airj:outputVariableMappingList (pr:MappingFVar1_1);		airj:outputVariableMappingList (pr:MappingFVar1_1);
	air:rule :Rule21;		air:rule :Rule21;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
	airj:branch air:then;		airj:branch air:then;
Line 246:		Line 245:
	airj:outputVariableMappingList (pr:MappingFVar1_2);		airj:outputVariableMappingList (pr:MappingFVar1_2);
	air:rule :Rule21;		air:rule :Rule21;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
	airj:branch air:then;		airj:branch air:then;
Line 281:		Line 280:
	airj:outputVariableMappingList (pr:MappingFVar1_1);		airj:outputVariableMappingList (pr:MappingFVar1_1);
	air:rule :Rule21;		air:rule :Rule21;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
	airj:branch air:then;		airj:branch air:then;
Line 294:		Line 293:
	airj:outputVariableMappingList (pr:MappingFVar1_2);		airj:outputVariableMappingList (pr:MappingFVar1_2);
	air:rule :Rule21;		air:rule :Rule21;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
	airj:branch air:then;		airj:branch air:then;
Line 304:		Line 303:
	pmll:outputdata {:s1 air:compliant-with :ExamplePolicy . };		pmll:outputdata {:s1 air:compliant-with :ExamplePolicy . };
	air:rule :Rule211;		air:rule :Rule211;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];
	airj:flowDependency pr:Event3_1;		airj:flowDependency pr:Event3_1;
	airj:branch air:then;		airj:branch air:then;
Line 317:		Line 316:
	pmll:outputdata { :s2 air:non-compliant-with :ExamplePolicy . };		pmll:outputdata { :s2 air:non-compliant-with :ExamplePolicy . };
	air:rule :Rule211;		air:rule :Rule211;
-	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];	+	#airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];
	airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;		airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;
	airj:branch air:else;		airj:branch air:else;

Image:RuleApplication.jpg

Ankesh — Mon, 16 Nov 2009 03:58:15 GMT

uploaded a new version of "[[Image:RuleApplication.jpg]]"

New page

Image:AIRJustificationUsingPML.jpg

Ankesh — Mon, 16 Nov 2009 03:56:37 GMT

uploaded a new version of "[[Image:AIRJustificationUsingPML.jpg]]"

New page

PML Based AIR Justification

Ankesh — Mon, 16 Nov 2009 03:55:50 GMT

←Older revision		Revision as of 03:55, 16 November 2009
Line 36:		Line 36:
	## pmll:outputdata (rdfs:subPropertyOf pmlj:conclusion)		## pmll:outputdata (rdfs:subPropertyOf pmlj:conclusion)
	# air:description		# air:description
-	# airj:~~hasMatchedGraph~~	+	# airj:branch
	# pmll:inputdata		# pmll:inputdata
	# pmlj:mapFrom		# pmlj:mapFrom
Line 75:		Line 75:
	The ''RuleApplication'' event captures the step where a rule is applied. It is linked to the rule through the ''air:rule'' property. One of the main functions of the ''airj:RuleApplication'' event is to find bindings for variables in the rule. Some of the variables may be bound already in one of the ancestor rules (parent rule, parent rule of parent rule , ...). In order to find the variable bindings, the known graph (input graph + inferred triples) must contain a sub-graph that matches the pattern in the ''air:if'' condition of the rule and confirms to the bindings of the variables that are bound already. If such sub-graphs (matched graph) exist then the variables are mapped to the constants at the corresponding positions in the the sub-graph, for each sub-graph. Once the mappings are determined, the ''air:then'' actions (air:Action) are effected. When no such matching graphs are found and the world is closed, i.e. it is assumed that all triples not in the known graph are not believed, the ''air:else'' actions are effected. The effected ''air:Action'' is either the triggering of one of the child-rules or the addition of inferred triples to the known graph. <br><br>		The ''RuleApplication'' event captures the step where a rule is applied. It is linked to the rule through the ''air:rule'' property. One of the main functions of the ''airj:RuleApplication'' event is to find bindings for variables in the rule. Some of the variables may be bound already in one of the ancestor rules (parent rule, parent rule of parent rule , ...). In order to find the variable bindings, the known graph (input graph + inferred triples) must contain a sub-graph that matches the pattern in the ''air:if'' condition of the rule and confirms to the bindings of the variables that are bound already. If such sub-graphs (matched graph) exist then the variables are mapped to the constants at the corresponding positions in the the sub-graph, for each sub-graph. Once the mappings are determined, the ''air:then'' actions (air:Action) are effected. When no such matching graphs are found and the world is closed, i.e. it is assumed that all triples not in the known graph are not believed, the ''air:else'' actions are effected. The effected ''air:Action'' is either the triggering of one of the child-rules or the addition of inferred triples to the known graph. <br><br>
	[[Image:RuleApplication.jpg\|550px\|thumb\|right\|''RuleApplication'' ''Event'']]		[[Image:RuleApplication.jpg\|550px\|thumb\|right\|''RuleApplication'' ''Event'']]
-	The mappings for already bound variables is described through the ''airj:inputVariableMappingList'' property, and the ''airj:outputVariableMappingList'' property is used to describe the variable mappings after the rule has been applied. The output variable mappings is the union of input variable mappings and the new variable bindings. The ~~existence of~~ a ~~matched~~ graph is ~~described by the boolean~~ property - ''airj:~~hasMatchedGraph~~''. The triples that are added to the known graph are linked by the ''airj:outputdata'' property. When some ''air:description'' is attached with the ''air:Action'' of the rule, defined in the policy document, then the current event is annotated with it using the same ''air:description'' property.<br><br>	+	The mappings for already bound variables is described through the ''airj:inputVariableMappingList'' property, and the ''airj:outputVariableMappingList'' property is used to describe the variable mappings after the rule has been applied. The output variable mappings is the union of input variable mappings and the new variable bindings. The branch taken depending on whether a matching sub-graph exists, is declared using ''airj:branch'' property. The range of ''airj:branch'' property is one of {''air:then'', ''air:else''}. The triples that are added to the known graph are linked by the ''airj:outputdata'' property. When some ''air:description'' is attached with the ''air:Action'' of the rule, defined in the policy document, then the current event is annotated with it using the same ''air:description'' property.<br><br>
	A ''airj:RuleApplication'' event has two kinds of dependencies - flow control and data- on other events. When the rule of the current ''airj:RuleApplication'' event is a child rule of another rule, the event has a flow control dependency over some ''RuleApplication'' event of the parent rule. The input variable bindings for the current event are the output of this event. When the current event has a matched graph, the sub graphs of the matched graph could come from either the original (input) graph or from the inferred triples. The current event has data dependency in the former case over an ''airj:Extraction'' event where the input graph is extracted (parsed) from the input data log, and on the ''airj:RuleApplication'' event where the triples were added to the known graph in the latter. If the current event doesn't have a matched graph, i.e. the ''air:else'' actions are effected, then data dependency is used to describe all the sources of data for the known graph, none of whose sub-graphs matched the pattern in the ''air:if'' condition. As mentioned earlier, the effecting of actions depend on some ''airj:ClosingTheWorld'' event. The current event has data dependency, and also flow control dependency, over the same ''airj:ClosingTheWorld'' event, which has data dependencies on all prior events where triples are outputted. The flow control and data dependencies are described through the ''airj:flowDependency'' and ''airj:dataDependency'' properties, respectively.<br><br>		A ''airj:RuleApplication'' event has two kinds of dependencies - flow control and data- on other events. When the rule of the current ''airj:RuleApplication'' event is a child rule of another rule, the event has a flow control dependency over some ''RuleApplication'' event of the parent rule. The input variable bindings for the current event are the output of this event. When the current event has a matched graph, the sub graphs of the matched graph could come from either the original (input) graph or from the inferred triples. The current event has data dependency in the former case over an ''airj:Extraction'' event where the input graph is extracted (parsed) from the input data log, and on the ''airj:RuleApplication'' event where the triples were added to the known graph in the latter. If the current event doesn't have a matched graph, i.e. the ''air:else'' actions are effected, then data dependency is used to describe all the sources of data for the known graph, none of whose sub-graphs matched the pattern in the ''air:if'' condition. As mentioned earlier, the effecting of actions depend on some ''airj:ClosingTheWorld'' event. The current event has data dependency, and also flow control dependency, over the same ''airj:ClosingTheWorld'' event, which has data dependencies on all prior events where triples are outputted. The flow control and data dependencies are described through the ''airj:flowDependency'' and ''airj:dataDependency'' properties, respectively.<br><br>

Line 173:		Line 173:
	:s2 :p :o . };		:s2 :p :o . };
	air:rule :Rule1;		air:rule :Rule1;
-	airj:~~hasMatchedGraph true~~.	+	airj:branch air:then.

	pr:Event2 a airj:RuleApplication;		pr:Event2 a airj:RuleApplication;
	airj:outputVariableMappingList ().		airj:outputVariableMappingList ().
	air:rule :Rule2;		air:rule :Rule2;
-	airj:~~hasMatchedGraph true~~.	+	airj:branch air:then.

	pr:MappingFVar1_1 a pmlj:Mapping;		pr:MappingFVar1_1 a pmlj:Mapping;
Line 189:		Line 189:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	air:description ":s1 satisfies the first set of checks";		air:description ":s1 satisfies the first set of checks";
	airj:dataDependency pr:Event1, pr:extractInputGraph.		airj:dataDependency pr:Event1, pr:extractInputGraph.
Line 202:		Line 202:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	air:description ":s2 satisfies the first set of checks";		air:description ":s2 satisfies the first set of checks";
	airj:dataDependency pr:Event1, pr:extractInputGraph.		airj:dataDependency pr:Event1, pr:extractInputGraph.
Line 212:		Line 212:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];
	airj:flowDependency pr:Event3_1;		airj:flowDependency pr:Event3_1;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	airj:dataDependency pr:extractInputGraph.		airj:dataDependency pr:extractInputGraph.

Line 225:		Line 225:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];
	airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;		airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;
-	airj:~~hasMatchedGraph false~~;	+	airj:branch air:else;
	airj:dataDependency pr:ClosingTheWorld1.		airj:dataDependency pr:ClosingTheWorld1.
	</pre>		</pre>
Line 239:		Line 239:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	air:description ":s1 satisfies the first set of checks";		air:description ":s1 satisfies the first set of checks";
	airj:dataDependency pr:Event1, pr:extractInputGraph.		airj:dataDependency pr:Event1, pr:extractInputGraph.
Line 248:		Line 248:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	air:description ":s2 satisfies the first set of checks";		air:description ":s2 satisfies the first set of checks";
	airj:dataDependency pr:Event1, pr:extractInputGraph.		airj:dataDependency pr:Event1, pr:extractInputGraph.
Line 283:		Line 283:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	air:description ":s1 satisfies the first set of checks";		air:description ":s1 satisfies the first set of checks";
	airj:dataDependency pr:Event1, pr:extractInputGraph.		airj:dataDependency pr:Event1, pr:extractInputGraph.
Line 296:		Line 296:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event2];
	airj:flowDependency pr:Event2;		airj:flowDependency pr:Event2;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	air:description ":s2 satisfies the first set of checks";		air:description ":s2 satisfies the first set of checks";
	airj:dataDependency pr:Event1, pr:extractInputGraph.		airj:dataDependency pr:Event1, pr:extractInputGraph.
Line 306:		Line 306:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_1];
	airj:flowDependency pr:Event3_1;		airj:flowDependency pr:Event3_1;
-	airj:~~hasMatchedGraph true~~;	+	airj:branch air:then;
	airj:dataDependency pr:extractInputGraph.		airj:dataDependency pr:extractInputGraph.

Line 319:		Line 319:
	airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];		airj:inputVariableMappingList [ airj:outputVariableMappingListOf pr:Event3_2];
	airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;		airj:flowDependency pr:Event3_2, pr:ClosingTheWorld1;
-	airj:~~hasMatchedGraph false~~;	+	airj:branch air:else;
	airj:dataDependency pr:ClosingTheWorld1.		airj:dataDependency pr:ClosingTheWorld1.
	</pre>		</pre>