Changes between Version 27 and Version 28 of Event/2011/GCI

Timestamp:

11/15/11 15:29:06 (13 years ago)

Author:

Nuwan Waidyanatha

Comment:

--

Event/2011/GCI

@@ -12 +12 @@
  * Build library(ies) '''Emergency Data Exchange Language Distribution Element'''
 Difficulty : '''Hard''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
-'''Specific: '''EDXL-DE is the final wrapper (envelope) of all EDXL data parcels. We may be delivering a EDXL Resource Management (RM) information and Situational Reporting (SITREP) information to the managers of several emergency organizations. The DE will contain who, when, and where those RM and SITREP data parcels would be delivered. Every EDXL message (data parcel) must carry this information. Otherwise, it cannot use available distribution methods and would need to rely on its own protocol; that's not very user friendly. [[BR]]
-'''Measurable: ''' It is purely a coding task that involves playing with XML and developing a class, possibly within the 3R**** framework. [[BR]]
-'''Attainable: ''' [[BR]]
-Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM; then add the EDXL-DE component to that. [[BR]]
-Step 2 :: Then expand on that concept with EDXL-HAVE and EDXL-SITREP to generalize the library [[BR]]
+'''Specific: '''[http://docs.oasis-open.org/emergency/edxl-de/v1.0/EDXL-DE_Spec_v1.0.pdf | EDXL-DE] is the final wrapper (envelope) of all EDXL data parcels. We may be delivering a EDXL Resource Management (RM) information and Situational Reporting (SITREP) information to the managers of several emergency organizations. The DE will contain who, when, and where those RM and SITREP data parcels would be delivered. Every EDXL message (data parcel) must carry this information. Otherwise, it cannot use available distribution methods and would need to rely on its own protocol; that's not very user friendly. [[BR]]
+'''Measurable: ''' It is purely a coding task that involves playing with XML and developing a class, possibly within the '''??? 3R**** ???''' framework. [[BR]]
+'''Attainable: ''' run through the steps [[BR]]
+Step 1 :: select one of the existing EDXL-based applications in Eden, I recommend the EDXL-RM;
+Step 2 :: discuss each of the attributes/elements; then determine how EDXL-DE would be added to EDXL-RM as a pop-up GUI. [[BR]]
+Step 3 :: create some example XML files to get a feel for the inputs and outputs
+Step 4 :: write code to add to take the inputs EDXL-RM and EDXL-DE to package the data for delivery
+Step 5 :: test the code, fix bugs, and generalize the functions
+Step 6 :: Apply to EDXL-HAVE and EDXL-SITREP to generalize the library [[BR]]
 '''Relevant: ''' Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP http://www.oasis-open.org/standards#edxl [[BR]]
-'''Time-bound: ''' [[BR]]
-'''Evaluate: ''' Involve producing XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE[[BR]]
+'''Time-bound: ''' If steps 1 - 4 are completed that can be a full accomplishment; additional work is a bonus [[BR]]
+'''Evaluate: ''' Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE[[BR]]
 '''Reevaluate: ''' Use an API to add and strip the EDXL-DE to any EDXL data standard. Use the same set of XML files to run through this process [[BR]]
+
 * Packaging
  * Easy (Fran): [InstallationGuidelines/Windows/User Windows Installer for End-Users]