This charter is an updated version of the 2002-01-26 charter: it reflects the change of chairs which occurred on 22 July 2002. No other modification has been made.
The advent of XML makes it easier for systems in different environments to exchange information. The universality of XML makes it a very attractive way to communicate information between programs. Programmers can use different operating systems, programming languages, etc, and have their software communicate with each other in an interoperable manner. Moreover, XML, XML namespaces and XML schemas serve as useful tools for providing mechanisms to deal with structured extensibility in a distributed environment, especially when used in combination.
The same way programmatic interfaces have been been available since the early days of the World Wide Web via HTML forms, programs are now accessible by exchanging XML data through an interface, e.g. by using SOAP Version 1.2, the XML-based protocol produced by the XML Protocol Working Group. The services provided by those programs are called Web services.
The power of Web services, apart from their great interoperability and extensibility thanks to the use of XML, is that they can then be combined in order to achieve more complex operations.
In order to get a complete automation of such interactions, the architecture of Web services needs to be better understood, and several technologies need to be developed.
Several proposals have been published by different organizations to address different parts of the required task. The goal of the Web Services Architecture Working Group is to lay out a coherent architecture, by producing architectural documents and advising W3C regarding work in the Web services area.
The remainder of this section describes in detail the requirements and deliverables of Web Services Architecture Working Group, part of the Web Services Activity.
The area of Web services is broad. Many different functionalities are required in order to obtain a fully automated, functional, distributed system. The Working Group is tasked to come up with a document which will describe the architecture of Web Services.
The following goals are sought:
Keys to the success of Web services are privacy and security. The Working Group will assess how these need to be addressed.
The architecture document will identify the technologies necessary for Web services to be used, described, discovered, how Web services interact with each other (such as long-time conversations, routing, composition, ...), etc. The Working Group will use the conclusions reached during the Web services workshop as an input for this work. The Working Group should also identify what existing W3C technologies already address functions required by the architecture identified.
In particular, the Working Group will clearly delimit the boundaries of each identified component, and model the interfaces between them, so that the scope of new Working Groups created to address each piece of is unambiguously defined.
The Working Group will also provide a model of the various Web services concepts used in the various Working Groups in order to ensure that the various specifications actually work together and use the same concepts and terminology. The Working Group may also suggest a glossary used by Web Services specifications in order to ensure the consistency of Web Services terms.
The Working Group will also assess the relationship with the work conducted in the Semantic Web Activity.
The Working Group shall start by developing a requirements document detailing and refining the scope of its work.
The Working Group will describe a detailed architecture. However, it is out of the scope of the Working Group to design the technologies suggested. The Working Group should describe those identified technologies by defining their scope.
Those descriptions will be used as input by the Web Service Coordination Group for the chartering of new Working Groups at a later date.
The W3C Web Services Activity is chartered with developing a set of technologies which will lead Web services to their full potential.
The architecture document produced by the Web Services Architecture Working Group will be of crucial importance to the future developments of the Web Services Activity.
Working Groups developing Web services technology must coordinate with the Web Services Architecture Working Group in order to keep a coherent overall architecture. This is why the high-level view developed by the Working Group will be influenced by work happening in other Working Groups, particularly the ones under the Web Services Activity.
Such coordination will take place in the Web Services Coordination Group; its task is to coordinate efforts in the Web Services Activity and other related groups. The Coordination Group will use the architecture document produced by the Web Services Architecture Group as a guide for its decisions.
Even though it is likely that some proposals made by independent parties are already trying to address some of the architecture that the Working Group will come up with, not all those areas will be ready for standardization at the same time.
The Web Services Architecture Working Group will be developing and maintaining a roadmap. Input gathered at the Coordination Group level will be used to provide such a deliverable.
These are subject to revision due to editorial needs and external scheduling issues; updates will be negotiated with the related groups and recorded on the Web Services Architecture Working Group home page. Meeting dates are mentioned here for planning purposes.
The expected duration of the Working Group is 2 years, through January 2004.
XML and XML-derived activities have become a strategic technology in W3C and elsewhere. Each deliverable of any Working Group must satisfy the dependencies from other W3C Working Groups before it can advance to Candidate Recommendation.
The Web Services Description Working Group will take the architecture document produced by the Web Services Architecture Working Group into account while developing its description language.
The Web Services Coordination Group, as well as new Working Groups formed under the Web Services Activity, will also pay particular attention to the documents produced by the Web Services Architecture Working Group.
The Web Services Architecture Working Group should liaise with at least the following groups outside W3C:
To join the Web Services Architecture Working Group, please follow the instructions of section 4.2.3 of the Process Document, sending email to the Working Group Chair and the W3C Team contact. The nomination must include explicit agreement to this charter, including its goals, an IPR disclosure and the level of effort required of the representative.
Each Member organization may have at most two participants in the Working Group. Only Working Group participants may engage in formal votes on substantive issues. When a formal vote is required, each Member organization or group of related Members is allowed one vote, even though the Member may have several participants in the Working Group.
The W3C Team is expected to have at most two participants in the Working Group (including the Team contact). When a formal vote is required, the Team is allowed one vote.
Membership is also open to invited experts from the community, selected by the Chair in order to balance the technical experience of the group.
Each participant should expect to spend one day per week on work for this Working Group.
The Working Group will utilize a public mailing list <email@example.com> for its technical email communications. It is referred to in the rest of this document as the Working Group mailing list.
A Member-only mailing list <firstname.lastname@example.org> is available for administrative purposes only.
The Working Group has a home page that records the history of the group, provides access to the archives, meeting minutes, updated schedule of deliverables, membership list, and relevant documents and resources. The page will be available to the public and will be maintained by the Chair in collaboration with the W3C team contact.
The Working Group will have distributed and face-to-face meetings.
A one to two hour Working Group distributed meeting will be held every week. When necessary to meet agreed-upon deadlines, distributed meetings may be held twice a week.
The Working Group may schedule face-to-face meetings in a manner that maximizes co-location with events that Working Group members would be attending anyway.
Participation in meetings (distributed or face-to-face) is limited to participants in good standing and individuals invited at the discretion of the Chair to specific meetings.
Decisions taken in meetings must be announced on the Working Group mailing list. Observers may take part in decision-making at the discretion of the Chair.
Meeting records must include attendance, the results of group decisions, and action items. They must be made publicly available except for non-technical issues that do not directly affect the output of the Working Group. The Chair will decide which issues are not made public.
To be successful, we expect the Working Group to have approximately 10 to 15 active participants. A large public review group that will participate in the mailing list discussions is expected.
The Chair for the Web Services Architecture Working Group will be Christopher Ferris (Sun Microsystems).
Note: The new Chairs for the Web Services Architecture Working Group are Michael Champion (Software AG) and Dave Hollander (Contivo) effective 22 July 2002.
Initially, the Team will only have one participant in the Working Group, the Team contact. Hugo Haas will be full-time Team contact for both the Web Services Architecture Working Group and Web Services Coordination Group.
W3C promotes an open working environment. Whenever possible, technical decisions should be made unencumbered by intellectual property right (IPR) claims. W3C's policy for intellectual property is set out in section 2.2 of the W3C Process document.
Members of the Working Group are expected to disclose any intellectual property they have in the area. This WG will work on a royalty-free basis, as defined in the W3C Current Patent Practice document. The Working Group is thus obliged to produce a specification which relies only on intellectual property available on a royalty-free basis.
If it proves impossible to produce specifications implementable on a royalty-free basis, then a Patent Advisory Group will be launched as described in the W3C Current Patent Practice document.
Members disclose patent and other IPR claims by sending email to <email@example.com>, an archived mailing list that is readable by Members and the W3C Team. Members must disclose all IPR claims to this mailing list but they may also copy other recipients. IPR disclosures are expected to be made public; Members should specify if their disclosure is confidential.