OASIS Emergency Management TC

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

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

    Posted 01-31-2006 00:17
     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


    Title: Re: [emergency] FW: Suggestion: Add incidentKeyword to contentObject
    O.K. I'm going to assume that I misunderstood and change it to meet Rex's description prior to the meeting tomorrow. This will be a change to the DOM, Data Dictionary, and schema. Please, please, please check to make sure that I don't get them out of sync.
     
    Patti


    From: Renato Iannella [mailto:renato@nicta.com.au]
    Sent: Mon 1/30/2006 5:42 PM
    To: Rex Brooks; Emergency_Mgt_TC TC
    Cc: Tim Grapes; Aymond, Patti; Lee Tincher
    Subject: Re: [emergency] FW: Suggestion: Add incidentKeyword to contentObject



    On 31 Jan 2006, at 08:06, Rex Brooks wrote:

    > Excuse me, Please, if my memory has turned to swiss cheese, but I 
    > would have sworn we agreed that EDXL-DE  could have multiple 
    > contentObjects with one and only one payload each, and one and only 
    > one DistributionType, so that no contentObjects could be of a type 
    > different than the DistributionType.

    That is my recollection as well....

    Cheers...  Renato Iannella
    National ICT Australia (NICTA)



    --------------------------------------------------------------------------
    This email and any attachments may be confidential. They may contain legally
    privileged information or copyright material. You should not read, copy,
    use or disclose them without authorisation. If you are not an intended
    recipient, please contact us at once by return email and then delete both
    messages. We do not accept liability in connection with computer virus,
    data corruption, delay, interruption, unauthorised access or unauthorised
    amendment. This notice should not be removed.

    IEM CONFIDENTIAL INFORMATION PLEASE READ OUR NOTICE:
    http://www.ieminc.com/e_mail_confidentiality_notice.html



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