Demo

The interactive demonstration shows how requests to the Service List Registry can be constructed to access lists of available audiovisual media services. A client device, display, agent, or application can use queries like these to discover and access compatible services that are relevant to the user context.

  1. Providers - Select optional query Parameters and then Submit request to retrieve a list of matching service provider offerings. Select an Offering to view details and set the list address for the next step.
  2. Lists - For a selected offering, Submit request to retrieve a list of available services. Select a Service to view details and available service instances.

1Get provider offerings

Providers

Parameters

Only nationally regulated services

Offerings

Offering detail

2Get list of services

Lists

 

Services

Service detail

Notes

Providers
The parameter values and responses returned and any visual representations are for demonstration purposes only and do not imply the participation, registration or availability of specific services.
URL
The URL or Uniform Resource Locator is used to request a response to the Service List Registry query.
Protocol
The HTTPS secure protocol must be used for all queries to provide privacy and security by automatically encrypting every request and response over a secure connection.
Method
The GET HTTP method requests a representation of the specified resource. Requests using GET should only be used to request data and should not contain a body.
Server
The server domain may be selected from a list of available options.
Parameters
Multiple parameters may be provided in a query, presented in the specified order. Where a parameter is not included in the query, the response will include results matching any or no value for that parameter.
Values
Multiple values may be provided for a parameter, presented in alphabetic order. The parameter key is repeated followed by square brackets encoded as %5B%5D. The response will combine matches to any of the values provided and will also include results with no specified value for that parameter.
Case
All query parameters and values are case sensitive and will be compared accordingly by the server. The capitalisation used here is defined by specification and alternative forms are invalid.
Offerings
The XML response is rendered for more convenient viewing in Results or as a formatted Body. The relevant Headers and Timing details can be viewed in separate tabs. The raw response body can also be viewed in a new browser window. The response body contains a list of zero or more service offerings that match the supplied query parameters. These are returned in alphabetical order. If no offerings match the query parameters, an empty list is returned.
Offering detail
Selecting an item in the Offerings Results tab will display further information about the offering in the Offering Detail pane. This includes information about the service provider and the offering.
Services
When an offering is selected in the Offerings Results tab, the service list can be requested. The response is rendered in the panel below. Any regional variations of a service list will be presented in a hierarchical list of regions. Selecting a region will request a service list for that region. If there are no regional variations, the default list of services will be presented.
Service detail
Selecting a service in the Services Results tab will display further information about the service in the Service Detail pane. This includes information about the service and any available instances of that service.
Status
The status of a response will be indicated by an HTTP response status code returned in the header.
200 OK
Returned for a successful request.
400 Bad Request
Returned if the request is invalid.
Size
The size of the response body is shown as a character count. This reflects how much data the client receives and processes, even if the response is compressed or cached.
Timing
The time taken to process the request is indicated in milliseconds. This depends on many factors including client location and network conditions but it is typically less than a second. Previous responses cached by the browser may be displayed almost immediately.