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

IETF · RFC · RFC9290

RFC9290 · Concise Problem Details for Constrained Application Protocol (CoAP) APIs

Concise Problem Details for Constrained Application Protocol (CoAP) APIs

This document defines a concise "problem detail" as a way to carry machine-readable details of errors in a Representational State Transfer (REST) response to avoid the need to define new error response formats for REST APIs for constrained environments. The format is inspired by, but intended to be more concise than, the problem details for HTTP APIs defined in RFC 7807.

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

This document defines a concise "problem detail" as a way to carry machine-readable details of errors in a Representational State Transfer (REST) response to avoid the need to define new error response formats for REST APIs for constrained environments. The format is inspired by, but intended to be more concise than, the problem details for HTTP APIs defined in RFC 7807.

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

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

Полные импортированные сведения карточки
{
  "id": "RFC9290",
  "number": 9290,
  "title_en": "Concise Problem Details for Constrained Application Protocol (CoAP) APIs",
  "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": "This document defines a concise \"problem detail\" as a way to carry machine-readable details of errors in a Representational State Transfer (REST) response to avoid the need to define new error response formats for REST APIs for constrained environments. The format is inspired by, but intended to be more concise than, the problem details for HTTP APIs defined in RFC 7807.",
  "authors": [
    "T. Fossati",
    "C. Bormann"
  ],
  "organizations": [],
  "publication_date": "2022-10-01",
  "current_status": "PROPOSED STANDARD",
  "current_status_ru": "Предлагаемый стандарт",
  "publication_status": "PROPOSED STANDARD",
  "publication_status_ru": "Предлагаемый стандарт",
  "lifecycle": "active",
  "lifecycle_ru": "Действующий",
  "stream": "IETF",
  "stream_ru": "IETF",
  "area": "wit",
  "area_ru": "Веб и транспорт Интернета",
  "working_group": "core",
  "source_draft": "draft-ietf-core-problem-details-08",
  "page_count": 21,
  "doi": "10.17487/RFC9290",
  "keywords": [
    "CoAP",
    "API",
    "Problem Details",
    "CBOR Tag",
    "Language Tag",
    "Bidi"
  ],
  "formats": [
    "HTML",
    "TXT",
    "PDF",
    "XML"
  ],
  "relations": {
    "obsoletes": [],
    "obsoleted_by": [],
    "updates": [],
    "updated_by": [],
    "is_also": [],
    "see_also": []
  },
  "links": {
    "info": "https://www.rfc-editor.org/info/rfc9290/",
    "html": "https://www.rfc-editor.org/rfc/rfc9290.html",
    "txt": "https://www.rfc-editor.org/rfc/rfc9290.txt",
    "datatracker": "https://datatracker.ietf.org/doc/rfc9290/"
  }
}