XMLTV / worked schedule interpretation · Primary-source explanation; no UK IPTV implementation or account test. Instructions are based on publisher guidance; a UK IPTV account was not tested on this platform.
Identify what the field expects
A player asking for guide data may not accept the supplier’s ordinary website homepage. Before pasting an address, establish whether the control expects machine-readable XMLTV, another supported format or a publisher-specific setup. A page explaining how a feed works is useful documentation, but it is not automatically the feed body itself.
Read the source metadata roles
The XMLTV DTD describes source-info-url as a human-readable information address and source-data-url as the place the actual data is obtained. It notes that source situations can vary, so a field name is context rather than a universal download recipe. Preserve the supplier’s legitimate instructions and do not fabricate a new endpoint by adding an XML extension to a homepage.
Use a hypothetical mistaken copy
Suppose a guide export cites a help page explaining an authorised subscription route. Copying that help-page address into a parser can return a perfectly readable HTML document instead of programme data. The result does not show that the television’s EPG offset is wrong. The next step is to confirm the intended data route with the responsible publisher, keeping credentials private.
Verify the received document deliberately
For the actual supported input, confirm the response type, expected guide structure and applicable account access without posting private URLs to a public checker. Keep successful download, successful parsing and correct channel mapping as separate observations. This article explains source-reference roles; it supplies no working UK IPTV feed endpoint or guarantee of third-party data access.