[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (SAF-14) Syndrome/Protocol generictemplate (with substitutable parameters)
[ http://tools.oasis-open.org/issues/browse/SAF-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeffrey Vaught updated SAF-14:
------------------------------
After further discussion, the proposal might muddy the spec, as a token in the xquery would mean XQUERY alone isn't sufficient. Perhaps this becomes a non-normative best practice.
Sending out a discussion thread.
> Syndrome/Protocol generic template (with substitutable parameters)
> ------------------------------------------------------------------
>
> Key: SAF-14
> URL: http://tools.oasis-open.org/issues/browse/SAF-14
> Project: OASIS Symptoms Automation Framework (SAF) TC
> Issue Type: Task
> Reporter: Jeffrey Vaught
> Assignee: Jeffrey Vaught
>
> Syndromes signature & Protocol directives could be generic in nature, containing substitutable parameters.
> For example, signature could be (in English, not xpath/xquery): if blah occurs {0} times within {1} minutes.
> The Syndrome/Protocol would be effectively instantiated by substituting meaningful values, such as "if blah occurs 3 times within 5 minutes.
> This is critical from the collaboration perspective, ie: Cloud provider could publish generic Syndromes, while consumers could instantiate those Syndromes per above.
> Notes
> Might require no changes to the spec. Interfaces might better support this?
--
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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]