specs.json

{
 "IETF": {
  "id": "http://webconcepts.info/specs/IETF/",
  "name": "Internet Engineering Task Force",
  "short": "IETF",
  "series": [{
   "I-D": {
    "id": "http://webconcepts.info/specs/IETF/I-D/",
    "name": "Internet Draft",
    "short": "I-D",
    "specs": [{
     "amundsen-richardson-foster-alps": {
      "id": "http://webconcepts.info/specs/IETF/I-D/amundsen-richardson-foster-alps",
      "title": "Application-Level Profile Semantics (ALPS)",
      "name": "Internet Draft amundsen-richardson-foster-alps",
      "URI": "urn:ietf:id:amundsen-richardson-foster-alps",
      "URL": "https://datatracker.ietf.org/doc/html/draft-amundsen-richardson-foster-alps",
      "abstract": "This document describes ALPS, a data format for defining simple descriptions of application-level semantics, similar in complexity to HTML microformats. An ALPS document can be used as a profile to explain the application semantics of a document with an application-agnostic media type (such as HTML, HAL, Collection+JSON, Siren, etc.). This increases the reusability of profile documents across media types.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/alps+json" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/alps+xml" }]}},{
     "cavage-http-signatures": {
      "id": "http://webconcepts.info/specs/IETF/I-D/cavage-http-signatures",
      "title": "Signing HTTP Messages",
      "name": "Internet Draft cavage-http-signatures",
      "URI": "urn:ietf:id:cavage-http-signatures",
      "URL": "https://datatracker.ietf.org/doc/html/draft-cavage-http-signatures",
      "abstract": "When communicating over the Internet using the HTTP protocol, it can be desirable for a server or client to authenticate the sender of a particular message. It can also be desirable to ensure that the message was not tampered with during transit. This document describes a way for servers and clients to simultaneously add authentication and message integrity to HTTP messages by using a digital signature.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Signature" }]}},{
     "cedik-http-warning": {
      "id": "http://webconcepts.info/specs/IETF/I-D/cedik-http-warning",
      "title": "Communicating Warning Information in HTTP APIs",
      "name": "Internet Draft cedik-http-warning",
      "URI": "urn:ietf:id:cedik-http-warning",
      "URL": "https://datatracker.ietf.org/doc/html/draft-cedik-http-warning",
      "abstract": "This document defines a new HTTP header field Content-Warning and a standard response format for representing warning information in HTTP APIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Warning" }]}},{
     "combs-http-indeterminate-range": {
      "id": "http://webconcepts.info/specs/IETF/I-D/combs-http-indeterminate-range",
      "title": "HTTP/1.1: Range Responses of Indeterminate Length",
      "name": "Internet Draft combs-http-indeterminate-range",
      "URI": "urn:ietf:id:combs-http-indeterminate-range",
      "URL": "https://datatracker.ietf.org/doc/html/draft-combs-http-indeterminate-range",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document updates RFC 7233 Part 5 of the eight-part specification that defines the protocol referred to as \"HTTP/1.1\". Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests. This document improves support for responding to range requests for resources of indeterminate size.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Indefinite-Ranges" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Range" }]}},{
     "divilly-atom-hierarchy": {
      "id": "http://webconcepts.info/specs/IETF/I-D/divilly-atom-hierarchy",
      "title": "Hierarchy Relations for Atom",
      "name": "Internet Draft divilly-atom-hierarchy",
      "URI": "urn:ietf:id:divilly-atom-hierarchy",
      "URL": "https://datatracker.ietf.org/doc/html/draft-divilly-atom-hierarchy",
      "abstract": "Many applications, besides blogs, provide their data in the form of syndicated Web feeds using formats such as Atom. Some such applications organize Atom Entries in a hierarchical fashion similar to a file system. This specification describes a means of communicating about Atom Entries that are hierarchically related to each other since resource identifiers are opaque to clients and cannot be directly manipulated for the purposes of representation exchange, i.e., navigation. This specification proposes new link relations for hierarchically related Atom resources.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/down" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/up" }]}},{
     "draft-ietf-httpbis-resumable-upload": {
      "id": "http://webconcepts.info/specs/IETF/I-D/draft-ietf-httpbis-resumable-upload",
      "title": "Resumable Uploads for HTTP",
      "name": "Internet Draft draft-ietf-httpbis-resumable-upload",
      "URI": "urn:ietf:id:draft-ietf-httpbis-resumable-upload",
      "URL": "https://datatracker.ietf.org/doc/html/draft-draft-ietf-httpbis-resumable-upload",
      "abstract": "HTTP clients often encounter interrupted data transfers as a result of canceled requests or dropped connections. Prior to interruption, part of a representation may have been exchanged. To complete the data transfer of the entire representation, it is often desirable to issue subsequent requests that transfer only the remainder of the representation. HTTP range requests support this concept of resumable downloads from server to client. This document describes a mechanism that supports resumable uploads from client to server using HTTP.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Upload-Incomplete" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Upload-Offset" }]}},{
     "drechsler-httpbis-improved-caching": {
      "id": "http://webconcepts.info/specs/IETF/I-D/drechsler-httpbis-improved-caching",
      "title": "Hypertext Transfer Protocol: Improved HTTP Caching",
      "name": "Internet Draft drechsler-httpbis-improved-caching",
      "URI": "urn:ietf:id:drechsler-httpbis-improved-caching",
      "URL": "https://datatracker.ietf.org/doc/html/draft-drechsler-httpbis-improved-caching",
      "abstract": "This document describes an improved HTTP caching method which can be applied in addition to the standard caching behavior for HTTP. It defines the associated header field that controls this improved caching mechanism and a modified caching operation which is slightly different to standard caching operation for HTTP.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cache-NT" }]}},{
     "hoffman-xml2rfc": {
      "id": "http://webconcepts.info/specs/IETF/I-D/hoffman-xml2rfc",
      "title": "The 'XML2RFC' version 3 Vocabulary",
      "name": "Internet Draft hoffman-xml2rfc",
      "URI": "urn:ietf:id:hoffman-xml2rfc",
      "URL": "https://datatracker.ietf.org/doc/html/draft-hoffman-xml2rfc",
      "abstract": "This document defines the \"XML2RFC\" version 3 vocabulary; an XML-based language used for writing RFCs and Internet-Drafts. It is heavily derived from the version 2 vocabulary that is also under discussion. This document obsoletes the v2 grammar described in RFC 2629 and its expected followup, draft-reschke-xml2rfc.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/derivedfrom" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/rfc+xml" }]}},{
     "ietf-calext-caldav-attachments": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-calext-caldav-attachments",
      "title": "CalDAV Managed Attachments",
      "name": "Internet Draft ietf-calext-caldav-attachments",
      "URI": "urn:ietf:id:ietf-calext-caldav-attachments",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-calext-caldav-attachments",
      "abstract": "This specification defines an extension to the calendar access protocol (CalDAV) to allow attachments associated with iCalendar data to be stored and managed on the server.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cal-Managed-ID" }]}},{
     "ietf-core-dynlink": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-core-dynlink",
      "title": "Dynamic Resource Linking for Constrained RESTful Environments",
      "name": "Internet Draft ietf-core-dynlink",
      "URI": "urn:ietf:id:ietf-core-dynlink",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-core-dynlink",
      "abstract": "For CoAP Dynamic linking of state updates between resources, either on an endpoint or between endpoints, is defined with the concept of Link Bindings. This specification defines conditional observation attributes that work with Link Bindings or with CoAP Observe.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/boundto" }]}},{
     "ietf-core-http-mapping": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-core-http-mapping",
      "title": "Guidelines for HTTP-to-CoAP Mapping Implementations",
      "name": "Internet Draft ietf-core-http-mapping",
      "URI": "urn:ietf:id:ietf-core-http-mapping",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-core-http-mapping",
      "abstract": "This document provides reference information for implementing a cross-protocol network proxy that performs translation from the HTTP protocol to the CoAP protocol. This will enable a HTTP client to access resources on a CoAP server through the proxy. This document describes how a HTTP request is mapped to a CoAP request, and then how a CoAP response is mapped back to a HTTP response. This includes guidelines for URI mapping, media type mapping and additional proxy implementation issues. This document covers the Reverse, Forward and Interception cross-protocol proxy cases.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/coap-payload" }]}},{
     "ietf-core-links-json": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-core-links-json",
      "title": "Representing CoRE Formats in JSON and CBOR",
      "name": "Internet Draft ietf-core-links-json",
      "URI": "urn:ietf:id:ietf-core-links-json",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-core-links-json",
      "abstract": "JavaScript Object Notation (JSON) is a text-based data format which is popular for Web based data exchange. Concise Binary Object Representation (CBOR) is a binary data format which has been optimized for data exchange for the Internet of Things (IoT). For many IoT scenarios, CBOR formats will be preferred since it can help decrease transmission payload sizes as well as implementation code sizes compared to other data formats. Web Linking (RFC 5988) provides a way to represent links between Web resources as well as the relations expressed by them and attributes of such a link. In constrained networks, a collection of Web links can be exchanged in the CoRE link format (RFC 6690). Outside of constrained environments, it may be useful to represent these collections of Web links in JSON, and similarly, inside constrained environments, in CBOR. This specification defines a common format for this.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/link-format+cbor" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/link-format+json" }]}},{
     "ietf-core-senml": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-core-senml",
      "title": "Media Types for Sensor Measurement Lists (SenML)",
      "name": "Internet Draft ietf-core-senml",
      "URI": "urn:ietf:id:ietf-core-senml",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-core-senml",
      "abstract": "This specification defines media types for representing simple sensor measurements and device parameters in the Sensor Measurement Lists (SenML). Representations are defined in JavaScript Object Notation (JSON), Concise Binary Object Representation (CBOR), eXtensible Markup Language (XML), and Efficient XML Interchange (EXI), which share the common SenML data model. A simple sensor, such as a temperature sensor, could use this media type in protocols such as HTTP or CoAP to transport the measurements of the sensor or to be configured.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/senml+cbor" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/senml+exi" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/senml+json" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/senml+xml" }]}},{
     "ietf-httpapi-deprecation-header": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpapi-deprecation-header",
      "title": "The Deprecation HTTP Header",
      "name": "Internet Draft ietf-httpapi-deprecation-header",
      "URI": "urn:ietf:id:ietf-httpapi-deprecation-header",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-deprecation-header",
      "abstract": "The HTTP Deprecation response header field can be used to signal to consumers of a URI-identified resource that the use of the resource has been deprecated. Additionally, the deprecation link relation can be used to link to a resource that provides additional context for the deprecation, and possibly ways in which clients can find a replacement for the deprecated resource.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Deprecation" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/deprecation" }]}},{
     "ietf-httpapi-idempotency-key-header": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpapi-idempotency-key-header",
      "title": "The Idempotency-Key HTTP Header Field",
      "name": "Internet Draft ietf-httpapi-idempotency-key-header",
      "URI": "urn:ietf:id:ietf-httpapi-idempotency-key-header",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-idempotency-key-header",
      "abstract": "The HTTP Idempotency-Key request header field can be used to carry idempotency key in order to make non-idempotent HTTP methods such as \"POST\" or \"PATCH\" fault-tolerant.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Idempotency-Key" }]}},{
     "ietf-httpapi-linkset": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpapi-linkset",
      "title": "Linkset: Media Types and a Link Relation Type for Link Sets",
      "name": "Internet Draft ietf-httpapi-linkset",
      "URI": "urn:ietf:id:ietf-httpapi-linkset",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-linkset",
      "abstract": "This specification defines two document formats and respective media types for representing sets of links as stand-alone resources. One format is JSON-based, the other aligned with the format for representing links in the HTTP \"Link\" header field. This specification also introduces a link relation type to support discovery of sets of links.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/linkset" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/linkset" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/linkset+json" }]}},{
     "ietf-httpapi-ratelimit-headers": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpapi-ratelimit-headers",
      "title": "Rate-Limit Header Fields for HTTP",
      "name": "Internet Draft ietf-httpapi-ratelimit-headers",
      "URI": "urn:ietf:id:ietf-httpapi-ratelimit-headers",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-ratelimit-headers",
      "abstract": "This document defines the RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset header fields for HTTP, thus allowing servers to publish current request quotas and clients to shape their request policy and avoid being throttled out.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/RateLimit-Limit" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/RateLimit-Remaining" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/RateLimit-Reset" }]}},{
     "ietf-httpbis-binary-message": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-binary-message",
      "title": "Binary Representation of HTTP Messages",
      "name": "Internet Draft ietf-httpbis-binary-message",
      "URI": "urn:ietf:id:ietf-httpbis-binary-message",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-binary-message",
      "abstract": "This document defines a binary format for representing HTTP messages.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/message/bhttp" }]}},{
     "ietf-httpbis-cache-header": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-cache-header",
      "title": "The Cache-Status HTTP Response Header Field",
      "name": "Internet Draft ietf-httpbis-cache-header",
      "URI": "urn:ietf:id:ietf-httpbis-cache-header",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-cache-header",
      "abstract": "To aid debugging, HTTP caches often append header fields to a response explaining how they handled the request in an ad hoc manner. This specification defines a standard mechanism to do so that is aligned with HTTP's caching model.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cache-Status" }]}},{
     "ietf-httpbis-client-cert-field": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-client-cert-field",
      "title": "Client-Cert HTTP Header Field",
      "name": "Internet Draft ietf-httpbis-client-cert-field",
      "URI": "urn:ietf:id:ietf-httpbis-client-cert-field",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-cert-field",
      "abstract": "This document defines HTTP extension header fields that allow a TLS terminating reverse proxy to convey the client certificate information of a mutually-authenticated TLS connection to the origin server in a common and predictable manner.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Client-Cert" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Client-Cert-Chain" }]}},{
     "ietf-httpbis-client-hints": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-client-hints",
      "title": "HTTP Client Hints",
      "name": "Internet Draft ietf-httpbis-client-hints",
      "URI": "urn:ietf:id:ietf-httpbis-client-hints",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-client-hints",
      "abstract": "HTTP defines proactive content negotiation to allow servers to select the appropriate response for a given request, based upon the user agent's characteristics, as expressed in request headers. In practice, clients are often unwilling to send those request headers, because it is not clear whether they will be used, and sending them impacts both performance and privacy. This document defines an Accept-CH response header that servers can use to advertise their use of request headers for proactive content negotiation, along with a set of guidelines for the creation of such headers, colloquially known as \"Client Hints.\"",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-CH" }]}},{
     "ietf-httpbis-key": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-key",
      "title": "The Key HTTP Response Header Field",
      "name": "Internet Draft ietf-httpbis-key",
      "URI": "urn:ietf:id:ietf-httpbis-key",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-key",
      "abstract": "The 'Key' header field for HTTP responses allows an origin server to describe the cache key for a negotiated response: a short algorithm that can be used upon later requests to determine if the same response is reusable. Key has the advantage of avoiding an additional round trip for validation whenever a new request differs slightly, but not significantly, from prior requests. Key also informs user agents of the request characteristics that might result in different content, which can be useful if the user agent is not sending Accept* fields in order to reduce the risk of fingerprinting.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Key" }]}},{
     "ietf-httpbis-priority": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-priority",
      "title": "Extensible Prioritization Scheme for HTTP",
      "name": "Internet Draft ietf-httpbis-priority",
      "URI": "urn:ietf:id:ietf-httpbis-priority",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-priority",
      "abstract": "This document describes a scheme for prioritizing HTTP responses. This scheme expresses the priority of each HTTP response using absolute values, rather than as a relative relationship between a group of HTTP responses. This document defines the Priority header field for communicating the initial priority in an HTTP version-independent manner, as well as HTTP/2 and HTTP/3 frames for reprioritizing the responses. These share a common format structure that is designed to provide future extensibility.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Priority" }]}},{
     "ietf-httpbis-rfc6265bis": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-rfc6265bis",
      "title": "HTTP State Management Mechanism",
      "name": "Internet Draft ietf-httpbis-rfc6265bis",
      "URI": "urn:ietf:id:ietf-httpbis-rfc6265bis",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-rfc6265bis",
      "abstract": "This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet. This document obsoletes RFC 2965.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cookie" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Set-Cookie" }]}},{
     "ietf-httpbis-safe-method-w-body": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-safe-method-w-body",
      "title": "The HTTP QUERY Method",
      "name": "Internet Draft ietf-httpbis-safe-method-w-body",
      "URI": "urn:ietf:id:ietf-httpbis-safe-method-w-body",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-safe-method-w-body",
      "abstract": "This specification defines a new HTTP method, QUERY, as a safe, idempotent request method that can carry request content.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Query" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/QUERY" }]}},{
     "ietf-httpbis-tunnel-protocol": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-tunnel-protocol",
      "title": "The Tunnel-Protocol HTTP Header Field",
      "name": "Internet Draft ietf-httpbis-tunnel-protocol",
      "URI": "urn:ietf:id:ietf-httpbis-tunnel-protocol",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-tunnel-protocol",
      "abstract": "This specification allows HTTP CONNECT requests to indicate what protocol will be used within the tunnel once established, using the Tunnel-Protocol header field.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Tunnel-Protocol" }]}},{
     "ietf-httpbis-variants": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-httpbis-variants",
      "title": "HTTP Variants",
      "name": "Internet Draft ietf-httpbis-variants",
      "URI": "urn:ietf:id:ietf-httpbis-variants",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-httpbis-variants",
      "abstract": "This specification introduces an alternative way to communicate a secondary cache key for a HTTP resource, using the HTTP \"Variants\" and \"Variant-Key\" response header fields. Its aim is to make HTTP proactive content negotiation more cache-friendly.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Variant-Key" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Variants" }]}},{
     "ietf-jsonbis-rfc7159bis": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-jsonbis-rfc7159bis",
      "title": "The JavaScript Object Notation (JSON) Data Interchange Format",
      "name": "Internet Draft ietf-jsonbis-rfc7159bis",
      "URI": "urn:ietf:id:ietf-jsonbis-rfc7159bis",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-jsonbis-rfc7159bis",
      "abstract": "JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/json" }]}},{
     "ietf-oauth-v2-http-mac": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-oauth-v2-http-mac",
      "title": "OAuth 2.0 Message Authentication Code (MAC) Tokens",
      "name": "Internet Draft ietf-oauth-v2-http-mac",
      "URI": "urn:ietf:id:ietf-oauth-v2-http-mac",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-oauth-v2-http-mac",
      "abstract": "This specification describes how to use MAC Tokens in HTTP requests to access OAuth 2.0 protected resources. An OAuth client willing to access a protected resource needs to demonstrate possession of a cryptographic key by using it with a keyed message digest function to the request. The document also defines a key distribution protocol for obtaining a fresh session key.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-access-token-type/": "http://webconcepts.info/concepts/oauth-access-token-type/mac" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/kid" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/mac_algorithm" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/mac_key" }]}},{
     "ietf-ohai-ohttp": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-ohai-ohttp",
      "title": "Oblivious HTTP",
      "name": "Internet Draft ietf-ohai-ohttp",
      "URI": "urn:ietf:id:ietf-ohai-ohttp",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-ohai-ohttp",
      "abstract": "This document describes a system for the forwarding of encrypted HTTP messages. This allows a client to make multiple requests of a server without the server being able to link those requests to the client or to identify the requests as having come from the same client.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/message/ohttp-req" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/message/ohttp-res" }]}},{
     "ietf-webpush-vapid": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ietf-webpush-vapid",
      "title": "Voluntary Application Server Identification (VAPID) for Web Push",
      "name": "Internet Draft ietf-webpush-vapid",
      "URI": "urn:ietf:id:ietf-webpush-vapid",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ietf-webpush-vapid",
      "abstract": "An application server can use the method described to voluntarily identify itself to a push service. This identification information can be used by the push service to attribute requests that are made by the same application server to a single entity. An application server can include additional information that the operator of a push service can use to contact the operator of the application server. This identification information can be used to restrict the use of a push subscription a single application server.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/vapid" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/webpush-options+json" }]}},{
     "inadarei-api-health-check": {
      "id": "http://webconcepts.info/specs/IETF/I-D/inadarei-api-health-check",
      "title": "Health Check Response Format for HTTP APIs",
      "name": "Internet Draft inadarei-api-health-check",
      "URI": "urn:ietf:id:inadarei-api-health-check",
      "URL": "https://datatracker.ietf.org/doc/html/draft-inadarei-api-health-check",
      "abstract": "This document proposes a service health check response format for HTTP APIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/vnd.health+json" }]}},{
     "kelly-json-hal": {
      "id": "http://webconcepts.info/specs/IETF/I-D/kelly-json-hal",
      "title": "JSON Hypertext Application Language",
      "name": "Internet Draft kelly-json-hal",
      "URI": "urn:ietf:id:kelly-json-hal",
      "URL": "https://datatracker.ietf.org/doc/html/draft-kelly-json-hal",
      "abstract": "This document proposes a media type for representing resources and their relations with hyperlinks.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/hal+json" }]}},{
     "koch-openpgp-webkey-service": {
      "id": "http://webconcepts.info/specs/IETF/I-D/koch-openpgp-webkey-service",
      "title": "OpenPGP Web Key Service",
      "name": "Internet Draft koch-openpgp-webkey-service",
      "URI": "urn:ietf:id:koch-openpgp-webkey-service",
      "URL": "https://datatracker.ietf.org/doc/html/draft-koch-openpgp-webkey-service",
      "abstract": "This specification describes a service to locate OpenPGP keys by mail address using a Web service and the HTTPS protocol.  It also provides a method for secure communication between the key owner and the mail provider to publish and revoke the public key.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/openpgpkey" }]}},{
     "michaud-xml-hal": {
      "id": "http://webconcepts.info/specs/IETF/I-D/michaud-xml-hal",
      "title": "XML Hypertext Application Language",
      "name": "Internet Draft michaud-xml-hal",
      "URI": "urn:ietf:id:michaud-xml-hal",
      "URL": "https://datatracker.ietf.org/doc/html/draft-michaud-xml-hal",
      "abstract": "This document proposes a media type for representing resources and their relations with hyperlinks.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/hal+xml" }]}},{
     "mogul-http-dupsup": {
      "id": "http://webconcepts.info/specs/IETF/I-D/mogul-http-dupsup",
      "title": "Duplicate Suppression in HTTP",
      "name": "Internet Draft mogul-http-dupsup",
      "URI": "urn:ietf:id:mogul-http-dupsup",
      "URL": "https://datatracker.ietf.org/doc/html/draft-mogul-http-dupsup",
      "abstract": "A significant fraction of Web content is often exactly duplicated under several different URIs. This duplication can lead to suboptimal use of network bandwidth, and unnecessary latency for users. Much of this duplication can be avoided through the use of a simple mechanism, described here, which allows a cache to efficiently substitute one byte-for-byte identical value for another. By doing so, the cache avoids some or all of the network costs associated with retrieving the duplicate value.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/SubOK" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Subst" }]}},{
     "nottingham-http-poe": {
      "id": "http://webconcepts.info/specs/IETF/I-D/nottingham-http-poe",
      "title": "POST Once Exactly (POE)",
      "name": "Internet Draft nottingham-http-poe",
      "URI": "urn:ietf:id:nottingham-http-poe",
      "URL": "https://datatracker.ietf.org/doc/html/draft-nottingham-http-poe",
      "abstract": "This specification describes a pattern of use that allows HTTP clients to automatically retry POST requests in a manner that assures no unintended side effects will take place, and defines mechanisms to allow implementations to automatically determine when such patterns are supported.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/POE" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/POE-Links" }]}},{
     "nottingham-json-home": {
      "id": "http://webconcepts.info/specs/IETF/I-D/nottingham-json-home",
      "title": "Home Documents for HTTP APIs",
      "name": "Internet Draft nottingham-json-home",
      "URI": "urn:ietf:id:nottingham-json-home",
      "URL": "https://datatracker.ietf.org/doc/html/draft-nottingham-json-home",
      "abstract": "This document proposes a \"home document\" format for non-browser HTTP clients.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/home" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/home+json" }]}},{
     "nottingham-linked-cache-inv": {
      "id": "http://webconcepts.info/specs/IETF/I-D/nottingham-linked-cache-inv",
      "title": "Linked Cache Invalidation",
      "name": "Internet Draft nottingham-linked-cache-inv",
      "URI": "urn:ietf:id:nottingham-linked-cache-inv",
      "URL": "https://datatracker.ietf.org/doc/html/draft-nottingham-linked-cache-inv",
      "abstract": "This memo defines two new link types that indicate relationships between resources in terms of cache invalidation, along with a HTTP cache-control extension that takes advantage of those relationships to use them to extend response freshness. Collectively, this is referred to as Linked Cache Invalidation (LCI).",
      "concepts": [{
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/inv-maxage" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/inv-by" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/invalidates" }]}},{
     "pot-authentication-link": {
      "id": "http://webconcepts.info/specs/IETF/I-D/pot-authentication-link",
      "title": "Link Relationship Types for Authentication",
      "name": "Internet Draft pot-authentication-link",
      "URI": "urn:ietf:id:pot-authentication-link",
      "URL": "https://datatracker.ietf.org/doc/html/draft-pot-authentication-link",
      "abstract": "This specification defines a set of relationships that may be used to indicate where a user may authenticate, log out, register a new account or find out who is currently authenticated.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/authenticate" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/authenticated-as" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/logout" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/register-user" }]}},{
     "pot-prefer-push": {
      "id": "http://webconcepts.info/specs/IETF/I-D/pot-prefer-push",
      "title": "HTTP-client suggested Push Preference",
      "name": "Internet Draft pot-prefer-push",
      "URI": "urn:ietf:id:pot-prefer-push",
      "URL": "https://datatracker.ietf.org/doc/html/draft-pot-prefer-push",
      "abstract": "\"Prefer-Push\" is a HTTP header that a client may use to request that a server uses HTTP/2 Push to send related resources as identified by their link relationships.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Prefer-Push" }]}},{
     "pratt-httpbis-bytes-live-range-unit": {
      "id": "http://webconcepts.info/specs/IETF/I-D/pratt-httpbis-bytes-live-range-unit",
      "title": "HTTP bytes-live Range Unit for Live Content",
      "name": "Internet Draft pratt-httpbis-bytes-live-range-unit",
      "URI": "urn:ietf:id:pratt-httpbis-bytes-live-range-unit",
      "URL": "https://datatracker.ietf.org/doc/html/draft-pratt-httpbis-bytes-live-range-unit",
      "abstract": "To accommodate byte range requests for content that has data appended over time, this document defines a new HTTP range unit named \"bytes-live\". The \"bytes-live\" range unit provides the ability for a client to specify a byte range in a GET or HEAD request which starts at an arbitrary byte offset within the representation and ends at an indeterminate offset, represented by \"*\".",
      "concepts": [{
       "http://webconcepts.info/concepts/http-range-unit/": "http://webconcepts.info/concepts/http-range-unit/bytes-live" }]}},{
     "reschke-http-get-location": {
      "id": "http://webconcepts.info/specs/IETF/I-D/reschke-http-get-location",
      "title": "The Hypertext Transfer Protocol (HTTP) GET-Location header",
      "name": "Internet Draft reschke-http-get-location",
      "URI": "urn:ietf:id:reschke-http-get-location",
      "URL": "https://datatracker.ietf.org/doc/html/draft-reschke-http-get-location",
      "abstract": "Several hypertext transfer protocol (HTTP) extensions use methods other than GET to expose information.  This has the drawback that this kind of information is harder to identify (missing a URL to which a GET request could be applied) and to cache. This document specifies a simple extension header through which a server can advertise a substitute URL that an HTTP client subsequently can use with the GET method.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/GET-Location" }]}},{
     "ruellan-http-accept-push-policy": {
      "id": "http://webconcepts.info/specs/IETF/I-D/ruellan-http-accept-push-policy",
      "title": "Accept-Push-Policy Header Field",
      "name": "Internet Draft ruellan-http-accept-push-policy",
      "URI": "urn:ietf:id:ruellan-http-accept-push-policy",
      "URL": "https://datatracker.ietf.org/doc/html/draft-ruellan-http-accept-push-policy",
      "abstract": "The \"Accept-Push-Policy\" and \"Push-Policy\" header fields enable a client and a server to negotiate the behaviour of the server regarding the usage of push on a per-request basis.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Push-Policy" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Push-Policy" }]}},{
     "shelby-exi-registration": {
      "id": "http://webconcepts.info/specs/IETF/I-D/shelby-exi-registration",
      "title": "The +exi Media Type Suffix",
      "name": "Internet Draft shelby-exi-registration",
      "URI": "urn:ietf:id:shelby-exi-registration",
      "URL": "https://datatracker.ietf.org/doc/html/draft-shelby-exi-registration",
      "abstract": "Efficient XML Interchange (EXI) is an XML representation technique specified by the W3C to provide a time and space efficient encoding for XML documents. This document defines a new Structured Syntax Suffix \"+exi\" for use in a specific class of protocols, where \"exi\" content-type encoding or the generic \"application/exi\" media type are not applicable.",
      "concepts": [{
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+exi" }]}},{
     "snell-link-method": {
      "id": "http://webconcepts.info/specs/IETF/I-D/snell-link-method",
      "title": "HTTP Link and Unlink Methods",
      "name": "Internet Draft snell-link-method",
      "URI": "urn:ietf:id:snell-link-method",
      "URL": "https://datatracker.ietf.org/doc/html/draft-snell-link-method",
      "abstract": "This specification defines the semantics of the LINK and UNLINK HTTP methods.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/LINK" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/UNLINK" }]}},{
     "snell-more-link-relations": {
      "id": "http://webconcepts.info/specs/IETF/I-D/snell-more-link-relations",
      "title": "Additional Link Relations and the urn:social Namespace",
      "name": "Internet Draft snell-more-link-relations",
      "URI": "urn:ietf:id:snell-more-link-relations",
      "URL": "https://datatracker.ietf.org/doc/html/draft-snell-more-link-relations",
      "abstract": "This specification defines a number of additional Link Relation Types that can used for a variety of purposes.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/bcc" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/bfrom" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/bto" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/cc" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/from" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/generator" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/location" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/mentionedby" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/provider" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/source" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/to" }]}},{
     "soilandreyes-arcp": {
      "id": "http://webconcepts.info/specs/IETF/I-D/soilandreyes-arcp",
      "title": "The Archive and Packaging (arcp) URI scheme",
      "name": "Internet Draft soilandreyes-arcp",
      "URI": "urn:ietf:id:soilandreyes-arcp",
      "URL": "https://datatracker.ietf.org/doc/html/draft-soilandreyes-arcp",
      "abstract": "This specification proposes the Application and Packaging Pointer URI scheme \"arcp\". arcp URIs can be used to consume or reference hypermedia resources bundled inside a file archive or an application package, as well as to resolve URIs for archive resources within a programmatic framework. This URI scheme provides mechanisms to generate a unique base URI to represent the root of the archive, so that relative URI references in a bundled resource can be resolved within the archive without having to extract the archive content on the local file system. An arcp URI can be used for purposes of isolation (e.g. when consuming multiple archives), security constraints (avoiding \"climb out\" from the archive), or for externally identifying sub-resources referenced by hypermedia formats.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/arcp" }]}},{
     "svensson-profiled-representations": {
      "id": "http://webconcepts.info/specs/IETF/I-D/svensson-profiled-representations",
      "title": "Indicating, Discovering, Negotiating, and Writing Profiled Representations",
      "name": "Internet Draft svensson-profiled-representations",
      "URI": "urn:ietf:id:svensson-profiled-representations",
      "URL": "https://datatracker.ietf.org/doc/html/draft-svensson-profiled-representations",
      "abstract": "This document details approaches for enriching HTTP interactions with information pertaining to the profiles to which resource representations conform. It surveys approaches that were recently introduced to indicate the profile of a resource representation, and to make representations that conform to a profile discoverable. It introduces a generally applicable approach to negotiate for a resource representation that conforms to a profile preferred by a user agent. That approach leverages the existing content negotiation mechanism but applies it to the profile dimension to which it was previously not applied. The document also shows how a server can convey which profiled representations it is able to accept from a user agent.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Profile" }]}},{
     "thomson-http-content-signature": {
      "id": "http://webconcepts.info/specs/IETF/I-D/thomson-http-content-signature",
      "title": "Content-Signature Header Field for HTTP",
      "name": "Internet Draft thomson-http-content-signature",
      "URI": "urn:ietf:id:thomson-http-content-signature",
      "URL": "https://datatracker.ietf.org/doc/html/draft-thomson-http-content-signature",
      "abstract": "A Content-Signature header field is defined for use in HTTP. This header field carries a signature of the payload body of a message.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Signature" }]}},{
     "thomson-http-nice": {
      "id": "http://webconcepts.info/specs/IETF/I-D/thomson-http-nice",
      "title": "Marking HTTP Requests as Unimportant",
      "name": "Internet Draft thomson-http-nice",
      "URI": "urn:ietf:id:thomson-http-nice",
      "URL": "https://datatracker.ietf.org/doc/html/draft-thomson-http-nice",
      "abstract": "An HTTP \"Nice\" header field is defined that marks a request as low priority. Intermediaries can choose to discard the request or serve it from cache rather than forwarding it to an origin server. This enables constrained origin servers, such as those that rely on battery power, to avoid expending limited resources on serving requests.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Nice" }]}},{
     "west-origin-cookies": {
      "id": "http://webconcepts.info/specs/IETF/I-D/west-origin-cookies",
      "title": "Origin Cookies",
      "name": "Internet Draft west-origin-cookies",
      "URI": "urn:ietf:id:west-origin-cookies",
      "URL": "https://datatracker.ietf.org/doc/html/draft-west-origin-cookies",
      "abstract": "This document updates RFC 6265, defining the \"origin\" attribute for cookies and the \"Origin-Cookie\" header field, which together allow servers to choose to harmonize the security policy of their cookies with the same-origin policy which governs other available client-side storage mechanisms.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Origin-Cookie" }]}},{
     "wilde-home-xml": {
      "id": "http://webconcepts.info/specs/IETF/I-D/wilde-home-xml",
      "title": "Home Documents for HTTP Services: XML Syntax",
      "name": "Internet Draft wilde-home-xml",
      "URI": "urn:ietf:id:wilde-home-xml",
      "URL": "https://datatracker.ietf.org/doc/html/draft-wilde-home-xml",
      "abstract": "The specification for HTTP API Home Documents provides a JSON syntax only. This specification provides an XML syntax for the same data model, so that the concept of Home Documents can be consistently exposed in both JSON- and XML-based HTTP APIs. It also defines the link relation type \"home\" so that applications can identify links to home documents.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/home+xml" }]}},{
     "zern-webp": {
      "id": "http://webconcepts.info/specs/IETF/I-D/zern-webp",
      "title": "WebP Image Format",
      "name": "Internet Draft zern-webp",
      "URI": "urn:ietf:id:zern-webp",
      "URL": "https://datatracker.ietf.org/doc/html/draft-zern-webp",
      "abstract": "WebP is a RIFF-based image file format which supports lossless and lossy compression as well as alpha (transparency) and animation. It covers use cases similar to JPEG, PNG and GIF.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/image/webp" }]}},{
     "zyp-json-schema": {
      "id": "http://webconcepts.info/specs/IETF/I-D/zyp-json-schema",
      "title": "A JSON Media Type for Describing the Structure and Meaning of JSON Documents",
      "name": "Internet Draft zyp-json-schema",
      "URI": "urn:ietf:id:zyp-json-schema",
      "URL": "https://datatracker.ietf.org/doc/html/draft-zyp-json-schema",
      "abstract": "JSON (JavaScript Object Notation) Schema defines the media type \"application/schema+json\", a JSON based format for defining the structure of JSON data. JSON Schema provides a contract for what JSON data is required for a given application and how to interact with it. JSON Schema is intended to define validation, documentation, hyperlink navigation, and interaction control of JSON data.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/create" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/full" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/instances" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/root" }]}}]}},{
   "RFC": {
    "id": "http://webconcepts.info/specs/IETF/RFC/",
    "name": "Request for Comments",
    "short": "RFC",
    "specs": [{
     "1738": {
      "id": "http://webconcepts.info/specs/IETF/RFC/1738",
      "title": "Uniform Resource Locators (URL)",
      "name": "RFC 1738",
      "URI": "urn:ietf:rfc:1738",
      "URL": "https://datatracker.ietf.org/doc/html/rfc1738",
      "abstract": "This document specifies a Uniform Resource Locator (URL), the syntax and semantics of formalized information for location and access of resources via the Internet.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/ftp" }]}},{
     "1874": {
      "id": "http://webconcepts.info/specs/IETF/RFC/1874",
      "title": "SGML Media Types",
      "name": "RFC 1874",
      "URI": "urn:ietf:rfc:1874",
      "URL": "https://datatracker.ietf.org/doc/html/rfc1874",
      "abstract": "This document proposes new media sub-types of Text/SGML and Application/SGML. These media types can be used in the exchange of SGML documents and their entities. Specific details for the exchange or encapsulation of groups of related SGML entities using MIME are currently being considered by the mimesgml Working Group.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/sgml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/sgml" }]}},{
     "2068": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2068",
      "title": "Hypertext Transfer Protocol - HTTP/1.1",
      "name": "RFC 2068",
      "URI": "urn:ietf:rfc:2068",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2068",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, object-oriented protocol which can be used for many tasks, such as name servers and distributed object management systems, through extension of its request methods. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as \"HTTP/1.1\".",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Base" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Version" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Public" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/URI" }]}},{
     "2220": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2220",
      "title": "The Application/MARC Content-type",
      "name": "RFC 2220",
      "URI": "urn:ietf:rfc:2220",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2220",
      "abstract": "This memorandum provides a mechanism for representing objects which are files of Machine-Readable Cataloging records (MARC). The MARC formats are standards for the representation and communication of bibliographic and related information. A MARC record contains metadata for an information resource following MARC format specifications.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/marc" }]}},{
     "2295": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2295",
      "title": "Transparent Content Negotiation in HTTP",
      "name": "RFC 2295",
      "URI": "urn:ietf:rfc:2295",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2295",
      "abstract": "HTTP allows web site authors to put multiple versions of the same information under a single URL. Transparent content negotiation is an extensible negotiation mechanism, layered on top of HTTP, for automatically selecting the best version when the URL is accessed. This enables the smooth deployment of new web data formats and markup tags.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Features" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Alternates" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Negotiate" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/TCN" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Variant-Vary" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/506" }]}},{
     "2310": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2310",
      "title": "The Safe Response Header Field",
      "name": "RFC 2310",
      "URI": "urn:ietf:rfc:2310",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2310",
      "abstract": "This document defines a HTTP response header field called Safe, which can be used to indicate that repeating a HTTP request is safe. Such an indication will allow user agents to handle retries of some safe requests, in particular safe POST requests, in a more user-friendly way.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Safe" }]}},{
     "2324": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2324",
      "title": "Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0)",
      "name": "RFC 2324",
      "URI": "urn:ietf:rfc:2324",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2324",
      "abstract": "This document describes HTCPCP, a protocol for controlling, monitoring, and diagnosing coffee pots.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Additions" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/418" }]}},{
     "2388": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2388",
      "title": "Returning Values from Forms: multipart/form-data",
      "name": "RFC 2388",
      "URI": "urn:ietf:rfc:2388",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2388",
      "abstract": "This specification defines an Internet Media Type, multipart/form-data, which can be used by a wide variety of applications and transported by a wide variety of protocols as a way of returning a set of values as the result of a user filling out a form.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/multipart/form-data" }]}},{
     "2392": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2392",
      "title": "Content-ID and Message-ID Uniform Resource Locators",
      "name": "RFC 2392",
      "URI": "urn:ietf:rfc:2392",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2392",
      "abstract": "The Uniform Resource Locator (URL) schemes, \"cid:\" and \"mid:\" allow references to messages and the body parts of messages. For example, within a single multipart message, one HTML body part might include embedded references to other parts of the same message.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/cid" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/mid" }]}},{
     "2397": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2397",
      "title": "The \"data\" URL scheme",
      "name": "RFC 2397",
      "URI": "urn:ietf:rfc:2397",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2397",
      "abstract": "A new URL scheme, \"data\", is defined. It allows inclusion of small data items as \"immediate\" data, as if it had been included externally.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/data" }]}},{
     "2518": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2518",
      "title": "HTTP Extensions for Distributed Authoring - WEBDAV",
      "name": "RFC 2518",
      "URI": "urn:ietf:rfc:2518",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2518",
      "abstract": "This document specifies a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, namespace manipulation, and resource locking (collision avoidance).",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Status-URI" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/102" }]}},{
     "2616": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2616",
      "title": "Hypertext Transfer Protocol -- HTTP/1.1",
      "name": "RFC 2616",
      "URI": "urn:ietf:rfc:2616",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2616",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. It is a generic, stateless, protocol which can be used for many tasks beyond its use for hypertext, such as name servers and distributed object management systems, through extension of its request methods, error codes and headers. A feature of HTTP is the typing and negotiation of data representation, allowing systems to be built independently of the data being transferred. HTTP has been in use by the World-Wide Web global information initiative since 1990. This specification defines the protocol referred to as \"HTTP/1.1\", and is an update to RFC 2068.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/identity" }]}},{
     "2648": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2648",
      "title": "A URN Namespace for IETF Documents",
      "name": "RFC 2648",
      "URI": "urn:ietf:rfc:2648",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2648",
      "abstract": "A system for Uniform Resource Names (URNs) must be capable of supporting new naming systems. As an example of proposing a new namespace, this document proposes the \"ietf\" namespace. This namespace consists of the RFC family of documents (RFCs, STDs, FYIs, and BCPs) developed by the IETF and published by the RFC Editor, the minutes of working groups (WG) and birds of a feather (BOF) meetings that occur during IETF conferences, and the Internet Drafts published by the Internet Drafts Editor. Both the current URN framework and URN syntax support this namespace.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/ietf" }]}},{
     "2660": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2660",
      "title": "The Secure HyperText Transfer Protocol (S-HTTP)",
      "name": "RFC 2660",
      "URI": "urn:ietf:rfc:2660",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2660",
      "abstract": "This memo describes a syntax for securing messages sent using the Hypertext Transfer Protocol (HTTP), which forms the basis for the World Wide Web. Secure HTTP (S-HTTP) provides independently applicable security services for transaction confidentiality, authenticity/integrity and non-repudiability of origin. The protocol emphasizes maximum flexibility in choice of key management mechanisms, security policies and cryptographic algorithms by supporting option negotiation between parties for each transaction.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Security-Scheme" }]}},{
     "2774": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2774",
      "title": "An HTTP Extension Framework",
      "name": "RFC 2774",
      "URI": "urn:ietf:rfc:2774",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2774",
      "abstract": "A wide range of applications have proposed various extensions of the HTTP protocol. Current efforts span an enormous range, including distributed authoring, collaboration, printing, and remote procedure call mechanisms. These HTTP extensions are not coordinated, since there has been no standard framework for defining extensions and thus, separation of concerns. This document describes a generic extension mechanism for HTTP, which is designed to address the tension between private agreement and public specification and to accommodate extension of applications using HTTP clients, servers, and proxies. The proposal associates each extension with a globally unique identifier, and uses HTTP header fields to carry the extension identifier and related information between the parties involved in the extended communication.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/C-Ext" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/C-Man" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/C-Opt" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Ext" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Man" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Opt" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/510" }]}},{
     "2965": {
      "id": "http://webconcepts.info/specs/IETF/RFC/2965",
      "title": "HTTP State Management Mechanism",
      "name": "RFC 2965",
      "URI": "urn:ietf:rfc:2965",
      "URL": "https://datatracker.ietf.org/doc/html/rfc2965",
      "abstract": "This document specifies a way to create a stateful session with Hypertext Transfer Protocol (HTTP) requests and responses. It describes three new headers, Cookie, Cookie2, and Set-Cookie2, which carry state information between participating origin servers and user agents. The method described here differs from Netscape's Cookie proposal [Netscape], but it can interoperate with HTTP/1.0 user agents that use Netscape's method.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cookie2" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Set-Cookie2" }]}},{
     "3023": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3023",
      "title": "XML Media Types",
      "name": "RFC 3023",
      "URI": "urn:ietf:rfc:3023",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3023",
      "abstract": "This document standardizes five new media types - text/xml, application/xml, text/xml-external-parsed-entity, application/xml-external-parsed-entity, and application/xml-dtd - for use in exchanging network entities that are related to the Extensible Markup Language (XML). This document also standardizes a convention (using the suffix '+xml') for naming media types outside of these five types when those media types represent XML MIME (Multipurpose Internet Mail Extensions) entities. XML MIME entities are currently exchanged via the HyperText Transfer Protocol on the World Wide Web, are an integral part of the WebDAV protocol for remote web authoring, and are expected to have utility in many domains.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/xml-external-parsed-entity" }]}},{
     "3044": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3044",
      "title": "Using The ISSN (International Serial Standard Number) as URN (Uniform Resource Names) within an ISSN-URN Namespace",
      "name": "RFC 3044",
      "URI": "urn:ietf:rfc:3044",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3044",
      "abstract": "This document presents how the ISSN - International Standard Serial Number - which is a persistent number for unique identification of serials widely recognised and used in the bibliographic world, can be supported within the Uniform Resource Name (URN) framework as a specific URN namespace identifier. An ISSN URN resolution system using the ISSN identifier as Uniform resource Name within an ISN URN Namespace has been developed by the ISSN International Centre (ISSN-IC) and is operating as a demonstrator to evaluate all requirements to deploy it in an operational environment. This proceeds from concepts and proposals developed in several IETF RFCs emphasising the way to implement and to use \"recognised\" existing numbering system within the URN framework (RFC 2248, RFC 2141, RFC 2611).",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/issn" }]}},{
     "3121": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3121",
      "title": "A URN Namespace for OASIS",
      "name": "RFC 3121",
      "URI": "urn:ietf:rfc:3121",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3121",
      "abstract": "This document describes a URN (Uniform Resource Name) namespace that is engineered by the Organization for the Advancement of Structured Information Standards (OASIS) for naming persistent resources published by OASIS (such as OASIS Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents).",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/oasis" }]}},{
     "3187": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3187",
      "title": "Using International Standard Book Numbers as Uniform Resource Names",
      "name": "RFC 3187",
      "URI": "urn:ietf:rfc:3187",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3187",
      "abstract": "This document discusses how International Standard Book Numbers (ISBN) can be supported within the URN (Uniform Resource Names) framework and the syntax for URNs defined in RFC 2141. Much of the discussion below is based on the ideas expressed in RFC 2288.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/isbn" }]}},{
     "3229": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3229",
      "title": "Delta encoding in HTTP",
      "name": "RFC 3229",
      "URI": "urn:ietf:rfc:3229",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3229",
      "abstract": "This document describes how delta encoding can be supported as a compatible extension to HTTP/1.1. Many HTTP (Hypertext Transport Protocol) requests cause the retrieval of slightly modified instances of resources for which the client already has a cache entry. Research has shown that such modifying updates are frequent, and that the modifications are typically much smaller than the actual entity. In such cases, HTTP would make more efficient use of network bandwidth if it could transfer a minimal description of the changes, rather than the entire new instance of the resource. This is called \"delta encoding.\"",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/A-IM" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Delta-Base" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/IM" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/226" }]}},{
     "3230": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3230",
      "title": "Instance Digests in HTTP",
      "name": "RFC 3230",
      "URI": "urn:ietf:rfc:3230",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3230",
      "abstract": "HTTP/1.1 defines a Content-MD5 header that allows a server to include a digest of the response body.  However, this is specifically defined to cover the body of the actual message, not the contents of the full file (which might be quite different, if the response is a Content-Range, or uses a delta encoding).  Also, the Content-MD5 is limited to one specific digest algorithm; other algorithms, such as SHA-1 (Secure Hash Standard), may be more appropriate in some circumstances.  Finally, HTTP/1.1 provides no explicit mechanism by which a client may request a digest.  This document proposes HTTP extensions that solve these problems.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Digest" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Want-Digest" }]}},{
     "3253": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3253",
      "title": "Versioning Extensions to WebDAV (Web Distributed Authoring and Versioning)",
      "name": "RFC 3253",
      "URI": "urn:ietf:rfc:3253",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3253",
      "abstract": "This document specifies a set of methods, headers, and resource types that define the WebDAV (Web Distributed Authoring and Versioning) versioning extensions to the HTTP/1.1 protocol. WebDAV versioning will minimize the complexity of clients that are capable of interoperating with a variety of versioning repository managers, to facilitate widespread deployment of applications capable of utilizing the WebDAV Versioning services. WebDAV versioning includes automatic versioning for versioning-unaware clients, version history management, workspace management, baseline management, activity management, and URL namespace versioning.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Label" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/BASELINE-CONTROL" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/CHECKIN" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/CHECKOUT" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/LABEL" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MERGE" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MKACTIVITY" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MKWORKSPACE" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/REPORT" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/UNCHECKOUT" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/UPDATE" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/VERSION-CONTROL" }]}},{
     "3508": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3508",
      "title": "H.323 Uniform Resource Locator (URL) Scheme Registration",
      "name": "RFC 3508",
      "URI": "urn:ietf:rfc:3508",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3508",
      "abstract": "ITU-T Recommendation H.323 version 4 introduced an H.323-specific Uniform Resource Locator (URL). This document reproduces the H323-URL definition found in H.323, and is published as an RFC for ease of access and registration with the Internet Assigned Numbers Authority (IANA).",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/h323" }]}},{
     "3510": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3510",
      "title": "Internet Printing Protocol/1.1: IPP URL Scheme",
      "name": "RFC 3510",
      "URI": "urn:ietf:rfc:3510",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3510",
      "abstract": "This memo defines the \"ipp\" URL (Uniform Resource Locator) scheme. This memo updates IPP/1.1: Encoding and Transport (RFC 2910), by expanding and clarifying Section 5, \"IPP URL Scheme\", of RFC 2910. An \"ipp\" URL is used to specify the network location of a print service that supports the IPP Protocol (RFC 2910), or of a network resource (for example, a print job) managed by such a print service.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/ipp" }]}},{
     "3648": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3648",
      "title": "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol",
      "name": "RFC 3648",
      "URI": "urn:ietf:rfc:3648",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3648",
      "abstract": "This specification extends the Web Distributed Authoring and Versioning (WebDAV) Protocol to support the server-side ordering of collection members. Of particular interest are orderings that are not based on property values, and so cannot be achieved using a search protocol's ordering option and cannot be maintained automatically by the server. Protocol elements are defined to let clients specify the position in the ordering of each collection member, as well as the semantics governing the ordering.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Ordering-Type" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Position" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/ORDERPATCH" }]}},{
     "3744": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3744",
      "title": "Web Distributed Authoring and Versioning (WebDAV) Access Control Protocol",
      "name": "RFC 3744",
      "URI": "urn:ietf:rfc:3744",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3744",
      "abstract": "This document specifies a set of methods, headers, message bodies, properties, and reports that define Access Control extensions to the WebDAV Distributed Authoring Protocol. This protocol permits a client to read and modify access control lists that instruct a server whether to allow or deny operations upon a resource (such as HyperText Transfer Protocol (HTTP) method invocations) by a given principal. A lightweight representation of principals as Web resources supports integration of a wide range of user management repositories. Search operations allow discovery and manipulation of principals using human names.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/ACL" }]}},{
     "3859": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3859",
      "title": "Common Profile for Presence (CPP)",
      "name": "RFC 3859",
      "URI": "urn:ietf:rfc:3859",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3859",
      "abstract": "At the time this document was written, numerous presence protocols were in use (largely as components of commercial instant messaging services), and little interoperability between services based on these protocols has been achieved.  This specification defines common semantics and data formats for presence to facilitate the creation of gateways between presence services.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/pres" }]}},{
     "3860": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3860",
      "title": "Common Profile for Instant Messaging (CPIM)",
      "name": "RFC 3860",
      "URI": "urn:ietf:rfc:3860",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3860",
      "abstract": "At the time this document was written, numerous instant messaging protocols were in use, and little interoperability between services based on these protocols has been achieved. This specification defines common semantics and data formats for instant messaging to facilitate the creation of gateways between instant messaging services.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/im" }]}},{
     "3870": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3870",
      "title": "application/rdf+xml Media Type Registration",
      "name": "RFC 3870",
      "URI": "urn:ietf:rfc:3870",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3870",
      "abstract": "This document describes a media type (application/rdf+xml) for use with the Extensible Markup Language (XML) serialization of the Resource Description Framework (RDF). RDF is a language designed to support the Semantic Web, by facilitating resource description and data exchange on the Web. RDF provides common structures that can be used for interoperable data exchange and follows the World Wide Web Consortium (W3C) design principles of interoperability, evolution, and decentralization.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/rdf+xml" }]}},{
     "3902": {
      "id": "http://webconcepts.info/specs/IETF/RFC/3902",
      "title": "The \"application/soap+xml\" Media Type",
      "name": "RFC 3902",
      "URI": "urn:ietf:rfc:3902",
      "URL": "https://datatracker.ietf.org/doc/html/rfc3902",
      "abstract": "This document defines the \"application/soap+xml\" media type which can be used to describe SOAP 1.2 messages serialized as XML 1.0.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/soap+xml" }]}},{
     "4112": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4112",
      "title": "Electronic Commerce Modeling Language (ECML) Version 2 Specification",
      "name": "RFC 4112",
      "URI": "urn:ietf:rfc:4112",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4112",
      "abstract": "Electronic commerce frequently requires a substantial exchange of information in order to complete a purchase or other transaction, especially the first time the parties communicate. A standard set of hierarchically-organized payment-related information field names in an XML syntax is defined so that this task can be more easily automated. This is the second version of an Electronic Commerce Modeling Language (ECML) and is intended to meet the requirements of RFC 3505.",
      "concepts": [{
       "http://webconcepts.info/concepts/xml-ns/": "http://webconcepts.info/concepts/xml-ns/urn:ietf:params:xml:schema:ECMLv2" }]}},{
     "4122": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4122",
      "title": "A Universally Unique IDentifier (UUID) URN Namespace",
      "name": "RFC 4122",
      "URI": "urn:ietf:rfc:4122",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4122",
      "abstract": "This specification defines a Uniform Resource Name namespace for UUIDs (Universally Unique IDentifier), also known as GUIDs (Globally Unique IDentifier). A UUID is 128 bits long, and can guarantee uniqueness across space and time. UUIDs were originally used in the Apollo Network Computing System and later in the Open Software Foundation's (OSF) Distributed Computing Environment (DCE), and then in Microsoft Windows platforms. This specification is derived from the DCE specification with the kind permission of the OSF (now known as The Open Group). Information from earlier versions of the DCE specification have been incorporated into this document.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/uuid" }]}},{
     "4151": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4151",
      "title": "Content-ID and Message-ID Uniform Resource Locators",
      "name": "RFC 4151",
      "URI": "urn:ietf:rfc:4151",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4151",
      "abstract": "This document describes the \"tag\" Uniform Resource Identifier (URI) scheme. Tag URIs (also known as \"tags\") are designed to be unique across space and time while being tractable to humans. They are distinct from most other URIs in that they have no authoritative resolution mechanism. A tag may be used purely as an entity identifier. Furthermore, using tags has some advantages over the common practice of using \"http\" URIs as identifiers for non-HTTP-accessible resources.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/tag" }]}},{
     "4180": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4180",
      "title": "Common Format and MIME Type for Comma-Separated Values (CSV) Files",
      "name": "RFC 4180",
      "URI": "urn:ietf:rfc:4180",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4180",
      "abstract": "This RFC documents the format used for Comma-Separated Values (CSV) files and registers the associated MIME type \"text/csv\".",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/csv" }]}},{
     "4229": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4229",
      "title": "HTTP Header Field Registrations",
      "name": "RFC 4229",
      "URI": "urn:ietf:rfc:4229",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4229",
      "abstract": "This document defines the initial contents of a permanent IANA registry for HTTP header fields and a provisional repository for HTTP header fields",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Title" }]}},{
     "4248": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4248",
      "title": "The telnet URI Scheme",
      "name": "RFC 4248",
      "URI": "urn:ietf:rfc:4248",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4248",
      "abstract": "This document specifies the telnet Uniform Resource Identifier (URI) scheme that was originally specified in RFC 1738. The purpose of this document is to allow RFC 1738 to be made obsolete while keeping the information about the scheme on standards track.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/telnet" }]}},{
     "4287": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4287",
      "title": "Atom Syndication Format",
      "name": "RFC 4287",
      "URI": "urn:ietf:rfc:4287",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4287",
      "abstract": "Atom is an XML-based document format that describes lists of related information known as \"feeds\". Feeds are composed of a number of items, known as \"entries\", each with an extensible set of attached metadata. For example, each entry has a title.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/alternate" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/enclosure" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/related" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/self" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/via" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/atom+xml" }]}},{
     "4324": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4324",
      "title": "Calendar Access Protocol (CAP)",
      "name": "RFC 4324",
      "URI": "urn:ietf:rfc:4324",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4324",
      "abstract": "The Calendar Access Protocol (CAP) described in this memo permits a Calendar User (CU) to utilize a Calendar User Agent (CUA) to access an iCAL-based Calendar Store (CS). At the time of this writing, three vendors are implementing CAP, but it has already been determined that some changes are needed. In order to get implementation experience, the participants felt that a CAP specification is needed to preserve many years of work. Many properties in CAP which have had many years of debate, can be used by other iCalendar protocols.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/cap" }]}},{
     "4437": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4437",
      "title": "Web Distributed Authoring and Versioning (WebDAV): Redirect Reference Resources",
      "name": "RFC 4437",
      "URI": "urn:ietf:rfc:4437",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4437",
      "abstract": "This specification defines an extension to Web Distributed Authoring and Versioning (WebDAV) to allow clients to author HTTP redirect reference resources whose default response is an HTTP/1.1 3xx (Redirection) status code. A redirect reference makes it possible to access the target resourced indirectly through any URI mapped to the redirect reference resource. This specification does not address remapping of trees of resources or regular expression based redirections. There are no integrity guarantees associated with redirect reference resources. Other mechanisms can also be used to achieve the same functionality as this specification. This specification allows operators to experiment with this mechanism and develop experience on what is the best approach to the problem.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Apply-To-Redirect-Ref" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Redirect-Ref" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MKREDIRECTREF" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/UPDATEREDIRECTREF" }]}},{
     "4452": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4452",
      "title": "The \"info\" URI Scheme for Information Assets with Identifiers in Public Namespaces",
      "name": "RFC 4452",
      "URI": "urn:ietf:rfc:4452",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4452",
      "abstract": "This document defines the \"info\" Uniform Resource Identifier (URI) scheme for information assets with identifiers in public namespaces. Namespaces participating in the \"info\" URI scheme are regulated by an \"info\" Registry mechanism.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/info" }]}},{
     "4501": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4501",
      "title": "Domain Name System Uniform Resource Identifiers",
      "name": "RFC 4501",
      "URI": "urn:ietf:rfc:4501",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4501",
      "abstract": "This document defines Uniform Resource Identifiers for Domain Name System resources.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/dns" }]}},{
     "4559": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4559",
      "title": "SPNEGO-based Kerberos and NTLM HTTP Authentication in Microsoft Windows",
      "name": "RFC 4559",
      "URI": "urn:ietf:rfc:4559",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4559",
      "abstract": "This document describes how the Microsoft Internet Explorer (MSIE) and Internet Information Services (IIS) incorporated in Microsoft Windows 2000 use Kerberos for security enhancements of web transactions. The Hypertext Transport Protocol (HTTP) auth-scheme of \"negotiate\" is defined here; when the negotiation results in the selection of Kerberos, the security services of authentication and, optionally, impersonation (the IIS server assumes the windows identity of the principal that has been authenticated) are performed. This document explains how HTTP authentication utilizes the Simple and Protected GSS-API Negotiation mechanism. Details of Simple And Protected Negotiate (SPNEGO) implementation are not provided in this document.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/Negotiate" }]}},{
     "4729": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4729",
      "title": "A Uniform Resource Name (URN) Namespace for the Near Field Communication (NFC) Forum",
      "name": "RFC 4729",
      "URI": "urn:ietf:rfc:4729",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4729",
      "abstract": "This document describes the Namespace Identifier (NID) for Uniform Resource Name (URN) resources published by the Near Field Communication (NFC) Forum. The NFC Forum defines and manages resources that utilize this URN identification model. Management activities for these and other resource types are provided by the NFC Forum Technical Committee.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/nfc" }]}},{
     "4745": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4745",
      "title": "Common Policy: A Document Format for Expressing Privacy Preferences",
      "name": "RFC 4745",
      "URI": "urn:ietf:rfc:4745",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4745",
      "abstract": "This document defines a framework for authorization policies controlling access to application-specific data. This framework combines common location- and presence-specific authorization aspects. An XML schema specifies the language in which common policy rules are represented. The common policy framework can be extended to other application domains.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/auth-policy+xml" }, {
       "http://webconcepts.info/concepts/xml-ns/": "http://webconcepts.info/concepts/xml-ns/urn:ietf:params:xml:ns:common-policy" }, {
       "http://webconcepts.info/concepts/xml-schema/": "http://webconcepts.info/concepts/xml-schema/urn:ietf:params:xml:schema:common-policy" }]}},{
     "4791": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4791",
      "title": "Calendaring Extensions to WebDAV (CalDAV)",
      "name": "RFC 4791",
      "URI": "urn:ietf:rfc:4791",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4791",
      "abstract": "This document defines extensions to the Web Distributed Authoring and Versioning (WebDAV) protocol to specify a standard way of accessing, managing, and sharing calendaring and scheduling information based on the iCalendar format. This document defines the \"calendar-access\" feature of CalDAV.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MKCALENDAR" }]}},{
     "4918": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4918",
      "title": "HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)",
      "name": "RFC 4918",
      "URI": "urn:ietf:rfc:4918",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4918",
      "abstract": "Web Distributed Authoring and Versioning (WebDAV) consists of a set of methods, headers, and content-types ancillary to HTTP/1.1 for the management of resource properties, creation and management of resource collections, URL namespace manipulation, and resource locking (collision avoidance).",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/DAV" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Depth" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Destination" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Lock-Token" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Overwrite" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Timeout" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/COPY" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/LOCK" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MKCOL" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/MOVE" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/PROPFIND" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/PROPPATCH" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/UNLOCK" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/207" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/422" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/423" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/424" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/507" }]}},{
     "4946": {
      "id": "http://webconcepts.info/specs/IETF/RFC/4946",
      "title": "Atom License Extension",
      "name": "RFC 4946",
      "URI": "urn:ietf:rfc:4946",
      "URL": "https://datatracker.ietf.org/doc/html/rfc4946",
      "abstract": "This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/license" }]}},{
     "5005": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5005",
      "title": "Feed Paging and Archiving",
      "name": "RFC 5005",
      "URI": "urn:ietf:rfc:5005",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5005",
      "abstract": "Syndicated Web feeds (using formats such as Atom) are often split into multiple documents to save bandwidth, allow \"sliding window\" access, or for other purposes. This specification formalizes two types of feeds that can span one or more feed documents; \"paged\" feeds and \"archived\" feeds. Additionally, it defines \"complete\" feeds to cover the case when a single feed document explicitly represents all of the feed's entries.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/current" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/first" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/last" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/next" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/next-archive" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/prev-archive" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/previous" }]}},{
     "5023": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5023",
      "title": "Atom Publishing Protocol (AtomPub)",
      "name": "RFC 5023",
      "URI": "urn:ietf:rfc:5023",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5023",
      "abstract": "The Atom Publishing Protocol (AtomPub) is an application-level protocol for publishing and editing Web resources. The protocol is based on HTTP transfer of Atom-formatted representations. The Atom format is documented in the Atom Syndication Format.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Slug" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/edit" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/edit-media" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/atomcat+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/atomsvc+xml" }]}},{
     "5141": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5141",
      "title": "A Uniform Resource Name (URN) Namespace for the International Organization for Standardization (ISO)",
      "name": "RFC 5141",
      "URI": "urn:ietf:rfc:5141",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5141",
      "abstract": "This document describes a Uniform Resource Name Namespace Identification (URN NID) for the International Organization for Standardization (ISO). This URN NID is intended for use for the identification of persistent resources published by the ISO standards body (including documents, document metadata, extracted resources such as standard schemata and standard value sets, and other resources).",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/iso" }]}},{
     "5147": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5147",
      "title": "URI Fragment Identifiers for the text/plain Media Type",
      "name": "RFC 5147",
      "URI": "urn:ietf:rfc:5147",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5147",
      "abstract": "This memo defines URI fragment identifiers for text/plain MIME entities. These fragment identifiers make it possible to refer to parts of a text/plain MIME entity, either identified by character position or range, or by line position or range. Fragment identifiers may also contain information for integrity checks to make them more robust.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/plain" }]}},{
     "5261": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5261",
      "title": "An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors",
      "name": "RFC 5261",
      "URI": "urn:ietf:rfc:5261",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5261",
      "abstract": "Extensible Markup Language (XML) documents are widely used as containers for the exchange and storage of arbitrary data in today's systems. In order to send changes to an XML document, an entire copy of the new version must be sent, unless there is a means of indicating only the portions that have changed. This document describes an XML patch framework utilizing XML Path language (XPath) selectors. These selector values and updated new data content constitute the basis of patch operations described in this document. In addition to them, with basic <add>, <replace>, and <remove> directives a set of patches can then be applied to update an existing XML document.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/patch-ops-error+xml" }]}},{
     "5323": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5323",
      "title": "Web Distributed Authoring and Versioning (WebDAV) SEARCH",
      "name": "RFC 5323",
      "URI": "urn:ietf:rfc:5323",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5323",
      "abstract": "This document specifies a set of methods, headers, and properties composing Web Distributed Authoring and Versioning (WebDAV) SEARCH, an application of the HTTP/1.1 protocol to efficiently search for DAV resources based upon a set of client-supplied criteria.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/DASL" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/SEARCH" }]}},{
     "5724": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5724",
      "title": "URI Scheme for Global System for Mobile Communications (GSM) Short Message Service (SMS)",
      "name": "RFC 5724",
      "URI": "urn:ietf:rfc:5724",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5724",
      "abstract": "This memo specifies the Uniform Resource Identifier (URI) scheme \"sms\" for specifying one or more recipients for an SMS message. SMS messages are two-way paging messages that can be sent from and received by a mobile phone or a suitably equipped networked device.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/sms" }]}},{
     "5789": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5789",
      "title": "PATCH Method for HTTP",
      "name": "RFC 5789",
      "URI": "urn:ietf:rfc:5789",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5789",
      "abstract": "Several applications extending the Hypertext Transfer Protocol (HTTP) require a feature to do partial resource modification. The existing HTTP PUT method only allows a complete replacement of a document. This proposal adds a new HTTP method, PATCH, to modify an existing HTTP resource.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Patch" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/PATCH" }]}},{
     "5829": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5829",
      "title": "Link Relation Types for Simple Version Navigation between Web Resources",
      "name": "RFC 5829",
      "URI": "urn:ietf:rfc:5829",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5829",
      "abstract": "This specification defines a set of link relation types that may be used on Web resources for navigation between a resource and other resources related to version control, such as past versions and working copies.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/latest-version" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/predecessor-version" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/successor-version" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/version-history" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/working-copy" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/working-copy-of" }]}},{
     "5842": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5842",
      "title": "Binding Extensions to Web Distributed Authoring and Versioning (WebDAV)",
      "name": "RFC 5842",
      "URI": "urn:ietf:rfc:5842",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5842",
      "abstract": "This specification defines bindings, and the BIND method for creating multiple bindings to the same resource. Creating a new binding to a resource causes at least one new URI to be mapped to that resource. Servers are required to ensure the integrity of any bindings that they allow to be created.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/BIND" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/REBIND" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/UNBIND" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/208" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/508" }]}},{
     "5849": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5849",
      "title": "The OAuth 1.0 Protocol",
      "name": "RFC 5849",
      "URI": "urn:ietf:rfc:5849",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5849",
      "abstract": "OAuth provides a method for clients to access server resources on behalf of a resource owner (such as a different client or an end-user). It also provides a process for end-users to authorize third-party access to their server resources without sharing their credentials (typically, a username and password pair), using user-agent redirections.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/OAuth" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Authorization" }]}},{
     "5861": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5861",
      "title": "HTTP Cache-Control Extensions for Stale Content",
      "name": "RFC 5861",
      "URI": "urn:ietf:rfc:5861",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5861",
      "abstract": "This document defines two independent HTTP Cache-Control extensions that allow control over the use of stale responses by caches.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/stale-if-error" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/stale-while-revalidate" }]}},{
     "5870": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5870",
      "title": "A Uniform Resource Identifier for Geographic Locations ('geo' URI)",
      "name": "RFC 5870",
      "URI": "urn:ietf:rfc:5870",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5870",
      "abstract": "This document specifies a Uniform Resource Identifier (URI) for geographic locations using the 'geo' scheme name. A 'geo' URI identifies a physical location in a two- or three-dimensional coordinate reference system in a compact, simple, human-readable, and protocol-independent way. The default coordinate reference system used is the World Geodetic System 1984 (WGS-84).",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/geo" }]}},{
     "5985": {
      "id": "http://webconcepts.info/specs/IETF/RFC/5985",
      "title": "HTTP-Enabled Location Delivery (HELD)",
      "name": "RFC 5985",
      "URI": "urn:ietf:rfc:5985",
      "URL": "https://datatracker.ietf.org/doc/html/rfc5985",
      "abstract": "This document defines a Layer 7 Location Configuration Protocol (L7 LCP) and describes the use of HTTP and HTTP/TLS as transports for the L7 LCP. The L7 LCP is used for retrieving location information from a server within an access network. It includes options for retrieving location information in two forms: by value and by reference. The protocol is an extensible application-layer protocol that is independent of the session layer.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/held+xml" }]}},{
     "6017": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6017",
      "title": "Electronic Data Interchange - Internet Integration (EDIINT) Features Header Field",
      "name": "RFC 6017",
      "URI": "urn:ietf:rfc:6017",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6017",
      "abstract": "With the maturity of the Electronic Data Interchange - Internet Integration (EDIINT) standards of AS1, AS2, and AS3, applications and additional features are being built upon the basic secure transport functionality. These features are not necessarily supported by all EDIINT applications and could cause potential problems with implementations. The EDIINT-Features header field provides a means to resolve these problems and support new functionality.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/EDIINT-Features" }]}},{
     "6068": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6068",
      "title": "The 'mailto' URI Scheme",
      "name": "RFC 6068",
      "URI": "urn:ietf:rfc:6068",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6068",
      "abstract": "This document defines the format of Uniform Resource Identifiers (URIs) to identify resources that are reached using Internet mail. It adds better internationalization and compatibility with Internationalized Resource Identifiers to the previous syntax of 'mailto' URIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/mailto" }]}},{
     "6207": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6207",
      "title": "The Media Types application/mods+xml, application/mads+xml, application/mets+xml, application/marcxml+xml, and application/sru+xml",
      "name": "RFC 6207",
      "URI": "urn:ietf:rfc:6207",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6207",
      "abstract": "This document specifies media types for the following formats: MODS (Metadata Object Description Schema), MADS (Metadata Authority Description Schema), METS (Metadata Encoding and Transmission Standard), MARCXML (MARC21 XML Schema), and the SRU (Search/Retrieve via URL Response Format) protocol response XML schema. These are all XML schemas providing representations of various forms of information including metadata and search results.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/mads+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/marcxml+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/mets+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/mods+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/sru+xml" }]}},{
     "6265": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6265",
      "title": "HTTP State Management Mechanism",
      "name": "RFC 6265",
      "URI": "urn:ietf:rfc:6265",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6265",
      "abstract": "This document defines the HTTP Cookie and Set-Cookie header fields. These header fields can be used by HTTP servers to store state (called cookies) at HTTP user agents, letting the servers maintain a stateful session over the mostly stateless HTTP protocol. Although cookies have many historical infelicities that degrade their security and privacy, the Cookie and Set-Cookie header fields are widely used on the Internet.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cookie" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Set-Cookie" }]}},{
     "6266": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6266",
      "title": "Use of the Content-Disposition Header Field in the Hypertext Transfer Protocol (HTTP)",
      "name": "RFC 6266",
      "URI": "urn:ietf:rfc:6266",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6266",
      "abstract": "RFC 2616 defines the Content-Disposition response header field, but points out that it is not part of the HTTP/1.1 Standard. This specification takes over the definition and registration of Content-Disposition, as used in HTTP, and clarifies internationalization aspects.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Disposition" }]}},{
     "6271": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6271",
      "title": "The Atom \"deleted-entry\" Element",
      "name": "RFC 6271",
      "URI": "urn:ietf:rfc:6271",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6271",
      "abstract": "This specification adds mechanisms to the Atom Syndication Format that publishers of Atom Feed and Entry documents can use to explicitly identify Atom entries that have been removed.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/atomdeleted+xml" }]}},{
     "6350": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6350",
      "title": "vCard Format Specification",
      "name": "RFC 6350",
      "URI": "urn:ietf:rfc:6350",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6350",
      "abstract": "This document defines the vCard data format for representing and exchanging a variety of information about individuals and other entities (e.g., formatted and structured name and delivery addresses, email address, multiple telephone numbers, photograph, logo, audio clips, etc.). This document obsoletes RFCs 2425, 2426, and 4770, and updates RFC 2739.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/vcard" }]}},{
     "6351": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6351",
      "title": "xCard: vCard XML Representation",
      "name": "RFC 6351",
      "URI": "urn:ietf:rfc:6351",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6351",
      "abstract": "This document defines the XML schema of the vCard data format.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/vcard+xml" }]}},{
     "6415": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6415",
      "title": "Web Host Metadata",
      "name": "RFC 6415",
      "URI": "urn:ietf:rfc:6415",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6415",
      "abstract": "This specification describes a method for locating host metadata as well as information about individual resources controlled by the host.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/lrdd" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/host-meta" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/host-meta.json" }]}},{
     "6455": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6455",
      "title": "The WebSocket Protocol",
      "name": "RFC 6455",
      "URI": "urn:ietf:rfc:6455",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6455",
      "abstract": "The WebSocket Protocol enables two-way communication between a client running untrusted code in a controlled environment to a remote host that has opted-in to communications from that code. The security model used for this is the origin-based security model commonly used by web browsers. The protocol consists of an opening handshake followed by basic message framing, layered over TCP. The goal of this technology is to provide a mechanism for browser-based applications that need two-way communication with servers that does not rely on opening multiple HTTP connections (e.g., using XMLHttpRequest or <iframe>s and long polling).",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-WebSocket-Accept" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-WebSocket-Extensions" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-WebSocket-Key" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-WebSocket-Protocol" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-WebSocket-Version" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/ws" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/wss" }]}},{
     "6573": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6573",
      "title": "The Item and Collection Link Relations",
      "name": "RFC 6573",
      "URI": "urn:ietf:rfc:6573",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6573",
      "abstract": "RFC 5988 standardized a means of indicating the relationships between resources on the Web. This specification defines a pair of reciprocal link relation types that may be used to express the relationship between a collection and its members.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/collection" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/item" }]}},{
     "6579": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6579",
      "title": "The 'disclosure' Link Relation Type",
      "name": "RFC 6579",
      "URI": "urn:ietf:rfc:6579",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6579",
      "abstract": "This document specifies the 'disclosure' link relation type. It designates a list of IPR disclosures made with respect to the material for which such a relation type is specified.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/disclosure" }]}},{
     "6585": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6585",
      "title": "Additional HTTP Status Codes",
      "name": "RFC 6585",
      "URI": "urn:ietf:rfc:6585",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6585",
      "abstract": "This document specifies additional HyperText Transfer Protocol (HTTP) status codes for a variety of common situations.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/428" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/429" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/431" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/511" }]}},{
     "6596": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6596",
      "title": "The Canonical Link Relation",
      "name": "RFC 6596",
      "URI": "urn:ietf:rfc:6596",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6596",
      "abstract": "RFC 5988 specifies a way to define relationships between links on the web. This document describes a new type of such a relationship, \"canonical\", to designate an Internationalized Resource Identifier (IRI) as preferred over resources with duplicative content.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/canonical" }]}},{
     "6638": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6638",
      "title": "Scheduling Extensions to CalDAV",
      "name": "RFC 6638",
      "URI": "urn:ietf:rfc:6638",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6638",
      "abstract": "This document defines extensions to the Calendaring Extensions to WebDAV (CalDAV) \"calendar-access\" feature to specify a standard way of performing scheduling operations with iCalendar-based calendar components. This document defines the \"calendar-auto-schedule\" feature of CalDAV.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If-Schedule-Tag-Match" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Schedule-Reply" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Schedule-Tag" }]}},{
     "6690": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6690",
      "title": "Constrained RESTful Environments (CoRE) Link Format",
      "name": "RFC 6690",
      "URI": "urn:ietf:rfc:6690",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6690",
      "abstract": "This specification defines Web Linking using a link format for use by constrained web servers to describe hosted resources, their attributes, and other relationships between links. Based on the HTTP Link Header field defined in RFC 5988, the Constrained RESTful Environments (CoRE) Link Format is carried as a payload and is assigned an Internet media type. \"RESTful\" refers to the Representational State Transfer (REST) architecture. A well-known URI is defined as a default entry point for requesting the links hosted by a server.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/hosts" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/link-format" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/core" }]}},{
     "6694": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6694",
      "title": "The \"about\" URI Scheme",
      "name": "RFC 6694",
      "URI": "urn:ietf:rfc:6694",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6694",
      "abstract": "This document describes the \"about\" URI scheme, which is widely used by Web browsers and some other applications to designate access to their internal resources, such as settings, application information, hidden built-in functionality, and so on.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/about" }]}},{
     "6713": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6713",
      "title": "The 'application/zlib' and 'application/gzip' Media Types",
      "name": "RFC 6713",
      "URI": "urn:ietf:rfc:6713",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6713",
      "abstract": "This document defines the 'application/gzip' and 'application/zlib' media types for compressed data using the gzip and zlib compression formats.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/gzip" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/zlib" }]}},{
     "6749": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6749",
      "title": "The OAuth 2.0 Authorization Framework",
      "name": "RFC 6749",
      "URI": "urn:ietf:rfc:6749",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6749",
      "abstract": "The OAuth 2.0 authorization framework enables a third-party application to obtain limited access to an HTTP service, either on behalf of a resource owner by orchestrating an approval interaction between the resource owner and the HTTP service, or by allowing the third-party application to obtain access on its own behalf. This specification replaces and obsoletes the OAuth 1.0 protocol described in RFC 5849.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-authorization-endpoint-response-type/": "http://webconcepts.info/concepts/oauth-authorization-endpoint-response-type/code" }, {
       "http://webconcepts.info/concepts/oauth-authorization-endpoint-response-type/": "http://webconcepts.info/concepts/oauth-authorization-endpoint-response-type/token" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/access_token" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/client_id" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/client_secret" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/code" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/error" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/error_description" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/error_uri" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/expires_in" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/grant_type" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/password" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/redirect_uri" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/refresh_token" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/response_type" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/scope" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/state" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/token_type" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/username" }]}},{
     "6750": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6750",
      "title": "The OAuth 2.0 Authorization Framework: Bearer Token Usage",
      "name": "RFC 6750",
      "URI": "urn:ietf:rfc:6750",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6750",
      "abstract": "This specification describes how to use bearer tokens in HTTP requests to access OAuth 2.0 protected resources. Any party in possession of a bearer token (a \"bearer\") can use it to get access to the associated resources (without demonstrating possession of a cryptographic key). To prevent misuse, bearer tokens need to be protected from disclosure in storage and in transport.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/Bearer" }, {
       "http://webconcepts.info/concepts/oauth-access-token-type/": "http://webconcepts.info/concepts/oauth-access-token-type/Bearer" }, {
       "http://webconcepts.info/concepts/oauth-extension-error/": "http://webconcepts.info/concepts/oauth-extension-error/insufficient_scope" }, {
       "http://webconcepts.info/concepts/oauth-extension-error/": "http://webconcepts.info/concepts/oauth-extension-error/invalid_request" }, {
       "http://webconcepts.info/concepts/oauth-extension-error/": "http://webconcepts.info/concepts/oauth-extension-error/invalid_token" }]}},{
     "6764": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6764",
      "title": "Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)",
      "name": "RFC 6764",
      "URI": "urn:ietf:rfc:6764",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6764",
      "abstract": "This specification describes how DNS SRV records, DNS TXT records, and well-known URIs can be used together or separately to locate CalDAV (Calendaring Extensions to Web Distributed Authoring and Versioning (WebDAV)) or CardDAV (vCard Extensions to WebDAV) services.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/caldav" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/carddav" }]}},{
     "6768": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6768",
      "title": "Media Resource Control Protocol Version 2 (MRCPv2)",
      "name": "RFC 6768",
      "URI": "urn:ietf:rfc:6768",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6768",
      "abstract": "The Media Resource Control Protocol Version 2 (MRCPv2) allows client hosts to control media service resources such as speech synthesizers, recognizers, verifiers, and identifiers residing in servers on the network. MRCPv2 is not a \"stand-alone\" protocol -- it relies on other protocols, such as the Session Initiation Protocol (SIP), to coordinate MRCPv2 clients and servers and manage sessions between them, and the Session Description Protocol (SDP) to describe, discover, and exchange capabilities. It also depends on SIP and SDP to establish the media sessions and associated parameters between the media source or sink and the media server. Once this is done, the MRCPv2 exchange operates over the control session established above, allowing the client to control the media processing resources on the speech resource server.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/nlsml+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/grammar-ref-list" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/session" }]}},{
     "6772": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6772",
      "title": "Geolocation Policy: A Document Format for Expressing Privacy Preferences for Location Information",
      "name": "RFC 6772",
      "URI": "urn:ietf:rfc:6772",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6772",
      "abstract": "This document defines an authorization policy language for controlling access to location information.  It extends the Common Policy authorization framework to provide location-specific access control.  More specifically, this document defines condition elements specific to location information in order to restrict access to data based on the current location of the Target. Furthermore, this document defines two algorithms for reducing the granularity of returned location information.  The first algorithm is defined for usage with civic location information, whereas the other one applies to geodetic location information.  Both algorithms come with limitations.  There are circumstances where the amount of location obfuscation provided is less than what is desired.  These algorithms might not be appropriate for all application domains.",
      "concepts": [{
       "http://webconcepts.info/concepts/xml-ns/": "http://webconcepts.info/concepts/xml-ns/urn:ietf:params:xml:ns:basic-location-profiles" }, {
       "http://webconcepts.info/concepts/xml-ns/": "http://webconcepts.info/concepts/xml-ns/urn:ietf:params:xml:ns:geolocation-policy" }, {
       "http://webconcepts.info/concepts/xml-schema/": "http://webconcepts.info/concepts/xml-schema/urn:ietf:params:xml:schema:basic-location-profiles" }, {
       "http://webconcepts.info/concepts/xml-schema/": "http://webconcepts.info/concepts/xml-schema/urn:ietf:params:xml:schema:geolocation-policy" }]}},{
     "6797": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6797",
      "title": "HTTP Strict Transport Security (HSTS)",
      "name": "RFC 6797",
      "URI": "urn:ietf:rfc:6797",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6797",
      "abstract": "This specification defines a mechanism enabling web sites to declare themselves accessible only via secure connections and/or for users to be able to direct their user agent(s) to interact with given sites only over secure connections. This overall policy is referred to as HTTP Strict Transport Security (HSTS). The policy is declared by web sites via the Strict-Transport-Security HTTP response header field and/or by other means, such as user agent configuration, for example.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Strict-Transport-Security" }]}},{
     "6839": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6839",
      "title": "Additional Media Type Structured Syntax Suffixes",
      "name": "RFC 6839",
      "URI": "urn:ietf:rfc:6839",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6839",
      "abstract": "A content media type name sometimes includes partitioned meta-information distinguished by a structured syntax to permit noting an attribute of the media as a suffix to the name. This document defines several structured syntax suffixes for use with media type registrations. In particular, it defines and registers the \"+json\", \"+ber\", \"+der\", \"+fastinfoset\", \"+wbxml\" and \"+zip\" structured syntax suffixes, and provides a media type structured syntax suffix registration form for the \"+xml\" structured syntax suffix.",
      "concepts": [{
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+ber" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+der" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+fastinfoset" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+json" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+wbxml" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+zip" }]}},{
     "6861": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6861",
      "title": "The \"create-form\" and \"edit-form\" Link Relations",
      "name": "RFC 6861",
      "URI": "urn:ietf:rfc:6861",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6861",
      "abstract": "RFC 5988 standardized a means of indicating the relationships between resources on the Web. This specification defines link relation types that may be used to express the relationships between a resource and an input form for constructing data submissions.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/create-form" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/edit-form" }]}},{
     "6892": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6892",
      "title": "The 'describes' Link Relation Type",
      "name": "RFC 6892",
      "URI": "urn:ietf:rfc:6892",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6892",
      "abstract": "This specification defines the 'describes' link relation type that allows resource representations to indicate that they are describing another resource. In contexts where applications want to associate described resources and description resources, and want to build services based on these associations, the 'describes' link relation type provides the opposite direction of the 'describedby' link relation type, which already is a registered link relation type.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/describes" }]}},{
     "6902": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6902",
      "title": "JavaScript Object Notation (JSON) Patch",
      "name": "RFC 6902",
      "URI": "urn:ietf:rfc:6902",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6902",
      "abstract": "JSON Patch defines a JSON document structure for expressing a sequence of operations to apply to a JavaScript Object Notation (JSON) document; it is suitable for use with the HTTP PATCH method. The \"application/json-patch+json\" media type is used to identify such patch documents.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/json-patch+json" }]}},{
     "6903": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6903",
      "title": "Additional Link Relation Types",
      "name": "RFC 6903",
      "URI": "urn:ietf:rfc:6903",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6903",
      "abstract": "This specification defines a number of additional link relation types that can be used for a range of purposes in a variety of applications types.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/about" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/preview" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/privacy-policy" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/terms-of-service" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/type" }]}},{
     "6906": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6906",
      "title": "The 'profile' Link Relation Type",
      "name": "RFC 6906",
      "URI": "urn:ietf:rfc:6906",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6906",
      "abstract": "This specification defines the 'profile' link relation type that allows resource representations to indicate that they are following one or more profiles. A profile is defined not to alter the semantics of the resource representation itself, but to allow clients to learn about additional semantics (constraints, conventions, extensions) that are associated with the resource representation, in addition to those defined by the media type and possibly other mechanisms.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/profile" }]}},{
     "6920": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6920",
      "title": "Naming Things with Hashes",
      "name": "RFC 6920",
      "URI": "urn:ietf:rfc:6920",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6920",
      "abstract": "This document defines a set of ways to identify a thing (a digital object in this case) using the output from a hash function. It specifies a new URI scheme for this purpose, a way to map these to HTTP URLs, and binary and human-speakable formats for these names. The various formats are designed to support, but not require, a strong link to the referenced object, such that the referenced object may be authenticated to the same degree as the reference to it. The reason for this work is to standardise current uses of hash outputs in URLs and to support new information-centric applications and other uses of hash outputs in protocols.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/ni" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/nih" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/ni" }]}},{
     "6922": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6922",
      "title": "The application/sql Media Type",
      "name": "RFC 6922",
      "URI": "urn:ietf:rfc:6922",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6922",
      "abstract": "This document registers the application/sql media type to be used for the Structured Query Language (SQL).",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/sql" }]}},{
     "6940": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6940",
      "title": "REsource LOcation And Discovery (RELOAD) Base Protocol",
      "name": "RFC 6940",
      "URI": "urn:ietf:rfc:6940",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6940",
      "abstract": "This specification defines REsource LOcation And Discovery (RELOAD), a peer-to-peer (P2P) signaling protocol for use on the Internet. A P2P signaling protocol provides its clients with an abstract storage and messaging service between a set of cooperating peers that form the overlay network. RELOAD is designed to support a P2P Session Initiation Protocol (P2PSIP) network, but can be utilized by other applications with similar requirements by defining new usages that specify the Kinds of data that need to be stored for a particular application. RELOAD defines a security model based on a certificate enrollment service that provides unique identities. NAT traversal is a fundamental service of the protocol. RELOAD also allows access from \"client\" nodes that do not need to route traffic or store data for others.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/p2p-overlay+xml" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/reload" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/reload-config" }]}},{
     "6963": {
      "id": "http://webconcepts.info/specs/IETF/RFC/6963",
      "title": "A Uniform Resource Name (URN) Namespace for Examples",
      "name": "RFC 6963",
      "URI": "urn:ietf:rfc:6963",
      "URL": "https://datatracker.ietf.org/doc/html/rfc6963",
      "abstract": "This document defines a Uniform Resource Name (URN) namespace identifier enabling the generation of URNs that are appropriate for use in documentation and in URN-related testing and experimentation.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/example" }]}},{
     "7009": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7009",
      "title": "OAuth 2.0 Token Revocation",
      "name": "RFC 7009",
      "URI": "urn:ietf:rfc:7009",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7009",
      "abstract": "This document proposes an additional endpoint for OAuth authorization servers, which allows clients to notify the authorization server that a previously obtained refresh or access token is no longer needed. This allows the authorization server to clean up security credentials. A revocation request will invalidate the actual token and, if applicable, other tokens based on the same authorization grant.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-extension-error/": "http://webconcepts.info/concepts/oauth-extension-error/unsupported_token_type" }, {
       "http://webconcepts.info/concepts/oauth-token-type-hint/": "http://webconcepts.info/concepts/oauth-token-type-hint/access_token" }, {
       "http://webconcepts.info/concepts/oauth-token-type-hint/": "http://webconcepts.info/concepts/oauth-token-type-hint/refresh_token" }]}},{
     "7030": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7030",
      "title": "Enrollment over Secure Transport",
      "name": "RFC 7030",
      "URI": "urn:ietf:rfc:7030",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7030",
      "abstract": "This document profiles certificate enrollment for clients using Certificate Management over CMS (CMC) messages over a secure transport. This profile, called Enrollment over Secure Transport (EST), describes a simple, yet functional, certificate management protocol targeting Public Key Infrastructure (PKI) clients that need to acquire client certificates and associated Certification Authority (CA) certificates. It also supports client-generated public/private key pairs as well as key pairs generated by the CA.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/csrattrs" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/est" }]}},{
     "7033": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7033",
      "title": "WebFinger",
      "name": "RFC 7033",
      "URI": "urn:ietf:rfc:7033",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7033",
      "abstract": "This specification defines the WebFinger protocol, which can be used to discover information about people or other entities on the Internet using standard HTTP methods. WebFinger discovers information for a URI that might not be usable as a locator otherwise, such as account or email URIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/jrd+json" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/webfinger" }]}},{
     "7034": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7034",
      "title": "HTTP Header Field X-Frame-Options",
      "name": "RFC 7034",
      "URI": "urn:ietf:rfc:7034",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7034",
      "abstract": "To improve the protection of web applications against clickjacking, this document describes the X-Frame-Options HTTP header field, which declares a policy, communicated from the server to the client browser, regarding whether the browser may display the transmitted content in frames that are part of other web pages.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/X-Frame-Options" }]}},{
     "7049": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7049",
      "title": "Concise Binary Object Representation (CBOR)",
      "name": "RFC 7049",
      "URI": "urn:ietf:rfc:7049",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7049",
      "abstract": "The Concise Binary Object Representation (CBOR) is a data format whose design goals include the possibility of extremely small code size, fairly small message size, and extensibility without the need for version negotiation. These design goals make it different from earlier binary serializations such as ASN.1 and MessagePack.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/cbor" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+cbor" }]}},{
     "7072": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7072",
      "title": "A Reputation Query Protocol",
      "name": "RFC 7072",
      "URI": "urn:ietf:rfc:7072",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7072",
      "abstract": "This document defines a mechanism to conduct queries for reputation information over the HyperText Transfer Protocol (HTTP) using JavaScript Object Notation (JSON) as the payload meta-format.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/repute-template" }]}},{
     "7089": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7089",
      "title": "HTTP framework for time-based access to resource states - Memento",
      "name": "RFC 7089",
      "URI": "urn:ietf:rfc:7089",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7089",
      "abstract": "The HTTP-based Memento framework bridges the present and past Web. It facilitates obtaining representations of prior states of a given resource by introducing datetime negotiation and TimeMaps. Datetime negotiation is a variation on content negotiation that leverages the given resource's URI and a user agent's preferred datetime. TimeMaps are lists that enumerate URIs of resources that encapsulate prior states of the given resource. The framework also facilitates recognizing a resource that encapsulates a frozen prior state of another resource.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Datetime" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Memento-Datetime" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/memento" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/original" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/timegate" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/timemap" }]}},{
     "7111": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7111",
      "title": "URI Fragment Identifiers for the text/csv Media Type",
      "name": "RFC 7111",
      "URI": "urn:ietf:rfc:7111",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7111",
      "abstract": "This memo defines URI fragment identifiers for text/csv MIME entities. These fragment identifiers make it possible to refer to parts of a text/csv MIME entity identified by row, column, or cell. Fragment identification can use single items or ranges.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/csv" }]}},{
     "7168": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7168",
      "title": "The Hyper Text Coffee Pot Control Protocol for Tea Efflux Appliances (HTCPCP-TEA)",
      "name": "RFC 7168",
      "URI": "urn:ietf:rfc:7168",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7168",
      "abstract": "The Hyper Text Coffee Pot Control Protocol (HTCPCP) specification does not allow for the brewing of tea, in all its variety and complexity. This paper outlines an extension to HTCPCP to allow for pots to provide networked tea-brewing facilities.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Additions" }]}},{
     "7207": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7207",
      "title": "A Uniform Resource Name (URN) Namespace for Eurosystem Messaging",
      "name": "RFC 7207",
      "URI": "urn:ietf:rfc:7207",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7207",
      "abstract": "This document defines and registers with IANA a Uniform Resource Name (URN) namespace for usage within messages standardized by the Eurosystem. The URN namespace is managed by Deutsche Bundesbank, which is a member of the European System of Central Banks (ESCB).",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/eurosystem" }]}},{
     "7230": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7230",
      "title": "Hypertext Transfer Protocol (HTTP/1.1): Message Syntax and Routing",
      "name": "RFC 7230",
      "URI": "urn:ietf:rfc:7230",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7230",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document provides an overview of HTTP architecture and its associated terminology, defines the \"http\" and \"https\" Uniform Resource Identifier (URI) schemes, defines the HTTP/1.1 message syntax and parsing requirements, and describes general security concerns for implementations.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/compress" }, {
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/deflate" }, {
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/gzip" }, {
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/x-compress" }, {
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/x-gzip" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Close" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Connection" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Length" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Host" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/TE" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Trailer" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Transfer-Encoding" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Upgrade" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Via" }, {
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/chunked" }, {
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/compress" }, {
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/deflate" }, {
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/gzip" }, {
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/x-compress" }, {
       "http://webconcepts.info/concepts/http-transfer-coding/": "http://webconcepts.info/concepts/http-transfer-coding/x-gzip" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/http" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/message/http" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/http" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/https" }]}},{
     "7231": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7231",
      "title": "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content",
      "name": "RFC 7231",
      "URI": "urn:ietf:rfc:7231",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7231",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/identity" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Charset" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Encoding" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Language" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Allow" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Encoding" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Language" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Location" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Type" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Date" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Expect" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/From" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Location" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/MIME-Version" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Max-Forwards" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Referer" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Retry-After" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Server" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/User-Agent" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Vary" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/CONNECT" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/DELETE" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/GET" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/HEAD" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/OPTIONS" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/POST" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/PUT" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/TRACE" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/100" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/101" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/200" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/201" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/202" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/203" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/204" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/205" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/300" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/301" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/302" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/303" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/305" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/306" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/307" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/400" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/402" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/403" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/404" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/405" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/406" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/408" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/409" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/410" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/411" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/413" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/414" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/415" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/417" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/426" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/500" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/501" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/502" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/503" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/504" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/505" }]}},{
     "7232": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7232",
      "title": "Hypertext Transfer Protocol (HTTP/1.1): Conditional Requests",
      "name": "RFC 7232",
      "URI": "urn:ietf:rfc:7232",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7232",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/ETag" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If-Match" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If-Modified-Since" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If-None-Match" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If-Unmodified-Since" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Last-Modified" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/304" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/412" }]}},{
     "7233": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7233",
      "title": "Hypertext Transfer Protocol (HTTP/1.1): Range Requests",
      "name": "RFC 7233",
      "URI": "urn:ietf:rfc:7233",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7233",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Ranges" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Range" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/If-Range" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Range" }, {
       "http://webconcepts.info/concepts/http-range-unit/": "http://webconcepts.info/concepts/http-range-unit/bytes" }, {
       "http://webconcepts.info/concepts/http-range-unit/": "http://webconcepts.info/concepts/http-range-unit/none" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/206" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/416" }]}},{
     "7234": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7234",
      "title": "Hypertext Transfer Protocol (HTTP/1.1): Caching",
      "name": "RFC 7234",
      "URI": "urn:ietf:rfc:7234",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7234",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/max-age" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/max-stale" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/min-fresh" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/must-revalidate" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/no-cache" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/no-store" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/no-transform" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/only-if-cached" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/private" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/proxy-revalidate" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/public" }, {
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/s-maxage" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Age" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Cache-Control" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Expires" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Pragma" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Warning" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/110" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/111" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/112" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/113" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/199" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/214" }, {
       "http://webconcepts.info/concepts/http-warn-code/": "http://webconcepts.info/concepts/http-warn-code/299" }]}},{
     "7235": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7235",
      "title": "Hypertext Transfer Protocol (HTTP/1.1): Authentication",
      "name": "RFC 7235",
      "URI": "urn:ietf:rfc:7235",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7235",
      "abstract": "The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Authorization" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Proxy-Authenticate" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Proxy-Authorization" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/WWW-Authenticate" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/401" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/407" }]}},{
     "7239": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7239",
      "title": "Forwarded HTTP Extension",
      "name": "RFC 7239",
      "URI": "urn:ietf:rfc:7239",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7239",
      "abstract": "This document defines an HTTP extension header field that allows proxy components to disclose information lost in the proxying process, for example, the originating IP address of a request or IP address of the proxy on the user-agent-facing interface. In a path of proxying components, this makes it possible to arrange it so that each subsequent component will have access to, for example, all IP addresses used in the chain of proxied HTTP requests. This document also specifies guidelines for a proxy administrator to anonymize the origin of a request.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-forwarded-parameter/": "http://webconcepts.info/concepts/http-forwarded-parameter/by" }, {
       "http://webconcepts.info/concepts/http-forwarded-parameter/": "http://webconcepts.info/concepts/http-forwarded-parameter/for" }, {
       "http://webconcepts.info/concepts/http-forwarded-parameter/": "http://webconcepts.info/concepts/http-forwarded-parameter/host" }, {
       "http://webconcepts.info/concepts/http-forwarded-parameter/": "http://webconcepts.info/concepts/http-forwarded-parameter/proto" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Forwarded" }]}},{
     "7240": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7240",
      "title": "Prefer Header for HTTP",
      "name": "RFC 7240",
      "URI": "urn:ietf:rfc:7240",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7240",
      "abstract": "This specification defines an HTTP header field that can be used by a client to request that certain behaviors be employed by a server while processing a request.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Prefer" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Preference-Applied" }, {
       "http://webconcepts.info/concepts/http-preference/": "http://webconcepts.info/concepts/http-preference/handling" }, {
       "http://webconcepts.info/concepts/http-preference/": "http://webconcepts.info/concepts/http-preference/respond-async" }, {
       "http://webconcepts.info/concepts/http-preference/": "http://webconcepts.info/concepts/http-preference/return" }, {
       "http://webconcepts.info/concepts/http-preference/": "http://webconcepts.info/concepts/http-preference/wait" }]}},{
     "7284": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7284",
      "title": "The Profile URI Registry",
      "name": "RFC 7284",
      "URI": "urn:ietf:rfc:7284",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7284",
      "abstract": "This document defines a registry for profile URIs to be used in specifications standardizing profiles.",
      "concepts": [{
       "http://webconcepts.info/concepts/profile-uri/": "http://webconcepts.info/concepts/profile-uri/urn:example:profile-uri" }]}},{
     "7303": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7303",
      "title": "XML Media Types",
      "name": "RFC 7303",
      "URI": "urn:ietf:rfc:7303",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7303",
      "abstract": "This specification standardizes three media types - application/xml, application/xml-external-parsed-entity, and application/xml-dtd - for use in exchanging network entities that are related to the Extensible Markup Language (XML) while defining text/xml and text/xml-external-parsed-entity as aliases for the respective application/ types. This specification also standardizes the '+xml' suffix for naming media types outside of these five types when those media types represent XML MIME entities.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/xml-dtd" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/xml-external-parsed-entity" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+xml" }]}},{
     "7351": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7351",
      "title": "A Media Type for XML Patch Operations",
      "name": "RFC 7351",
      "URI": "urn:ietf:rfc:7351",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7351",
      "abstract": "The XML Patch media type \"application/xml-patch+xml\" defines an XML document structure for expressing a sequence of patch operations that are applied to an XML document. The XML Patch document format's foundations are defined in RFC 5261, this specification defines a document format and a media type registration, so that XML Patch documents can be labeled with a media type, for example in HTTP conversations. In addition to the media type registration, this specification also updates RFC 5261 in some aspects, limiting these updates to cases where RFC 5261 needed to be fixed, or was hard to understand.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/xml-patch+xml" }]}},{
     "7390": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7390",
      "title": "Group Communication for the Constrained Application Protocol (CoAP)",
      "name": "RFC 7390",
      "URI": "urn:ietf:rfc:7390",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7390",
      "abstract": "The Constrained Application Protocol (CoAP) is a specialized web transfer protocol for constrained devices and constrained networks. It is anticipated that constrained devices will often naturally operate in groups (e.g., in a building automation scenario, all lights in a given room may need to be switched on/off as a group). This specification defines how CoAP should be used in a group communication context.  An approach for using CoAP on top of IP multicast is detailed based on existing CoAP functionality as well as new features introduced in this specification.  Also, various use cases and corresponding protocol flows are provided to illustrate important concepts.  Finally, guidance is provided for deployment in various network topologies.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/coap-group+json" }]}},{
     "7396": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7396",
      "title": "JSON Merge Patch",
      "name": "RFC 7396",
      "URI": "urn:ietf:rfc:7396",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7396",
      "abstract": "This specification defines the JSON merge patch format and processing rules. The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/merge-patch+json" }]}},{
     "7464": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7464",
      "title": "JavaScript Object Notation (JSON) Text Sequences",
      "name": "RFC 7464",
      "URI": "urn:ietf:rfc:7464",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7464",
      "abstract": "This document describes the JavaScript Object Notation (JSON) text sequence format and associated media type \"application/json-seq\". A JSON text sequence consists of any number of JSON texts, all encoded in UTF-8, each prefixed by an ASCII Record Separator (0x1E), and each ending with an ASCII Line Feed character (0x0A).",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/json-seq" }]}},{
     "7469": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7469",
      "title": "Public Key Pinning Extension for HTTP",
      "name": "RFC 7469",
      "URI": "urn:ietf:rfc:7469",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7469",
      "abstract": "This document defines a new HTTP header that allows web host operators to instruct user agents to remember (\"pin\") the hosts' cryptographic identities over a period of time. During that time, user agents (UAs) will require that the host presents a certificate chain including at least one Subject Public Key Info structure whose fingerprint matches one of the pinned fingerprints for that host. By effectively reducing the number of trusted authorities who can authenticate the domain during the lifetime of the pin, pinning may reduce the incidence of man-in-the-middle attacks due to compromised Certification Authorities.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Public-Key-Pins" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Public-Key-Pins-Report-Only" }]}},{
     "7486": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7486",
      "title": "HTTP Origin-Bound Authentication (HOBA)",
      "name": "RFC 7486",
      "URI": "urn:ietf:rfc:7486",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7486",
      "abstract": "HTTP Origin-Bound Authentication (HOBA) is a digital-signature-based design for an HTTP authentication method. The design can also be used in JavaScript-based authentication embedded in HTML. HOBA is an alternative to HTTP authentication schemes that require passwords and therefore avoids all problems related to passwords, such as leakage of server-side password databases.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/HOBA" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Hobareg" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/hoba" }]}},{
     "7512": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7512",
      "title": "The PKCS #11 URI Scheme",
      "name": "RFC 7512",
      "URI": "urn:ietf:rfc:7512",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7512",
      "abstract": "This memo specifies a PKCS #11 Uniform Resource Identifier (URI) Scheme for identifying PKCS #11 objects stored in PKCS #11 tokens and also for identifying PKCS #11 tokens, slots, or libraries.  The URI scheme is based on how PKCS #11 objects, tokens, slots, and libraries are identified in \"PKCS #11 v2.20: Cryptographic Token Interface Standard\".",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/pkcs11" }]}},{
     "7515": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7515",
      "title": "JSON Web Signature (JWS)",
      "name": "RFC 7515",
      "URI": "urn:ietf:rfc:7515",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7515",
      "abstract": "JSON Web Signature (JWS) represents content secured with digital signatures or Message Authentication Codes (MACs) using JSON-based data structures. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and an IANA registry defined by that specification. Related encryption capabilities are described in the separate JSON Web Encryption (JWE) specification.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/jose" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/jose+json" }]}},{
     "7517": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7517",
      "title": "JSON Web Key (JWK)",
      "name": "RFC 7517",
      "URI": "urn:ietf:rfc:7517",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7517",
      "abstract": "A JSON Web Key (JWK) is a JavaScript Object Notation (JSON) data structure that represents a cryptographic key. This specification also defines a JWK Set JSON data structure that represents a set of JWKs. Cryptographic algorithms and identifiers for use with this specification are described in the separate JSON Web Algorithms (JWA) specification and IANA registries established by that specification.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/jwk+json" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/jwk-set+json" }]}},{
     "7519": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7519",
      "title": "JSON Web Token (JWT)",
      "name": "RFC 7519",
      "URI": "urn:ietf:rfc:7519",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7519",
      "abstract": "JSON Web Token (JWT) is a compact, URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JSON object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or integrity protected with a Message Authentication Code (MAC) and/or encrypted.",
      "concepts": [{
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/aud" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/exp" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/iat" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/iss" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/jti" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/nbf" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/sub" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/jwt" }, {
       "http://webconcepts.info/concepts/oauth-uri/": "http://webconcepts.info/concepts/oauth-uri/urn:ietf:params:oauth:token-type:jwt" }]}},{
     "7521": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7521",
      "title": "Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants",
      "name": "RFC 7521",
      "URI": "urn:ietf:rfc:7521",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7521",
      "abstract": "This specification provides a framework for the use of assertions with OAuth 2.0 in the form of a new client authentication mechanism and a new authorization grant type. Mechanisms are specified for transporting assertions during interactions with a token endpoint; general processing rules are also specified. The intent of this specification is to provide a common framework for OAuth 2.0 to interwork with other identity systems using assertions and to provide alternative client authentication mechanisms. Note that this specification only defines abstract message flows and processing rules. In order to be implementable, companion specifications are necessary to provide the corresponding concrete instantiations.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/assertion" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/client_assertion" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/client_assertion_type" }]}},{
     "7522": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7522",
      "title": "Security Assertion Markup Language (SAML) 2.0 Profile for OAuth 2.0 Client Authentication and Authorization Grants",
      "name": "RFC 7522",
      "URI": "urn:ietf:rfc:7522",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7522",
      "abstract": "This specification defines the use of a Security Assertion Markup Language (SAML) 2.0 Bearer Assertion as a means for requesting an OAuth 2.0 access token as well as for client authentication.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-uri/": "http://webconcepts.info/concepts/oauth-uri/urn:ietf:params:oauth:client-assertion-type:saml2-bearer" }, {
       "http://webconcepts.info/concepts/oauth-uri/": "http://webconcepts.info/concepts/oauth-uri/urn:ietf:params:oauth:grant-type:saml2-bearer" }]}},{
     "7523": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7523",
      "title": "JSON Web Token (JWT) Profile for OAuth 2.0 Client Authentication and Authorization Grants",
      "name": "RFC 7523",
      "URI": "urn:ietf:rfc:7523",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7523",
      "abstract": "This specification defines the use of a JSON Web Token (JWT) Bearer Token as a means for requesting an OAuth 2.0 access token as well as for client authentication.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-uri/": "http://webconcepts.info/concepts/oauth-uri/urn:ietf:params:oauth:client-assertion-type:jwt-bearer" }, {
       "http://webconcepts.info/concepts/oauth-uri/": "http://webconcepts.info/concepts/oauth-uri/urn:ietf:params:oauth:grant-type:jwt-bearer" }]}},{
     "7538": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7538",
      "title": "The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)",
      "name": "RFC 7538",
      "URI": "urn:ietf:rfc:7538",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7538",
      "abstract": "This document specifies the additional Hypertext Transfer Protocol (HTTP) status code 308 (Permanent Redirect).",
      "concepts": [{
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/308" }]}},{
     "7540": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7540",
      "title": "Hypertext Transfer Protocol Version 2",
      "name": "RFC 7540",
      "URI": "urn:ietf:rfc:7540",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7540",
      "abstract": "This specification describes an optimized expression of the semantics of the Hypertext Transfer Protocol (HTTP). HTTP/2 enables a more efficient use of network resources and a reduced perception of latency by introducing header field compression and allowing multiple concurrent exchanges on the same connection. It also introduces unsolicited push of representations from servers to clients. This specification is an alternative to, but does not obsolete, the HTTP/1.1 message syntax. HTTP's existing semantics remain unchanged.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/HTTP2-Settings" }, {
       "http://webconcepts.info/concepts/http-method/": "http://webconcepts.info/concepts/http-method/PRI" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/421" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x0" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x1" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x2" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x3" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x4" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x5" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x6" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x7" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x8" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0x9" }]}},{
     "7565": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7565",
      "title": "The 'acct' URI Scheme",
      "name": "RFC 7565",
      "URI": "urn:ietf:rfc:7565",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7565",
      "abstract": "This document defines the 'acct' Uniform Resource Identifier (URI) scheme as a way to identify a user's account at a service provider, irrespective of the particular protocols that can be used to interact with the account.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/acct" }]}},{
     "7591": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7591",
      "title": "OAuth 2.0 Dynamic Client Registration Protocol",
      "name": "RFC 7591",
      "URI": "urn:ietf:rfc:7591",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7591",
      "abstract": "This specification defines mechanisms for dynamically registering OAuth 2.0 clients with authorization servers. Registration requests send a set of desired client metadata values to the authorization server. The resulting registration responses return a client identifier to use at the authorization server and the client metadata values registered for the client. The client can then use this registration information to communicate with the authorization server using the OAuth 2.0 protocol. This specification also defines a set of common client metadata fields and values for clients to use during registration.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/client_id" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/client_id_issued_at" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/client_name" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/client_secret" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/client_secret_expires_at" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/client_uri" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/contacts" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/grant_types" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/jwks_uri" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/logo_uri" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/policy_uri" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/redirect_uris" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/redirect_uris" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/response_types" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/scope" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/software_id" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/software_version" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/token_endpoint_auth_method" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/tos_uri" }, {
       "http://webconcepts.info/concepts/oauth-token-endpoint-auth-method/": "http://webconcepts.info/concepts/oauth-token-endpoint-auth-method/client_secret_basic" }, {
       "http://webconcepts.info/concepts/oauth-token-endpoint-auth-method/": "http://webconcepts.info/concepts/oauth-token-endpoint-auth-method/client_secret_post" }, {
       "http://webconcepts.info/concepts/oauth-token-endpoint-auth-method/": "http://webconcepts.info/concepts/oauth-token-endpoint-auth-method/none" }]}},{
     "7592": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7592",
      "title": "OAuth 2.0 Dynamic Client Registration Management Protocol",
      "name": "RFC 7592",
      "URI": "urn:ietf:rfc:7592",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7592",
      "abstract": "This specification defines methods for management of OAuth 2.0 dynamic client registrations for use cases in which the properties of a registered client may need to be changed during the lifetime of the client. Not all authorization servers supporting dynamic client registration will support these management methods.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/registration_access_token" }, {
       "http://webconcepts.info/concepts/oauth-client-metadata/": "http://webconcepts.info/concepts/oauth-client-metadata/registration_client_uri" }]}},{
     "7595": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7595",
      "title": "Guidelines and Registration Procedures for URI Schemes",
      "name": "RFC 7595",
      "URI": "urn:ietf:rfc:7595",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7595",
      "abstract": "This document updates the guidelines and recommendations, as well as the IANA registration processes, for the definition of Uniform Resource Identifier (URI) schemes.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/example" }]}},{
     "7615": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7615",
      "title": "The Hypertext Transfer Protocol (HTTP) Authentication-Info and Proxy-Authentication-Info Response Header Fields",
      "name": "RFC 7615",
      "URI": "urn:ietf:rfc:7615",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7615",
      "abstract": "This specification defines the \"Authentication-Info\" and \"Proxy-Authentication-Info\" response header fields for use in HTTP authentication schemes which need to return information once the client's authentication credentials have been accepted.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Authentication-Info" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Proxy-Authentication-Info" }]}},{
     "7616": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7616",
      "title": "HTTP Digest Access Authentication",
      "name": "RFC 7616",
      "URI": "urn:ietf:rfc:7616",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7616",
      "abstract": "The Hypertext Transfer Protocol (HTTP) provides a simple challenge-response authentication mechanism that may be used by a server to challenge a client request and by a client to provide authentication information. This document defines the HTTP Digest Authentication scheme that can be used with the HTTP authentication mechanism.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/Digest" }, {
       "http://webconcepts.info/concepts/http-hash-alg/": "http://webconcepts.info/concepts/http-hash-alg/MD5" }, {
       "http://webconcepts.info/concepts/http-hash-alg/": "http://webconcepts.info/concepts/http-hash-alg/SHA-256" }, {
       "http://webconcepts.info/concepts/http-hash-alg/": "http://webconcepts.info/concepts/http-hash-alg/SHA-512-256" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Authorization" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/WWW-Authenticate" }]}},{
     "7617": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7617",
      "title": "The 'Basic' HTTP Authentication Scheme",
      "name": "RFC 7617",
      "URI": "urn:ietf:rfc:7617",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7617",
      "abstract": "This document defines the \"Basic\" Hypertext Transfer Protocol (HTTP) authentication scheme, which transmits credentials as user-id/password pairs, encoded using Base64.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/Basic" }]}},{
     "7635": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7635",
      "title": "Session Traversal Utilities for NAT (STUN) Extension",
      "name": "RFC 7635",
      "URI": "urn:ietf:rfc:7635",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7635",
      "abstract": "This document proposes the use of OAuth 2.0 to obtain and validate ephemeral tokens that can be used for Session Traversal Utilities for NAT (STUN) authentication. The usage of ephemeral tokens ensures that access to a STUN server can be controlled even if the tokens are compromised.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/stun-key" }]}},{
     "7636": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7636",
      "title": "Proof Key for Code Exchange by OAuth Public Clients",
      "name": "RFC 7636",
      "URI": "urn:ietf:rfc:7636",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7636",
      "abstract": "OAuth 2.0 public clients utilizing the Authorization Code Grant are susceptible to the authorization code interception attack.  This specification describes the attack as well as a technique to mitigate against the threat through the use of Proof Key for Code Exchange (PKCE, pronounced \"pixy\").",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/code_challenge" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/code_challenge_method" }, {
       "http://webconcepts.info/concepts/oauth-parameter/": "http://webconcepts.info/concepts/oauth-parameter/code_verifier" }, {
       "http://webconcepts.info/concepts/pkce-code-challenge-method/": "http://webconcepts.info/concepts/pkce-code-challenge-method/S256" }, {
       "http://webconcepts.info/concepts/pkce-code-challenge-method/": "http://webconcepts.info/concepts/pkce-code-challenge-method/plain" }]}},{
     "7639": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7639",
      "title": "The ALPN HTTP Header Field",
      "name": "RFC 7639",
      "URI": "urn:ietf:rfc:7639",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7639",
      "abstract": "This specification allows HTTP CONNECT requests to indicate what protocol is intended to be used within the tunnel once established, using the ALPN header field.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/ALPN" }]}},{
     "7644": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7644",
      "title": "System for Cross-domain Identity Management: Protocol",
      "name": "RFC 7644",
      "URI": "urn:ietf:rfc:7644",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7644",
      "abstract": "The System for Cross-domain Identity Management (SCIM) specification is an HTTP-based protocol that makes managing identities in multi-domain scenarios easier to support via a standardized service. Examples include, but are not limited to, enterprise-to-cloud service providers and inter-cloud scenarios.  The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models.  SCIM's intent is to reduce the cost and complexity of user management operations by providing a common user schema, an extension model, and a service protocol defined by this document.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/scim+json" }]}},{
     "7662": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7662",
      "title": "OAuth 2.0 Token Introspection",
      "name": "RFC 7662",
      "URI": "urn:ietf:rfc:7662",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7662",
      "abstract": "This specification defines a method for a protected resource to query an OAuth 2.0 authorization server to determine the active state of an OAuth 2.0 token and to determine meta-information about this token. OAuth 2.0 deployments can use this method to convey information about the authorization context of the token from the authorization server to the protected resource.",
      "concepts": [{
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/active" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/aud" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/client_id" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/exp" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/iat" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/iss" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/jti" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/nbf" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/scope" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/sub" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/token_type" }, {
       "http://webconcepts.info/concepts/oauth-token-introspection-response/": "http://webconcepts.info/concepts/oauth-token-introspection-response/username" }]}},{
     "7694": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7694",
      "title": "Hypertext Transfer Protocol (HTTP) Client-Initiated Content-Encoding",
      "name": "RFC 7694",
      "URI": "urn:ietf:rfc:7694",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7694",
      "abstract": "In HTTP, content codings allow for payload encodings such as for compression or integrity checks. In particular, the \"gzip\" content coding is widely used for payload data sent in response messages. Content codings can be used in request messages as well, however discoverability is not on par with response messages. This document extends the HTTP \"Accept-Encoding\" header field for use in responses, to indicate that content codings are supported in requests.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Encoding" }]}},{
     "7711": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7711",
      "title": "PKIX over Secure HTTP (POSH)",
      "name": "RFC 7711",
      "URI": "urn:ietf:rfc:7711",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7711",
      "abstract": "Experience has shown that it is difficult to deploy proper PKIX certificates for Transport Layer Security (TLS) in multi-tenanted environments. As a result, domains hosted in such environments often deploy applications using certificates that identify the hosting service, not the hosted domain. Such deployments force end users and peer services to accept a certificate with an improper identifier, resulting in degraded security. This document defines methods that make it easier to deploy certificates for proper server identity checking in non-HTTP application protocols. Although these methods were developed for use in the Extensible Messaging and Presence Protocol (XMPP) as a Domain Name Association (DNA) prooftype, they might also be usable in other non-HTTP application protocols.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/posh" }]}},{
     "7725": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7725",
      "title": "An HTTP Status Code to Report Legal Obstacles",
      "name": "RFC 7725",
      "URI": "urn:ietf:rfc:7725",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7725",
      "abstract": "This document specifies a Hypertext Transfer Protocol (HTTP) status code for use when resource access is denied as a consequence of legal demands.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/451" }]}},{
     "7763": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7763",
      "title": "The text/markdown Media Type",
      "name": "RFC 7763",
      "URI": "urn:ietf:rfc:7763",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7763",
      "abstract": "This document registers the text/markdown media type for use with Markdown, a family of plain-text formatting syntaxes that optionally can be converted to formal markup languages such as HTML.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/markdown" }]}},{
     "7800": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7800",
      "title": "Proof-of-Possession Key Semantics for JSON Web Tokens (JWTs)",
      "name": "RFC 7800",
      "URI": "urn:ietf:rfc:7800",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7800",
      "abstract": "This specification describes how to declare in a JSON Web Token (JWT) that the presenter of the JWT possesses a particular proof-of-possession key and how the recipient can cryptographically confirm proof of possession of the key by the presenter. Being able to prove possession of a key is also sometimes described as the presenter being a holder-of-key.",
      "concepts": [{
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/cnf" }, {
       "http://webconcepts.info/concepts/jwt-confirmation-method/": "http://webconcepts.info/concepts/jwt-confirmation-method/jku" }, {
       "http://webconcepts.info/concepts/jwt-confirmation-method/": "http://webconcepts.info/concepts/jwt-confirmation-method/jwe" }, {
       "http://webconcepts.info/concepts/jwt-confirmation-method/": "http://webconcepts.info/concepts/jwt-confirmation-method/jwk" }, {
       "http://webconcepts.info/concepts/jwt-confirmation-method/": "http://webconcepts.info/concepts/jwt-confirmation-method/kid" }]}},{
     "7804": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7804",
      "title": "Salted Challenge Response HTTP Authentication Mechanism",
      "name": "RFC 7804",
      "URI": "urn:ietf:rfc:7804",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7804",
      "abstract": "This specification describes a family of HTTP authentication mechanisms called the Salted Challenge Response Authentication Mechanism (SCRAM), which provides a more robust authentication mechanism than a plaintext password protected by Transport Layer Security (TLS) and avoids the deployment obstacles presented by earlier TLS-protected challenge response authentication mechanisms.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/SCRAM-SHA-1" }, {
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/SCRAM-SHA-256" }]}},{
     "7807": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7807",
      "title": "Problem Details for HTTP APIs",
      "name": "RFC 7807",
      "URI": "urn:ietf:rfc:7807",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7807",
      "abstract": "This document defines a \"problem detail\" as a way to carry machine-readable details of errors in a HTTP response, to avoid the need to invent new error response formats for HTTP APIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/problem+json" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/problem+xml" }]}},{
     "7808": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7808",
      "title": "Time Zone Data Distribution Service",
      "name": "RFC 7808",
      "URI": "urn:ietf:rfc:7808",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7808",
      "abstract": "This document defines a time zone data distribution service that allows reliable, secure, and fast delivery of time zone data and leap-second rules to client systems such as calendaring and scheduling applications or operating systems.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/timezone" }]}},{
     "7838": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7838",
      "title": "HTTP Alternate Services",
      "name": "RFC 7838",
      "URI": "urn:ietf:rfc:7838",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7838",
      "abstract": "This document specifies \"alternative services\" for HTTP, which allow an origin's resources to be authoritatively available at a separate network location, possibly accessed with a different protocol configuration.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Alt-Svc" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Alt-Used" }, {
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0xa" }]}},{
     "7932": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7932",
      "title": "Brotli Compressed Data Format",
      "name": "RFC 7932",
      "URI": "urn:ietf:rfc:7932",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7932",
      "abstract": "This specification defines a lossless compressed data format that compresses data using a combination of the LZ77 algorithm and Huffman coding, with efficiency comparable to the best currently available general-purpose compression methods.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/br" }]}},{
     "7946": {
      "id": "http://webconcepts.info/specs/IETF/RFC/7946",
      "title": "The GeoJSON Format",
      "name": "RFC 7946",
      "URI": "urn:ietf:rfc:7946",
      "URL": "https://datatracker.ietf.org/doc/html/rfc7946",
      "abstract": "GeoJSON is a geospatial data interchange format based on JavaScript Object Notation (JSON). It defines several types of JSON objects and the manner in which they are combined to represent data about geographic features, their properties, and their spatial extents. GeoJSON uses a geographic coordinate reference system, World Geodetic System 1984, and units of decimal degrees.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/geo+json" }]}},{
     "8030": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8030",
      "title": "Generic Event Delivery Using HTTP Push",
      "name": "RFC 8030",
      "URI": "urn:ietf:rfc:8030",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8030",
      "abstract": "This document describes a simple protocol for the delivery of real-time events to user agents. This scheme uses HTTP/2 server push.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/TTL" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Topic" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Urgency" }]}},{
     "8053": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8053",
      "title": "HTTP Authentication Extensions for Interactive Clients",
      "name": "RFC 8053",
      "URI": "urn:ietf:rfc:8053",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8053",
      "abstract": "This document specifies extensions for the HTTP authentication framework for interactive clients. Currently, fundamental features of HTTP-level authentication are insufficient for complex requirements of various Web-based applications. This forces these applications to implement their own authentication frameworks by means such as HTML forms, which becomes one of the hurdles against introducing secure authentication mechanisms handled jointly by servers and user agents. The extended framework fills gaps between Web application requirements and HTTP authentication provisions to solve the above problems, while maintaining compatibility with existing Web and non-Web uses of HTTP authentication.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Authentication-Control" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Optional-WWW-Authenticate" }]}},{
     "8057": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8057",
      "title": "Uniform Resource Name (URN) Namespaces for Broadband Forum",
      "name": "RFC 8057",
      "URI": "urn:ietf:rfc:8057",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8057",
      "abstract": "This document describes the Namespace Identifiers (NIDs) \"bbf\", \"broadband-forum-org\", and \"dslforum-org\" for Uniform Resource Names (URNs) used to identify resources published by Broadband Forum (BBF). BBF specifies and manages resources that utilize these three URN identification models. Management activities for these and other resource types are handled by BBF.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/bbf" }, {
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/broadband-forum-org" }, {
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/dslforum-org" }]}},{
     "8069": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8069",
      "title": "URN Namespace for IEEE",
      "name": "RFC 8069",
      "URI": "urn:ietf:rfc:8069",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8069",
      "abstract": "This document describes the Namespace Identifier (NID) 'ieee' for Uniform Resource Names (URNs) used to identify resources published by the Institute of Electrical and Electronics Engineers (IEEE). IEEE specifies and manages resources that utilize this URN identification model. Management activities for these and other resources types are handled by the manager of the IEEE Registration Authority.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/ieee" }]}},{
     "8081": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8081",
      "title": "The \"font\" Top-Level Media Type",
      "name": "RFC 8081",
      "URI": "urn:ietf:rfc:8081",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8081",
      "abstract": "This memo serves to register and document the \"font\" top-level media type, under which subtypes for representation formats for fonts may be registered. This document also serves as a registration application for a set of intended subtypes, which are representative of some existing subtypes already in use, and currently registered under the \"application\" tree by their separate registrations.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/collection" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/otf" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/sfnt" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/ttf" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/woff" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/woff2" }]}},{
     "8089": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8089",
      "title": "The \"file\" URI Scheme",
      "name": "RFC 8089",
      "URI": "urn:ietf:rfc:8089",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8089",
      "abstract": "This document provides a more complete specification of the \"file\" Uniform Resource Identifier (URI) scheme and replaces the very brief definition in Section 3.10 of RFC 1738. It defines a common syntax that is intended to interoperate across the broad spectrum of existing usages. At the same time, it notes some other current practices around the use of file URIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/file" }]}},{
     "8091": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8091",
      "title": "A Media Type Structured Syntax Suffix for JSON Text Sequences",
      "name": "RFC 8091",
      "URI": "urn:ietf:rfc:8091",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8091",
      "abstract": "Structured Syntax Suffixes for media types allow other media types to build on them and make it explicit that they are built on an existing media type as their foundation. This specification defines and registers \"json-seq\" as a structured syntax suffix for JSON text sequences.",
      "concepts": [{
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+json-seq" }]}},{
     "8107": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8107",
      "title": "Advertising Digital Identifier (Ad-ID) URN Namespace Definition",
      "name": "RFC 8107",
      "URI": "urn:ietf:rfc:8107",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8107",
      "abstract": "Advertising Digital Identifiers (Ad-IDs) are used to identify advertising assets across all media platforms. This document defines the formal Uniform Resource Name (URN) Namespace Identifier (NID) \"adid\" for Ad-IDs.",
      "concepts": [{
       "http://webconcepts.info/concepts/urn-namespace/": "http://webconcepts.info/concepts/urn-namespace/adid" }]}},{
     "8118": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8118",
      "title": "The application/pdf Media Type",
      "name": "RFC 8118",
      "URI": "urn:ietf:rfc:8118",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8118",
      "abstract": "The Portable Document Format (PDF) is an ISO standard (ISO 32000-1:2008) defining a final-form document representation language in use for document exchange, including on the Internet, since 1993. This document provides an overview of the PDF format and updates the media type registration of \"application/pdf\".",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/pdf" }]}},{
     "8120": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8120",
      "title": "Mutual Authentication Protocol for HTTP",
      "name": "RFC 8120",
      "URI": "urn:ietf:rfc:8120",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8120",
      "abstract": "This document specifies an authentication scheme for the Hypertext Transfer Protocol (HTTP) that is referred to as either the Mutual authentication scheme or the Mutual authentication protocol. This scheme provides true mutual authentication between an HTTP client and an HTTP server using password-based authentication. Unlike the Basic and Digest authentication schemes, the Mutual authentication scheme specified in this document assures the user that the server truly knows the user's encrypted password.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-authentication-scheme/": "http://webconcepts.info/concepts/http-authentication-scheme/Mutual" }]}},{
     "8141": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8141",
      "title": "Uniform Resource Names (URNs)",
      "name": "RFC 8141",
      "URI": "urn:ietf:rfc:8141",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8141",
      "abstract": "A Uniform Resource Name (URN) is a Uniform Resource Identifier (URI) that is assigned under the \"urn\" URI scheme and a particular URN namespace, with the intent that the URN will be a persistent, location-independent resource identifier. With regard to URN syntax, this document defines the canonical syntax for URNs (in a way that is consistent with URI syntax), specifies methods for determining URN-equivalence, and discusses URI conformance. With regard to URN namespaces, this document specifies a method for defining a URN namespace and associating it with a namespace identifier, and it describes procedures for registering namespace identifiers with the Internet Assigned Numbers Authority (IANA). This document obsoletes both RFCs 2141 and 3406.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/urn" }]}},{
     "8142": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8142",
      "title": "GeoJSON Text Sequences",
      "name": "RFC 8142",
      "URI": "urn:ietf:rfc:8142",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8142",
      "abstract": "This document describes the GeoJSON text sequence format and \"application/geo+json-seq\" media type. This format is based on JavaScript Object Notation (JSON) Text Sequences and GeoJSON, and makes arbitrarily large geographic datasets incrementally parseable without restricting the form of GeoJSON texts within a sequence.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/geo+json-seq" }]}},{
     "8144": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8144",
      "title": "Use of the Prefer Header Field in Web Distributed Authoring and Versioning (WebDAV)",
      "name": "RFC 8144",
      "URI": "urn:ietf:rfc:8144",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8144",
      "abstract": "This document defines how the Prefer header field (RFC 7240) can be used by a Web Distributed Authoring and Versioning (WebDAV) client to request that certain behaviors be employed by a server while constructing a response to a request. Furthermore, it defines the new \"depth-noroot\" preference.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-preference/": "http://webconcepts.info/concepts/http-preference/depth-noroot" }]}},{
     "8147": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8147",
      "title": "Next-Generation Pan-European eCall",
      "name": "RFC 8147",
      "URI": "urn:ietf:rfc:8147",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8147",
      "abstract": "This document describes how to use IP-based emergency services mechanisms to support the next generation of the Pan-European in-vehicle emergency call service defined under the eSafety initiative of the European Commission (generally referred to as \"eCall\"). eCall is a standardized and mandated system for a special form of emergency calls placed by vehicles, providing real-time communications and an integrated set of related data. This document also registers MIME media types and an Emergency Call Data Type for the eCall vehicle data and metadata/control data, and an INFO package to enable carrying this data in SIP INFO requests. Although this specification is designed to meet the requirements of next-generation Pan-European eCall (NG-eCall), it is specified generically such that the technology can be reused or extended to suit requirements across jurisdictions.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/EmergencyCallData.Control+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/EmergencyCallData.eCall.MSD" }, {
       "http://webconcepts.info/concepts/xml-ns/": "http://webconcepts.info/concepts/xml-ns/urn:ietf:params:xml:ns:EmergencyCallData:control" }]}},{
     "8152": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8152",
      "title": "CBOR Object Signing and Encryption (COSE)",
      "name": "RFC 8152",
      "URI": "urn:ietf:rfc:8152",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8152",
      "abstract": "Concise Binary Object Representation (CBOR) is a data format designed for small code size and small message size. There is a need for the ability to have basic security services defined for this data format. This document defines the CBOR Object Signing and Encryption (COSE) protocol. This specification describes how to create and process signatures, message authentication codes, and encryption using CBOR for serialization. This specification additionally describes how to represent cryptographic keys using CBOR.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/cose" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/cose-key" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/cose-key-set" }]}},{
     "8164": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8164",
      "title": "Opportunistic Security for HTTP/2",
      "name": "RFC 8164",
      "URI": "urn:ietf:rfc:8164",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8164",
      "abstract": "This document describes how \"http\" URIs can be accessed using Transport Layer Security (TLS) and HTTP/2 to mitigate pervasive monitoring attacks. This mechanism not a replacement for \"https\" URIs; it is vulnerable to active attacks.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/http-opportunistic" }]}},{
     "8188": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8188",
      "title": "Encrypted Content-Encoding for HTTP",
      "name": "RFC 8188",
      "URI": "urn:ietf:rfc:8188",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8188",
      "abstract": "This memo introduces a content coding for HTTP that allows message payloads to be encrypted.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/aes128gcm" }]}},{
     "8216": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8216",
      "title": "HTTP Live Streaming",
      "name": "RFC 8216",
      "URI": "urn:ietf:rfc:8216",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8216",
      "abstract": "This document describes a protocol for transferring unbounded streams of multimedia data. It specifies the data format of the files and the actions to be taken by the server (sender) and the clients (receivers) of the streams. It describes version 7 of this protocol.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/vnd.apple.mpegurl" }]}},{
     "8246": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8246",
      "title": "HTTP Immutable Responses",
      "name": "RFC 8246",
      "URI": "urn:ietf:rfc:8246",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8246",
      "abstract": "The immutable HTTP response Cache-Control extension allows servers to identify resources that will not be updated during their freshness lifetime. This ensures that a client never needs to revalidate a cached fresh resource to be certain it has not been modified.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-cache-directive/": "http://webconcepts.info/concepts/http-cache-directive/immutable" }]}},{
     "8255": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8255",
      "title": "Multiple Language Content Type",
      "name": "RFC 8255",
      "URI": "urn:ietf:rfc:8255",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8255",
      "abstract": "This document defines the 'multipart/multilingual' content type, which is an addition to the Multipurpose Internet Mail Extensions (MIME) standard. This content type makes it possible to send one message that contains multiple language versions of the same information. The translations would be identified by a language tag and selected by the email client based on a user's language settings.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Translation-Type" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/multipart/multilingual" }]}},{
     "8259": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8259",
      "title": "JavaScript Object Notation (JSON)",
      "name": "RFC 8259",
      "URI": "urn:ietf:rfc:8259",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8259",
      "abstract": "JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/json" }]}},{
     "8283": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8283",
      "title": "CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets",
      "name": "RFC 8283",
      "URI": "urn:ietf:rfc:8283",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8283",
      "abstract": "The Constrained Application Protocol (CoAP), although inspired by HTTP, was designed to use UDP instead of TCP. The message layer of CoAP over UDP includes support for reliable delivery, simple congestion control, and flow control. Some environments benefit from the availability of CoAP carried over reliable transports such as TCP or Transport Layer Security (TLS). This document outlines the changes required to use CoAP over TCP, TLS, and WebSockets transports. It also formally updates RFC 7641 for use with these transports and RFC 7959 to enable the use of larger messages over a reliable transport.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/coap+tcp" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/coap+ws" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/coaps+tcp" }, {
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/coaps+ws" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/coap" }]}},{
     "8288": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8288",
      "title": "Web Linking",
      "name": "RFC 8288",
      "URI": "urn:ietf:rfc:8288",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8288",
      "abstract": "This specification defines a way to indicate the relationships between resources on the Web (\"links\") and the type of those relationships (\"link relation types\"). It also defines the use of such links in HTTP headers with the Link header field.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Link" }]}},{
     "8297": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8297",
      "title": "An HTTP Status Code for Indicating Hints",
      "name": "RFC 8297",
      "URI": "urn:ietf:rfc:8297",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8297",
      "abstract": "This memo introduces an informational status code for HTTP that can be used for indicating hints to help a client start making preparations for processing the final response.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/103" }]}},{
     "8336": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8336",
      "title": "The ORIGIN HTTP/2 Frame",
      "name": "RFC 8336",
      "URI": "urn:ietf:rfc:8336",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8336",
      "abstract": "This document specifies the ORIGIN frame for HTTP/2, to indicate what origins are available on a given connection.",
      "concepts": [{
       "http://webconcepts.info/concepts/http2-frame-type/": "http://webconcepts.info/concepts/http2-frame-type/0xc" }]}},{
     "8392": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8392",
      "title": "CBOR Web Token (CWT)",
      "name": "RFC 8392",
      "URI": "urn:ietf:rfc:8392",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8392",
      "abstract": "CBOR Web Token (CWT) is a compact means of representing claims to be transferred between two parties. The claims in a CWT are encoded in the Concise Binary Object Representation (CBOR), and CBOR Object Signing and Encryption (COSE) is used for added application-layer security protection. A claim is a piece of information asserted about a subject and is represented as a name/value pair consisting of a claim name and a claim value. CWT is derived from JSON Web Token (JWT) but uses CBOR rather than JSON.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/cwt" }]}},{
     "8417": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8417",
      "title": "Security Event Token (SET)",
      "name": "RFC 8417",
      "URI": "urn:ietf:rfc:8417",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8417",
      "abstract": "This specification defines the Security Event Token (SET) data structure. A SET describes statements of fact from the perspective of an issuer about a subject. These statements of fact represent an event that occurred directly to or about a security subject, for example, a statement about the issuance or revocation of a token on behalf of a subject. This specification is intended to enable representing security- and identity-related events. A SET is a JSON Web Token (JWT), which can be optionally signed and/or encrypted. SETs can be distributed via protocols such as HTTP.",
      "concepts": [{
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/events" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/toe" }, {
       "http://webconcepts.info/concepts/jwt-claim/": "http://webconcepts.info/concepts/jwt-claim/txn" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/secevent+jwt" }, {
       "http://webconcepts.info/concepts/structured-syntax-suffix/": "http://webconcepts.info/concepts/structured-syntax-suffix/+jwt" }]}},{
     "8470": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8470",
      "title": "Using Early Data in HTTP",
      "name": "RFC 8470",
      "URI": "urn:ietf:rfc:8470",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8470",
      "abstract": "Using TLS early data creates an exposure to the possibility of a replay attack. This document defines mechanisms that allow clients to communicate with servers about HTTP requests that are sent in early data. Techniques are described that use these mechanisms to mitigate the risk of replay.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Early-Data" }, {
       "http://webconcepts.info/concepts/http-status-code/": "http://webconcepts.info/concepts/http-status-code/425" }]}},{
     "8473": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8473",
      "title": "Token Binding over HTTP",
      "name": "RFC 8473",
      "URI": "urn:ietf:rfc:8473",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8473",
      "abstract": "This document describes a collection of mechanisms that allow HTTP servers to cryptographically bind security tokens (such as cookies and OAuth tokens) to TLS connections. We describe both first-party and federated scenarios. In a first-party scenario, an HTTP server is able to cryptographically bind the security tokens that it issues to a client -- and that the client subsequently returns to the server -- to the TLS connection between the client and the server. Such bound security tokens are protected from misuse, since the server can generally detect if they are replayed inappropriately, e.g., over other TLS connections. Federated Token Bindings, on the other hand, allow servers to cryptographically bind security tokens to a TLS connection that the client has with a different server than the one issuing the token.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Include-Referred-Token-Binding-ID" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-Token-Binding" }]}},{
     "8574": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8574",
      "title": "cite-as: A Link Relation to Convey a Preferred URI for Referencing",
      "name": "RFC 8574",
      "URI": "urn:ietf:rfc:8574",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8574",
      "abstract": "A web resource is routinely referenced by means of the URI with which it is directly accessed. But cases exist where referencing a resource by means of a different URI is preferred. This specification defines a link relation type that can be used to convey such a preference.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/cite-as" }]}},{
     "8594": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8594",
      "title": "The Sunset HTTP Header Field",
      "name": "RFC 8594",
      "URI": "urn:ietf:rfc:8594",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8594",
      "abstract": "This specification defines the Sunset HTTP response header field, which indicates that a URI is likely to become unresponsive at a specified point in the future. It also defines a sunset link relation type that allows linking to resources providing information about an upcoming resource or service sunset.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sunset" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/sunset" }]}},{
     "8613": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8613",
      "title": "Object Security for Constrained RESTful Environments (OSCORE)",
      "name": "RFC 8613",
      "URI": "urn:ietf:rfc:8613",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8613",
      "abstract": "This document defines Object Security for Constrained RESTful Environments (OSCORE), a method for application-layer protection of the Constrained Application Protocol (CoAP), using CBOR Object Signing and Encryption (COSE). OSCORE provides end-to-end protection between endpoints communicating using CoAP or CoAP-mappable HTTP. OSCORE is designed for constrained nodes and networks supporting a range of proxy operations, including translation between different transport protocols.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/OSCORE" }]}},{
     "8631": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8631",
      "title": "Link Relation Types for Web Services",
      "name": "RFC 8631",
      "URI": "urn:ietf:rfc:8631",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8631",
      "abstract": "Many resources provided on the Web are part of sets of resources that are provided in a context that is managed by one particular service provider. Often, these sets of resources are referred to as \"Web services\" or \"Web APIs\". This specification defines link relations that represent relationships from Web services or APIs to resources that provide documentation, descriptions, metadata, or status information for these resources. Documentation is primarily intended for human consumers, whereas descriptions are primarily intended for automated consumers. Metadata provides information about a service's context. This specification also defines a link relation to identify status resources that are used to represent information about service status.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/service-desc" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/service-doc" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/service-meta" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/status" }]}},{
     "8674": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8674",
      "title": "The \"safe\" HTTP Preference",
      "name": "RFC 8674",
      "URI": "urn:ietf:rfc:8674",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8674",
      "abstract": "This specification defines a preference for HTTP requests that expresses a desire to avoid objectionable content, according to the definition of that term by the origin server. This specification does not define a precise semantic for \"safe\". Rather, the term is interpreted by the server and within the scope of each web site that chooses to act upon this information. Support for this preference by clients and servers is optional.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-preference/": "http://webconcepts.info/concepts/http-preference/safe" }]}},{
     "8905": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8905",
      "title": "The 'payto' URI scheme for payments",
      "name": "RFC 8905",
      "URI": "urn:ietf:rfc:8905",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8905",
      "abstract": "This document defines the 'payto' Uniform Resource Identifier (URI) scheme for designating targets for payments. A unified URI scheme for all payment target types allows applications to offer user interactions with URIs that represent payment targets, simplifying the introduction of new payment systems and applications.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/payto" }]}},{
     "8959": {
      "id": "http://webconcepts.info/specs/IETF/RFC/8959",
      "title": "The \"secret-token\" URI Scheme",
      "name": "RFC 8959",
      "URI": "urn:ietf:rfc:8959",
      "URL": "https://datatracker.ietf.org/doc/html/rfc8959",
      "abstract": "This document registers the \"secret-token\" URI scheme to aid in the identification of authentication tokens.",
      "concepts": [{
       "http://webconcepts.info/concepts/uri-scheme/": "http://webconcepts.info/concepts/uri-scheme/secret-token" }]}},{
     "9163": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9163",
      "title": "Expect-CT Extension for HTTP",
      "name": "RFC 9163",
      "URI": "urn:ietf:rfc:9163",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9163",
      "abstract": "This document defines a new HTTP header field named \"Expect-CT\", which allows web host operators to instruct user agents (UAs) to expect valid Signed Certificate Timestamps (SCTs) to be served on connections to these hosts. Expect-CT allows web host operators to discover misconfigurations in their Certificate Transparency (CT) deployments. Further, web host operators can use Expect-CT to ensure that if a UA that supports Expect-CT accepts a misissued certificate, that certificate will be discoverable in Certificate Transparency logs.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Expect-CT" }]}},{
     "9209": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9209",
      "title": "The Proxy-Status HTTP Response Header Field",
      "name": "RFC 9209",
      "URI": "urn:ietf:rfc:9209",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9209",
      "abstract": "This document defines the Proxy-Status HTTP response field to convey the details of an intermediary's response handling, including generated errors.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Proxy-Status" }]}},{
     "9213": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9213",
      "title": "Targeted HTTP Cache Control",
      "name": "RFC 9213",
      "URI": "urn:ietf:rfc:9213",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9213",
      "abstract": "This specification defines a convention for HTTP response header fields that allow cache directives to be targeted at specific caches or classes of caches. It also defines one such header field, the CDN-Cache-Control response header field, which is targeted at content delivery network (CDN) caches.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/CDN-Cache-Control" }]}},{
     "9239": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9239",
      "title": "Updates to ECMAScript Media Types",
      "name": "RFC 9239",
      "URI": "urn:ietf:rfc:9239",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9239",
      "abstract": "This document describes the registration of media types for the ECMAScript and JavaScript programming languages and conformance requirements for implementations of these types. This document obsoletes RFC 4329 (\"Scripting Media Types)\", replacing the previous registrations with information and requirements aligned with common usage and implementation experiences.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/ecmascript" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/javascript" }]}},{
     "9512": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9512",
      "title": "YAML Media Type",
      "name": "RFC 9512",
      "URI": "urn:ietf:rfc:9512",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9512",
      "abstract": "This document registers the application/yaml media type and the +yaml structured syntax suffix with IANA. Both identify document components that are serialized according to the YAML specification.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/yaml" }]}},{
     "9530": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9530",
      "title": "Digest Fields",
      "name": "RFC 9530",
      "URI": "urn:ietf:rfc:9530",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9530",
      "abstract": "This document defines HTTP fields that support integrity digests. The Content-Digest field can be used for the integrity of HTTP message content. The Repr-Digest field can be used for the integrity of HTTP representations. Want-Content-Digest and Want-Repr-Digest can be used to indicate a sender's interest and preferences for receiving the respective Integrity fields.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Digest" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Repr-Digest" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Want-Content-Digest" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Want-Repr-Digest" }]}},{
     "9652": {
      "id": "http://webconcepts.info/specs/IETF/RFC/9652",
      "title": "The Link-Template HTTP Header Field",
      "name": "RFC 9652",
      "URI": "urn:ietf:rfc:9652",
      "URL": "https://datatracker.ietf.org/doc/html/rfc9652",
      "abstract": "This specification defines the Link-Template HTTP header field, providing a means for describing the structure of a link between two resources so that new links can be generated.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Link-Template" }]}}]}}]},
 "ISO": {
  "id": "http://webconcepts.info/specs/ISO/",
  "name": "International Organization for Standardization",
  "short": "ISO",
  "series": [{
   "IEC": {
    "id": "http://webconcepts.info/specs/ISO/IEC/",
    "name": "International Electrotechnical Commission",
    "short": "IEC",
    "specs": [{
     "10918-5": {
      "id": "http://webconcepts.info/specs/ISO/IEC/10918-5",
      "title": "Information technology — Digital compression and coding of continuous-tone still images: JPEG File Interchange Format (JFIF) ",
      "name": "ISO/IEC 10918-5",
      "URI": "urn:iso:std:iso-iec:10918:-5",
      "URL": "http://www.iso.org/obp/ui/#iso:std:iso-iec:10918:-5",
      "abstract": "The JPEG File Interchange Format (JFIF) is a minimal file format which enables the exchange of JPEG encoded images (according to Rec. ITU-T T.81 / ISO/IEC 10918-1) having 1 or 3 colour channels and 8 bits per colour channel between a wide variety of platforms and applications. This minimal format does not include some advanced features found in various other specified file formats. The purpose of this format is to provide for a basic form of exchange of JPEG images. The optional inclusion of thumbnail images for rapid browsing is also supported.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/image/jpeg" }]}},{
     "14496-22": {
      "id": "http://webconcepts.info/specs/ISO/IEC/14496-22",
      "title": "Information technology — Coding of audio-visual objects — Part 22: Open Font Format",
      "name": "ISO/IEC 14496-22",
      "URI": "urn:iso:std:iso-iec:14496:-22",
      "URL": "http://www.iso.org/obp/ui/#iso:std:iso-iec:14496:-22",
      "abstract": "ISO/IEC 14496-22:2015 specifies the Open Font Format (OFF) specification, the TrueType and Compact Font Format (CFF) outline formats, and the TrueType hinting language. Many references to both TrueType and PostScript exist throughout this document, as Open Font Format fonts combine the two technologies.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/font-sfnt" }]}},{
     "23009-1": {
      "id": "http://webconcepts.info/specs/ISO/IEC/23009-1",
      "title": "Information technology — Dynamic adaptive streaming over HTTP (DASH) — Part 1: Media presentation description and segment formats",
      "name": "ISO/IEC 23009-1",
      "URI": "urn:iso:std:iso-iec:23009:-1",
      "URL": "http://www.iso.org/obp/ui/#iso:std:iso-iec:23009:-1",
      "abstract": "ISO/IEC 23009-1:2014 primarily specifies formats for the Media Presentation Description and Segments for dynamic adaptive streaming delivery of MPEG media over HTTP. It is applicable to streaming services over the Internet.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/dash+xml" }]}}]}}]},
 "JCP": {
  "id": "http://webconcepts.info/specs/JCP/",
  "name": "Java Community Process",
  "short": "JCP",
  "series": [{
   "JSR": {
    "id": "http://webconcepts.info/specs/JCP/JSR/",
    "name": "Java Specification Request",
    "short": "JSR",
    "specs": [{
     "200": {
      "id": "http://webconcepts.info/specs/JCP/JSR/200",
      "title": "Pack200: A Packed Class Deployment Format For Java Applications",
      "name": "JSR 200",
      "URL": "http://www.jcp.org/en/jsr/detail?id=200",
      "abstract": "This document specifies an archive format called \"Pack200\". It is optimized for applications written in the Javatm programming language. Such applications are usually delivered as collections of classes, sometimes with associated resource files. This format allows any number (from one to hundreds of thousands) of Java classes to be encoded by a compressor, transmitted compactly in a single block of bytes, and decoded by a decompressor into equivalent Java class files. Because it can also represent class resources and other \"side files\", it can serve as an alternative to the JAR archive for some deployment tasks, notably downloading Java applications.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/pack200-gzip" }]}}]}}]},
 "OASIS": {
  "id": "http://webconcepts.info/specs/OASIS/",
  "name": "Organization for the Advancement of Structured Information Standards",
  "short": "OASIS",
  "series": [{
   "standard": {
    "id": "http://webconcepts.info/specs/OASIS/standard/",
    "name": "Standard",
    "specs": [{
     "odata-v4.0-part1-protocol": {
      "id": "http://webconcepts.info/specs/OASIS/standard/odata-v4.0-part1-protocol",
      "title": "OData Version 4.0 Part 1: Protocol",
      "name": "OASIS Standard odata-v4.0-part1-protocol",
      "URI": "urn:oasis:names:specification:odata-v4.0-part1-protocol",
      "URL": "http://docs.oasis-open.org/odata/odata/v4.0/odata-v4.0-part1-protocol.html",
      "abstract": "The Open Data Protocol (OData) enables the creation of REST-based data services, which allow resources, identified using Uniform Resource Locators (URLs) and defined in a data model, to be published and edited by Web clients using simple HTTP messages. This specification defines the core semantics and the behavioral aspects of the protocol.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/OData-EntityId" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/OData-Isolation" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/OData-MaxVersion" }]}},{
     "repeatable-requests-v1.0": {
      "id": "http://webconcepts.info/specs/OASIS/standard/repeatable-requests-v1.0",
      "title": "Repeatable Requests Version 1.0",
      "name": "OASIS Standard repeatable-requests-v1.0",
      "URI": "urn:oasis:names:specification:repeatable-requests-v1.0",
      "URL": "https://docs.oasis-open.org/odata/repeatable-requests/v1.0/cs01/repeatable-requests-v1.0-cs01.html",
      "abstract": "This document describes a method to provide the ability to retry unsafe (i.e. POST, PUT, PATCH, DELETE) requests without incurring unintended side-effects. This specification can be applied to any HTTP based protocol.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Repeatability-Client-ID" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Repeatability-First-Sent" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Repeatability-Request-ID" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Repeatability-Result" }]}},{
     "saml-bindings-2.0-os": {
      "id": "http://webconcepts.info/specs/OASIS/standard/saml-bindings-2.0-os",
      "title": "Bindings for the OASIS Security Assertion Markup Language (SAML) V2.0",
      "name": "OASIS Standard saml-bindings-2.0-os",
      "URI": "urn:oasis:names:specification:saml-bindings-2.0-os",
      "URL": "http://docs.oasis-open.org/security/saml/v2.0/saml-bindings-2.0-os.pdf",
      "abstract": "This specification defines protocol bindings for the use of SAML assertions and request-response messages in communications protocols and frameworks.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/samlassertion+xml" }]}},{
     "saml-metadata-2.0-os": {
      "id": "http://webconcepts.info/specs/OASIS/standard/saml-metadata-2.0-os",
      "title": "Metadata for the OASIS Security Assertion Markup Language (SAML) V2.0",
      "name": "OASIS Standard saml-metadata-2.0-os",
      "URI": "urn:oasis:names:specification:saml-metadata-2.0-os",
      "URL": "http://docs.oasis-open.org/security/saml/v2.0/saml-metadata-2.0-os.pdf",
      "abstract": "SAML profiles require agreements between system entities regarding identifiers, binding support and endpoints, certificates and keys, and so forth. A metadata specification is useful for describing this information in a standardized way. This document defines an extensible metadata format for SAML system entities, organized by roles that reflect SAML profiles. Such roles include that of Identity Provider, Service Provider, Affiliation, Attribute Authority, Attribute Consumer, and Policy Decision Point.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/samlmetadata+xml" }]}},{
     "xliff-core-v2.1": {
      "id": "http://webconcepts.info/specs/OASIS/standard/xliff-core-v2.1",
      "title": "XLIFF Version 2.1",
      "name": "OASIS Standard xliff-core-v2.1",
      "URI": "urn:oasis:names:specification:xliff-core-v2.1",
      "URL": "http://docs.oasis-open.org/xliff/xliff-core/v2.1/xliff-core-v2.1.html",
      "abstract": "This document defines version 2.1 of the XML Localization Interchange File Format (XLIFF). The purpose of this vocabulary is to store localizable data and carry it from one step of the localization process to the other, while allowing interoperability between and among tools.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/xliff+xml" }]}}]}}]},
 "W3C": {
  "id": "http://webconcepts.info/specs/W3C/",
  "name": "World Wide Web Consortium",
  "short": "W3C",
  "series": [{
   "TR": {
    "id": "http://webconcepts.info/specs/W3C/TR/",
    "name": "Technical Report",
    "short": "TR",
    "specs": [{
     "COWL": {
      "id": "http://webconcepts.info/specs/W3C/TR/COWL",
      "title": "Confinement with Origin Web Labels",
      "name": "W3C TR http://www.w3.org/TR/COWL",
      "URI": "http://www.w3.org/TR/COWL",
      "URL": "http://www.w3.org/TR/COWL",
      "abstract": "This specification defines an API for specifying privacy and integrity policies on data, in the form of origin labels, and a mechanism for confining code according to such policies. This allows Web application authors and server operators to share data with untrusted—buggy but not malicious—code (e.g., in a mashup scenario) yet impose restrictions on how the code can share the data further.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-COWL" }]}},{
     "CSP2": {
      "id": "http://webconcepts.info/specs/W3C/TR/CSP2",
      "title": "Content Security Policy Level 2",
      "name": "W3C TR http://www.w3.org/TR/CSP2",
      "URI": "http://www.w3.org/TR/CSP2",
      "URL": "http://www.w3.org/TR/CSP2",
      "abstract": "This document defines a policy language used to declare a set of content restrictions for a web resource, and a mechanism for transmitting the policy from a server to a client where the policy is enforced.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Security-Policy" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Security-Policy-Report-Only" }]}},{
     "CSP3": {
      "id": "http://webconcepts.info/specs/W3C/TR/CSP3",
      "title": "Content Security Policy Level 3",
      "name": "W3C TR http://www.w3.org/TR/CSP3",
      "URI": "http://www.w3.org/TR/CSP3",
      "URL": "http://www.w3.org/TR/CSP3",
      "abstract": "This document defines a mechanism by which web developers can control the resources which a particular page can fetch or execute, as well as a number of security-relevant policy decisions.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Security-Policy" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Security-Policy-Report-Only" }]}},{
     "P3P": {
      "id": "http://webconcepts.info/specs/W3C/TR/P3P",
      "title": "The Platform for Privacy Preferences 1.0 (P3P1.0) Specification",
      "name": "W3C TR http://www.w3.org/TR/P3P",
      "URI": "http://www.w3.org/TR/P3P",
      "URL": "http://www.w3.org/TR/P3P",
      "abstract": "This is the specification of the Platform for Privacy Preferences (P3P). This document, along with its normative references, includes all the specification necessary for the implementation of interoperable P3P applications.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/P3P" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/P3Pv1" }]}},{
     "PNG": {
      "id": "http://webconcepts.info/specs/W3C/TR/PNG",
      "title": "Portable Network Graphics",
      "name": "W3C TR http://www.w3.org/TR/PNG",
      "URI": "http://www.w3.org/TR/PNG",
      "URL": "http://www.w3.org/TR/PNG",
      "abstract": "This document describes PNG (Portable Network Graphics), an extensible file format for the lossless, portable, well-compressed storage of raster images. PNG provides a patent-free replacement for GIF and can also replace many common uses of TIFF. Indexed-color, grayscale, and truecolor images are supported, plus an optional alpha channel. Sample depths range from 1 to 16 bits. PNG is designed to work well in online viewing applications, such as the World Wide Web, so it is fully streamable with a progressive display option. PNG is robust, providing both full file integrity checking and simple detection of common transmission errors. Also, PNG can store gamma and chromaticity data for improved color matching on heterogeneous platforms.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/image/png" }]}},{
     "SOAP": {
      "id": "http://webconcepts.info/specs/W3C/TR/SOAP",
      "title": "Simple Object Access Protocol (SOAP) 1.1",
      "name": "W3C TR http://www.w3.org/TR/SOAP",
      "URI": "http://www.w3.org/TR/SOAP",
      "URL": "http://www.w3.org/TR/SOAP",
      "abstract": "SOAP is a lightweight protocol for exchange of information in a decentralized, distributed environment. It is an XML based protocol that consists of three parts: an envelope that defines a framework for describing what is in a message and how to process it, a set of encoding rules for expressing instances of application-defined datatypes, and a convention for representing remote procedure calls and responses. SOAP can potentially be used in combination with a variety of other protocols; however, the only bindings defined in this document describe how to use SOAP in combination with HTTP and HTTP Extension Framework.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/SOAPAction" }]}},{
     "WD-http-pep": {
      "id": "http://webconcepts.info/specs/W3C/TR/WD-http-pep",
      "title": "PEP - An Extension Mechanism for HTTP",
      "name": "W3C TR http://www.w3.org/TR/WD-http-pep",
      "URI": "http://www.w3.org/TR/WD-http-pep",
      "URL": "http://www.w3.org/TR/WD-http-pep",
      "abstract": " HTTP is used increasingly in applications that need more facilities than the standard version of the protocol provides, ranging from distributed authoring, collaboration, and printing, to various remote procedure call mechanisms. The Protocol Extension Protocol (PEP) is an extension mechanism designed to address the tension between private agreement and public specification and to accommodate extension of applications such as HTTP clients, servers, and proxies. The PEP mechanism is designed to associate each extension with a URI, and use a few new RFC 822 derived header fields to carry the extension identifier and related information between the parties involved in an extended transaction. This document defines PEP and describes the interactions between PEP and HTTP/1.1. PEP is intended to be compatible with HTTP/1.0 inasmuch as HTTP/1.1 is compatible with HTTP/1.0. It is proposed that the PEP extension mechanism be included in future versions of HTTP. The PEP extension mechanism may be applicable to other information exchange not mentioned in this document. It is recommended that readers get acquainted with section 1.4 for a suggested reading of this specification and a list of sections specific for HTTP based applications.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/C-PEP" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/C-PEP-Info" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/PEP" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/PEP-Info" }]}},{
     "WD-proxy": {
      "id": "http://webconcepts.info/specs/W3C/TR/WD-proxy",
      "title": "Notification for Proxy Caches",
      "name": "W3C TR http://www.w3.org/TR/WD-proxy",
      "URI": "http://www.w3.org/TR/WD-proxy",
      "URL": "http://www.w3.org/TR/WD-proxy",
      "abstract": "A mechanism to enable better functioning of proxies is proposed. This mechanism allows proxies to inform a remote server about transactions performed using the cache and for servers to inform proxies when data becomes stale.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Proxy-Features" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Proxy-Instruction" }]}},{
     "WOFF2": {
      "id": "http://webconcepts.info/specs/W3C/TR/WOFF2",
      "title": "WOFF File Format 2.0",
      "name": "W3C TR http://www.w3.org/TR/WOFF2",
      "URI": "http://www.w3.org/TR/WOFF2",
      "URL": "http://www.w3.org/TR/WOFF2",
      "abstract": "Based on experience with WOFF 1.0, which is widely deployed, this specification was developed to provide improved compression and thus lower use of network bandwidth, while still allowing fast decompression even on mobile devices. This is achieved by combining a content-aware preprocessing step and improved entropy coding, compared to the Flate compression used in WOFF 1.0.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/font/woff2" }]}},{
     "activitystreams-core": {
      "id": "http://webconcepts.info/specs/W3C/TR/activitystreams-core",
      "title": "Activity Streams 2.0",
      "name": "W3C TR http://www.w3.org/TR/activitystreams-core",
      "URI": "http://www.w3.org/TR/activitystreams-core",
      "URL": "http://www.w3.org/TR/activitystreams-core",
      "abstract": "This specification details a model for representing potential and completed activities using the JSON format.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/activity+json" }]}},{
     "appmanifest": {
      "id": "http://webconcepts.info/specs/W3C/TR/appmanifest",
      "title": "Manifest for Web Application",
      "name": "W3C TR http://www.w3.org/TR/appmanifest",
      "URI": "http://www.w3.org/TR/appmanifest",
      "URL": "http://www.w3.org/TR/appmanifest",
      "abstract": "This specification defines a JSON-based manifest that provides developers with a centralized place to put metadata associated with a web application. This includes, but is not limited to, the web application's name, links to icons, as well as the preferred URL to open when a user launches the web application. The manifest also allows developers to declare a default orientation for their web application, as well as providing the ability to set the display mode for the application (e.g., in fullscreen). Additionally, the manifest allows a developer to \"scope\" a web application to a URL. This restricts the URLs to which the application can be navigated and provides a means to \"deep link\" into a web application from other applications. Using this metadata, user agents can provide developers with means to create user experiences that are more comparable to that of a native application. In addition, this specification defines the manifest link type, which provides a declarative means for a document to be associated with a manifest.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/manifest" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/manifest+json" }]}},{
     "clear-site-data": {
      "id": "http://webconcepts.info/specs/W3C/TR/clear-site-data",
      "title": "Clear Site Data",
      "name": "W3C TR http://www.w3.org/TR/clear-site-data",
      "URI": "http://www.w3.org/TR/clear-site-data",
      "URL": "http://www.w3.org/TR/clear-site-data",
      "abstract": "This document defines an imperative mechanism which allows web developers to instruct a user agent to clear a user's locally stored data related to a host and its subdomains.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Clear-Site-Data" }]}},{
     "cors": {
      "id": "http://webconcepts.info/specs/W3C/TR/cors",
      "title": "Cross-Origin Resource Sharing (CORS)",
      "name": "W3C TR http://www.w3.org/TR/cors",
      "URI": "http://www.w3.org/TR/cors",
      "URL": "http://www.w3.org/TR/cors",
      "abstract": "This document defines a mechanism to enable client-side cross-origin requests. Specifications that enable an API to make cross-origin requests to resources can use the algorithms defined by this specification. If such an API is used on http://example.org resources, a resource on http://hello-world.example can opt in using the mechanism described by this specification (e.g., specifying Access-Control-Allow-Origin: http://example.org as response header), which would allow that resource to be fetched cross-origin from http://example.org.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Allow-Credentials" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Allow-Headers" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Allow-Methods" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Allow-Origin" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Expose-Headers" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Max-Age" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Request-Headers" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Access-Control-Request-Method" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Origin" }]}},{
     "csp-pinning": {
      "id": "http://webconcepts.info/specs/W3C/TR/csp-pinning",
      "title": "Content Security Policy Pinning",
      "name": "W3C TR http://www.w3.org/TR/csp-pinning",
      "URI": "http://www.w3.org/TR/csp-pinning",
      "URL": "http://www.w3.org/TR/csp-pinning",
      "abstract": "This document defines a new HTTP header that allows authors to instruct user agents to remember (\"pin\") and enforce a Content Security Policy for a set of hosts for a period of time.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Security-Policy-Pin" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Content-Security-Policy-Report-Only-Pin" }]}},{
     "device-memory-1": {
      "id": "http://webconcepts.info/specs/W3C/TR/device-memory-1",
      "title": "Device Memory",
      "name": "W3C TR http://www.w3.org/TR/device-memory-1",
      "URI": "http://www.w3.org/TR/device-memory-1",
      "URL": "http://www.w3.org/TR/device-memory-1",
      "abstract": "This document defines a HTTP Client Hint header to surface device capability for memory i.e. device RAM, in order to enable web apps to customize content depending on device memory constraints.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Device-Memory" }]}},{
     "edge-arch": {
      "id": "http://webconcepts.info/specs/W3C/TR/edge-arch",
      "title": "Edge Architecture Specification",
      "name": "W3C TR http://www.w3.org/TR/edge-arch",
      "URI": "http://www.w3.org/TR/edge-arch",
      "URL": "http://www.w3.org/TR/edge-arch",
      "abstract": "This document defines the Edge Architecture, which extend the Web infrastructure through the use of HTTP surrogates - intermediaries that act on behalf of an origin server.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Surrogate-Capability" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Surrogate-Control" }]}},{
     "epr": {
      "id": "http://webconcepts.info/specs/W3C/TR/epr",
      "title": "Entry Point Regulation (EPR)",
      "name": "W3C TR http://www.w3.org/TR/epr",
      "URI": "http://www.w3.org/TR/epr",
      "URL": "http://www.w3.org/TR/epr",
      "abstract": "Entry Point Regulation aims to mitigate the risk of reflected cross-site scripting (XSS), cross-site script inclusion (XSSI), and cross-site request forgery (CSRF) attacks by demarcating the areas of an application which are intended to be externally referencable. A specified policy is applied on external requests for all non-demarcated resources.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/EPR" }]}},{
     "eventsource": {
      "id": "http://webconcepts.info/specs/W3C/TR/eventsource",
      "title": "Server-Sent Events",
      "name": "W3C TR http://www.w3.org/TR/eventsource",
      "URI": "http://www.w3.org/TR/eventsource",
      "URL": "http://www.w3.org/TR/eventsource",
      "abstract": " specification defines an API for opening an HTTP connection for receiving push notifications from a server in the form of DOM events. The API is designed such that it can be extended to work with other push notification schemes such as Push SMS.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Last-Event-ID" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/event-stream" }]}},{
     "exi": {
      "id": "http://webconcepts.info/specs/W3C/TR/exi",
      "title": "Efficient XML Interchange (EXI) Format 1.0",
      "name": "W3C TR http://www.w3.org/TR/exi",
      "URI": "http://www.w3.org/TR/exi",
      "URL": "http://www.w3.org/TR/exi",
      "abstract": "This document is the specification of the Efficient XML Interchange (EXI) format. EXI is a very compact representation for the Extensible Markup Language (XML) Information Set that is intended to simultaneously optimize performance and the utilization of computational resources. The EXI format uses a hybrid approach drawn from the information and formal language theories, plus practical techniques verified by measurements, for entropy encoding XML information. Using a relatively simple algorithm, which is amenable to fast and compact implementation, and a small set of datatype representations, it reliably produces efficient encodings of XML event streams. The grammar production system and format definition of EXI are presented.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-content-coding/": "http://webconcepts.info/concepts/http-content-coding/exi" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/exi" }]}},{
     "feature-policy-1": {
      "id": "http://webconcepts.info/specs/W3C/TR/feature-policy-1",
      "title": "Feature Policy",
      "name": "W3C TR http://www.w3.org/TR/feature-policy-1",
      "URI": "http://www.w3.org/TR/feature-policy-1",
      "URL": "http://www.w3.org/TR/feature-policy-1",
      "abstract": "This specification defines a mechanism that allows developers to selectively enable and disable use of various browser features and APIs.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Feature-Policy" }]}},{
     "fetch-metadata": {
      "id": "http://webconcepts.info/specs/W3C/TR/fetch-metadata",
      "title": "Fetch Metadata Request Headers",
      "name": "W3C TR http://www.w3.org/TR/fetch-metadata",
      "URI": "http://www.w3.org/TR/fetch-metadata",
      "URL": "http://www.w3.org/TR/fetch-metadata",
      "abstract": "This document defines a set of Fetch metadata request headers that aim to provide servers with enough information to make a priori decisions about whether or not to service a request based on the way it was made, and the context in which it will be used.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-Fetch-Dest" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-Fetch-Mode" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-Fetch-Site" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Sec-Fetch-User" }]}},{
     "html": {
      "id": "http://webconcepts.info/specs/W3C/TR/html",
      "title": "Hypertext Markup Language (HTML)",
      "name": "W3C TR http://www.w3.org/TR/html",
      "URI": "http://www.w3.org/TR/html",
      "URL": "http://www.w3.org/TR/html",
      "abstract": "This specification defines the 5th major version, second minor revision of the core language of the World Wide Web: the Hypertext Markup Language (HTML). In this version, new features continue to be introduced to help Web application authors, new elements continue to be introduced based on research into prevailing authoring practices, and special attention continues to be given to defining clear conformance criteria for user agents in an effort to improve interoperability.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/alternate" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/author" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/bookmark" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/external" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/help" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/icon" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/license" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/next" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/nofollow" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/noopener" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/noreferrer" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/prev" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/search" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/stylesheet" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/tag" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/xhtml+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/multipart/x-mixed-replace" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/html" }]}},{
     "html4": {
      "id": "http://webconcepts.info/specs/W3C/TR/html4",
      "title": "Hypertext Markup Language (HTML) 4.01 Specification",
      "name": "W3C TR http://www.w3.org/TR/html4",
      "URI": "http://www.w3.org/TR/html4",
      "URL": "http://www.w3.org/TR/html4",
      "abstract": "This specification defines the HyperText Markup Language (HTML), the publishing language of the World Wide Web. This specification defines HTML 4.01, which is a subversion of HTML 4. In addition to the text, multimedia, and hyperlink features of the previous versions of HTML (HTML 3.2 and HTML 2.0), HTML 4 supports more multimedia options, scripting languages, style sheets, better printing facilities, and documents that are more accessible to users with disabilities. HTML 4 also takes great strides towards the internationalization of documents, with the goal of making the Web truly World Wide.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/appendix" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/chapter" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/contents" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/copyright" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/glossary" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/index" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/section" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/start" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/subsection" }]}},{
     "indieauth": {
      "id": "http://webconcepts.info/specs/W3C/TR/indieauth",
      "title": "IndieAuth",
      "name": "W3C TR http://www.w3.org/TR/indieauth",
      "URI": "http://www.w3.org/TR/indieauth",
      "URL": "http://www.w3.org/TR/indieauth",
      "abstract": "IndieAuth is an identity layer on top of OAuth 2.0, primarily used to obtain an OAuth 2.0 Bearer Token for use by Micropub clients. End-Users and Clients are all represented by URLs. IndieAuth enables Clients to verify the identity of an End-User, as well as to obtain an access token that can be used to access resources under the control of the End-User.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/authorization_endpoint" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/redirect_uri" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/token_endpoint" }]}},{
     "json-ld": {
      "id": "http://webconcepts.info/specs/W3C/TR/json-ld",
      "title": "JSON-LD 1.0",
      "name": "W3C TR http://www.w3.org/TR/json-ld",
      "URI": "http://www.w3.org/TR/json-ld",
      "URL": "http://www.w3.org/TR/json-ld",
      "abstract": "JSON is a useful data serialization and messaging format. This specification defines JSON-LD, a JSON-based format to serialize Linked Data. The syntax is designed to easily integrate into deployed systems that already use JSON, and provides a smooth upgrade path from JSON to JSON-LD. It is primarily intended to be a way to use Linked Data in Web-based programming environments, to build interoperable Web services, and to store Linked Data in JSON-based storage engines.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/ld+json" }]}},{
     "json-rdf": {
      "id": "http://webconcepts.info/specs/W3C/TR/json-rdf",
      "title": "RDF 1.1 JSON Alternate Serialization (RDF/JSON)",
      "name": "W3C TR http://www.w3.org/TR/json-rdf",
      "URI": "http://www.w3.org/TR/json-rdf",
      "URL": "http://www.w3.org/TR/json-rdf",
      "abstract": "The Resource Description Framework (RDF) is a framework for representing information in the Web. This document defines a textual syntax for RDF called RDF/JSON that allows an RDF graph to be completely written in a form compatible with the JavaScript Object Notation (JSON) and alternative to the one recommended in JSON-LD. The syntax defined in this document should not be used unless there is a specific reason to do so. Use of JSON-LD is recommended.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/rdf+json" }]}},{
     "ldp": {
      "id": "http://webconcepts.info/specs/W3C/TR/ldp",
      "title": "Linked Data Platform 1.0 (LDP)",
      "name": "W3C TR http://www.w3.org/TR/ldp",
      "URI": "http://www.w3.org/TR/ldp",
      "URL": "http://www.w3.org/TR/ldp",
      "abstract": "Linked Data Platform (LDP) defines a set of rules for HTTP operations on web resources, some based on RDF, to provide an architecture for read-write Linked Data on the web.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Accept-Post" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/describedby" }]}},{
     "micropub": {
      "id": "http://webconcepts.info/specs/W3C/TR/micropub",
      "title": "Micropub",
      "name": "W3C TR http://www.w3.org/TR/micropub",
      "URI": "http://www.w3.org/TR/micropub",
      "URL": "http://www.w3.org/TR/micropub",
      "abstract": "Micropub is an open API standard that is used to create posts on one's own domain using third-party clients. Web apps and native apps (e.g. iPhone, Android) can use Micropub to post short notes, photos, events or other posts to your own site.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/micropub" }]}},{
     "network-error-logging-1": {
      "id": "http://webconcepts.info/specs/W3C/TR/network-error-logging-1",
      "title": "Network Error Logging",
      "name": "W3C TR http://www.w3.org/TR/network-error-logging-1",
      "URI": "http://www.w3.org/TR/network-error-logging-1",
      "URL": "http://www.w3.org/TR/network-error-logging-1",
      "abstract": "This document defines a mechanism that enables developers to declare a network error reporting policy for a web application. A user agent can use this policy to report encountered network errors that prevented it from successfully fetching requested resources.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/NEL" }]}},{
     "owl-time": {
      "id": "http://webconcepts.info/specs/W3C/TR/owl-time",
      "title": "Time Ontology in OWL",
      "name": "W3C TR http://www.w3.org/TR/owl-time",
      "URI": "http://www.w3.org/TR/owl-time",
      "URL": "http://www.w3.org/TR/owl-time",
      "abstract": "OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalAfter" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalBefore" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalContains" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalDisjoint" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalDuring" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalEquals" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalFinishedBy" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalFinishes" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalIn" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalMeets" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalMetBy" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalOverlappedBy" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalOverlaps" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalStartedBy" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/intervalStarts" }]}},{
     "payment-method-manifest": {
      "id": "http://webconcepts.info/specs/W3C/TR/payment-method-manifest",
      "title": "Payment Method Manifest",
      "name": "W3C TR http://www.w3.org/TR/payment-method-manifest",
      "URI": "http://www.w3.org/TR/payment-method-manifest",
      "URL": "http://www.w3.org/TR/payment-method-manifest",
      "abstract": "This specification defines the machine-readable manifest file, known as a payment method manifest, describing how a payment method participates in the Web Payments ecosystem, and how such files are to be used.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/payment-method-manifest" }]}},{
     "powder-dr": {
      "id": "http://webconcepts.info/specs/W3C/TR/powder-dr",
      "title": "Protocol for Web Description Resources (POWDER): Description Resources",
      "name": "W3C TR http://www.w3.org/TR/powder-dr",
      "URI": "http://www.w3.org/TR/powder-dr",
      "URL": "http://www.w3.org/TR/powder-dr",
      "abstract": "The purpose of the Protocol for Web Description Resources (POWDER) is to provide a means for individuals or organizations to describe a group of resources through the publication of machine-readable metadata, as motivated by the POWDER Use Cases. This document details the creation and lifecycle of Description Resources (DRs), which encapsulate such metadata. These are typically represented in a highly constrained XML dialect that is relatively human-readable. The meaning of such DRs are underpinned by formal semantics, accessible by performing a GRDDL Transform.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/describedby" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/powder+xml" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/powder-s+xml" }]}},{
     "preload": {
      "id": "http://webconcepts.info/specs/W3C/TR/preload",
      "title": "Preload",
      "name": "W3C TR http://www.w3.org/TR/preload",
      "URI": "http://www.w3.org/TR/preload",
      "URL": "http://www.w3.org/TR/preload",
      "abstract": "This specification defines the preload keyword that may be used with link elements. This keyword provides a declarative fetch primitive that initiates an early fetch and separates fetching from resource execution.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/preload" }]}},{
     "rdf11-concepts": {
      "id": "http://webconcepts.info/specs/W3C/TR/rdf11-concepts",
      "title": "RDF 1.1 Concepts and Abstract Syntax",
      "name": "W3C TR http://www.w3.org/TR/rdf11-concepts",
      "URI": "http://www.w3.org/TR/rdf11-concepts",
      "URL": "http://www.w3.org/TR/rdf11-concepts",
      "abstract": "The Resource Description Framework (RDF) is a framework for representing information in the Web. This document defines an abstract syntax (a data model) which serves to link all RDF-based languages and specifications. The abstract syntax has two key data structures: RDF graphs are sets of subject-predicate-object triples, where the elements may be IRIs, blank nodes, or datatyped literals. They are used to express descriptions of resources. RDF datasets are used to organize collections of RDF graphs, and comprise a default graph and zero or more named graphs. RDF 1.1 Concepts and Abstract Syntax also introduces key concepts and terminology, and discusses datatyping and the handling of fragment identifiers in IRIs within RDF graphs.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/genid" }]}},{
     "reporting-1": {
      "id": "http://webconcepts.info/specs/W3C/TR/reporting-1",
      "title": "Reporting API 1",
      "name": "W3C TR http://www.w3.org/TR/reporting-1",
      "URI": "http://www.w3.org/TR/reporting-1",
      "URL": "http://www.w3.org/TR/reporting-1",
      "abstract": "This document defines a generic reporting framework which allows web developers to associate a set of named reporting endpoints with an origin. Various platform features (like Content Security Policy, Network Error Reporting, and others) will use these endpoints to deliver feature-specific reports in a consistent manner.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Report-To" }]}},{
     "resource-hints": {
      "id": "http://webconcepts.info/specs/W3C/TR/resource-hints",
      "title": "Resource Hints",
      "name": "W3C TR http://www.w3.org/TR/resource-hints",
      "URI": "http://www.w3.org/TR/resource-hints",
      "URL": "http://www.w3.org/TR/resource-hints",
      "abstract": "This specification defines the dns-prefetch, preconnect, prefetch, and prerender relationships of the HTML Link Element (<link>). These primitives enable the developer, and the server generating or delivering the resources, to assist the user agent in the decision process of which origins it should connect to, and which resources it should fetch and preprocess to improve page performance.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/dns-prefetch" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/preconnect" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/prefetch" }, {
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/prerender" }]}},{
     "server-timing": {
      "id": "http://webconcepts.info/specs/W3C/TR/server-timing",
      "title": "Server Timing",
      "name": "W3C TR http://www.w3.org/TR/server-timing",
      "URI": "http://www.w3.org/TR/server-timing",
      "URL": "http://www.w3.org/TR/server-timing",
      "abstract": "This specification enables a server to communicate performance metrics about the request-response cycle to the user agent. It also standardizes a JavaScript interface to enable applications to collect, process, and act on these metrics to optimize application delivery.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Server-Timing" }]}},{
     "service-workers-1": {
      "id": "http://webconcepts.info/specs/W3C/TR/service-workers-1",
      "title": "Service Workers 1",
      "name": "W3C TR http://www.w3.org/TR/service-workers-1",
      "URI": "http://www.w3.org/TR/service-workers-1",
      "URL": "http://www.w3.org/TR/service-workers-1",
      "abstract": "This specification describes a method that enables applications to take advantage of persistent background processing, including hooks to enable bootstrapping of web applications while offline. The core of this system is an event-driven Web Worker, which responds to events dispatched from documents and other sources. A system for managing installation, versions, and upgrades is provided. The service worker is a generic entry point for event-driven background processing in the Web Platform that is extensible by other specifications.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Service-Worker" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Service-Worker-Allowed" }]}},{
     "tabular-data-model": {
      "id": "http://webconcepts.info/specs/W3C/TR/tabular-data-model",
      "title": "Model for Tabular Data and Metadata on the Web",
      "name": "W3C TR http://www.w3.org/TR/tabular-data-model",
      "URI": "http://www.w3.org/TR/tabular-data-model",
      "URL": "http://www.w3.org/TR/tabular-data-model",
      "abstract": "Tabular data is routinely transferred on the web in a variety of formats, including variants on CSV, tab-delimited files, fixed field formats, spreadsheets, HTML tables, and SQL dumps. This document outlines a data model, or infoset, for tabular data and metadata about that tabular data that can be used as a basis for validation, display, or creating other formats. It also contains some non-normative guidance for publishing tabular data as CSV and how that maps into the tabular data model. An annotated model of tabular data can be supplemented by separate metadata about the table. This specification defines how implementations should locate that metadata, given a file containing tabular data. The standard syntax for that metadata is defined in tabular metadata. Note, however, that applications may have other means to create annotated tables, e.g., through some application specific APIs; this model does not depend on the specificities described in tabular-metadata.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/csvm" }]}},{
     "timesheet": {
      "id": "http://webconcepts.info/specs/W3C/TR/timesheet",
      "title": "SMIL Timesheets 1.0",
      "name": "W3C TR http://www.w3.org/TR/timesheet",
      "URI": "http://www.w3.org/TR/timesheet",
      "URL": "http://www.w3.org/TR/timesheet",
      "abstract": "This document defines an XML timing language that makes SMIL 3.0 element and attribute timing control available to a wide range of other XML languages. This language allows SMIL timing to be integrated into a wide variety of a-temporal languages, even when several such languages are combined in a compound document. Because of its similarity with external style and positioning descriptions in the Cascading Style Sheet (CSS) language, this functionality has been termed SMIL Timesheets.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/timesheet" }]}},{
     "trace-context": {
      "id": "http://webconcepts.info/specs/W3C/TR/trace-context",
      "title": "Trace Context",
      "name": "W3C TR http://www.w3.org/TR/trace-context",
      "URI": "http://www.w3.org/TR/trace-context",
      "URL": "http://www.w3.org/TR/trace-context",
      "abstract": "This specification defines standard HTTP headers and a value format to propagate context information that enables distributed tracing scenarios. The specification standardizes how context information is sent and modified between services. Context information uniquely identifies individual requests in a distributed system and also defines a means to add and propagate provider-specific context information.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/traceparent" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/tracestate" }]}},{
     "tracking-dnt": {
      "id": "http://webconcepts.info/specs/W3C/TR/tracking-dnt",
      "title": "Tracking Preference Expression (DNT)",
      "name": "W3C TR http://www.w3.org/TR/tracking-dnt",
      "URI": "http://www.w3.org/TR/tracking-dnt",
      "URL": "http://www.w3.org/TR/tracking-dnt",
      "abstract": "This specification defines the technical mechanisms for expressing a tracking preference via the DNT request header field in HTTP, via an HTML DOM property readable by embedded scripts, and via properties accessible to various user agent plug-in or extension APIs. It also defines mechanisms for sites to signal whether and how they honor this preference, both in the form of a machine-readable tracking status resource at a well-known location and via a \"Tk\" response header field, and a mechanism for allowing the user to approve exceptions to DNT as desired.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/DNT" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Tk" }, {
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/tracking-status+json" }, {
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/dnt" }]}},{
     "trig": {
      "id": "http://webconcepts.info/specs/W3C/TR/trig",
      "title": "TriG",
      "name": "W3C TR http://www.w3.org/TR/trig",
      "URI": "http://www.w3.org/TR/trig",
      "URL": "http://www.w3.org/TR/trig",
      "abstract": "The Resource Description Framework (RDF) is a general-purpose language for representing information in the Web. This document defines a textual syntax for RDF called TriG that allows an RDF dataset to be completely written in a compact and natural text form, with abbreviations for common usage patterns and datatypes. TriG is an extension of the Turtle [turtle] format.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/application/trig" }]}},{
     "upgrade-insecure-requests": {
      "id": "http://webconcepts.info/specs/W3C/TR/upgrade-insecure-requests",
      "title": "Upgrade Insecure Requests",
      "name": "W3C TR http://www.w3.org/TR/upgrade-insecure-requests",
      "URI": "http://www.w3.org/TR/upgrade-insecure-requests",
      "URL": "http://www.w3.org/TR/upgrade-insecure-requests",
      "abstract": "This document defines a mechanism which allows authors to instruct a user agent to upgrade a priori insecure resource requests to secure transport before fetching them.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/Upgrade-Insecure-Requests" }]}},{
     "void": {
      "id": "http://webconcepts.info/specs/W3C/TR/void",
      "title": "Describing Linked Datasets with the VoID Vocabulary",
      "name": "W3C TR http://www.w3.org/TR/void",
      "URI": "http://www.w3.org/TR/void",
      "URL": "http://www.w3.org/TR/void",
      "abstract": "VoID is an RDF Schema vocabulary for expressing metadata about RDF datasets. It is intended as a bridge between the publishers and users of RDF data, with applications ranging from data discovery to cataloging and archiving of datasets. This document is a detailed guide to the VoID vocabulary. It describes how VoID can be used to express general metadata based on Dublin Core, access metadata, structural metadata, and links between datasets. It also provides deployment advice and discusses the discovery of VoID descriptions.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/void" }]}},{
     "webappsec-change-password-url": {
      "id": "http://webconcepts.info/specs/W3C/TR/webappsec-change-password-url",
      "title": "A Well-Known URL for Changing Passwords",
      "name": "W3C TR http://www.w3.org/TR/webappsec-change-password-url",
      "URI": "http://www.w3.org/TR/webappsec-change-password-url",
      "URL": "http://www.w3.org/TR/webappsec-change-password-url",
      "abstract": "This specification defines a well-known URL that sites can use to make their change password forms discoverable by tools. This simple affordance provides a way for software to help the user find the way to change their password.",
      "concepts": [{
       "http://webconcepts.info/concepts/well-known-uri/": "http://webconcepts.info/concepts/well-known-uri/change-password" }]}},{
     "webmention": {
      "id": "http://webconcepts.info/specs/W3C/TR/webmention",
      "title": "Webmention",
      "name": "W3C TR http://www.w3.org/TR/webmention",
      "URI": "http://www.w3.org/TR/webmention",
      "URL": "http://www.w3.org/TR/webmention",
      "abstract": "Webmention is a simple way to notify any URL when you link to it on your site. From the receiver's perspective, it's a way to request notifications when other sites link to it.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/webmention" }]}},{
     "websub": {
      "id": "http://webconcepts.info/specs/W3C/TR/websub",
      "title": "WebSub",
      "name": "W3C TR http://www.w3.org/TR/websub",
      "URI": "http://www.w3.org/TR/websub",
      "URL": "http://www.w3.org/TR/websub",
      "abstract": "An open, simple, web-scale and decentralized pubsub protocol. Anybody can play. As opposed to more developed (and more complex) pubsub specs like Jabber Publish-Subscribe this spec's base profile (the barrier-to-entry to speak it) is dead simple. The fancy bits required for high-volume publishers and subscribers are optional. The base profile is HTTP-based, as opposed to XMPP (see more on this below). To dramatically simplify this spec in several places where we had to choose between supporting A or B, we took it upon ourselves to say \"only A\", rather than making it an implementation decision. We offer this spec in hopes that it fills a need or at least advances the state of the discussion in the pubsub space. Polling is extremely wasteful and high latency. We think a decentralized pubsub layer is a fundamental, missing layer in the Internet architecture today and its existence, more than just enabling the obvious lower latency feed readers, would enable many cool applications, most of which we can't even imagine. But we're looking forward to decentralized social networking.",
      "concepts": [{
       "http://webconcepts.info/concepts/link-relation/": "http://webconcepts.info/concepts/link-relation/hub" }]}},{
     "webvtt": {
      "id": "http://webconcepts.info/specs/W3C/TR/webvtt",
      "title": "Web Video Text Tracks (WebVTT)",
      "name": "W3C TR http://www.w3.org/TR/webvtt",
      "URI": "http://www.w3.org/TR/webvtt",
      "URL": "http://www.w3.org/TR/webvtt",
      "abstract": "This specification defines WebVTT, the Web Video Text Tracks format. Its main use is for marking up external text track resources in connection with the HTML <track> element. WebVTT files provide captions or subtitles for video content, and also text video descriptions, chapters for content navigation, and more generally any form of metadata that is time-aligned with audio or video content.",
      "concepts": [{
       "http://webconcepts.info/concepts/media-type/": "http://webconcepts.info/concepts/media-type/text/vtt" }]}}]}}]},
 "Webhook": {
  "id": "http://webconcepts.info/specs/Webhook/",
  "name": "The Webhook Standard",
  "short": "Webhook",
  "series": [{
   "standard": {
    "id": "http://webconcepts.info/specs/Webhook/standard/",
    "name": "Standard",
    "specs": [{
     "webhooks": {
      "id": "http://webconcepts.info/specs/Webhook/standard/webhooks",
      "title": "Standard Webhooks",
      "name": "Webhook Standard webhooks",
      "URL": "https://github.com/standard-webhooks/webhooks",
      "abstract": "Webhooks are becoming increasingly popular and are used by many of the world's top companies for sending events to users of their APIs. However, the ecosystem is fragmented, with each webhook provider using different implementations and varying quality. Even high quality implementations vary, making them inherently incompatible. This fragmentation is a pain for the providers and consumers, stifling innovation.",
      "concepts": [{
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/webhook-id" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/webhook-signature" }, {
       "http://webconcepts.info/concepts/http-header/": "http://webconcepts.info/concepts/http-header/webhook-timestamp" }]}}]}}]}
}