XMLTV / applied guide-data decisions · 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 the layer being edited
A URL can be stored as text or an attribute inside an XML guide. The XML representation and the eventual URL value are different layers. When a parser reports an entity-related error, do not immediately rewrite the provider’s query into a different address. First determine whether the surrounding XML was serialized correctly.
Use a harmless illustrative value
Suppose an illustrative address has two query fields joined by an ampersand. In the XML source, the ampersand must be represented appropriately, commonly as &, so the parser can recover the intended character value. That is not the same operation as replacing a reserved character with a percent-encoded sequence inside the URI. The intended value after parsing is the comparison that matters.
Avoid repeated manual conversions
Applying escaping twice can leave literal escape text where an application expected a character, while decoding at the wrong layer can break the document structure. Preserve a private original and use an XML-aware serializer for generated output. A global search-and-replace through a credential-bearing feed can introduce errors that are harder to diagnose than the original parser message.
Verify both structure and recovered value
After a permitted correction, parse the XML and compare the recovered sanitized URL components with the intended value. Keep authentication secrets out of examples or public validators. This article explains serialization layers using the XML and URI specifications; it supplies no UK IPTV feed credentials or claim that changing a query activates access.