[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [emergency-comment] NIMS STEP comment - TractorFax
Thanks Jerome,
This is important information for us to have, so I am copying the OASIS EM TC list with this reply. While I can only speak for myself, I think that the gap analysis I assume you have conducted to fill "shortfalls" in EDXL coverage of incident management systems could be perhaps one of the most important tools we can support. Since NIMS STEP has been absorbed by P-TAC Center, I will add this to an ongoing ticket I have open with P-TAC concerning a FEMA Grant-supported project that uses Incident Resource Inventory System (IRIS). What I am working on is third-party translation ontology that can provide EDXL-compatible terms/datatypes for Resources in the FEMA Resource Typing system which the firestations we are supporting need to coordinate and align with their own industry-supplied inventories. It is no easy task getting interoperability at this level. I understand the problem only too well. Here in California the company-product attempting to build a monopoly-based interoperability by giving away the beginners-level version of their software product is making substantial inroads that I consider a long-term recipe for disaster, but I won't go into details, in order to avoid arguments and entanglements that would only make the situation even less solvable. However, please keep beating the drums. In the long term, the only way we can deliver interoperability to the Emergency Management field is through is to provide low-to-no cost software systems at a basic level that products such as you provide can build upon, and that is the approach I am taking while working to improve the overall situation with standards. Speaking of Standards, we are looking for vendors who are not necessarily OASIS members who can vouch for using the EDXM-SitRep v1.0 specification so we can move forward to an OASIS-wide vote for Standard status. If you could help in that effort, we would be grateful. However, in the meantime, you have brought forward a set of issues that needs to be addressed and I thank you again for that. I wish I could be more hopeful, but I do think that if we can provide those low-cost alternative for local jurisidctions, they will work with us to build more advanced systems which implement genuine interoperability for the long term. Thanks, Rex Brooks On 10/16/2012 7:20 AM, Jerome Hamilton wrote:
-- Rex Brooks Starbourne Communications Design Email: rexb@starbourne.com GeoAddress: 1361 Addison St. Apt. A Berkeley, CA 94702 Phone: 510-898-0670 |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]