[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Candidate Frequently Asked Questions for the OASIS web site
The following FAQ's were provided by Alan Weissberger in his White paper. We should discuss these on email and on the call. OASIS Staff want us to give them a set of FAQs to put on the web site. -------------------- . Frequently Asked Questions 1. Who is participating in the OASIS WSRM TC and how often do they meet? A variety of companies are active in the WSRM TC. The members include: Booz Allen Hamilton, BT, Cyclone Commerce, Fujitsu (3), Hewlett-Packard, Hitachi(3), NEC Corporation(2), Novell, Oracle (3), SAP, See Beyond, SUN Micro (2), University of Hong Kong. There are also many observers. Membership in OASIS is required to participate in the WSRM TC. Telecon meetings are held weekly and face-to-face meetings are held about every two or three months. 2. When will the WS Reliability spec be completed and what is it based on? Agreement was reached in Nov 2003 on a committee draft spec (v0.52), which was implemented in a demo at the Philadelphia XML Conference, in February 2004. The TC has recently voted on a committee draft spec (v.0.992) which is out for public review, to complete on April 19, 2004. Note that the spec is based on Requirements issues that have been compiled for the committee’s internal use (over 100 requirements have been identified). - An OASIS standard could be approved in the 2nd Quarter of 2004, after the public review. 3. Who participated in the demo of WS Reliability? Fujitsu, Hitachi, NEC, Oracle, and SUN Micro. The demo was based on v0.52 of the spec. 4. Who will benefit from the completed WS Reliability spec? • WS middleware companies that implement the spec will benefit because it will be universally interoperable. Initial testing can be done with any company that implements it. The license to implement the spec is royalty free. • Application program developers will also benefit, as their web based applications will be reliable and robust, operating over WS Reliability middleware. Using the implemented middleware will also be royalty free. • WS End users will benefit in accordance with their application requirements. For example, “at most once delivery” implies duplicate elimination. This is important for placing orders, banking transactions, and insurance claims processing. If an end user is sending a Purchase Order, for example, he wants to know it actually arrived at the destination and it arrived exactly once (not multiple times). This is particularly vital for financial applications. 5. Who will generate application specific profiles for the WS Reliability spec? WS-I will most likely develop such profiles. The WS-I Requirements Working Group has already discussed doing this upon completion of the spec. -- ---------------------------------------------------- Tom Rutt email: tom@coastin.com; trutt@fsw.fujitsu.com Tel: +1 732 801 5744 Fax: +1 732 774 5133
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]