OASIS Emergency Management TC

Re: [emergency] EDXL-DE routing and valueListUrn

  • 1.  Re: [emergency] EDXL-DE routing and valueListUrn

    Posted 03-20-2006 23:19
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    emergency message

    [Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


    Subject: Re: [emergency] EDXL-DE routing and valueListUrn


    David -
    
    While I understand the urgency and while I do not necessarily disagree with 
    the contents of your slides on a National Effort for Emergency Data 
    Distribution, I would like to add a few words of caution.
    
    First, what you have outlined are uses cases and requirements for one domain 
    of use - alerts as related to secure US DoD sensor nets. I deal with folks 
    doing sensor systems and networks in a number of other countries - all 
    civilian. Any of these applications using sensors can create alerts. For 
    example, a new water portal in Canada that will send alerts based on stream 
    flow gauges, traffic alerts being generated by the new generation of ITS 
    capabilities, weather alerts, and systems function alerts being generated by 
    transducers, and so forth. We cannot loose sight of all the other potential 
    use cases that drives the requirements for EDXL - now and in the future.
    
    Second, and related to the first, is the fact that OASIS is an international 
    standards organization. As such, we cannot ignore requirements for using 
    EDXL that may be extremely viable in other countries. It is unfortunate that 
    we have had little input from organizations in other countries that have 
    requirements similar to the US DoD. That is why I am very pleased with the 
    progress of the Sensor Standards Harmonization work that NIST is 
    spearheading.
    
    Third, we would be remiss in ignoring the potential for alerts coming from 
    the emerging sensor nets being designed, built, and fairly recently deployed 
    for home systems and office buildings (office sensor networks are much more 
    mature). See http://www.usipv6.com/CES_Presentations/CES_Itaru_Mimura.pdf as 
    well as all the work being done at UCLA (SOS) and Sun (SUN SPOT). These 
    systems are envisioned as being able to automatically generate alerts (fire, 
    carbon monoxide, health, etc).
    
    Finally, and anyone (someone) correct me if I am wrong, but perhaps the 
    COMCARE EPAD system would be a repository/registry solution.
    
    So, I agree that current DHS and DoD requirements are very valid and those 
    requirements must be answered by EDXL. But let's make sure we remain 
    balanced in our approach so that other communities outside DoD and DHS are 
    also fairly represented at that CAP and EDXL have used well beyond.
    
    Cheers
    
    Carl