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

 


Help: OASIS Mailing Lists Help | MarkMail Help

ebxml-bp message

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


Subject: RE: Questions regarding bpSS


Comments imbedded

John

-----Original Message-----
From: Himagiri Mukkamala [mailto:himagiri@sybase.com]
Sent: Wednesday, June 20, 2001 4:39 PM
To: ebxml-bp@lists.ebxml.org
Subject: Questions regarding bpSS


I've a few questions with the current version of BPSS.
Can someone from the bpSS group answer these or
consider these for tomorrows conf call.


1.  Notification of Failure DTD
     In ebXML, the BPSS does not define  what the Nofication of Failure
dtd looks like.  Is there a location where we can find this dtd?
Since the other business signal follow's RN's business signal, can we
use
RosettaNet's Notification of Failure dtd?

<John Yunker>The RosettaNet notification of failure (NOF) guideline and dtd
are available in the public areas of RosettaNet. Notification of failure
message is part of an administrative transaction, and is not a signal, but a
business message containing administrative actions.</John Yunker>

Will be there be specific service and action elements for the same.

<John Yunker>N090 shows notification of failure as a seperate transaction
that references the original transaction, thus specific service and action
elements would be required</John Yunker>

2.  Business Signals
     Is there a location where we can grab the dtd's for the business
signal? Currently, the business signals defined in ebXML are RN's
version
1.1 business signal dtd which are different than the business signals
that are currently in RNIF 2.0. Is there a plan with next version of
bpSS
to align with the latest version of RNIF 2.0 or stick to 1.1

<John Yunker>There was protracted discusion around the 1.1 vs. 2.0 issue.
The 1.1 version was adopted because of the ability to place business
semantics in the signals.  Please note that ebXML TRP covers all of RNIF 2.0
without any signal business content, so adoption of 2.0 signal messages
would be redundant.  From BPSS documentation: "The business signal payload
structures provided herein are optional and normative and are intended to
provide business and legal semantic to the business signals."</John Yunker>

3.  AcceptanceAcknowledgement

    Is there a condition when there could be a
negativeAcceptanceAcknowledgment, or the only way
the responder can send denial of acceptanceAcknowledgment
is by not sending it and the requester times out on it.
I guess the question would be, is there provision in the bpss
to send a negativeAcceptanceAcknowledgment.

<John Yunker>By definition a negative acknowledgement is an exception.  An
exception can be sent in response to any message within the context of
processing that message.</John Yunker>

Thanks,
himagiri


------------------------------------------------------------------
To unsubscribe from this elist send a message with the single word
"unsubscribe" in the body to: ebxml-bp-request@lists.ebxml.org


[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