[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [saf] Incident Id Proposal
IncidentID: Two thumbs up. Ability to pass an IncidentID to a prescription: Three thumbs up. UberIncidentID: Two thumbs up on the notion that we need to somehow support a complex linking of related symptoms... I think we might have to get more sophisticated though. BTW, not to get in to politics, Jeff and Paul, but pollution is never caused by poor environmental oversight. It might be able to be prevented (or more likely converted in to a revenue source for governments) by proper environment oversight, but not caused by poor oversight.... :-) I also think we might need something for "Alarms" or monitored values (such as a server temperature). Perhaps we could use CorrelationID instead of IncidentID, but not entirely sure that feels comfortable to me... -Alvin -----Original Message----- From: Vaught, Jeffrey A [mailto:Jeffrey.Vaught@ca.com] Sent: Friday, December 10, 2010 11:28 AM To: David Snelling; saf@lists.oasis-open.org Subject: RE: [saf] Incident Id Proposal Thinking aloud: With Dave's proposed IncidentId one could ensure that Symptoms "Slight Headache" and "Severe Headache" are an escalation of the same Headache... as opposed to distinct Headaches (perhaps weeks apart). The Diagnostician could even use this information to close the incident (clear the symptom store, etc) upon seeing Symptom "Headache Gone". I don't think we've discussed the mechanics of this, and perhaps it is an implementation detail. Paul discussed a higher level context such as when the Headaches are caused by Pollution which is caused by poor Environmental Oversight. It's a tiering of Incidents something like this... All of these Incidents are related to poor Environmental Oversight: IncidentID=A1 -- symptom1="increased pollution" IncidentID=A2 -- symptom1="improper environmental spending" All of these Incidents are related to Pollution: IncidentID=B1 -- symptom1="slight headache" symptom2="severe headache" IncidentID=B2 -- symptom1="dirty windows" IncidentID=B3 -- symptom1="bad tasting drinking water" In Paul's scenario, some kind of UberIncidentID would link together the Pollution symptoms, and a UberUberIncidentID would link together the Environmental Oversight symptoms. It seems unlikely that a simple symptom emitter would be able to provide these Uber*IncidentIDs. So maybe these kinds of relationships are defined elsewhere, and leveraged by the Diagnostian. -----Original Message----- From: David Snelling [mailto:david.snelling@uk.fujitsu.com] Sent: Friday, December 10, 2010 8:48 AM To: saf@lists.oasis-open.org Subject: [saf] Incident Id Proposal Folks, For my AI from today's call: Proposal: Include a new top level, optional element in Symptom. Field: IncidentId Type: anyURI Properties: Optional, Unique (to the incident in question), Immutable Description: This optional identifier may be included in a Symptom to assist consumers in associating this symptom with others. Care should be taken to establish basic mechanisms to ensure that it is unique to an incident. Schema: <IncidentID>xsd:anyURI</IncidentID> Notes: - We could use a more generic term like CoordinationID. - We might consider saying how this might be passed (in a standard way) to Practitioners in the prescription. Just a thought. Take care: Dr. David Snelling < David . Snelling . UK . Fujitsu . com > Fujitsu Laboratories of Europe Limited Hayes Park Central Hayes End Road Hayes, Middlesex UB4 8FE Reg. No. 4153469 +44-7590-293439 (Mobile) ______________________________________________________________________ Fujitsu Laboratories of Europe Limited Hayes Park Central, Hayes End Road, Hayes, Middlesex, UB4 8FE Registered No. 4153469 This e-mail and any attachments are for the sole use of addressee(s) and may contain information which is privileged and confidential. Unauthorised use or copying for disclosure is strictly prohibited. The fact that this e-mail has been scanned by Trendmicro Interscan does not guarantee that it has not been intercepted or amended nor that it is virus-free. --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php --------------------------------------------------------------------- To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]