[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: First call in 2011
Hi all, First of all, a very happy new year to
everyone, and I hope you all enjoyed your holiday breaks! I also hope we will
meet in person again and release a mature spec in 2011! As for our first call this year, it seems
that we may be a bit low in numbers for Monday, so be prepared for a "catching-up"
like discussion (or even cancelation depending on the numbers). As a reminder, last time we were discussing
about related symptoms, incident id, and case reference. We could try to
finalize proposals for this one, and warming up for related issues. I
personally like this triple as each one seems to handle different needs: -
RelatedSymptoms provide means
to refer to other symptoms using metadata to denote the kind of relationship,
e.g. supersedes, causality, repetition etc. This would be set by the emitter
probably (?) -
IncidentID, is a rudimentary
form of relating symptoms based on the emitter's understanding, e.g. emitting
symptoms that are all related to a server down incident. -
CaseID, is a more comprehensive
grouping of symptoms based on the diagnosticians' (and other experts') more
complete understanding and holistic picture. As such, a case is not the same as
an incident, and it can be used to link to external case management systems. I am still lacking a symptom which could
potentially participate in multiple incidents... Any thoughts? Thanks and hope to speak to you soon, Stavros
|
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]