Re: [emergency] Message Type and Status

[Art Botterell <acb@incident.com>]

In both cases I don't think it's up to use to define the behavior of  
particular systems.  Our task is to abstract the distinctions that  
frequently make a difference in behavior.

E.g., a "test" message might be discarded by most, but might be  
essential for a network monitoring function.  Or a single application  
might have an "actual" and an "exercise" mode.

Our job isn't to determine that for the implementers, it's just to  
allow the most common and significant distinctions to be  
represented.  IMHO, of course...

- Art


On Jun 7, 2005, at 6/7/05 10:18 PM, Renato Iannella wrote:

>
>
> The "Message Type" element defines "the function of the message"
> and includes values: Report, Update, Cancel, Request, Response,  
> Dispatch, Ack, Error.
>
> Q1: Do we need to define any behaviours for these values that  
> indicate any processing
> differences? For example, If I have a "Report" message and a  
> "Request" message, do I need
> to do anything different? (or is it informational and to be used  
> for routing?).
>
> Obviously, Cancel, Ack, and Error must contain a Reference, and NO  
> message contents.
>
>
>
> Cheers...
>
> Dr Renato Iannella
> Project Leader, NICTA, Brisbane, QLD, AUSTRALIA
> P: +61 7 3000 0484 F: +61 7 3000 0480 M: +61 4 1313 2206
> E: renato@nicta.com.au W: http://nicta.com.au
>
>
> ---------------------------------------------------------------------- 
> ----
> 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.
>
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs  
> in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
>