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


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-charter-discuss message

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

Subject: RE: [oasis-charter-discuss] Re: Proposed Charter for OASIS Business Document Exchange (BusDox) TC

The OASIS Standard (2007) ebMS 3.0 Part 1, Core
Specification defines a Web Services-based messaging
protocol that supports receipts using the Receipt Signal


The AS4 profile of ebMS 3.0 (CS of April 2010) profiles this
Receipt signal to achieve the equivalent of AS2 Message
Disposition Notifications (MDNs) that provide
Non-Repudiation of Receipt (NRR).


The AS4 NRR feature reuses structures from the OASIS
Standard (2006) ebXML Business Process Specification Schema:


The new ebMS 3.0 Part 2, Advanced Features specification
shows how these receipts can be exchanged in multi-hop
networks through a series multiple SOAP intermediaries,
achieving end-to-end non-repudiation of receipt. In ebMS,
these intermediaries can be configured to support either
"push" or "pull" forwarding,  and support a mailbox-style
model where intermittently connected endpoints (e.g. for
SMEs that are only connected a few hours per day, not
necessarily at the same time) exchange messages (user
messages and receipts) via an intermediary that temporarily
stores messages.


There are references to ebMS in the BusDox charter, so this
can be discussed further in the TC once it starts.


-----Original Message-----
From: Andrea Caccia [mailto:andrea.caccia@studiocaccia.com] 
Sent: 10 November 2010 15:21
To: oasis-charter-discuss@lists.oasis-open.org
Cc: Jens Jakob Andersen; Mikkel Hippe Brun; Pim van der
Eijk; Tim McGrath; tg@itcrew.dk; Paul Fremantle; Gianfranco
Tabasso; mary.mcrae@oasis-open.org
Subject: [oasis-charter-discuss] Re: Proposed Charter for
OASIS Business Document Exchange (BusDox) TC

One of the relevant aspects in some business document
exchange is when is required a third party certification of
sending and delivering of documents in some moment in time,
e.g. in a public tender or when you need to proof that a
document has been sent and delivered or made available to
the recipient and when.
This can be done in many different ways but I suggest that
this TC includes recommendations on how to do this in a
standardized and interoperable way.
I'm participating to an ETSI standardization work that deals
with this problem and addressing gatewaying between REM
(Registered Elextronic Mail, see ETSI TS 102 640) and BusDox
as developed within the PEPPOL project and I propose this TC
can liaise and take advantage from this work.

Best regards,
Andrea Caccia

To unsubscribe from this mail list, you must leave the OASIS
TC that generates this mail.  Follow this link to all your
TCs in OASIS at:

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