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


Ignore:
Timestamp:
11/15/11 16:03:53 (13 years ago)
Author:
Nuwan Waidyanatha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/2011/GCI

    v31 v32  
    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 [http://en.wikipedia.org/wiki/EDXL | EDXL] data package. 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]]
     
    6161* '''Map elements between EDXL-SITREP and EDXL-RM'''
    6262Difficulty : '''EASY''' Proposed by: [http://lirneasia.net/profiles/nuwan-waidyanatha | Nuwan][[BR]]
    63 '''Specific    : ''' [[BR]]
    64 '''Measurable  : ''' [[BR]]
     63'''Specific    : ''' There are several elements within the EDXL-SITREP data standard that are identical to that of [http://docs.oasis-open.org/emergency/edxl-rm/v1.0/EDXL-RM-SPEC-V1.0.pdf | EDXL-RM]. The objective is to create a descriptive table of those elements that a programmer can use to develop a set of procedures to strip the RM data from SITREP to manage records in the relational database [[BR]]
     64'''Measurable  : ''' Requires diligently investigating each and every data element then comparing them with the two data standards SITREP and RM. Requires knowledge of data types and XML. If not, this exercise will help the student learn about XML and data standards [[BR]]
    6565'''Attainable  : ''' [[BR]]
     66Step 1 :: Go through EDXL-RM and EDXL-SITREP documentations
     67Step 2 :: create example files to get an understanding of the data and structure
     68Step 3 :: develop the table with RM and SITREP elements with a description
     69Step 4 :: develop a simple XSL file to strip the RM data from SITREP
    6670'''Relevant    : ''' [[BR]]
    6771'''Time-bound  : ''' [[BR]]