RFC 4078: The TV-Anytime Content Reference Identifier (CRID)
In plain English — editorial summary, not part of the RFC
The Uniform Resource Locator (URL) scheme "CRID:" has been devised to allow references to current or future scheduled publications of broadcast media content over television distribution platforms and the Internet. The initial intended application is as an embedded link within scheduled programme description metadata that can be used by the home user or agent to associate a programme selection with the corresponding programme location information for subsequent automatic acquisition. This document reproduces the \%TV-Anytime CRID definition found in the \%TV-Anytime content referencing specification, and is published as an RFC for ease of access and registration with the Internet Assigned Numbers Authority (IANA). This memo provides information for the Internet community.
Document record
- Document ID
- RFC4078
- Published
- May 2005
- Authors
- N. Earnshaw; S. Aoki; A. Ashley; W. Kameyama
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 10
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4195A Uniform Resource Name (URN) Namespace for the TV-Anytime ForumCurrent
October 2005
- RFC 4095Attaching Meaning to Solicitation Class KeywordsCurrent
May 2005
- RFC 3987Internationalized Resource Identifiers (IRIs)Current
January 2005
- RFC 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
- RFC 3966The tel URI for Telephone NumbersUpdated
December 2004
- RFC 3953Telephone Number Mapping (ENUM) Service Registration for Presence ServicesUpdated
January 2005
- RFC 3761The E.164 to Uniform Resource Identifiers (URI) Dynamic Delegation Discovery System (DDDS) Application (ENUM)Obsoleted
April 2004
- RFC 4415IANA Registration for Enumservice VoiceUpdated
February 2006
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?