EM TC Notification, Messages and Methods SC 05/27/03 Meeting Minutes

[CSubatch@eteam.com]

Notification, Methods and Messages Subcommittee
Emergency Management TC
May 27, 2003

Much thanks to Joyce Kern for taking minutes this week.

Attendees:

Elliott Christian
Joyce Kern
Cathy M Subatch
John Silva
Gary Ham
Art Botterell
Bill Schroeder
Jerry Weltman 

Meeting Notes
Requirements/Use Cases

• Art - any more discussion on requirements and/or use cases.  No additional discussions
  
  Top level of object diagram.
  • Art send out last week Did everyone get a chance to review.  Any discussion/questions/issues.  
  • All agreed .. this is the General Structure that we want to use
  • Start next week with next week copy of data dictionary for top level block - with
    items from workshop in VA.
  • Elliott - send whole thing at once with all changes (not so big of an XML structure)
  • Art - suggested that we go to www.incident.com/cap site, look under documents,
    and grab current data dictionary.  Compare to email Art sent out.  apply
    changes from workshop.
    
    GIS Input
    Elliott will give Art the input that he gave Art verbally, in writing, for the structure
    
    Incident Notification
    • Art - other item we have working is incident notification form.
    • Gary - industry meeting ... based on that, Gary has been given the go-ahead
      to make a full schema of incident occurrences
    • Art - what do messages signify?
    • Gary - in the documentation for sw, there is a notion of how info is posted
      between collaboration groups ... provides access to structure by people who
      built info.  Send that info to another operational group that can pull that
      information.  It is a structure of information for documenting the incident
      itself
    • Art - XML representation of database structure for an incident.
    • Gary - this is a usage, accessed provision, ... replication if the information is pulled (update).
    • Art - one of the functionalities that might be provided would be soap message brokering service
    • Gary - where authorizations and validation is managed from government offices
    • Art - mission - controlled information "space"
    • Gary - policy of this group is not to limit the data structure
      
      Action Items
      
      • Art - next week we will have first review of data dictionary.  Art will not
        try to make all the definitions 11179 compliant.  He is looking for assistance for that.
      • Elliott - separate usage notes from definition.  This will be included in
        the same document
      • Discuss our process for proceeding
        
        Conference:
        Art - 3rd week in June is World Disaster Conference in Toronto.  What aspects of
        design do we want to focus on?  Do we focus on terminology again, or new
        topic?  what are our priorities?  Bill Schroeder is attending this workshop.
        Art is as well.
        
        Next Meeting
        
        The next meeting will be held Tuesday, June 3 at 9:30am PDT/12:30pm EDT.
        Dial in: 1.800.453.7412
        Access Code: 604776