OASIS Emergency Management TC

 View Only

RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject

  • 1.  RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject

    Posted 01-30-2006 18:06
     MHonArc v2.5.0b2 -->
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    
    

    emergency message

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


    Subject: RE: [emergency] FW: Suggestion: Add incidentKeyword to contentObject


    I don't think anyone on the TC is interested in going back for a 60-day 
    review at this point in the EDXL-DE.  If anyone feels strongly the other 
    way with respect to this change, please let me know. Elysa
    
    At 09:44 AM 1/30/2006, Rex Brooks wrote:
    >As I just mentioned, I think this last change request from Mark Carlson, 
    >would, if adopted, require an additional 60-day public comment period.
    >
    >Rex
    >
    >At 8:47 AM -0600 1/30/06, Elysa Jones wrote:
    >>As to where we are with the documentation to OASIS, we still must 
    >>1)  populate the Revision History table (I am working on that now and 
    >>should have something for the group to review by COB tomorrow); 2)  Make 
    >>the correction to the DOM as per Dave Ellis comment on the list this 
    >>weekend (action:  Patti) and 3)  If we agree on the list that the 
    >>recommended change as further discussed this weekend on the list by Dave 
    >>and below by Tim, then we can make this change.  We need to get these 
    >>final - FINAL changed in by 2/1 if possible and vote by CoB that 
    >>day.  This will keep us on the same schedule for an OASIS wide vote the 
    >>end of March.  Stay tuned for a meeting to be called for a vote 2/1.  If 
    >>you are a voting member and cannot be available during some part of that 
    >>day (Wed), please let me know. Thanks, Elysa
    >>
    >>At 08:12 AM 1/30/2006, you wrote:
    >>>All,
    >>>
    >>>Just to make sure we are clear, the incidentID and Description are already
    >>>included in the ContentObject as optional.  Being optional, an incident may
    >>>or may not be related to the content, and the spec contains a business rule
    >>>that each DE may contain only one content object.
    >>>
    >>>Mark is suggesting addition of an optional incidentKeyword to classify the
    >>>incident, which is not a complicated request.  I think the decision really
    >>>comes down to where we draw the line and get the DE published, and where we
    >>>begin considering additional requests for the next version.
    >>>
    >>>Regards,
    >>>
    >>>Tim Grapes
    >>>Evolution Technologies, Inc.
    >>>Disaster Management egov Initiative
    >>>Science and Technology Directorate/OIC
    >>>Department of Homeland Security
    >>>Office:  (703) 654-6075
    >>>Mobile:  (703) 304-4829
    >>>tgrapes@evotecinc.com
    >>>tim.grapes@associates.dhs.gov
    >>>
    >>>
    >>>