Start Feedback and updating mechanism for procedures

Feedback and updating mechanism for procedures

A list of remaining open issues is included in 4 Conclusions.

This publication as a Working Group Note coincides with the end of the Working Group's charter period, and represents the culmination of the group's work.

Discussion of this document is invited on the public mailing list [email protected](public archives).

Expected readers include Web service specification authors, creators of Web service software, people making decisions about Web service technologies, and others.

This document has two main sections: a core concepts section (2 Concepts and Relationships ) and a stakeholder's perspectives section (3 Stakeholder's Perspectives).

The WSA describes both the minimal characteristics that are common to all Web services, and a number of characteristics that are needed by many, but not all, Web services.

The Web services architecture is an This document is intended for a diverse audience.

The aim here is to demonstrate that Web services can be made secure and indicate which key concepts and features of the architecture achieve that goal.

The key stakeholder's perspectives supported in this document reflect the major goals of the architecture itself: interopability, extensibility, security, Web integration, implementation and manageability.

For the purpose of this Working Group and this architecture, and without prejudice toward other definitions, we will use the following definition: [Definition: A Web service is a software system designed to support interoperable machine-to-machine interaction over a network.

It has an interface described in a machine-processable format (specifically WSDL).

Using this assertion as a basis, we can assess conformance to the architecture of a particular resource by looking for its identifier.