ebxml-msg message

Subject: [ebxml-msg] FW: Question

From: "Burdett, David" <david.burdett@commerceone.com>
To: "ebXML Messaging (E-mail)" <ebxml-msg@lists.oasis-open.org>
Date: Thu, 24 Jan 2002 15:24:09 -0800

Title: FW: Question

Forgot to copy to the list.

David

-----Original Message-----
From: Burdett, David
Sent: Thursday, January 24, 2002 12:43 PM
To: 'David Fischer'
Subject: RE: Question

David

How about you receive a message that contains a RefToMessageId for a message you did not send. This would not be picked up by a parser and should be reported with "ValueNotRecognized". Another example would be if you received a message where the ToParty contained an Id that you did not recognize (for example it wasn't for you).

"OtherXML" is really a catch-all. Although unlikely, it could be that some implementations generate errors that don't fall under the other three codes. So really it is a good saftey-net and therefore we should leave it in.

Hope this helps.

David
-----Original Message-----
From: David Fischer [mailto:david@drummondgroup.com]
Sent: Thursday, January 24, 2002 11:49 AM
To: ebXML Msg; David Burdett
Subject: Question

This is a question, not a request to change the spec.

David,

I am trying to determine when the errors: ValueNotRecognized and OtherXML would
be sent. In every case I can think of, these would result in parser errors
rather than ebXML errors so I am not sure when these apply.

Regards,

David Fischer
Drummond Group.