US Letters of Direction Choreography
Hide navigation
US Letters of Direction Choreography
1 Introduction
2 Scope
2.1 Introduction
2.2 Organisation of the Document
3 Normative References
4 Terms and Abbreviations
4.1 Terms and Definitions
4.2 Abbreviations
5 US Letters of Direction Choreography
5.1 Direct Communication
5.1.1 Core Choreography
5.1.2 Extended Choreography
5.2 Communication via a Hub
5.3 Disputing Letters of Direction
5.4 Scope of Message
5.5 Cover Letter for Letter of Direction cycle (informative)
5.6 Communicating Resource and Release Information to Licensees
5.6.1 Full Catalogue Transfers
5.6.2 Partial Catalogue Transfers
5.6.3 Ingestion of a LoDMessage information
5.7 Processes when receiving a message regarding a catalogue transfer (informative)
5.8 SFTP Choreography
5.8.1 Introduction
5.8.2 Folder Naming Convention
5.8.3 XML File Naming Convention
5.8.4 Supporting File Naming Convention
5.8.5 Manifest
5.8.6 Acknowledgement
5.8.7 Size of Batch
5.8.8 Hybrid Batches
5.9 Web Service Choreography
5.9.1 Introduction
5.9.2 Asymmetric Choreography
5.9.3 Symmetric Direct Choreography
5.9.4 Choreography via a Hub
5.9.5 URLs
5.9.6 Personalising the Feed
5.9.7 Web Server Set-up and Authentication
5.9.8 Identifying Web Service Callers Without Authentication
5.9.9 Web Service Commands
5.9.9.1 POST LoD
5.9.9.2 POST LoDConfirmation
5.9.9.3 GET LoDList
5.9.9.4 GET LoDConfirmationList
5.9.9.5 GET LoD
5.9.9.6 GET LoDConfirmation
6 Syntax & Semantics of Messages
6.1 Introduction
6.2 General Conformance Rules
6.2.1 Schema Validation
6.2.2 Namespace
6.2.3 Allowed Value Lists
6.2.4 Contractually Mandatory
6.2.5 Character Coding
6.3 Definition of Messages
6.4 Allowed Value Sets
Show navigation
6.3 Definition of Messages
The messages are defined in an XML Schema available
here
.
Search
x