RFC 5328: A Uniform Resource Name (URN) Namespace for the Digital Video Broadcasting Project (DVB)
In plain English — editorial summary, not part of the RFC
This document describes a Uniform Resource Name (URN) namespace for the Digital Video Broadcasting Project (DVB) for naming persistent resources defined within DVB standards. Example resources include technical documents and specifications, eXtensible Markup Language (XML) Schemas, classification schemes, XML Document Type Definitions (DTDs), namespaces, style sheets, media assets, and other types of resources produced or managed by DVB. This memo provides information for the Internet community.
Document record
- Document ID
- RFC5328
- Published
- September 2008
- Authors
- A. Adolf; P. MacAvock
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
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 3614A Uniform Resource Name (URN) Namespace for the Motion Picture Experts Group (MPEG)Current
September 2003
- RFC 5393Addressing an Amplification Vulnerability in Session Initiation Protocol (SIP) Forking ProxiesCurrent
December 2008
- RFC 5464The IMAP METADATA ExtensionCurrent
February 2009
- RFC 5174A Uniform Resource Name (URN) Namespace for the European Broadcasting Union (EBU)Current
May 2008
- RFC 5616Streaming Internet Messaging AttachmentsCurrent
August 2009
- RFC 4916Connected Identity in the Session Initiation Protocol (SIP)Current
June 2007
- RFC 5791RFC 2731 ("Encoding Dublin Core Metadata in HTML") Is ObsoleteCurrent
February 2010
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?