RE: [ebxml-iic] Conformance Profiles

[Jeff Turpin <jturpin@cyclonecommerce.com>]

You are correct that a Status-Request message for a non-reliable message
can still occur. However, I wanted the Conference level/profile to
reflect the recommendation of the spec (Section 7):

The Message Status Request Service consists of the following:
·	A Message Status Request message containing details regarding a
message previously sent is sent to a Message Service Handler (MSH)
·	The Message Service Handler receiving the request responds with
a Message Status Response message.
A Message Service Handler SHOULD respond to Message Status Requests for
messages that have been sent reliably and the MessageId in the
RefToMessageId is present in persistent storage (see section 6.1).
A Message Service Handler MAY respond to Message Status Requests for
messages that have not been sent reliably.


Since the behaviour of the Status Request Service is fairly well defined
when used in conjunction with Reliable Messaging, I felt that
Conformance Level 4 should reflect that. Now, we can add an additional
Conformance Level to reflect Message Status Service functionality when
Reliable Messaging is not present. I was trying to keep the number of
Conformance levels to a minimum, however, if we feel that the Message
Status Service(with non Reliable Messaging) will be widely used, then we
should add another Conformance level. Thanks for your feedback. Cheers!



Jeff Turpin
Cyclone Commerce, Inc.


-----Original Message-----
From: Michael Wang [mailto:mwang@tibco.com]
Sent: Wednesday, September 04, 2002 12:40 PM
To: Jeff Turpin
Cc: ebxml-iic@lists.oasis-open.org
Subject: Re: [ebxml-iic] Conformance Profiles


This comment may be a bit late but does Conformance Level/Profile 4
really require Conformance Level/Profile 2?

A StatusRequest message for a non-reliable message can still happen.
In that case, the messageStatus can simply return NotRecognized.
If this is correct then Profile4 will not exist and StatusRequest
can be part of Profile2.

-mw

Jeff Turpin wrote:
> 
> Per our earlier conversation regarding conformance levels/profiles,
the
> following levels/profiles map closely to the modules listed in the
ebXML
> 2.0 Messaging specification. Thoughts?
> 
> Conformance Level/Profile 1: Core Modules
>                                 Modules:
>                                         a. Security Module
>                                         b. Error Handling Module
>                                         c. SyncReply Module
> 
> Conformance Level/Profile 2: Message Service Handler Ping Service
> (requires Conformance Level/Profile 1: Core Modules)
> 
> Conformance Level/Profile 3: Reliable Messaging Module (requires
> Conformance Level/Profile 1: Core Modules)
>                                 Modules:
>                                         a. AckRequested/Acknowledgment
>                                         b. DuplicateElimination
>                                 Reliable Messaging
Parameters/Behaviour:
>                                         a. Retries
>                                         b. Retry Interval
>                                         c. TimeToLive
>                                         d. PersistDuration
>                                         e. syncReplyMode
> 
> Conformance Level/Profile 4: Message Status Service (requires
> Conformance Level/Profile 2: Reliable Messaging Module):
>                                 Modules:
>                                         a.
StatusRequest/StatusResponse
> 
> Conformance Level/Profile 5: Message Order Module: (requires
Conformance
> Level/Profile 2: Reliable Messaging Module):
>                                 Modules:
>                                         a. MessageOrder
> 
> Conformance Level/Profile 6: Multi-Hop Module: (requires Conformance
> Level/Profile 1: Core Modules)
> 
> Conformance Level/Profile 7: Multi-Hop Reliable Messaging Module:
> (requires Conformance Level/Profile 2: Reliable Messaging Module)
> 
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>