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: More on incidents

Hi all (again),
Some more discussions on incidents from archives:
Ability to pass an IncidentID to a prescription: Three thumbs up.
For this one we don’t really need to do anything, as the spec provides this capability anyway (i.e. Syndrome signature may return a collection of symptoms, and then the Protocol directive can extract any kind of arguments to pass down to the prescription).
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.
Alvin: 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.
Question: is the above not covered if we decide to support multiple incident IDs? I.e. a symptom would have three incident IDs: the direct incident one, the UberIncident and the UberUberIncident one :-)

This message w/attachments (message) is intended solely for the use of the intended recipient(s) and may contain information that is privileged, confidential or proprietary. If you are not an intended recipient, please notify the sender, and then please delete and destroy all copies and attachments, and be advised that any review or dissemination of, or the taking of any action in reliance on, the information contained in or attached to this message is prohibited.
Unless specifically indicated, this message is not an offer to sell or a solicitation of any investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Sender. Subject to applicable law, Sender may intercept, monitor, review and retain e-communications (EC) traveling through its networks/systems and may produce any such EC to regulators, law enforcement, in litigation and as required by law.
The laws of the country of each sender/recipient may impact the handling of EC, and EC may be archived, supervised and produced in countries other than the country in which you are located. This message cannot be guaranteed to be secure or free of errors or viruses.

References to "Sender" are references to any subsidiary of Bank of America Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a Condition to Any Banking Service or Activity * Are Not Insured by Any Federal Government Agency. Attachments that are part of this EC may have additional important disclosures and disclaimers, which you should read. This message is subject to terms available at the following link:
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you consent to the foregoing.

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