Changes between Version 9 and Version 10 of BluePrint/SAFIRE

Timestamp:

03/28/16 06:52:59 (9 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

BluePrint/SAFIRE

@@ -9 +9 @@
 
 ==== Missing features: ==== 
-1. Common Operating Picture with [wiki:BluePrint/CrisisMap Crisis Mapping]
-1. manage [wiki:BluePrint/Event event type] specific templates and messages
+1. Common Operating Picture with [wiki:BluePrint/CrisisMap Crisis Mapping] (who, what, when, and where)
+1. manage [wiki:BluePrint/Event event type] specific work flows pre-populated message templates and messages
 1. input and output [http://hxlstandard.org/standard/1_0final/dictionary/#crises HXL #Event], [https://www.oasis-open.org/news/announcements/emergency-data-exchange-language-situation-reporting-edxl-sitrep-v1-0-committee-s SITREP] and [http://docs.oasis-open.org/emergency/edxl-rm/v1.0/errata/EDXL-RM-v1.0-OS-errata-os.html RM] feeds '''[2]''' to serve as an aggregator and a publisher-subscriber
-1. approve or reject dispatch, incident reports, situational-reports, request-resources
-1. delivery options: HTTP, RSS/Atom, SMS, Email, FTP (dynamic labels)
-1. built on the Emergency Data Exchange Language (EDXL) SITREP and RM standards
-1. subscription management (who, what, when, and where) serve as a subhub
-1. Exchange data with other EDXL compliant systems
-1. support multiple language SITREP/RM message publication
+1. Desktop and Mobile applications to integrate and to server as a publisher and a subscriber
+1. Approve or Reject asset management, incident reports, situational-reporting, and resource messaging
+1. Support multiple language message delivery options: HTTP, RSS/Atom, SMS, Email, FTP
 1. digitally sign the messages
-1. Mobile application to server as a publisher and a subscriber
 1. Pictographs for reporting incidents and situational=reports
 1. Incident specific SOP check list