The convention bureau's English homepage lists different sponsors than its public translated subdomain. What should collection cover?
Select an answer to reveal the explanation.
Short Explanation
Language versions are separate storefronts, not carbon copies. If English and the translated subdomain tell different sponsor stories, collect both. Skipping the live localized URL hides a real public split.
Full Explanation
When the convention bureau’s English homepage lists different sponsors than its public translated subdomain, collection should cover each public language version because localized civic pages can diverge. Language versions are separate storefronts that may show inconsistent commercial or partnership claims. Collecting only the English site because translations are never authoritative fails; translated pages are live public civic (or bureau) content residents may rely on. Using a machine translation of the English page while skipping the live localized URL fails by inventing text and missing what was actually published. Changing the translated subdomain so sponsor lists are forced to match fails as unauthorized content modification outside OSINT. Exam caveat: divergence may be outdated translation or intentional market differences—report the difference, do not silently “fix” it. Operational check: capture both language URLs and sponsor lists with dates; deliver a divergence brief to the bureau for correction or explanation. In municipal practice, record the rationale in the case file so future staff know which control was chosen and which failure modes the rejected options would create for city services.