[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency-msg] Minutes for Meeting 07-11-06
Yup At 10:49 AM -0400 7/25/06, Lee Tincher wrote: >I'm in agreement. It was not my intention to attempt to "speed things up" >at all. I know that good standards take time and we need to be careful to >produce the best product we can. As usual you hit the nail on the head. > >Thanks, >Lee > >-----Original Message----- >From: Rex Brooks [mailto:rexb@starbourne.com] >Sent: Tuesday, July 25, 2006 10:04 AM >To: Lee Tincher; 'Tim Grapes'; 'Renato Iannella'; 'Emergency_Mgt_Msg_SC' >Subject: RE: [emergency-msg] Minutes for Meeting 07-11-06 > >I hear and understand, but would like to add that we are, after all, >only driving the first full draft of v1.0. Please excuse me if I >mangle a few metaphors here, but I sense a wave or some kind of tide >moving around us. Perhaps I'm just involved in too many of these >efforts at one time. > >However, because I am also involved on other TCs, I am currently part >of the crowd drowning in details for WSRP v2.0, which is far, far >less functional than originally planned, more than 3x as complex as >originally thought, and now, almost a year overdue getting into >public review, and just now getting to the nuts and bolts of the >first wave of public review issues, and finding it all a bit >daunting, more than four years into the process. > >I can testify that if we don't move in a timely way, the world will >spin out things like AJAX that make the bleeding edge work we thought >we were doing almost obsolete before it gets out the door. So, after >having forged the management system for the major transportation >systems (roadways, railways, airways, waterways), in EDXL_DE, we are >approximately now at the level of working out the traffic flows for >traffic categories, in this case resources, and we have identified >the major ones. I realize these are clumsy and inaccurate metaphors, >but I hope you get the idea. Basically, I'm in agreement with Lee >that we need to focus on getting these identified resource message >categories nailed down before the peripheral networks get out ahead >of us, eh? > >What I am learning is that the practitioners are required to push >ahead, and will do whatever works that they can glue together, but if >they have something to work with, even with some flaws and hiccups, >they will help us smooth it out provided we give them that something >to work with. Otherwise, they will give us an unending job of >untangling the messy mashups that convergence is forcing. We have to >keep swimming until we can get to the next hunk of ground high enough >to catch a glimpse of the changing landscape. Heckuva way to run a >railroad. > >Cheers, >Rex > >At 8:15 AM -0400 7/25/06, Lee Tincher wrote: >>Also we may want to keep in mind the requirement that we are focused on EOC >>to EOC level (and above) and not at the local incident. We may wish to >>expand at a future date, but the practitioners were very clear about that. >> >>Thanks, >>Lee >> >>-----Original Message----- >>From: Tim Grapes [mailto:tgrapes@evotecinc.com] >>Sent: Tuesday, July 25, 2006 8:10 AM >>To: 'Renato Iannella'; 'Emergency_Mgt_Msg_SC' >>Subject: RE: [emergency-msg] Minutes for Meeting 07-11-06 >> >>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 >> >> >> >>--------------------------------------------------------------------- >>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 >> >> >>--------------------------------------------------------------------- >>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 > > >-- >Rex Brooks >President, CEO >Starbourne Communications Design >GeoAddress: 1361-A Addison >Berkeley, CA 94702 >Tel: 510-849-2309 > >--------------------------------------------------------------------- >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 > > >--------------------------------------------------------------------- >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 -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]