• Recording Information Notification
Hide navigation
  • Recording Information Notification
    • 1 Introduction
    • 2 Organisation of the Document
    • 3 Normative References
    • 4 Terms and abbreviations
      • 4.1 Terms and definitions
      • 4.2 Abbreviations
    • 5 Choreography
      • 5.1 Overall Choreography
      • 5.2 Cloud-based storage choreography
        • 5.2.1 Introduction
        • 5.2.2 File naming convention
        • 5.2.3 Acknowledgement
      • 5.3 Web Service Choreography
        • 5.3.1 Introduction
        • 5.3.2 Choreography
        • 5.3.3 Personalising the feed
        • 5.3.4 Web Service set-up and authentication
        • 5.3.5 Identifying RIN message senders without authentication
        • 5.3.6 POST RIN Message
      • 5.4 Digitally signing RIN messages
        • 5.4.1 Overview
        • 5.4.2 Signing
        • 5.4.3 Evaluating a signature
    • 6 Syntax and semantics of RIN messages
      • 6.1 Introduction
      • 6.2 Granularity of RIN Messages
      • 6.3 General conformance rules
      • 6.4 Namespace of XML Schema
      • 6.5 Allowed-Value Sets
      • 6.6 Proprietary Identifiers
      • 6.7 Linking RIN messages to audio files
    • Annex A (informative) Release Notes
Show navigation

5.3.3 Personalising the feed

Many recipients of RIN messages will want to receive data from different business partners. In these cases it is essential that the web server of a receiving RIN processor knows who is calling one of its web services.

This can be done with or without formal authentication (see Clauses 5.3.4 and 5.3.5, respectively). The benefit of using formal authentication is that it also allows the two parties to secure their communication.

Search

    Powered by Instant Websites for Confluence