[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Jon Skeels response
Hi everyone,
I have had a couple more communications with Jon over the holidays. Below is his latest response, which I have not yet responded to. Please review the string.
This is more of an OASIS EM-TC issue to the extent that we may choose to engage. No one can make ROSS adopt and implement EDXL standards. But, we may choose to schedule a meeting between select OASIS EM-TC members and his team to attempt some education and help to bridge the gap.
Elysa, I don't know whether there is time on tomorrows wall to touch on this. Otherwise we may want to schedule a brief call to discuss
Thanks,
Tim
-----Original Message-----
From: Jon Skeels [mailto:jskeels@fs.fed.us]
Sent: Sunday, January 07, 2007 9:43 PM
To: tgrapes@evotecinc.com
Cc: Tim Grapes
Subject: Re: Let me know a time this week
Tim: Sorry for not getting back with you sooner. I have been off for the
holidays.
The situation with us is that we fully intended to support the Distribution
Element. In the end, we had to defer this work as it would take more
effort then the funding and time then we have available. Another issue we
have been faced with is that we are doing 2 way communication with other
systems, and they (the other systems are not developed using the EDXL
standard. We do intend to eventually incorporate the distribution element
into our services, but funding may be a factor.
In regards to the Resource Messaging Specification, we are so far along
with our work with the State of California and other groups, that meeting
that standard will likely be tough. We will soon be done with the services
that we will be using with the State of California CAD Systems. I have
listed a few of the services we are developing below. Once we are done, we
will provide you with more details on them.
createIncident (inbound to ROSS)
UpdateIncidentDetails (inbound to ROSS)
createResourceRequest (inbound to ROSS)
fillResourceRequest (inbound to ROSS)
placeResourceRequest (inbound to ROSS)
getResourceRequest (inbound to ROSS)
utfResourceRequest (inbound to ROSS)
notifyResourceRequest (inbound to ROSS)
cancelResourceRequest (inbound to ROSS)
createIncidentRequestandPlace (inbound to ROSS)
createRequestandPlace (inbound to ROSS)
createIncidentRequestandFill (inbound to ROSS)
createRequestandFill (inbound to ROSS)
createIncidentandRequest (inbound to ROSS)
getIncidentsRequestsByStatus (inbound to ROSS)
getIncidentAndRequests (inbound to ROSS)
releaseResource (inbound to ROSS)
updateResourceTravel (inbound to ROSS)
updateResourceAvailability (inbound to ROSS)
buildMasterRoster (inbound to ROSS)
createResourceRequestNotification (outbound from ROSS)
placeResourceRequestNotification (outbound from ROSS)
ResourceRequestOperationNotification (outbound from ROSS)
UpdateResourceRequestDetailsNotification (outbound from ROSS)
UpdateResourceAssignmentNotification (outbound from ROSS)
UpdateResourceKeyNotification (outbound from ROSS)
Jon
*************************************************************************
Jon C. Skeels, PMP
Senior Project Manager
WO-Fire & Aviation Staff
Information Systems Project Office
USDA Forest Service
740 Simms St
Golden, CO 80401
jskeels@fs.fed.us
Phone: 303-236-0630
Fax: 303-236-5221
Cell: 303-902-1897
**************************************************************************
tgrapes@evotecinc
.com
To
12/27/2006 02:41 "Jon Skeels" <jskeels@fs.fed.us>
PM cc
"Tim Grapes"
<tgrapes@evotecinc.com>
Subject
Re: Let me know a time this week
Jon,
It would be helpful to know what version of each standard you are
referring to. Some are still undergoing improvements through the OASIS
process and have not yet been formally published.
- The Common Alerting Protocol (CAP 1.1) is a publicly available standard
- The EDXL Distribution Element (DE 1.0 is also a publicly available
standard.
- The EDXL Hospital Availability Exchange (HAVE) was published for 60-day
public comment. You received a notice of that, and it would be very
helpful if you could submit any comments you have through the OASIS
process
- EDXL Resource Messaging is undergoing heavy vetting and enhancement in
the OASIS TC. It is expected to be published in mid-January for 60-day
public comment. Again, your formal comments at that time would be
extremely valuable.
Thanks - I am on vacation now and back in action on Tuesday. Have a Happy
New Year.
Tim
> Tim: Sorry not to have gotten back with you sooner. In regards to my
> concerns about EDXL, I have transmitted the standards to Lockheed for
> review and comparison with what we have actually done. I have asked them
> to give me an assessment as to if the EDXL Standard works or doesn't. I
> have ask for the reasons why it won't work and if it kind of works, then
> to
> provide suggestions for improvement. When I hear back from them which
> will
> be a few weeks, I will advise.
>
> Jon
>
> *************************************************************************
> Jon C. Skeels, PMP
> Senior Project Manager
> WO-Fire & Aviation Staff
> Information Systems Project Office
> USDA Forest Service
> 740 Simms St
> Golden, CO 80401
>
> jskeels@fs.fed.us
> Phone: 303-236-0630
> Fax: 303-236-5221
> Cell: 303-902-1897
>
**************************************************************************
>
>
>
>
>
> "Tim Grapes"
> <tgrapes@evotecin
> c.com>
To
> "'Jon Skeels'" <jskeels@fs.fed.us>
> 12/04/2006 05:57
cc
> AM
>
Subject
> Let me know a time this week
>
>
>
>
>
>
>
>
>
>
> Hey John,
> Sorry I missed your call on Friday. I appreciate you following up with
> details, but it would be helpful if we could spend a few minutes this
week
> on the phone to better understand the implementation issue. Give me any
> time that’s good for you and I’ll send a conference line.
>
> Actually, this is a perfect time to hear what you’ve found – input
> from the
> field in invaluable. The OASIS committee is meeting this week Tues
> through
> Thursday to work on the Resource Messaging specification together.
>
> We’ll work around any time that’s good for you.
> Thanks,
> Tim Grapes
> Evolution Technologies, Inc.
> Department of Homeland Security
> Science and Technology, C4ISR
> Office for Interoperability and Compatibility
> Disaster Management egov Initiative
> Office: (703) 654-6075
> Mobile: (703) 304-4829
> tgrapes@evotecinc.com
>
>
>
>
>
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.1.409 / Virus Database: 268.15.6/566 - Release Date: 12/3/2006
>
>
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.7/618 - Release Date: 1/6/2007 7:47 PM
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.432 / Virus Database: 268.16.7/619 - Release Date: 1/7/2007 6:29 PM
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]