|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
This is an approved document by ATSC (Advanced Television Systems Committee).
|
|
3.
|
Justification for the specific reference:
|
|
|
This document describes the interactive content environment provided by an ATSC 3.0 receiver.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
None
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
None
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Approved in May 2023.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
None
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[1] ATSC: "ATSC Standard: Signaling, Delivery, Synchronization, and Error Protection," Doc./
A/331:2023-03, Advanced Television Systems Committee, Washington, DC, 28 March/
2023./
[2] ATSC: "ATSC Standard: Service Announcement," Doc. A/332:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[3] ATSC: "ATSC Standard: Content Recovery in Redistribution Scenarios," Doc. A/336:2023-/
03, Advanced Television Systems Committee, Washington, DC, 28 March 2023./
[4] ATSC: "ATSC Standard: Application Event Delivery,” Doc. A/337:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[5] ATSC: "ATSC Standard: Captions and Subtitles,” Doc A/343:2023-03, Advanced Television/
Systems Committee, Washington, DC, 28 March 2023./
[6] ATSC: "ATSC Standard: ATSC 3.0 Security and Service Protection," Doc. A/360:2023-03,/
Advanced Television Systems Committee, Washington, DC, 28 March 2023./
[7] CTA: "CTA Specification: Web Application Video Ecosystem – Web Media API Snapshot/
2021", Doc. CTA-5000-D, Consumer Technology Association, Arlington, VA, December/
2021./
[8] CTA: "CTA Bulletin: Recommendations for User Overrides for Closed Caption Decoders",/
Doc. CTA-CEB35, December 2019./
[9] IEEE: "Use of the International Systems of Units (SI): The Modern Metric System," Doc. SI/
10, Institute of Electrical and Electronics Engineers, New York, NY./
[10] IETF: "Augmented BNF for Syntax Specifications: ABNF," Doc. RFC 5234, Internet/
Engineering Task Force, January 2008./
https://tools.ietf.org/html/rfc5234/
[11] IETF: "Hypertext Transfer Protocol (HTTP/1.1): Authentication," Doc. RFC 7235, Internet/
Engineering Task Force, June 2014./
https://tools.ietf.org/html/rfc7235/
[12] IETF: "Hypertext Transfer Protocol (HTTP/1.1): Caching," Doc. RFC 7234, Internet/
Engineering Task Force, June 2014./
https://tools.ietf.org/html/rfc7234/
[13] IETF: "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests," Doc. RFC 7232,/
Internet Engineering Task Force, June 2014./
https://tools.ietf.org/html/rfc7232/
[14] IETF: "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing," Doc. RFC/
7230, Internet Engineering Task Force, June 2014./
https://tools.ietf.org/html/rfc7230/
[15] IETF: "Hypertext Transfer Protocol (HTTP/1.1): Range Requests," Doc. RFC 7233, Internet/
Engineering Task Force, June 2014./
https://tools.ietf.org/html/rfc7233/
[16] IETF: "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content," Doc. RFC 7231,/
Internet Engineering Task Force, June 2014./
https://tools.ietf.org/html/rfc7231/
[17] IETF Internet-Draft: "JSON Schema: A Media Type for Describing JSON Documents",/
September 16, 2019. Work in Progress./
https://tools.ietf.org/html/draft-handrews-json-schema-02/
[18] IETF: "Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet/
Message Bodies," RFC 2045, Internet Engineering Task Force, November 1996./
https://tools.ietf.org/html/rfc2045/
[19] IETF: BCP 47, "Tags for Identifying Languages," Internet Engineering Task Force, Reston,/
VA, September 2009./
https://tools.ietf.org/html/bcp47/
[20] IETF: "The JavaScript Object Notation (JSON) Data Interchange Format," RFC 7159,/
Internet Engineering Task Force, March 2014./
https://tools.ietf.org/html/rfc7159/
[21] IETF: "The Web Origin Concept," RFC 6454, Internet Engineering Task Force, December/
2011./
https://tools.ietf.org/html/rfc6454/
[22] IETF: "The WebSocket Protocol," RFC 6455, Internet Engineering Task Force, December/
2011./
https://tools.ietf.org/html/rfc6455/
[23] IETF: "Uniform Resource Identifier (URI): Generic Syntax," RFC 3986, Internet/
Engineering Task Force, January 2005./
https://tools.ietf.org/html/rfc3986/
[24] IETF: "A Universally Unique IDentifier (UUID) URN Namespace," Doc. RFC 4122, Internet/
Engineering Task Force, July 2005./
https://tools.ietf.org/html/rfc4122/
[25] IETF: "The Base16, Base32, and Base64 Data Encodings," RFC 4648, Internet Engineering/
Task Force, October 2006./
https://tools.ietf.org/html/rfc4648/
[26] ISO/IEC: ISO/IEC 23009-1:2014, "Information technology — Dynamic adaptive streaming/
over HTTP (DASH) — Part 1: Media presentation description and segment formats,"/
International Organization for Standardization, 15 May 2014./
[27] W3C: "Encrypted Media Extensions," W3C Recommendation, World Wide Web/
Consortium, 18 September 2017./
http://www.w3.org/TR/encrypted-media//
[28] W3C: "UI Events KeyboardEvent key Values," Section 3.18, Media Controller Keys, W3C/
Candidate Recommendation, 1 June 2017, World Wide Web Consortium./
https://www.w3.org/TR/DOM-Level-3-Events-key/#keys-media-controller/
[29] W3C: "Media Source Extensions," W3C Recommendation, World Wide Web Consortium,/
17 November 2016./
https://www.w3.org/TR/media-source//
[30] W3C: "Mixed Content," W3C Candidate Recommendation, Worldwide Web Consortium, 2/
August 2016. (work in process)./
http://www.w3.org/TR/mixed-content//
[31] W3C: "XML Schema Part 2: Datatypes Second Edition," W3C Recommendation,/
Worldwide Web Consortium, 28 October 2004./
https://www.w3.org/TR/xmlschema-2//
[32] WHATWG: "Living Standard", "Fetch Commit Snapshot", 30 November 2020:/
https://fetch.spec.whatwg.org/commitsnapshots/eda41525e3b462ce2035dd3cfc4a6ec1fc093c1d//
[33] WHATWG: "HTML Living Standard," Section 4.8.3 "The img element," Web Hypertext/
Application Technology Working Group./
https://html.spec.whatwg.org/multipage/embedded-content.html#attr-img-src/
For WHATWG living standards, while it is recommended that implementations support the/
living standard, they must support the snapshot version of each WHATWG standard at the time of/
the earliest commit in 2020./
[34] ATSC: “ATSC Standard: System Discovery and Signaling,” Doc. A/321:2023-03, Advanced/
Television Systems Committee, Washington, DC, 28 March 2023./
[35] ATSC: “ATSC Standard: Link Layer Protocol,” Doc. A/330:2023-03, Advanced Television/
Systems Committee, Washington, DC, 28 March 2023.
|
|
9.
|
Qualification of
ATSC:
|
|
|
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
