The Service List Registry represents provenance information to describe the stated origin, jurisdiction, and contextual authority of service lists used in service discovery.
Provenance metadata enables users, implementers, and regulators to understand where service lists come from, who is asserting them, and the context in which they are intended to be used. This supports transparency and informed interpretation, without prescribing outcomes or decision-making.
The purpose of provenance is to make the source and asserted authority of service lists visible, while leaving responsibility for policy, legality, and editorial judgement with the appropriate parties.
By exposing provenance information consistently, the Service List Registry enables downstream systems and users to distinguish between different kinds of service lists, including those that reflect public or regulatory intent.
Provenance applies to the origin of a service list, the jurisdiction under which it is asserted, and any designation claimed by the submitting party or authority.
It does not assess the contents of service lists, determine their quality or completeness, or evaluate compliance with laws, regulations, or policy objectives.
Service lists may be made available by a range of parties, including broadcasters, platform operators, industry bodies, and public authorities.
Provenance information reflects assertions made by the submitting party or by a competent authority and is recorded and exposed by the Service List Registry as provided.
The Service List Registry records provenance as asserted and does not create or assign authoritative status.
In some cases, service lists are designated to reflect the intent of a recognised public authority acting within a defined jurisdiction. Such designation may arise from national regulation, public policy frameworks, or formally recognised mandates.
Where designation is explicit and attributable, provenance metadata may indicate that a service list reflects regulatory or public authority intent.
The significance of such designation derives from the authority and jurisdiction of the body making the designation, rather than from the presence of a label or flag alone.
Provenance information is always associated with a specific jurisdiction or set of jurisdictions under which a service list is asserted or designated.
A service list may indicate one or more target countries for discovery or relevance. Targeting or availability in multiple territories does not, in itself, imply regulatory designation or jurisdiction in those territories.
Where multiple service lists exist for the same territory, provenance metadata does not imply exclusivity, precedence, or obligation beyond what is explicitly defined by the relevant authority.
Provenance information provides context about origin and designation, but does not imply:
The Service List Registry applies provenance mechanisms conservatively and focuses on faithful representation of asserted information.
The platform does not:
Provenance information is documented, attributable, and auditable.
Where appropriate, references to the asserting authority, designation, or published framework may be provided alongside service list metadata.