Hi Jeff, I am definitely interested in attending the seminar. Keep me informed about the venue.
Regards Christie Davel Rockspider 082 6648 691 On Thu, 2003-11-20 at 10:23, [EMAIL PROTECTED] wrote: > > > Hi > I have made new arrangements for the talk and the following is the > information you need to start sending your RSVP's . > > DATE : 03 December 2003 > > TIME : 18h30 *for* 19h00 > > VENUE : **STILL TO BE DECIDED(depends on numbers)** > > EXTRAS : Axl says he's got some nice things to give away : > ^)) > > Please send your RSVP directly to me(I've set the reply address to my > one , and I hope that'll work) . > > Axl will cover the Web Services landscape in the following way: > > 1. A brief history of the internet, > 2. a brief history of Web Services, > 3. parallels that can be drawn from the growth in popularity of > the internet that can be applied to Web Services, > 4. problems we're facing in Web Services and > 5. an overview of how different technologies fit together in the > Web Services space. > > Axl is a a member of the following expert groups at JCP.org. > > 1. JSR 104 - Define a standard set of APIs and a protocol > for a "Trust Service" A key objective of the protocol > design > is to minimize the complexity of applications using XML > Signature.By becoming a client of the trust service, > the > application is relieved of the complexity and syntax of > the > underlying PKI used to establish trust relationships, > which may be > based upon a different specification such as > X.509/PKIX, > SPKI or PGP. > 2. JSR 105 - Define a standard set of APIs for XML digital > signatures services. The XML Digital Signature > specification > is defined by the W3C. This proposal is to define and > incorporate the high level implementation > independentJava APIs. > > 3. JSR 106 - Define a standard set of APIs for XML digital > encryption services. This proposal is to define and > incorporate the high level implementation independent > Java APIs. > > 4. JSR 115 - Define a contract between containers and > authorization service providers that will result in the > implementation of providers for use by containers. > > 5. JSR 155 - To provide a set of APIs, exchange patterns & > implementation to securely (integrity and > confidentiality) > exchange assertions between web services based on OASIS > SAML. > > 6. JSR 183 - Define a standard set of APIs for Web services > message security. The goal of this JSR is to enable > applications to construct secure SOAP message > exchanges. > > > > > Jeff Mutonho > > > _______________________________________________ > Jobs mailing list > [EMAIL PROTECTED] > http://www.ctjug.org.za/mailman/listinfo/jobs _______________________________________________ Jobs mailing list [EMAIL PROTECTED] http://www.ctjug.org.za/mailman/listinfo/jobs
