[OASIS Issue Tracker] Commented: (SAF-8) Associated Protocols mayhave dependencies between them

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

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

Jeffrey Vaught commented on SAF-8:
----------------------------------

After more discussion... three options:
1. Crisp the Spec to make the default "Any" clearer.
2. Support complex workflows
3. Support simple grouping, ie:
Do one of A or B or do both C and D:
<AssociatedProtocols>
	<Protocol uri="A"/>
	<Protocol uri="B"/>
	<ProtocolGroup>
		<Protocol uri="C"/>
		<Protocol uri="D"/>
	</ProtocolGroup >
</AssociatedProtocols>

Consensus amongst Fujitsu was #3.  CA had no strong objections.  Next step is to write up #3 in the Spec (at which point we will resolve this issue).

> Associated Protocols may have dependencies between them
> -------------------------------------------------------
>
>                 Key: SAF-8
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-8
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Alvin Black
>
> The Associated Protocols in a Syndrome may have dependencies between them, such as "all must be applied", "any one may be applied", "must be applied in order", or possibly organized into sub-groups.

-- 
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