ws-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Ws Wiki] Update of "WSTrackUs09" by RossGardler
Date Thu, 09 Jul 2009 13:32:39 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ws Wiki" for change notification.

The following page has been changed by RossGardler:
http://wiki.apache.org/ws/WSTrackUs09

The comment on the change is:
Move to conference planning wiki

------------------------------------------------------------------------------
+ This page has been moved to the [http://wiki.apache.org/concom-planning/WebServicesTrackUs09
Conference planning wiki]
- #format wiki
- #language en
- #pragma section-numbers off
  
- == Track Title ==
- 
- Project Management Committee: Web Services
- 
- Subprojects covered by Track: Axis2, Rampart, Sandesha, WS-Commons
- 
- PMC Liason/Spokesorganizer(s): Glen Daniels
- 
- Planning Team Mentor & Liason: Ross Gardler
- 
- === Track Description ===
- 
- The Apache Web Services Project is a constellation of software built around XML-based integration
and the "WS-*" set of standards (SOAP, WSDL, WS-Security, etc).  It includes everything from
the popular Axis2 SOAP stack to libraries to help you process WS-Policy, XML Schema, and Web
Service Security.  This track will introduce all the sub-projects, provide end-user case studies,
and give you a chance to interact directly with the developers.  Whether you have specific
questions or just need deeper knowledge of the Apache WS stack, the Web Services track is
the place to be.
- 
- ## Must be suitable for program, one paragraph, identify Who, What and Why.
- ## This must be oriented towards the technologist familiar with this subject
- ## matter, one who is not yet familiar but would be interested if they knew
- ## what the technology was, and the decision maker who would approve their
- ## attending this conference!
- ##
- 
- === Target Audience ===
- 
- 
- 
- ## This is for the planners use and marketing
- ##
- 
- ## Please list companies who might be interested in sponsoring this content,
- ## and include contact name and email, if known, for Delia to contact them
- ##
- ##
- 
- == Proposed Schedule ==
- 
- ## Your mentor will come in and insert any applicable trainings
- 
- || 09:00 - 10:00 || REGISTRATION    ||
- || 10:00 - 10:50 || Session 1       ||
- || 10:50 - 11:15 || BREAK           ||
- || 11:15 - 12:05 || Session 2       ||
- || 12:05 - 13:30 || LUNCH           ||
- || 13:30 - 14:20 || KEYNOTE         ||
- || 14:30 - 15:20 || Session 3       ||
- || 15:20 - 16:00 || BREAK           ||
- || 16:00 - 16:50 || Session 4       ||
- || 17:00 - 17:50 || Session 5       ||
- || 18:00         || END OF PROGRAM  ||
- 
- ## Do not change capitalized items!  These are part of the master schedule.
- ## The individual Session time blocks may be re-sliced, but remember that
- ## only five speakers per full day of content receive any speaker benefit.
- ##
- 
- ## Each session must be commercially attractive to the audience identified,
- ## if content doesn't "fit" into this track but is interesting or useful,
- ## consider an Additional Event, below
- ##
- 
- ## This must be completed in June, site opens on the 22nd.
- 
- === Session Title ===
- 
- Session Code:
- ## [Original from CMS, even if it will be revised, or leave blank if not entered]
- 
- Speaker:
- ## Include title, company affiliation, and note [email] here as a comment
- 
- _Session Description_
- 
- 
- 
- ## Must be suitable for program, one paragraph, identify Who, What and Why,
- ## note the requirements under the Track description, above.
- ##
- 
- _Target Audience_
- 
- ## For planners use, only if different than the main track
- ##
- 
- 
- ## Please list rejected sessions (by session code only), these submittors
- ## will be extended courtesies/discounts for their effort:
- ##
- ##
- 
- 
- 
- == Additional Events ==
- 
- ## Small-room (max 50) day of content?  No speaker compensation is attached
- ## to such events.  Attendees must be registered/paid for the conference.
- ## It can be organized as an unconference or other structure, or it can have
- ## a partially or fully spelled out program.  The first deadline to request
- ## this is the end of June, with no deadline yet for its content.
- 
- ## Evening Meetup/BOF's/Other?  No speaker compensation is attached to such
- ## events, they are free to the public.  The first deadline to request
- ## this is the end of July, with no deadline yet for its content.
- 
- 
- 
- == Questions and Answers ==
- 
- == Session Ideas ==
- 
-  * A session (panel w/demo?) on interoperability with representation from Stonehenge, CXF,
and any other WS providers that happen to be at the con (MS, Sun, etc?).
- 
-  * At least one "case study" session with examples of Apache WS technology in real-world
use
- 
-  * A "how it all fits together" session on the architecture of Axis2, the WS-Commons projects,
and the various modules.
- 
-  * An "ask the developers" panel where users can bring up whatever topics they're inspired
to discuss with committers from all the major WS projects
- 
-  * A hands-on intro session about getting started with A2 (like Deepal's quickstart stuff)
-  
-  * An intro session about securing web services with Apache WS projects ( covering WS-Security,
WS - Secure Conversation , WS - Trust , etc)
- 
-  * "Arc Talks" (like lightning but longer-lived :)) about each of the WS-Commons projects
- 
- 
- ----
- CategoryTemplate
- 

Mime
View raw message