Format scope and product scope differ
Tvheadend's documentation explicitly describes a recognised subset of XMLTV tags and attributes. That statement concerns the product's input handling. It is not a claim that all other fields are invalid in the underlying format or that another application must omit the same information.
Imagine a guide includes titles, descriptions and additional artwork metadata. One application displays the first two and ignores the artwork. A comparison that labels the whole guide broken would discard successful listing information and miss the narrower field-coverage question.
Check the exact field and purpose
Retain the element or attribute, its position in the record and the expected application display. A series title, episode subtitle, category and content rating can serve different purposes. Moving text arbitrarily between fields to force one interface can damage semantics for other supported importers.
A publisher should follow the current format and the receiving product's documented input requirements. If a necessary field is unsupported, ask about a supported alternative or feature request instead of assuming the parser can be persuaded by repeated refreshes. A refresh cannot implement a metadata field the application does not use.
Keep a minimum useful reproduction
An authorised developer can use a small nonprivate example containing the relevant field and enough programme context to demonstrate the issue. Preserve names and identities only where needed, and remove account-bearing source addresses. Do not post a complete private household guide merely to show one missing label.
Record the importer version, source retrieval result and fields that did appear. That evidence distinguishes partial metadata coverage from a parse failure or wrong channel mapping. This guide uses product documentation to explain the distinction; it does not claim IPTV Australia runs Tvheadend, supplies a tested XMLTV feed or verified every field in a real installation.
Questions about this guide
Does one ignored field make the entire guide invalid?
No. It can reflect a product’s supported metadata subset.
Can repeated refreshes add unsupported field handling?
No. The importer needs an implementation or a documented supported alternative.