Changes between Version 30 and Version 31 of Event/2011/GCI


Ignore:
Timestamp:
11/15/11 15:46:26 (10 years ago)
Author:
Nuwan Waidyanatha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/2011/GCI

    v30 v31  
    1111
    1212 * Build library(ies) '''Emergency Data Exchange Language Distribution Element'''
    13 Difficulty : '''Hard''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
    14 '''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 package) 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]]
     13Difficulty : '''HARD''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
     14'''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 package) 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]]
    1515'''Measurable: ''' It is purely a coding task that involves playing with XML and developing a class, possibly within or using the '''??? 3R**** ???''' framework It is basically a set of procedures for packing and unpacking EDXL-DE wrapped data. [[BR]]
    1616'''Attainable: ''' run through the steps [[BR]]
     
    2121Step 5 :: test the code, fix bugs, and generalize the functions [[BR]]
    2222Step 6 :: Apply to EDXL-HAVE and EDXL-SITREP to generalize the library [[BR]]
    23 '''Relevant: ''' Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP http://www.oasis-open.org/standards#edxl [[BR]]
     23'''Relevant  : ''' Applies to Sahana Interoperability policy. Present developments to investigate are: HAVE, RM, and SITREP http://www.oasis-open.org/standards#edxl [[BR]]
    2424'''Time-bound: ''' If steps 1 - 4 are completed that can be a full accomplishment; additional work is a bonus [[BR]]
    25 '''Evaluate: ''' Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE[[BR]]
     25'''Evaluate  : ''' Produce XML files with the EDXL-DE element appended to the EDXL-RM, SITREP, or HAVE[[BR]]
    2626'''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]]
    2727
     
    5858== Research ==
    5959* 3 x Create disaster scenarios & demos with data through pre-populate
    60 * Easy (Nuwan): Map elements between EDXL-SITREP and EDXL-RM to integrate the Situational Reporting and Resource Management components (deliverable: "table") with underlying schema
    61 * Medium (Nuwan): Develop a blue print (deliverable: "specifications document") for adding Transliteration to text entry controls, for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in
     60
     61* '''Map elements between EDXL-SITREP and EDXL-RM'''
     62Difficulty : '''EASY''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
     63'''Specific    : ''' [[BR]]
     64'''Measurable  : ''' [[BR]]
     65'''Attainable  : ''' [[BR]]
     66'''Relevant    : ''' [[BR]]
     67'''Time-bound  : ''' [[BR]]
     68'''Evaluate    : ''' [[BR]]
     69'''Reevaluate  : ''' [[BR]]
     70
     71:  to integrate the Situational Reporting and Resource Management components (deliverable: "table") with underlying schema
     72
     73* '''Blue print to add Transliteration to text entry controls'''
     74Difficulty : '''MEDIUM''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
     75'''Specific    : ''' , for example with http://www.google.com/ime/transliteration/ engine or any other generic plug-in[[BR]]
     76'''Measurable  : ''' [[BR]]
     77'''Attainable  : ''' [[BR]]
     78'''Relevant    : ''' [[BR]]
     79'''Time-bound  : ''' [[BR]]
     80'''Evaluate    : ''' [[BR]]
     81'''Reevaluate  : ''' [[BR]]
     82
    6283* Easy (Fran): Provide UTF8 names for Locations exported from [http://gadm.org GADM] in Vietnam, e.g. using [http://en.wikipedia.org/wiki/Vietnam#Administrative_subdivisions Wikipedia]
    6384 * see attached spreadsheet [http://eden.sahanafoundation.org/raw-attachment/wiki/Projects/GCI/VNM_adm4.7z VNM_adm4.7z] (L1 has been done, focus on L2 1st, then L3, then finally L4 if you can)