[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [emergency-msg] Example Message Semantics
Me, too, Renato, The table solution totally eliminates my initial skepticism about having all Message Elements present in the definition. I was envisioning the kind of involved semantics about semantics in textual descriptions of message factors and name/value pair signatures that I am accustomed to in other web services contexts. This is much mo' bettah! Cheers, and Thanks, Rex At 7:10 AM -0500 8/21/06, Aymond, Patti wrote: >I like it!!!! > >Patti > > >From: Renato Iannella [mailto:renato@nicta.com.au] >Sent: Mon 8/21/2006 1:36 AM >To: Emergency_Mgt_Msg_SC >Subject: [emergency-msg] Example Message Semantics > >-------------------------------------------------------------------------- >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>http://www.ieminc.com/e_mail_confidentiality_notice.html -- Rex Brooks President, CEO Starbourne Communications Design GeoAddress: 1361-A Addison Berkeley, CA 94702 Tel: 510-849-2309
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]