OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

emergency message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword tocontentObject



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.

  • Yellow is only important for Time to Live and Reply messaging.
  • Orange means being applied at the edge to restrict delivery to authorized recipients.
  • Pink means being used to assemble Collections of Interest (COI) for core message routing fabric.
    • This is a work in progress and we have significant findings on valueListUrn creation and usage.
  • Light Blue means a special case for external distribution systems (e.g. e-mail) or special Alerting Framework Web services routing (design in progress).
  • Dark Blue means actual Payload (may need to pick a different color).
  • The Green is still being evaluated for functionality (e.g. contentDescription is being used be Alerting Framework for GIS hover display of in route EDXL DE contentObjects).


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]
Sent: Friday, January 27, 2006 10:37 AM
To: emergency@lists.oasis-open.org
Subject: [emergency] FW: Suggestion: Add incidentKeyword to contentObject


Forwarding message from Mark Carlson…


Patti Iles Aymond, PhD
Senior Scientist
Bioterrorism Preparedness & Response

Innovative Emergency Management, Inc.

Managing Risk in a Complex World

8555 United Plaza Blvd.   Suite 100
Baton Rouge, LA 70809
(225) 952-8228 (phone)
(225) 952-8122 (fax)

From: Mark Carlson - Conneva, Inc. [mailto:conneva@gmail.com]
Sent: Thursday, January 26, 2006 11:37 AM
To: Aymond, Patti
Subject: Fwd: Suggestion: Add incidentKeyword to contentObject




I tried sending this message to the group, but the list server rejected my message.  Could you forward, please?



=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- =-=-=-=-=-=-=-=-


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.




Mark Carlson



Pub_Sub for TC.ppt

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]