Re: [Fwd: Re[2]: Concern with basic ebXML TRPSyntax/Semantics] (I'm Away)

["Michael Shalev" <Michael@idap.co.il>]

Hi,

I'm currently abroad, but will return on Sunday, April 16th.

Thanks, and have a nice day,

Michael Shalev
Director of Development
iDap Ltd.

>>> ebXML-Transport 04/13/00 19:28 >>>

I agree. XML DSig just came out of last call if I'm not mistaken.
However, we also need to be mindful that there would need to be
implementation(s) of this available. It may be that we'll need to
support PGP or S/MIME for some period of time to allow for
implementations to catch up with the W3C recommendation.

Cheers,

Chris

"Kit (Christopher) Lueder" wrote:

> I think the obvious answer is that W3C is developing an XML Signature
> specification, and we defer finalization of an ebXML signature solution
> until that is finalized. It would be unfortunate for the ebXML signature
> solution (i.e., based on PGP or S/MIME) to be different with and
> incompatible with the W3C signature solution.
> Kit.
>
> dick@8760.com wrote:
> > Bob,
> >
> > Please provide details showing how a PGP or S/MIME signed/encrypted payload is
> > supported in your proposal.
> > Dick Brooks
> > http://www.8760.com/
> >
> > ----- Original Message -----
> > From: Miller, Robert (GEIS) <Robert.Miller@geis.ge.com>
> > To: <ebXML-Transport@lists.oasis-open.org>
> > Sent: Tuesday, April 11, 2000 8:39 AM
> > Subject: RE: [Fwd: Re[2]: Concern with basic ebXML TRP Syntax/Semantics]
> >
> > > Gentle People,
> > >
> > > Could we get to a single XML document with reasonably small risk of XML
> > > parser failures beyond the ebXML header if we defined something like:
> > >
> > > <!ELEMENT ebXML (ebXMLHeader,ebXMLbody*)>
> > > <!ELEMENT ebXMLHeader ( ... )>
> > > <!ELEMENT ebXMLBody ANY>
> > >
> > > or for the 'body' parser,
> > >
> > > <!ELEMENT ebXML (ebXMLHeader,ebXMLbody*)>
> > > <!ELEMENT ebXMLHeader ANY>
> > > <!ELEMENT ebXMLBody ( ... )>
> > >
> > > Or perhaps the <ebXML> element could invoke some sort of XSLT filter that
> > > blew apart the document into standalone header and body XML files and
> > > invoked processing of the parts.  (NOTE: I'm not an XML guru, so I might
> > > just be blowing smoke here!)
> > >
> > > Cheers,
> > >         Bob
>
> --
>     _/    _/             Kit C. J. Lueder
>    _/   _/         _/   The MITRE Corp.         Tel:  703-883-5205
>   _/_/_/    _/  _/_/_/ 1820 Dolley Madison Bl  Cell: 703-577-2463
>  _/   _/   _/    _/   Mailstop W722           FAX:  703-883-7996
> _/    _/  _/    _/   McLean, VA 22102        Mail: kit@mitre.org
> Worse than an unanswered question is an unquestioned answer.