RE: What ebXML specifications do we need?

["Surendra Reddy" <SKREDDY@US.oracle.com>]

Since these three formats are completely different, I prefer
to keep them as separate documents/specifications.

--Surendra

Surendra Reddy
Oracle Corp.

> -----Original Message-----
> From: owner-ebxml-transport@lists.oasis-open.org
> [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of David
> Burdett
> Sent: Thursday, March 09, 2000 4:11 PM
> To: 'Dick Brooks'
> Cc: ebXML Transport (E-mail)
> Subject: RE: What ebXML specifications do we need?
>
>
> Dick
>
> If we have something titled simply "ebXML Security and Signature
> Specification" then how would we distinguish it from a similar
> specifcation
> we might develop in the future based on the W3C/IETF XML DSig work.
>
> Does it make more sense to have three specifications:
> 1. ebXML S/MIME Security and Signature Specification
> 2. ebXML PGP Security and Signature Specification, and
> 3. ebXML XML Dsig Security and Signature Specification
>
> ... or should we combine the first two into one?
>
> Thoughts?
>
> David
>
> -----Original Message-----
> From: Dick Brooks [mailto:dick@8760.com]
> Sent: Thursday, March 09, 2000 4:01 PM
> To: David Burdett; ebXML Transport (E-mail)
> Subject: RE: What ebXML specifications do we need?
>
>
> David, could I suggest rewording 6a to:
>
> 6a. ebXML Security and Signature Specification - how to use S/MIME
> or PGP to sign and encrypt ebXML Messages
>
> Thanks,
>
> Dick Brooks
> http://www.8760.com/
>
> -----Original Message-----
> From: owner-ebxml-transport@lists.oasis-open.org
> [mailto:owner-ebxml-transport@lists.oasis-open.org]On Behalf Of David
> Burdett
> Sent: Thursday, March 09, 2000 5:32 PM
> To: ebXML Transport (E-mail)
> Subject: What ebXML specifications do we need?
>
>
> Folks
>
> I thought it might be useful for us to identify all the specifications we
> need to develop. Here's my list for starters:
>
> 1. ebXML Message Header Specification - what we're working on
> 2a. ebXML MIME Message Envelope Specification - how to wrap header's and
> bodies in a MIME wrapper
> 2b. ebXML XML Message Envelope Specification - how to wrap headers and
> bodies in XML - we should do this later
> 3. ebXML Document Exchange Template Specification - defines how we handle
> requests, responses, message acks, cancel, error, etc and include state
> diagrams for each end.
> 4. ebXML Reliable Messaging Specification - how to achieve robust reliable
> once-only delivery of message in a vendor neutral, transport
> independent way
> 5a. ebXML Messaging over HTTP Specification - how to send ebXML Messages
> using HTTP or HTTPS
> 5b. ebXML Messaging over SMTP Specification - how to send ebXML Messages
> using SMTP
> 6a. ebXML S/MIME Security and Signature Specification - how to use S/MIME
> with ebXML Messages
> 6b. ebXML XMLDsig Security and Signature Specification - how to
> use IETF/W3C
> XML Digital Signatures with ebXML Messages - we wouldn't do this
> until later
> 7. ebXML Transaction Status Inquiry Specification - how to inquire on the
> current status of a transaction
> 8. ebXML Service Availability Specification - how to determine if
> a Service
> is up and running
> 9. ebXML Publish & Subscribe Specification - how to do Publish
> and Subscribe
> securely using any of the above
> 10. ebXML Messaging Discovery Specification - how to determine the
> parameters associated with a Service from the ebXML Messaging perspective.
> 11. ebXML Messaging Audit Trail Specification - how to create an
> audit trail
> of the messages exchanged during a transaction.
>
> In my view we need to do 1, 2 and 5 before we have a usable specification
> and 1 through 5 before we have one we can use in a B2B context.
>
> Thoughts?
>
> David
>
> Advanced Technology, CommerceOne
> 4400 Rosewood Drive 3rd Fl, Bldg 4, Pleasanton, CA 94588, USA
> Tel: +1 (925) 520 4422 or +1 (650) 623 2888;
> mailto:david.burdett@commerceone.com; Web: http://www.commerceone.com
>