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).
22.214.171.124 The Registry Approach 126.96.36.199 The Index Approach 188.8.131.52 Peer-to-Peer (P2P) Discovery 184.108.40.206 Discovery Service Trade-Offs 3.4.3 Federated Discovery Services 3.4.4 Functional Descriptions and Discovery 3.5 Web Service Semantics 3.5.1 Message semantics and visibility 3.5.2 Semantics of the Architectural Models 3.5.3 The Role of Metadata 3.6 Web Services Security 3.6.1 Security policies 3.6.2 Message Level Security Threats 220.127.116.11 Message Alteration 18.104.22.168 Confidentiality 22.214.171.124 Man-in-the-middle 126.96.36.199 Spoofing 188.8.131.52 Denial of Service 184.108.40.206 Replay Attacks 3.6.3 Web Services Security Requirements 220.127.116.11 Authentication Mechanisms 18.104.22.168 Authorization 22.214.171.124 Data Integrity and Data Confidentiality 126.96.36.199 Integrity of Transactions and Communications 188.8.131.52 Non-Repudiation 184.108.40.206 End-to-End Integrity and Confidentiality of Messages 220.127.116.11 Audit Trails 18.104.22.168 Distributed Enforcement of Security Policies 3.6.4 Security Consideration of This Architecture 22.214.171.124 Cross-Domain Identities 126.96.36.199 Distributed Policies 188.8.131.52 Trust Policies 184.108.40.206 Secure Discovery Mechanism 220.127.116.11 Trust and Discovery 18.104.22.168 Secure Messaging 3.6.5 Privacy Considerations 3.7 Peer-to-Peer Interaction 3.8 Web Services Reliability 3.8.1 Message reliability 3.8.2 Service reliability 3.8.3 Reliability and management 3.9 Web Service Management 3.10 Web Services and EDI: Transaction Tracking 3.10.1 When Something Goes Wrong 3.10.2 The Need for Tracking 3.10.3 Examples of Tracking 3.10.4 Requirements for Effective Tracking 3.10.5 Tracking and URIs 4 Conclusions 4.1 Requirements Analysis 4.2 Value of This Work 4.3 Significant Unresolved Issues A Overview of Web Services Specifications (Non-Normative) B An Overview of Web Services Security Technologies (Non-Normative) B.1 XML-Signature and XML-Encryption B.2 Web Services Security B.3 XML Key Management Specification (XKMS) 2.0 B.4 Security Assertion Markup Language (SAML) B.5 XACML: Communicating Policy Information B.6 Identity Federation C References (Non-Normative) D Acknowledgments (Non-Normative) Web services provide a standard means of interoperating between different software applications, running on a variety of platforms and/or frameworks.
This document (WSA) is intended to provide a common definition of a Web service, and define its place within a larger Web services framework to guide the community.
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.