Changes between Version 78 and Version 79 of Event/2014/IOTX/cap-codefest-2014


Ignore:
Timestamp:
05/15/14 08:59:29 (8 years ago)
Author:
Nuwan Waidyanatha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Event/2014/IOTX/cap-codefest-2014

    v78 v79  
    6363* Demonstrate the working solution
    6464==== (B) Validating parameters carrying scientific data ====
     65===== NON-CODING =====
     66(B.1) Develop a database of scientific parameter formats
     67* Identify commonly used scientific measures for the following hazard events
     68     * (B.1.1) Volcanic eruption
     69     * (B.1.2) Flash Floods
     70     * (B.1.3) Storm surge
     71     * (B.1.4) Landslide
     72     * (B.1.5) Typhoon
     73     * (B.1.6) Chemical spill
     74     * (B.1.7) Maritime accident
     75     * (B.1.8) Forest fire
     76     * (B.1.9) TBA
     77     * (B.1.10) TBA
     78===== CODING =====
     79(B.2) Develop a data structure and a GUI for managing relationships between the various ordered encoding of scientific
     80* e.g. wave-height would imply the ocean wave height but it can be in centimetres, meters, or inches
     81* possibly modelled as a pair object-property; where object is the wave and property is height)
    6582
    66 (B.1) Identify 5 to 10 sets of, hazard event specific, commonly used scientific measures
     83(B.3) Build the API for CAP publishers and subscribers to validate the scientific measures - task B.5 depends on this task
     84* The scientific measures are exchanged through CAP <parameter> elements
     85* API should parse the elements and then validate their conformity
    6786
    68 (B.2) Develop a data structure for managing relationships between the various ordered encoding of scientific measures (e.g. wave-height would imply the ocean wave height; possibly modeled as a pair object-property; where object is the wave and property is height)
    69 
    70 (B.3) Build the API for CAP publishers and subscribers to validate the scientific measures. The scientific measures are exchanged through CAP <parameter> elements.
    71 
    72 (B.4) Programmers from the four CAP-enabled software tools would submit their <parameter> element data through the API to match with an existing object and property.
     87(B.5) Test the validation Programmers from the four CAP-enabled software tools would submit their <parameter> element data through the API to match with an existing object and property.
    7388
    7489(B.5) The individual CAP-enabled software tools can exchange various CAP messages with <parameter> element values and the cross validated with the Sahana-Eden validation service.