⌕ Поиск по атласу

IETF · RFC · RFC8820

RFC8820 · URI Design and Ownership

URI Design and Ownership

Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme." In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of substructure in URIs is often problematic. This document provides guidance on the specification of URI substructure in standards. This document obsoletes RFC 7320 and updates RFC 3986.

Официальная английская аннотация

Section 1.1.1 of RFC 3986 defines URI syntax as "a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme." In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of substructure in URIs is often problematic. This document provides guidance on the specification of URI substructure in standards. This document obsoletes RFC 7320 and updates RFC 3986.

Связи документа

obsoletes: RFC7320

updates: RFC3986

is_also: BCP190

Официальный источник · 2020-06-01

Полные импортированные сведения карточки
{
  "id": "RFC8820",
  "number": 8820,
  "title_en": "URI Design and Ownership",
  "title_ru": "",
  "summary_ru": "",
  "purpose_ru": "",
  "use_ru": "",
  "full_translation_path": "",
  "full_translation_checked_at": "",
  "full_translation_source_sha256": "",
  "architect_note_ru": "",
  "topics_ru": [],
  "translation_state": "not_prepared",
  "verification_level": "not_prepared",
  "verification_level_ru": "Русская выжимка не подготовлена",
  "verification_note_ru": "",
  "abstract_en": "Section 1.1.1 of RFC 3986 defines URI syntax as \"a federated and extensible naming system wherein each scheme's specification may further restrict the syntax and semantics of identifiers using that scheme.\" In other words, the structure of a URI is defined by its scheme. While it is common for schemes to further delegate their substructure to the URI's owner, publishing independent standards that mandate particular forms of substructure in URIs is often problematic. This document provides guidance on the specification of URI substructure in standards. This document obsoletes RFC 7320 and updates RFC 3986.",
  "authors": [
    "M. Nottingham"
  ],
  "organizations": [],
  "publication_date": "2020-06-01",
  "current_status": "BEST CURRENT PRACTICE",
  "current_status_ru": "Лучшая современная практика",
  "publication_status": "BEST CURRENT PRACTICE",
  "publication_status_ru": "Лучшая современная практика",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "",
  "area_ru": "",
  "working_group": "NON WORKING GROUP",
  "source_draft": "draft-nottingham-rfc7320bis-03",
  "page_count": 8,
  "doi": "10.17487/RFC8820",
  "keywords": [
    "URI structure"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [
      "RFC7320"
    ],
    "obsoleted_by": [],
    "updates": [
      "RFC3986"
    ],
    "updated_by": [],
    "is_also": [
      "BCP190"
    ],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc8820/",
    "html": "https://www.rfc-editor.org/rfc/rfc8820.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc8820.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc8820/"
  }
}