RE: [emergency-msg] Minutes for Meeting 07-11-06

["Tim Grapes" <tgrapes@evotecinc.com>]

I tend to agree with Renato about the optionality and conditional rules.  We
also clearly have to understand message dependencies, but we do have a
couple of artifacts already developed to assist with that analysis (in fact,
message dependencies in some cases drive conditional rules).  We do need to
be careful where we draw the line.  I feel we need to address the obvious /
clear dependencies, without diving down into business process /
implementation.  Resource messages may be implemented in a number of ways
depending upon the type of system and the business need.

Thanks,   

Tim 
 

-----Original Message-----
From: Renato Iannella [mailto:renato@nicta.com.au] 
Sent: Tuesday, July 25, 2006 1:33 AM
To: Emergency_Mgt_Msg_SC
Subject: Re: [emergency-msg] Minutes for Meeting 07-11-06



On 25 Jul 2006, at 00:22, Rex Brooks wrote:

> That will be the first time that we could bring it to the TC for a  
> vote, if we get that far. While that isn't quite what our very  
> aggressive schedule aimed for, we pretty much knew a schedule THAT  
> aggressive was a bit unlikely to succeed. However, we will still be  
> likely to have it ready mid-August. We might even be able to get it  
> to OASIS in time for a mid-August start of a 60-day public comment  
> review period. That's a bit dicey, but we should certainly have it  
> ready by start of September.

There is a lot more complexity in the RM than we think.
The current "spreadsheet" approach is only part of the solution.
The dependencies between messages are also critical, as well as the
articulation of the "conditional" rules we discussed last week.

I don't want to set expectations that we would be finished soon ;-)


Cheers...  Renato Iannella
National ICT Australia (NICTA)



--------------------------------------------------------------------------
This email and any attachments may be confidential. They may contain legally
privileged information or copyright material. You should not read, copy,
use or disclose them without authorisation. If you are not an intended
recipient, please contact us at once by return email and then delete both
messages. We do not accept liability in connection with computer virus,
data corruption, delay, interruption, unauthorised access or unauthorised
amendment. This notice should not be removed.

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  You may a link to this group and all your TCs in OASIS
at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php 

-- 
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.4/396 - Release Date: 7/24/2006
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.10.4/396 - Release Date: 7/24/2006