OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-poc message

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

Subject: RE: Receipt Messages for the demo!!

The packaging section of POC proposal document treats the 
acknowledgement payload as business document instead of 
treating it as a protocol signal.
ex. The DocumentLabel field in the ebXML header for Request
Acknowledgement has the value of "Purchase Order Request Acknowledgement".
There is no such document type defined by Rosenttanet. 
Rosettanet does not create  custom acknowledgement messages
based on the received message.

My point is, we are creating confusing scenario by mixing the 
Rosettanet business documents (defined by PIPs) and signal
messages (defined by and scope limited to RNIF).

Instead we can live with just ebXMLHeader and no payload for
acknowledgement messages. This will at least keep the matters clean.

Just my thoughts.

Sanjay Patil
Work Phone: 408 350 9619

-----Original Message-----
From: Prasad Yendluri [mailto:pyendluri@vitria.com]
Sent: Saturday, July 29, 2000 7:13 PM
To: Patil, Sanjay
Cc: Ebxml-Poc (E-mail); Askary, Sid
Subject: Re: Receipt Messages for the demo!!


This was already discussed. We said, the RN acks would simply be payload as
as ebXML is concerned. The  Packaging section of the POC proposal document
shows <RN-Action-Message> or <RN-Signal-Message> in the payload. There are
ebXML level acks.

Regards, Prasad

"Patil, Sanjay" wrote:

> This is about "Receipt Acknowledgement" messages for the demo.
> Are we planning to use any payload for these messages? Since these
> messages are consumed by the service and not passed to the backend,
> we need to have ebXML specific payload, if any.
> I am not sure if TR&P has identified different signal message types
> as acknowledgement, exception and defined types for them.
> Of course, we can use RN payload for the demo, but that demonstrates
> no ebXML feature, as the ebXML service is not going to process the receipt
> payload in the receipt messages.
> Instead, maybe we can just use the ebXML header's DocumentLabel field
> to identify the "Receipt Acknowledgement" and not have any payload.
> Please ignore this message if this topic has already been discussed and
> decision has been made (I would still need to know the decision though).
> thanks,
> Sanjay Patil
> ------------------------------
> Work Phone: 408 350 9619
> http://www.netfish.com

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

Search: Match: Sort by:
Words: | Help

Powered by eList eXpress LLC