[OASIS Issue Tracker] Commented: (SAF-6) SignatureComposition/Decomposition and Partial matches

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/SAF-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=24871#action_24871 ] 

Jeffrey Vaught commented on SAF-6:
----------------------------------

Agreement on #1 & #3 proposals above, but discussion still needed on #2 (Composition of Syndromes).
The restriction is not XQuery, as certainly possible in XQuery to reference documents other than the Symptoms Store.  For referencing a Syndrome within a signature, the restriction is on the visibility of instantiated Syndromes within the Diagnostician.  

For example, let's assume Syndrome A should be triggered when Syndrome B is triggered, followed by a new Symptom X.
The XQuery signature could query the symptom store for Symptom X, but it cannot query the Diagnostician (Syndrome Activation Store??) to determine if Syndrome B is triggered, as it is not part of the spec.

To accommodate this capability, we would need to specify that the Diagnostician track/expose which Syndromes are triggered, and possibly which Syndromes are activated.  Activated means "at least one criteria of the Syndrome is matched", whereas Triggered means "all criteria for the Syndrome are matched".


> Signature Composition/Decomposition and Partial matches
> -------------------------------------------------------
>
>                 Key: SAF-6
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-6
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Jeffrey Vaught
>            Priority: Critical
>
> As termed in the Spec (Future Development): While the Signature in a Syndrome is specified as a single XPath expression, it is acknowledged by the authors that processing of this expression may be performed incrementally to reflect the dynamic nature of Symptom creation. It may be necessary to decompose, explicitly in the specification, this XPath expression into a conjunction of multiple, simpler expressions.  
> .
> Original discussion:
> Consider Syndrome #1 that has a signature of A & B & C within 10 minutes.  Symptoms A & B are generated.  Should the diagnostician detect the partial match and "recommend" Syndrome #1 has a possible diagnosis?   If the answer is "yes", we may need to add additional elements to our signature definition to accommodate such a scenario.  IMHO (Jeff and seconded by Dave) - better to factor this out to different Syndromes, ie: Syndrome #1 is A&B&C, but Syndrome #2 is A&B.  Now, if Symptoms A&B are generated, then Syndrome #2 is diagnosed and its associated prescription "could" tease Symptom C into existence - ultimately causing Syndrome #1 to be diagnosed.
> Additional discussion from 11/5/2009: 
> Might need sets/unions of xpath2 expressions in order to be fully decomposable (such as by authoring tools).
> For example, consider case where A is followed by B is followed by C within a 5 minute time window.  Below might be XQuery, not XPath, but for sake of argument should be Ok.
> (: ABDI time sequence query :)
> let $a := //SYMPTOM[CONTENT/MSG='INFO:bobcat_command, command'] intersect //SYMPTOM[CONTENT/EXTRA='APPSRVMN']
> let $b := //SYMPTOM[CONTENT/MSG='INFO:bobcat_command, waiting command completed'] intersect //SYMPTOM[CONTENT/EXTRA='APPSRVMN']
> let $c := //SYMPTOM[CONTENT/MSG='INFO:bobcat_command, command ended with exit code: 1'] intersect //SYMPTOM[CONTENT/EXTRA='APPSRVMN']
> return 	if (boolean($a) and boolean($b) and boolean($c) and
> 	($a/TIME < $b/TIME) and ($b/TIME < $c/TIME) and
> 	($c/TIME - $a/TIME < 300))
> 	then concat($a,$b,$c) 	else ()
> While it is possible to compose such an expression, it may not be possible to decompose that expression into its constituents (A, B, C, causal relation between them, and 5 minute constraint).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira