OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

saf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] Commented: (SAF-11) Symptom Grouping/Linking



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

Jeffrey Vaught commented on SAF-11:
-----------------------------------

CaseID not included, because Symptoms to be immutable (and adding a caseID from a case manager would require the symptom to be mutable).  Other groupings are now in the proposed Spec.

> Symptom Grouping/Linking
> ------------------------
>
>                 Key: SAF-11
>                 URL: http://tools.oasis-open.org/issues/browse/SAF-11
>             Project: OASIS Symptoms Automation Framework (SAF) TC
>          Issue Type: Task
>            Reporter: Jeffrey Vaught
>            Assignee: Alvin Black
>            Priority: Critical
>
> In the pre standards phase of this work, it was suggested that some form of "Group Id" or "Linking Tag" be included at the top level of the Symptom to indicate that this Symptom was in someway related to other Symptoms and that this relationship was identifiable by the creator of the Symptom.
> Notes
> •	Jeff: Could capture in the signature, but emitter is uniquely positioned to provide.
> •	Alvin: On/Off (state).  Alarmid.
> •	Vivian: Prototypes show this is important for performance.

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