Diamond 2 Programme Data Exchange (PDX) Schema v1.0 — POST-TX (Publications) This schema defines the XML structure for exchanging transmission data (POST-TX) between broadcasters and Diamond 2 / TEP (The Everyone Project). This is the standalone POST-TX schema. The Document root element accepts only Publications data. For PRE-TX (Programmes), see Diamond2_PreTX_v1.1.xsd. Date: 12.04.26 Version: 5.2 XSD Version: 1.0 Note: Some business rule constraints (e.g., conditional requirements when remove="true", WindowClosureDateTime only valid for onDemand, at most one SubChannel per ChannelPlatform may carry isCore="true") cannot be enforced by XSD 1.0 and are documented within the schema. These constraints will be validated by TEP during XML ingestion. Element Ordering: Ideally, this schema would allow all child elements to appear in any order. However, due to limitations in XSD 1.0, containers with repeating child elements (maxOccurs > 1) must use xs:sequence which mandates element order. Where possible (Publication type), xs:all has been used to allow flexible ordering. For containers that contain repeating elements (e.g., multiple ChannelPlatforms), element order must follow the schema definition, though in practice this typically reflects the natural/logical ordering anyway. Optional identifier for broadcaster's internal use. Not ingested into TEP. Optional creation timestamp. Optional update timestamp. Required date and time of publication/transmission. Optional closure date/time for on-demand availability window. Valid only when availabilityMode="onDemand". If omitted, interpreted as indefinite availability. Can be added/updated later by resubmitting with same publicationId. Required reference to the episode ID from the Pre-TX metadata. Note: If your transmission tracking system uses version IDs (e.g., episode123/01, episode123/02), remove the version suffix to provide just the episode ID (e.g., episode123). Publication availability mode. Optional broadcaster's unique ID for this publication event. Allows corrections to publication event data. Can be omitted if no scope for editing/corrections. Optional boolean indicating whether this is a repeat transmission/publication. Values: true (repeat) or false (first transmission/publication). If omitted, the first publication record received will be automatically treated as first (isRepeat=false). IMPORTANT: If your transmission records may be sent out of chronological order (i.e., a later transmission sent before an earlier one), do not omit this attribute, as the first record received will be marked as first transmission regardless of its actual transmission date. Optional boolean indicating whether this is the primary transmission/publication for reporting purposes. Values: true (primary) or false (not primary). The primary publication is typically the most important broadcast (e.g., peak-time transmission rather than an overnight repeat). If omitted, the first publication that is treated as first (isRepeat=false or inferred as such) will be automatically marked as primary. Set to "true" to delete a previously submitted publication record. When removing, only the publicationId attribute is required — all other attributes and child elements should be omitted. Represents a channel or platform on which the content was published. Multiple ChannelPlatform elements can be included if the publication was broadcast on multiple channels simultaneously. Required sub-channel identifying the core network feed or a regional variant. Every ChannelPlatform must include at least one SubChannel. Use isCore="true" to mark the core network feed; additional SubChannel elements represent regional variants (e.g., BBC One Wales, BBC One Scotland). Required human-readable sub-channel label (e.g., "Network", "Wales", "Scotland", "HD"). Optional sub-channel identifier. If omitted, defaults to the value of the label attribute. Set to "true" to indicate this SubChannel represents the core network feed (i.e., the content that goes out across the whole network rather than a regional opt-out). At most one SubChannel per ChannelPlatform may carry isCore="true". Omit or set to "false" for regional sub-channels. Note: The "at most one isCore per ChannelPlatform" constraint cannot be enforced by XSD 1.0 and is validated server-side by TEP. Required human-readable channel/platform label (e.g., "BBC One", "iPlayer", "ITV1"). Optional channel identifier. If omitted, defaults to the value of the label attribute.