RE: Today's call

Hi all,

Jacques comments and his analysis of some of the unique virtues of SAF make sense to me. Apologies regarding my continued absence, but the timing of meetings and my current bandwidth are making this near-impossible.

Thanks,

Paul

Paul Lipton

CA Technologies

VP, Industry Standards and Open Source

Member, CA Council for Technical Excellence

Office Phone: +1 609 583-9718

Mobile: +1 267 987-6887

Email: paul.lipton@ca.com

THIS MESSAGE MAY CONTAIN CONFIDENTIAL, PRIVILEGED OR OTHER LEGALLY PROTECTED INFORMATION. IT IS INTENDED FOR THE ADDRESSEE ONLY. IF YOU ARE NOT THE ADDRESSEE (OR SOMEONE THE ADDRESSEE AUTHORIZED TO RECEIVE THIS MESSAGE), YOU ARE PROHIBITED FROM COPYING, DISTRIBUTING OR OTHERWISE USING IT. PLEASE NOTIFY THE SENDER AND RETURN IT AT OUR COST. THANK YOU.

From: saf@lists.oasis-open.org [mailto:saf@lists.oasis-open.org] On Behalf Of Isaiadis, Stavros
Sent: Monday, February 06, 2012 6:53 AM
To: saf@lists.oasis-open.org
Subject: [saf] Today's call

Hi all,

I hope I can make it for the call today! The agenda will cover the Cloud profile again, hopefully with new comments arriving from SAF members; changes to the actual examples from me and Jeff; and a discussion around Jacques comment (attached below for your reference)

Feel free to suggest agenda items and/or start discussion about any of the above before the call.

Thanks and regards,

Stavros

Jacques’ comment (emphasis mine):

SAF is at my knowledge the only model that decouples (1) events (symptoms), (2) meaning at a larger level (syndromes) and (3) remedial process (Protocol) itself evaluated on the basis of new Symptoms. It closes the observation+analysis+remedial loop although not in a hardwired, rigid way: the model leaves the association between “syndromes” and “protocols” as something that can be evaluated, revised and improved.

Such a feature is overwhelmingly ignored in other action-focused knowledge models such as rule-based (e.g. ECA rules) or AI-inspired decision systems, where the association analysis/action is often considered as a “given”. SAF appears to be a pragmatic approach to model the troubleshooting process of any kind, and to handle the evolution of this process over time.

One technical comments:

The definition of Signature could have been more generic, and worded so that it is not tied to a particular technology (XQuery). Couldn’t just XPath be used as well? (or XSLT, if the generation of a document is important?)
Several attributes have just “labels” (enums) as values, e.g. Likelihood, Impact, Urgency in Syndrome. The spec could have made it clearer to users that the meaning of these values has to be defined by end-users in their particular domain and must be part of a SAF “profile” for this domain.
In Symptoms, the “RelatedSymptoms” field is immutable, assuming that this correlation set is known at the time the Symptom is created. This is a rather bold assumption… I personally would only use RelatedSymptoms for the most obvious dependencies (repetitions…), as “causality” and “supersedes” often imply some analysis that I am not sure can be done at Symptom creation time. If some “smart” Symptom dependencies have to be recorded, couldn’t some (basic) Syndromes do the job instead?

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.

saf message