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: RE: [saf] Model and Interfaces document


Dave,

 

No, no worries :-) It's just about whether they should be separate entities in the model or not (at least that's what I understand :-S) Currently they're not even roles in the spec are they? They are simply attributes in the Symptoms and that's it. So the question is: do we want to put them in a more central role (if there is justification) or just leave them as they are?

 

Cheers,

 

Stavros

 

 

From: David Snelling [mailto:David.Snelling@UK.Fujitsu.com]
Sent: 22 June 2010 12:50
To: Stavros Isaiadis
Cc: saf@lists.oasis-open.org
Subject: Re: [saf] Model and Interfaces document

 

Folks,

 

Just want to check on one thing here.

 

Surely you are not suggesting removing the reporter and Subject from the Symptom itself are you? I believe it is an essential component on the Symptom model.

 

If however if you are just talking about removing it from the list of roles, I less worried. Just seeking clarification.

 

Thanks.

 

On 22 Jun 2010, at 09:53, Stavros.Isaiadis@uk.fujitsu.com wrote:



Hi all,

 

Jeff you were quicker than me :-) I had already modified the model and interfaces document, but your comments gave me some food for thought.

 

is this a rework of the existing section(s) in the main Spec WD?  Do we plan to incorporate this into the main Spec WD?

 

I think we decided to add any more concrete interface discussion as an appendix to the spec, and keep the operations and interfaces discussion in the spec a bit abstract. I will see into putting everything together and modifying the spec this week.

 

What do the different colors represent?

 

The colored diagram I provided is a bit outdated and comes from an ontology editor, so not the best visualization for our purposes :-)

 

Subject/Reporter convolutes the Spec (in my opinion) w/o adding significant benefit.  I could see moving Symptom.confidence to Reporter, and possibly adding other attributes that could be leveraged by the Diagnostician – but would prefer to leave that as implementation specific.

 

Perhaps subject and reporter do not need to be included in such model, as you say because we haven't figured out why would anyone need them there (yet). To be discussed.

 

Also, the whole roles section will probably be removed if we merge with the main spec. I will send out another email with some proposed changes to the spec (to keep thing clean for the list).

 

The REST section is being put to test constantly here at FLE :-) So it will change continuously! More to come...

 

Cheers,

 

Stavros

 

--

Fujitsu Laboratories of Europe

______________________________________________________________________
                                        
 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.

 

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.


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