[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword tocontentObject
Patti
Attached are slides from the briefing on application of EDXL Distribution to the National Alerting Framework. Since we have an evolving Publication/Subscription infrastructure, I need to work with Tom Merkle how to explain the theory/best practices and not over explain implementation details.
In the slides you will see color coding of EDXL-DE elements and how they are proposed to be used by Alerting Framework.
As you can see, the green IncidentID and incidentDescription have not functionality in either explicit of Pub/Sub distribution. In fact, if we could predict incidents in advance and add them to a valueListURN/value pair for determining distribution during incidents, the TC should go to Las Vegas and win enough money to retire.
IncidentID should be assigned by appropriate authority during actual Incidents and used in Payloads distributed by the EDXL-DE. I believe this was Art’s comment when we added it.
David E. Ellis Information Management Architect (505) 844-6697
From: Aymond, Patti
[mailto:Patti.Aymond@iem.com]
Forwarding message from Mark Carlson…
Patti Iles Aymond, PhD Innovative Emergency Management, Inc. Managing Risk in a Complex World 8555 United Plaza
Blvd. Suite 100 From: Mark Carlson -
Conneva, Inc. [mailto:conneva@gmail.com]
Patti,
I tried sending this message to the group, but the list server rejected my message. Could you forward, please?
Mark =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-
I'm quite sure everyone is hoping for no more changes to the EDXL-DE schema at this point. However, as I have begun to work with the schema in our resourcing prototype, I have observed that while there are incidentID and incidentDescription elements in the contentObject, there is no provision to classify the incident using a valueListURN/value pair.
This would seem to be necessary for consistency. In other words, if it is a good idea to have an incidentDescription and incidentID in the contentObject, there should also be an optional incidentKeyword to classify the incident.
Regards,
Mark Carlson
IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE: |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]