Incremental updating algorithm association rules


A list of remaining open issues is included in 4 Conclusions.Patent disclosures relevant to this specification may be found on the Working Group's patent disclosure page.

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).

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).

3.4.2.1 The Registry Approach 3.4.2.2 The Index Approach 3.4.2.3 Peer-to-Peer (P2P) Discovery 3.4.2.4 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 3.6.2.1 Message Alteration 3.6.2.2 Confidentiality 3.6.2.3 Man-in-the-middle 3.6.2.4 Spoofing 3.6.2.5 Denial of Service 3.6.2.6 Replay Attacks 3.6.3 Web Services Security Requirements 3.6.3.1 Authentication Mechanisms 3.6.3.2 Authorization 3.6.3.3 Data Integrity and Data Confidentiality 3.6.3.4 Integrity of Transactions and Communications 3.6.3.5 Non-Repudiation 3.6.3.6 End-to-End Integrity and Confidentiality of Messages 3.6.3.7 Audit Trails 3.6.3.8 Distributed Enforcement of Security Policies 3.6.4 Security Consideration of This Architecture 3.6.4.1 Cross-Domain Identities 3.6.4.2 Distributed Policies 3.6.4.3 Trust Policies 3.6.4.4 Secure Discovery Mechanism 3.6.4.5 Trust and Discovery 3.6.4.6 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.