• Transfer of Catalogues of Releases and Resources by Reassignment of Rights Controller Information
Hide navigation
  • Transfer of Catalogues of Releases and Resources by Reassignment of Rights Controller Information
    • 1 Introduction
    • 2 Organisation of the document
    • 3 Normative references
    • 4 Terms and abbreviations
      • 4.1 Terms and definitions
      • 4.2 Abbreviations
    • 5 Message choreography
      • 5.1 Overall choreography
      • 5.2 Main cycle
        • 5.2.1 Step 1
        • 5.2.2 Step 2
        • 5.2.3 Step 3
        • 5.2.4 Step 4
      • 5.3 Confirmation cycle
        • 5.3.1 Introduction
        • 5.3.2 Step 1
        • 5.3.3 Step 2
        • 5.3.4 Step 3
      • 5.4 Summary
    • 6 Message definition
      • 6.1 Namespace
      • 6.2 Structure and content of the CatalogTransferMessage
        • 6.2.1 Structure
        • 6.2.2 Rules for initial CatalogTransferMessages
        • 6.2.3 Rules for update CatalogTransferMessages
      • 6.3 Structure and content of the CatalogTransferConfirmation
      • 6.4 Structure and content of the AcknowledgementMessage
      • 6.5 Syntax and semantics of messages
      • 6.6 Allowed value sets
      • 6.7 Namespace attribute
      • 6.8 Schema validation
      • 6.9 Indicating unknown values
      • 6.10 Contractually mandatory
      • 6.11 MessageID
    • 7 Message exchange protocol
Show navigation

6.5 Syntax and semantics of messages

The syntax and semantics of the messages defined in this standard are provided in an XSD file. The XSD is an integral part of this standard and can be accessed here. This includes the allowed value sets as specified in Clause 6.6.

A structural feature of the XSD is the cardinality for each field. These are:

  • 1-n means one or more;

  • 1 means exactly one;

  • 0-1 means none or one; and

  • 0-n means none to multiple.

Search

    Powered by Instant Websites for Confluence